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

Dan Seibel <Dan.Seibel@TELUS.COM> Mon, 09 November 2015 15:50 UTC

Return-Path: <Dan.Seibel@telus.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 2AC3C1B2DF4 for <dhcwg@ietfa.amsl.com>; Mon, 9 Nov 2015 07:50:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 DpVg2svPQ9vu for <dhcwg@ietfa.amsl.com>; Mon, 9 Nov 2015 07:50:43 -0800 (PST)
Received: from donder.nssi.telus.com (donder.nssi.telus.com [208.38.59.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7D3231B2DBC for <dhcwg@ietf.org>; Mon, 9 Nov 2015 07:50:43 -0800 (PST)
DomainKey-Signature: s=donder.nssi; d=telus.com; c=nofws; q=dns; h=X-IronPort-Anti-Spam-Filtered: X-IronPort-Anti-Spam-Result:X-IronPort-AV:Received: Received:From:To:Date:Subject:Thread-Topic:Thread-Index: Message-ID:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:user-agent: acceptlanguage:Content-Type:Content-Transfer-Encoding: MIME-Version; b=dC9mi97fQ3+2VPQXohgxCTbv9GHqJ9F5rXSrzThchQntsTLp+C4H5KrA eDzvk7wqevJxALXliXmEcNJnIwtva4zCYL/ZgbVnXNy1gJsMGi2aQnsGL iUJG/U/AZ4l9kGKsddUdyoF+BGucf73W0ecC7qZsXQ2kpbg3vKTVpbxZr 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2AKAgCUv0BW/5Jjso5VCYMPLFNvvj0BDYFhFwqFb4FCOBQBAQEBAQEBgQqENgEBBAEBAVAbHQEIDTImCAsUEgEEARKILgEMwE8BAQgCASCGVIR+hDERF4RgBY0bOT2INw+FD4gJgVtJg3eDGY8fg3IfAQFChCRShWYBAQE
X-IronPort-AV: E=Sophos;i="5.20,266,1444694400"; d="scan'208";a="459440303"
Received: from unknown (HELO WP40081.corp.ads) ([142.178.99.146]) by donder-o.nssi.telus.com with ESMTP/TLS/AES128-SHA; 09 Nov 2015 15:50:42 +0000
Received: from WP41072.corp.ads ([fe80::782e:6557:8fc4:def7]) by WP40081.corp.ads ([::1]) with mapi; Mon, 9 Nov 2015 08:50:41 -0700
From: Dan Seibel <Dan.Seibel@TELUS.COM>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Mon, 09 Nov 2015 08:50:38 -0700
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AdEbBmKTbwftk3lYQ+2W8C9ebSXh4Q==
Message-ID: <D2660C4C.7A833%dan.seibel@telus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.7.151005
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Cao4h7MEHeFOFlTp76h0_jON6W8>
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: Mon, 09 Nov 2015 15:50:46 -0000

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