Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)

<mohamed.boucadair@orange.com> Tue, 10 November 2015 06:57 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D79E41B33E2 for <dhcwg@ietfa.amsl.com>; Mon, 9 Nov 2015 22:57:31 -0800 (PST)
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 mTNEmY5DQ-ub for <dhcwg@ietfa.amsl.com>; Mon, 9 Nov 2015 22:57:30 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F14BA1B33E0 for <dhcwg@ietf.org>; Mon, 9 Nov 2015 22:57:27 -0800 (PST)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id 029FA3B4ABE; Tue, 10 Nov 2015 07:57:24 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.24]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id A16D9180053; Tue, 10 Nov 2015 07:57:20 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7D.corporate.adroot.infra.ftgroup ([fe80::9044:c5ee:4dd2:4f16%19]) with mapi id 14.03.0248.002; Tue, 10 Nov 2015 07:57:19 +0100
From: <mohamed.boucadair@orange.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Dan Seibel <Dan.Seibel@TELUS.COM>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AdEbBmKTbwftk3lYQ+2W8C9ebSXh4QAXHvOQAAfsRkA=
Date: Tue, 10 Nov 2015 06:57:19 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9AC89@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <D2660C4C.7A833%dan.seibel@telus.com> <bf0e92a92d2649f8a6974297dc447139@XCH-ALN-003.cisco.com>
In-Reply-To: <bf0e92a92d2649f8a6974297dc447139@XCH-ALN-003.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.11.10.31517
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/r2ekkoQZjzAqSo2JWMjGtkDwZGI>
Subject: Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2015 06:57:32 -0000

Hi Bernie,

Thank you for checking the document. Much appreciated!

Cheers,
Med

> -----Message d'origine-----
> De : Bernie Volz (volz) [mailto:volz@cisco.com]
> Envoyé : mardi 10 novembre 2015 03:58
> À : Dan Seibel; BOUCADAIR Mohamed IMT/OLN; dhcwg@ietf.org
> Objet : RE: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
> (MPTCP)
> 
> Dan:
> 
> Yes, the client should request this option. That is the normal behavior of
> clients.
> 
> And, yes, servers should only return the option if requested by the
> client.
> 
> Please see RFC 7227 and also my email regarding the ORO handling (Ticket
> #81 for the RFC3315 bis work).
> 
> And, Med ... a quick check of the options seems they are formatted
> correctly (as per the option guidelines and common practice).
> 
> - Bernie
> 
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Dan Seibel
> Sent: Monday, November 09, 2015 10:51 AM
> To: mohamed.boucadair@orange.com; dhcwg@ietf.org
> Subject: Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
> (MPTCP)
> 
> I think your document gives a good overall impression of how this will
> work (having no experience with MPTCP implementations I found this fairly
> easy to follow).
> 
> A few questions:
> 
> - in sections 4.2 you mention a client requests this option, but does it
> have to?  I.e could a server send this option without the client
> requesting it, and the client would still accept it? (should there be a
> MUST or SHOULD statement in there?)
> 
> - similarly, in section 5 I don¹t see any mention of if the server needs
> to see a request for this option to hand it out.
> 
> 
> 
> 
> 
> On 2015-11-05, 8:19 AM, "dhcwg on behalf of mohamed.boucadair@orange.com";
> <dhcwg-bounces@ietf.org on behalf of mohamed.boucadair@orange.com>; wrote:
> 
> >Dear all,
> >
> >Comments are more than welcome.
> >
> >Cheers,
> >Med
> >
> >> -----Message d'origine-----
> >> De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> >> Envoyé : jeudi 5 novembre 2015 16:19 À : BOUCADAIR Mohamed IMT/OLN;
> >> Tirumaleswar Reddy; JACQUENET Christian IMT/OLN Objet : New Version
> >> Notification for draft-boucadair-mptcp-dhc-02.txt
> >>
> >>
> >> A new version of I-D, draft-boucadair-mptcp-dhc-02.txt has been
> >> successfully submitted by Mohamed Boucadair and posted to the IETF
> >> repository.
> >>
> >> Name:		draft-boucadair-mptcp-dhc
> >> Revision:	02
> >> Title:		DHCP Options for Network-Assisted Multipath TCP (MPTCP)
> >> Document date:	2015-11-05
> >> Group:		Individual Submission
> >> Pages:		11
> >> URL:            https://www.ietf.org/internet-drafts/draft-boucadair-
> >> mptcp-dhc-02.txt
> >> Status:         https://datatracker.ietf.org/doc/draft-boucadair-mptcp-
> >> dhc/
> >> Htmlized:       https://tools.ietf.org/html/draft-boucadair-mptcp-dhc-
> 02
> >> Diff:           https://www.ietf.org/rfcdiff?url2=draft-boucadair-
> mptcp-
> >> dhc-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 consider a network-assisted
> model
> >>    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.
> >>
> >>
> >>
> >>
> >>
> >> 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.
> >>
> >> The IETF Secretariat
> >
> >_______________________________________________
> >dhcwg mailing list
> >dhcwg@ietf.org
> >https://www.ietf.org/mailman/listinfo/dhcwg
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg