--- 1/draft-ietf-tcpm-converters-02.txt 2018-10-18 08:13:15.376058467 -0700 +++ 2/draft-ietf-tcpm-converters-03.txt 2018-10-18 08:13:15.460060466 -0700 @@ -1,23 +1,23 @@ TCPM Working Group O. Bonaventure, Ed. Internet-Draft Tessares Intended status: Experimental M. Boucadair, Ed. -Expires: January 2, 2019 Orange +Expires: April 21, 2019 Orange S. Gundavelli Cisco S. Seo Korea Telecom - July 01, 2018 + October 18, 2018 0-RTT TCP Convert Protocol - draft-ietf-tcpm-converters-02 + draft-ietf-tcpm-converters-03 Abstract This document specifies an application proxy, called Transport Converter, to assist the deployment of TCP extensions such as Multipath TCP. This proxy is designed to avoid inducing extra delay when involved in a network-assisted connection (that is, 0-RTT). This specification assumes an explicit model, where the proxy is explicitly configured on hosts. @@ -31,37 +31,37 @@ the Converter Protocol. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- - Drafts is at https://datatracker.ietf.org/drafts/current/. + Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on January 2, 2019. + This Internet-Draft will expire on April 21, 2019. Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents - (https://trustee.ietf.org/license-info) in effect on the date of + (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 @@ -1414,41 +1414,43 @@ o 00 : initial version, designed to support Multipath TCP and TFO only o 00 to -01 : added section Section 5 describing the support of different standard tracks TCP options by Transport Converters, clarification of the IANA section, moved the SOCKS comparison to the appendix and various minor modifications o 01 to -02 : Minor modifications + o 02 to -03 : Minor modifications + 11. References 11.1. Normative References [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, DOI 10.17487/RFC0793, September 1981, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, - DOI 10.17487/RFC2119, March 1997, - . + DOI 10.17487/RFC2119, March 1997, . [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, DOI 10.17487/RFC4291, February 2006, . [RFC4727] Fenner, B., "Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers", RFC 4727, - DOI 10.17487/RFC4727, November 2006, - . + DOI 10.17487/RFC4727, November 2006, . [RFC4987] Eddy, W., "TCP SYN Flooding Attacks and Common Mitigations", RFC 4987, DOI 10.17487/RFC4987, August 2007, . [RFC5482] Eggert, L. and F. Gont, "TCP User Timeout Option", RFC 5482, DOI 10.17487/RFC5482, March 2009, . [RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP @@ -1504,40 +1506,40 @@ Contreras, L., and B. Peirens, "Extensions for Network- Assisted MPTCP Deployment Models", draft-boucadair-mptcp- plain-mode-10 (work in progress), March 2017. [I-D.boucadair-radext-tcpm-converter] Boucadair, M. and C. Jacquenet, "RADIUS Extensions for 0-RTT TCP Converters", draft-boucadair-radext-tcpm- converter-00 (work in progress), April 2018. [I-D.boucadair-tcpm-dhc-converter] - Boucadair, M., Jacquenet, C., and T. Reddy, "DHCP Options - for 0-RTT TCP Converters", draft-boucadair-tcpm-dhc- + Boucadair, M., Jacquenet, C., and R. K, "DHCP Options for + 0-RTT TCP Converters", draft-boucadair-tcpm-dhc- converter-00 (work in progress), April 2018. [I-D.ietf-mptcp-rfc6824bis] Ford, A., Raiciu, C., Handley, M., Bonaventure, O., and C. Paasch, "TCP Extensions for Multipath Operation with - Multiple Addresses", draft-ietf-mptcp-rfc6824bis-11 (work - in progress), May 2018. + Multiple Addresses", draft-ietf-mptcp-rfc6824bis-12 (work + in progress), October 2018. [I-D.ietf-tcpinc-tcpcrypt] Bittau, A., Giffin, D., Handley, M., Mazieres, D., Slack, Q., and E. Smith, "Cryptographic protection of TCP Streams - (tcpcrypt)", draft-ietf-tcpinc-tcpcrypt-12 (work in - progress), June 2018. + (tcpcrypt)", draft-ietf-tcpinc-tcpcrypt-13 (work in + progress), September 2018. [I-D.olteanu-intarea-socks-6] Olteanu, V. and D. Niculescu, "SOCKS Protocol Version 6", - draft-olteanu-intarea-socks-6-02 (work in progress), March - 2018. + draft-olteanu-intarea-socks-6-04 (work in progress), + August 2018. [I-D.peirens-mptcp-transparent] Peirens, B., Detal, G., Barre, S., and O. Bonaventure, "Link bonding with transparent Multipath TCP", draft- peirens-mptcp-transparent-00 (work in progress), July 2016. [IETFJ16] Bonaventure, O. and S. Seo, "Multipath TCP Deployment", IETF Journal, Fall 2016 , n.d.. @@ -1553,72 +1555,72 @@ [RFC1812] Baker, F., Ed., "Requirements for IP Version 4 Routers", RFC 1812, DOI 10.17487/RFC1812, June 1995, . [RFC1919] Chatel, M., "Classical versus Transparent IP Proxies", RFC 1919, DOI 10.17487/RFC1919, March 1996, . [RFC1928] Leech, M., Ganis, M., Lee, Y., Kuris, R., Koblas, D., and L. Jones, "SOCKS Protocol Version 5", RFC 1928, - DOI 10.17487/RFC1928, March 1996, - . + DOI 10.17487/RFC1928, March 1996, . [RFC2018] Mathis, M., Mahdavi, J., Floyd, S., and A. Romanow, "TCP Selective Acknowledgment Options", RFC 2018, - DOI 10.17487/RFC2018, October 1996, - . + DOI 10.17487/RFC2018, October 1996, . [RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing", BCP 38, RFC 2827, DOI 10.17487/RFC2827, May 2000, . [RFC3135] Border, J., Kojo, M., Griner, J., Montenegro, G., and Z. Shelby, "Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations", RFC 3135, - DOI 10.17487/RFC3135, June 2001, - . + DOI 10.17487/RFC3135, June 2001, . [RFC6181] Bagnulo, M., "Threat Analysis for TCP Extensions for Multipath Operation with Multiple Addresses", RFC 6181, - DOI 10.17487/RFC6181, March 2011, - . + DOI 10.17487/RFC6181, March 2011, . [RFC6555] Wing, D. and A. Yourtchenko, "Happy Eyeballs: Success with Dual-Stack Hosts", RFC 6555, DOI 10.17487/RFC6555, April 2012, . [RFC6887] Wing, D., Ed., Cheshire, S., Boucadair, M., Penno, R., and P. Selkirk, "Port Control Protocol (PCP)", RFC 6887, - DOI 10.17487/RFC6887, April 2013, - . + DOI 10.17487/RFC6887, April 2013, . [RFC6928] Chu, J., Dukkipati, N., Cheng, Y., and M. Mathis, "Increasing TCP's Initial Window", RFC 6928, - DOI 10.17487/RFC6928, April 2013, - . + DOI 10.17487/RFC6928, April 2013, . [RFC6978] Touch, J., "A TCP Authentication Option Extension for NAT Traversal", RFC 6978, DOI 10.17487/RFC6978, July 2013, . [RFC7323] Borman, D., Braden, B., Jacobson, V., and R. Scheffenegger, Ed., "TCP Extensions for High Performance", RFC 7323, DOI 10.17487/RFC7323, September 2014, . [RFC7414] Duke, M., Braden, R., Eddy, W., Blanton, E., and A. Zimmermann, "A Roadmap for Transmission Control Protocol (TCP) Specification Documents", RFC 7414, - DOI 10.17487/RFC7414, February 2015, - . + DOI 10.17487/RFC7414, February 2015, . Appendix A. Differences with SOCKSv5 The description above is a simplified description of the Converter protocol. At a first glance, the proposed solution could seem similar to the SOCKS v5 protocol [RFC1928]. This protocol is used to proxy TCP connections. The Client creates a connection to a SOCKS proxy, exchanges authentication information and indicates the destination address and port of the final server. At this point, the SOCKS proxy creates a connection towards the final server and relays