Last Call: <draft-ietf-tcpm-converters-16.txt> (0-RTT TCP Convert Protocol) to Experimental RFC

The IESG <> Fri, 14 February 2020 14:49 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 01D01120041; Fri, 14 Feb 2020 06:49:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-ietf-tcpm-converters-16.txt> (0-RTT TCP Convert Protocol) to Experimental RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.117.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <>
CC:, Michael Scharf <>,,,,
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <>
Date: Fri, 14 Feb 2020 06:49:25 -0800
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 14 Feb 2020 14:49:25 -0000

The IESG has received a request from the TCP Maintenance and Minor Extensions
WG (tcpm) to consider the following document: - '0-RTT TCP Convert Protocol'
  <draft-ietf-tcpm-converters-16.txt> as Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the mailing lists by 2020-02-28. Exceptionally, comments may
be sent to instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.


   This document specifies an application proxy, called Transport
   Converter, to assist the deployment of TCP extensions such as
   Multipath TCP.  A Transport Converter may provide conversion service
   for one or more TCP extensions.  The conversion service is provided
   by means of the TCP Convert Protocol (Convert).

   This protocol provides 0-RTT (Zero Round-Trip Time) conversion
   service since no extra delay is induced by the protocol compared to
   connections that are not proxied.  Also, the Convert Protocol does
   not require any encapsulation (no tunnels, whatsoever).

   This specification assumes an explicit model, where the Transport
   Converter is explicitly configured on hosts.

The file can be obtained via

IESG discussion can be tracked via

The following IPR Declarations may be related to this I-D: