IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Tue, 17 November 2015 15:28 UTC

Return-Path: <Ted.Lemon@nominum.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 982B71A9117; Tue, 17 Nov 2015 07:28:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level:
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585] 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 4qwxCI2PGpuz; Tue, 17 Nov 2015 07:28:46 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BF261A9115; Tue, 17 Nov 2015 07:28:46 -0800 (PST)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id C6951DA0096; Tue, 17 Nov 2015 15:28:45 +0000 (UTC)
Received: from mbx-03.WIN.NOMINUM.COM ([169.254.4.19]) by CAS-04.WIN.NOMINUM.COM ([64.89.235.67]) with mapi id 14.03.0224.002; Tue, 17 Nov 2015 07:28:46 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Niall O'Reilly <niall.oreilly@ucd.ie>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AdEbBmKTbwftk3lYQ+2W8C9ebSXh4QAfEywwABV+PgAAAJveAAABmjuAAAmZWQAAA4EzgABdzasAAAB6MQAAAH71AAAB8nKAAAGZCQAANcBUAAC4qL4A///Yhsw=
Date: Tue, 17 Nov 2015 15:28:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630797A045A5@mbx-03.WIN.NOMINUM.COM>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk> <m237w9g80l.wl-Niall.oReilly@ucd.ie>, <787AE7BB302AE849A7480A190F8B933008C9F043@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933008C9F043@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [71.233.41.235]
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/5DS_u84Bs0nJGbqJl16Sr2DFTUU>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
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, 17 Nov 2015 15:28:47 -0000

Neither text is correct.   If you are going to specify DHCP server behavior with normative language, you are updating RFC 3315, which you almost certainly do not want to do.   RFC 3315 already specifies the correct behavior.   Please remove this text.   RFC 7227 section 21.2 touches on this issue.
________________________________________
From: dhcwg [dhcwg-bounces@ietf.org] on behalf of mohamed.boucadair@orange.com [mohamed.boucadair@orange.com]
Sent: Tuesday, November 17, 2015 03:56
To: Niall O'Reilly
Cc: multipathtcp@ietf.org; dhcwg@ietf.org
Subject: Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)

Hi Niall,

Ok, noted.

Hope to hear more voices.

Cheers,
Med

> -----Message d'origine-----
> De : Niall O'Reilly [mailto:niall.oreilly@ucd.ie]
> Envoyé : vendredi 13 novembre 2015 17:49
> À : BOUCADAIR Mohamed IMT/OLN
> Cc : Simon Hobson; multipathtcp@ietf.org; dhcwg@ietf.org
> Objet : Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
> (MPTCP)
>
> On Thu, 12 Nov 2015 15:09:38 +0000,
> <mohamed.boucadair@orange.com> wrote:
> >
> > Re-,
> >
> > The change you asked for is as follows:
> >
> > ==============
> > OLD:
> >    The DHCP server MUST NOT reply with the DHCP MPTCP Concentrator
> >    option unless the client has explicitly requested for it.
> >
> > NEW:
> >    The DHCP server SHOULD NOT reply with the DHCP MPTCP Concentrator
> >    option unless the client has explicitly requested for it.
> > ==============
> >
> > Comments from the wg about this change is welcome.
>
>   Yes, please!  I think Simon has explained the need already.
>
>   Best regards,
>   Niall O'Reilly
>
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email