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

<mohamed.boucadair@orange.com> Mon, 22 October 2018 12:24 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1CF4130DFB; Mon, 22 Oct 2018 05:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3moWYf1VZnWE; Mon, 22 Oct 2018 05:24:27 -0700 (PDT)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8DBB127133; Mon, 22 Oct 2018 05:24:23 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 42dwgV0G5zz7vJY; Mon, 22 Oct 2018 14:24:22 +0200 (CEST)
Received: from localhost.localdomain (unknown [127.0.0.1]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 42dwgT6nRhz5vN6; Mon, 22 Oct 2018 14:24:21 +0200 (CEST)
Received: from opfedar07.bagnolet.francetelecom.fr by opfedar07.bagnolet.francetelecom.fr with queue id 736168-33; Mon, 22 Oct 2018 12:24:21 GMT
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.43]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 42dwgT69zqz5vN2; Mon, 22 Oct 2018 14:24:21 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM5F.corporate.adroot.infra.ftgroup ([fe80::e172:f13e:8be6:71cc%18]) with mapi id 14.03.0415.000; Mon, 22 Oct 2018 14:24:21 +0200
From: <mohamed.boucadair@orange.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "tcpm@ietf.org" <tcpm@ietf.org>
CC: "draft-ietf-tcpm-converters@ietf.org" <draft-ietf-tcpm-converters@ietf.org>
Thread-Topic: [tcpm] I-D Action: draft-ietf-tcpm-converters-01.txt
Thread-Index: AQHTtK4iDI+Mo6jxv0utHg3D/M2BoKQpg4TwgGLB2BCAoFPqwA==
Date: Mon, 22 Oct 2018 12:24:20 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302E018535@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <152027380186.14624.8843516061240272538@ietfa.amsl.com> <718b17025c25456490724ad442040422@rew09926dag03b.domain1.systemhost.net> <787AE7BB302AE849A7480A190F8B93302DF598FD@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302DF598FD@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/qlw8PqJEB8R3x0yrDDVfzKtchbM>
Subject: Re: [tcpm] I-D Action: draft-ietf-tcpm-converters-01.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 12:24:30 -0000

Hi Phil, all,

FWIW, an updated version among what it was mentioned in my reply is available online: 

https://datatracker.ietf.org/doc/draft-ietf-tcpm-converters/ 

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

Cheers,
Med

> -----Message d'origine-----
> De : tcpm [mailto:tcpm-bounces@ietf.org] De la part de
> mohamed.boucadair@orange.com
> Envoyé : jeudi 12 juillet 2018 14:23
> À : philip.eardley@bt.com; tcpm@ietf.org
> Objet : Re: [tcpm] I-D Action: draft-ietf-tcpm-converters-01.txt
> 
> Hi Phil,
> 
> Apologies of the delay to answer.
> 
> Thank you for sharing these comments.
> 
> Please see inline.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : tcpm [mailto:tcpm-bounces@ietf.org] De la part de
> philip.eardley@bt.com
> > Envoyé : jeudi 10 mai 2018 17:51
> > À : tcpm@ietf.org
> > Objet : Re: [tcpm] I-D Action: draft-ietf-tcpm-converters-01.txt
> >
> > 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)?
> 
> [Med] This is deployment-specific. The converter may behave in address
> sharing or address preservation modes. A text change is proposed here:
> https://github.com/obonaventure/draft-tcp-
> converters/pull/41/commits/de004090c1861f0f8b076285b4119d48f7ab47e8
> 
> "The Converter may behave in address preservation or address sharing modes as
> discussed in Section 5.4 of {{draft-nam-mptcp-deployment-considerations}}.
> Which behavior to use by a Converter is deployment-specific. If address
> sharing mode is enabled, the Converter MUST adhere to REQ-2 of RFC6888 which
> implies a default "IP address pooling" behavior of "Paired" (as defined in
> Section 4.1 of [RFC4787]) must be supported. This behavior is meant to avoid
> breaking applications that depend on the external address remaining constant.
> Also, maintaining the same external IP address for a client is meant to
> preserve the validity of the TFO cookie."
> 
> > -	How would the client access Ipv4 content?
> 
> [Med] We would like to avoid overloading the document with deployment-
> specific examples. Plenty of those are described in draft-nam-mptcp-
> deployment-considerations. We may add a pointer if needed.
> 
> > -	I assume the client has to be configured somehow with the converter's
> > address
> 
> [Med] Yes, we do have the following text in the draft:
> 
>    This document assumes that a client is configured with one or a list
>    of Converters (e.g., [I-D.boucadair-tcpm-dhc-converter]).
>    Configuration means are outside the scope of this document.
> 
> > -	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.
> 
> [Med]  I-D.boucadair-tcpm-dhc-converter specifies a procedure to provision
> one or multiple converters; each identified by a list of IP addresses. The
> procedure to follow for selecting the address to use will need to be
> specified. Should we include it in draft-ietf-tcpm-converters or in I-
> D.boucadair-tcpm-dhc-converter? I do prefer to leave that procedure out of
> draft-ietf-tcpm-converters because the selection may not only be based on the
> availability of an address, but based on other criteria.
> 
> > -	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.
> 
> [Med] This is normal MPTCP behavior. Do we really need to say something
> there?
> 
>  If the
> > converter-server connection fails, how does the client discover this?
> 
> [Med] This is done by means of the "Network Failure (65)" error code:
> 
>    o  Network Failure (65): This error indicates that the Converter is
>       experiencing a network failure to relay the request.
> 
>       The Converter MUST send this error code when it experiences
>       forwarding issues to relay a connection.
> 
>  I
> > assume packets build up at the converter and are dropped, and at some point
> > the converter informs the client.
> >
> > Thanks,
> > Best wishes,
> > phil
> >