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

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