0-RTT TCP Convert Protocol
draft-ietf-tcpm-converters-14

Document Type Active Internet-Draft (tcpm WG)
Last updated 2019-11-18 (latest revision 2019-11-03)
Replaces draft-bonaventure-mptcp-converters
Stream IETF
Intended RFC status Experimental
Formats plain text xml pdf htmlized bibtex
Stream WG state Submitted to IESG for Publication (wg milestone: Dec 2018 - Submit document on T... )
Document shepherd Michael Scharf
Shepherd write-up Show (last changed 2019-11-18)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Mirja K├╝hlewind
Send notices to Michael Scharf <michael.scharf@hs-esslingen.de>
TCPM Working Group                                   O. Bonaventure, Ed.
Internet-Draft                                                  Tessares
Intended status: Experimental                          M. Boucadair, Ed.
Expires: May 7, 2020                                              Orange
                                                           S. Gundavelli
                                                                   Cisco
                                                                  S. Seo
                                                           Korea Telecom
                                                              B. Hesmans
                                                                Tessares
                                                       November 04, 2019

                       0-RTT TCP Convert Protocol
                     draft-ietf-tcpm-converters-14

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.

   -- Editorial Note (To be removed by RFC Editor)

   Please update these statements with the RFC number to be assigned to
   this document: [This-RFC]

   Please update TBA statements with the port number to be assigned to
   the 0-RTT TCP Convert 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/.

   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."

Bonaventure, et al.        Expires May 7, 2020                  [Page 1]
Internet-Draft              Convert Protocol               November 2019

   This Internet-Draft will expire on May 7, 2020.

Copyright Notice

   Copyright (c) 2019 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
   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
     1.1.  The Problem . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Network-Assisted Connections: The Rationale . . . . . . .   4
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   6
   3.  Architecture & Behaviors  . . . . . . . . . . . . . . . . . .   7
     3.1.  Functional Elements . . . . . . . . . . . . . . . . . . .   7
     3.2.  Theory of Operation . . . . . . . . . . . . . . . . . . .   9
     3.3.  Data Processing at the Transport Converter  . . . . . . .  12
       3.3.1.  Base Behavior . . . . . . . . . . . . . . . . . . . .  12
       3.3.2.  Multipath TCP Specifics . . . . . . . . . . . . . . .  14
   4.  Sample Examples . . . . . . . . . . . . . . . . . . . . . . .  15
     4.1.  Outgoing Converter-Assisted Multipath TCP Connections . .  15
     4.2.  Incoming Converter-Assisted Multipath TCP Connection  . .  16
   5.  The Convert Protocol (Convert)  . . . . . . . . . . . . . . .  17
     5.1.  The Convert Fixed Header  . . . . . . . . . . . . . . . .  18
     5.2.  Convert TLVs  . . . . . . . . . . . . . . . . . . . . . .  18
       5.2.1.  Generic Convert TLV Format  . . . . . . . . . . . . .  18
       5.2.2.  Summary of Supported Convert TLVs . . . . . . . . . .  19
       5.2.3.  The Info TLV  . . . . . . . . . . . . . . . . . . . .  20
       5.2.4.  Supported TCP Extensions TLV  . . . . . . . . . . . .  20
       5.2.5.  Connect TLV . . . . . . . . . . . . . . . . . . . . .  21
       5.2.6.  Extended TCP Header TLV . . . . . . . . . . . . . . .  23
       5.2.7.  The Cookie TLV  . . . . . . . . . . . . . . . . . . .  24
       5.2.8.  Error TLV . . . . . . . . . . . . . . . . . . . . . .  24
   6.  Compatibility of Specific TCP Options with the Conversion
       Service . . . . . . . . . . . . . . . . . . . . . . . . . . .  28
Show full document text