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

[<[e-mail]>]

Hi Dan,

Thank you for the feedback. 

Please see inline. 

Cheers,
Med

> -----Message d'origine-----
> De : Dan Seibel [mailto:[e-mail]]
> Envoyé : lundi 9 novembre 2015 16:51
> À : BOUCADAIR Mohamed IMT/OLN; [e-mail]
> Objet : 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?)
> 
[Med] The client has to indicate the option if it needs to be provisioned with a concentrator. I changed the wording to make it clearer: 

"To discover one or more MPTCP Concentrators, the DHCPv4 client MUST include OPTION_V4_MPTCP in a Parameter Request List Option [RFC2132]."

> - 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.
> 
> 
[Med] We assumed that as being the default behavior of the server. In order to make it cleared, I added this sentence in section 5:

"The DHCP server MUST NOT reply with the DHCP MPTCP Concentrator option unless the client has explicitly requested for it."

> 
> 
> 
> On 2015-11-05, 8:19 AM, "dhcwg on behalf of [e-mail]"
> <[e-mail] on behalf of [e-mail]> wrote:
> 
> >Dear all,
> >
> >Comments are more than welcome.
> >
> >Cheers,
> >Med
> >
> >> -----Message d'origine-----
> >> De : [e-mail] [mailto:[e-mail]]
> >> 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
> >[e-mail]
> >https://www.ietf.org/mailman/listinfo/dhcwg