Subject: Re: [tcpm] I-D Action: draft-ietf-tcpm-converters-01.txt

From: <[email-masked]>
Date: Thu, 10 May 2018 15:51:00 +0000

Hi,

I remember in the London discussion there were some comments about things it would be good to add to the draft - mainly about more examples. I agree with this, it would be useful I think to cover:

-	The example is for one client. I assume multiple clients each require their own Ipv6 address on the converter (ie which is the source address for that client's converter-server(s) connections)?
-	How would the client access Ipv4 content?
-	I assume the client has to be configured somehow with the converter's address
-	What happens if the converter fails? I suppose the client has to somehow notice, and (at config time) it gets told the address for a back-up converter or a DNS name. 
-	What happens if a link fails? I assume if one of the client-converter links fails, then MPTCP shifts all the traffic to the other path. If the converter-server connection fails, how does the client discover this? I assume packets build up at the converter and are dropped, and at some point the converter informs the client. 

Thanks,
Best wishes,
phil

-----Original Message-----
From: tcpm [mailto:[email-masked]] On Behalf Of [email-masked]
Sent: 05 March 2018 18:17
To: [email-masked]
Cc: [email-masked]
Subject: [tcpm] I-D Action: draft-ietf-tcpm-converters-01.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
                          Bart Peirens
                          SungHoon Seo
                          Anandatirtha Nandugudi
	Filename        : draft-ietf-tcpm-converters-01.txt
	Pages           : 37
	Date            : 2018-03-05

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 Converter Protocol.

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-01
https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-converters-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tcpm-converters-01

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