Subject: [tcpm] Latest changes to draft-ietf-tcpm-converters

From: "Scharf, Michael" <[email-masked]>
Date: Thu, 13 Feb 2020 18:12:52 +0000

Hi all,

The AD review has resulted in a number of changes. Nonetheless, the suggestion is to directly head to IETF last call in order to finish this document.

If somebody insists in a second WGLC in TCPM to review these changes, please speak up *now* (i.e., within the next two days). By default I will assume that a second WGLC in TCPM is not needed for this EXP document, as the latest changes can also be discussed as part of an IETF last call.

Thanks

Michael
(as document shepherd)

-----Original Message-----
From: tcpm <[email-masked]> On Behalf Of [email-masked]
Sent: Thursday, February 13, 2020 6:44 PM
To: [email-masked]
Subject: Re: [tcpm] I-D Action: draft-ietf-tcpm-converters-16.txt

Hi all, 

This is a minor rev to prepare the document for the IETF LC. We removed the text about creating a mailing list for design expert review as per a suggestion from Mirja.

Cheers,
Med

> -----Message d'origine-----
> De : tcpm [mailto:[email-masked]] De la part de internet-
> [email-masked]
> Envoyé : jeudi 13 février 2020 18:38
> À : [email-masked]
> Cc : [email-masked]
> Objet : [tcpm] I-D Action: draft-ietf-tcpm-converters-16.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the TCP Maintenance and Minor Extensions
> WG of the IETF.
> 
>         Title           : 0-RTT TCP Convert Protocol
>         Authors         : Olivier Bonaventure
>                           Mohamed Boucadair
>                           Sri Gundavelli
>                           SungHoon Seo
>                           Benjamin Hesmans
> 	Filename        : draft-ietf-tcpm-converters-16.txt
> 	Pages           : 53
> 	Date            : 2020-02-13
> 
> Abstract:
>    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 IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tcpm-converters/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-tcpm-converters-16
> https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-converters-16
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-tcpm-converters-16
> 
> 
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> tcpm mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/tcpm

_______________________________________________
tcpm mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/tcpm