Re: [multipathtcp] I-D Action: draft-boucadair-mptcp-dhc-00.txt

<mohamed.boucadair@orange.com> Fri, 03 July 2015 07:15 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BACB51B2E32 for <multipathtcp@ietfa.amsl.com>; Fri, 3 Jul 2015 00:15:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 bYOHmWCmWMdq for <multipathtcp@ietfa.amsl.com>; Fri, 3 Jul 2015 00:15:56 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 359CE1B2E23 for <multipathtcp@ietf.org>; Fri, 3 Jul 2015 00:15:56 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 6E57F32490E; Fri, 3 Jul 2015 09:15:54 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.60]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 495C023805C; Fri, 3 Jul 2015 09:15:54 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([fe80::c1d7:e278:e357:11ad%19]) with mapi id 14.03.0235.001; Fri, 3 Jul 2015 09:15:53 +0200
From: mohamed.boucadair@orange.com
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, multipathtcp <multipathtcp@ietf.org>
Thread-Topic: I-D Action: draft-boucadair-mptcp-dhc-00.txt
Thread-Index: AQHQtM12FmWwAN3Ib0KCpE+wGlL5GZ3JP1WwgAAID7CAAArHsA==
Date: Fri, 03 Jul 2015 07:15:52 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933005353DAF@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <20150702134554.17997.15791.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933005353D02@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <913383AAA69FF945B8F946018B75898A478839DF@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A478839DF@xmb-rcd-x10.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.7.2.125417
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/GDtFY2Hv1Q_d1XzT57JY0mwKBoo>
Subject: Re: [multipathtcp] I-D Action: draft-boucadair-mptcp-dhc-00.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jul 2015 07:15:58 -0000

Hi Tiru,

Thank you for the comments. 

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com]
> Envoyé : vendredi 3 juillet 2015 08:27
> À : BOUCADAIR Mohamed IMT/OLN; multipathtcp
> Objet : RE: I-D Action: draft-boucadair-mptcp-dhc-00.txt
> 
> Hi Med,
> 
> My comments
> 1) How will this work if endpoint is MPTCP-aware but CPE is not capable of
> acting as MPTCP proxy ?

[Med] The draft assumes the following:

"This deployment scenario relies on MPTCP Proxy on both
   the CPE and the network sides (Figure 1). "

which means that the option is requested only when the CPE embeds an MPTCP proxy. 

As for an MPTCP-enabled host serviced by a CPE that does not embed an MPTCP proxy, the behavior is left unspecified because we considered it is out of scope.

> 2)You may want to discuss how the proposed mechanism can be used with
> https://tools.ietf.org/html/draft-ietf-mif-mpvd-dhcp-support-01

[Med] This is a good point...but the draft adopts a simple scheme where available access networks belong to the same administrative entity. We may clarify this point in the next revision.

> 
> Cheers,
> -Tiru
> 
> > -----Original Message-----
> > From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of
> > mohamed.boucadair@orange.com
> > Sent: Friday, July 03, 2015 11:24 AM
> > To: multipathtcp
> > Subject: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-dhc-00.txt
> >
> > Dear all,
> >
> > Comments and suggestions are more than welcome.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de
> > > internet-drafts@ietf.org Envoyé : jeudi 2 juillet 2015 15:46 À :
> > > i-d-announce@ietf.org Objet : I-D Action:
> > > draft-boucadair-mptcp-dhc-00.txt
> > >
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts
> > > directories.
> > >
> > >
> > >         Title           : DHCP Options for Network-Assisted Multipath
> TCP
> > > (MPTCP)
> > >         Authors         : Mohamed Boucadair
> > >                           Christian Jacquenet
> > > 	Filename        : draft-boucadair-mptcp-dhc-00.txt
> > > 	Pages           : 10
> > > 	Date            : 2015-07-02
> > >
> > > Abstract:
> > >    One of the promising deployment scenarios for Multipath TCP (MPTCP)
> > >    is to enable a Customer Premises Equipment (CPE) that is connected
> to
> > >    multiple networks (e.g., DSL, LTE, WLAN) to optimize the usage of
> its
> > >    network attachments.  Because of the lack of MPTCP support at the
> > >    server side, some service providers now consider a "network-
> assisted
> > >    mode" that relies upon the activation of a dedicated function
> called:
> > >    MPTCP Concentrator.  This document focuses on the explicit
> deployment
> > >    scheme where the identity of the MPTCP Concentrator(s) is
> explicitly
> > >    configured on connected hosts.
> > >
> > >    This document specifies DHCP (IPv4 and IPv6) options to configure
> > >    hosts with Multipath TCP (MPTCP) parameters.
> > >
> > >
> > >
> > > The IETF datatracker status page for this draft is:
> > > https://datatracker.ietf.org/doc/draft-boucadair-mptcp-dhc/
> > >
> > > There's also a htmlized version available at:
> > > https://tools.ietf.org/html/draft-boucadair-mptcp-dhc-00
> > >
> > >
> > > 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/
> > >
> > > _______________________________________________
> > > I-D-Announce mailing list
> > > I-D-Announce@ietf.org
> > > https://www.ietf.org/mailman/listinfo/i-d-announce
> > > Internet-Draft directories: http://www.ietf.org/shadow.html or
> > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> > _______________________________________________
> > multipathtcp mailing list
> > multipathtcp@ietf.org
> > https://www.ietf.org/mailman/listinfo/multipathtcp