0-RTT TCP converters
draft-bonaventure-mptcp-converters-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-07-17
Replaced by draft-ietf-tcpm-converters
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MPTCP Working Group                                       O. Bonaventure
Internet-Draft                                                  Tessares
Intended status: Experimental                               M. Boucadair
Expires: January 18, 2018                                         Orange
                                                              B. Peirens
                                                                Proxiums
                                                           July 17, 2017

                          0-RTT TCP converters
                 draft-bonaventure-mptcp-converters-01

Abstract

   This document proposes the utilisation of Transport Converters to aid
   the deployment of TCP extensions such as Multipath TCP.

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 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 18, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (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.

Bonaventure, et al.     Expires January 18, 2018                [Page 1]
Internet-Draft            0-RTT TCP converters                 July 2017

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Architecture . . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.1.  Differences with SOCKSv5 . . . . . . . . . . . . . . . . .  9
   3.  The Converter Protocol . . . . . . . . . . . . . . . . . . . . 12
     3.1.  The Fixed Header . . . . . . . . . . . . . . . . . . . . . 12
     3.2.  The TLV Messages . . . . . . . . . . . . . . . . . . . . . 12
       3.2.1.  The Connect TLV  . . . . . . . . . . . . . . . . . . . 13
       3.2.2.  Extended TCP Header TLV  . . . . . . . . . . . . . . . 14
       3.2.3.  Error TLV  . . . . . . . . . . . . . . . . . . . . . . 15
       3.2.4.  The Bootstrap TLV  . . . . . . . . . . . . . . . . . . 16
       3.2.5.  Supported TCP Options TLV  . . . . . . . . . . . . . . 16
   4.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     4.1.  Bootstrap  . . . . . . . . . . . . . . . . . . . . . . . . 18
     4.2.  Multipath TCP  . . . . . . . . . . . . . . . . . . . . . . 19
     4.3.  TCP Fast Open (TFO)  . . . . . . . . . . . . . . . . . . . 22
   5.  Interactions with middleboxes  . . . . . . . . . . . . . . . . 26
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 27
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 28
   8.  Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 29
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 31
     10.2. Informative References . . . . . . . . . . . . . . . . . . 31
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34

Bonaventure, et al.     Expires January 18, 2018                [Page 2]
Internet-Draft            0-RTT TCP converters                 July 2017

1.  Introduction

   Transport protocols like TCP evolve regularly [RFC7414].  Given the
   end-to-end nature of those protocols, a new feature can only be used
   once it has been deployed on both clients and servers.  Experience
   with TCP extensions reveals that the deployment of a new TCP
   extension requires many years [Fukuda2011].

   There are some situations where the transport stack used on clients
   (resp. servers) can be upgraded at a faster pace than the transport
   stack running on servers (resp. clients).  In those situations,
   clients would typically want to benefit from the features of an
   improved transport protocol even if the servers have not yet been
   upgraded and conversely.  In the past, Performance Enhancing Proxies
Show full document text