Re: [v6ops] Windows 10 doesn't honour 'M' flag in RA

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 13 December 2017 15:24 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15341126E7A; Wed, 13 Dec 2017 07:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 71_iJWycSl0v; Wed, 13 Dec 2017 07:24:26 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (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 668E6126CF6; Wed, 13 Dec 2017 07:24:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id vBDFOPti028352; Wed, 13 Dec 2017 08:24:26 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id vBDFOJHx027930 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 13 Dec 2017 08:24:19 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-10.nw.nos.boeing.com (2002:8988:efdb::8988:efdb) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 13 Dec 2017 07:24:18 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1347.000; Wed, 13 Dec 2017 07:24:18 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Naveen Kottapalli <naveen.sarma@gmail.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Thread-Topic: [v6ops] Windows 10 doesn't honour 'M' flag in RA
Thread-Index: AQHTc3ids/3rysN/2UOtzik0uog6BqNADGWAgAGWlID//8Bd4A==
Date: Wed, 13 Dec 2017 15:24:18 +0000
Message-ID: <97a10ed486fd4f8993cfade81f90c8da@XCH15-06-08.nw.nos.boeing.com>
References: <CANFmOtnJiKtBH9WuOjfAAaOxmrQ8SanU1ATiEY_zSA9DbAuUAA@mail.gmail.com> <CAAedzxptEK5nZTVHwuzG0aK119Ns61cdfNT3JWPafTGcAxMeeg@mail.gmail.com> <CANFmOtm2SU13o3Wey1XqhQf0WuuTzm80XXPp7Q9UGiV6Kvh5DA@mail.gmail.com> <alpine.DEB.2.20.1712120844540.8884@uplift.swm.pp.se> <b90e4615-eee9-839a-c65b-805824122c29@gmail.com> <7c3d5bb6f4cf4df98ce53c705816242c@XCH15-06-02.nw.nos.boeing.com> <CANFmOtmdORBxjT4zHf65uKNR6-YrEYHoMCBrcCogHBWP7+ifcw@mail.gmail.com>
In-Reply-To: <CANFmOtmdORBxjT4zHf65uKNR6-YrEYHoMCBrcCogHBWP7+ifcw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.137.12.6]
Content-Type: multipart/alternative; boundary="_000_97a10ed486fd4f8993cfade81f90c8daXCH150608nwnosboeingcom_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ezqKr3CR3-rEDbEGsZOb0XEZiuQ>
Subject: Re: [v6ops] Windows 10 doesn't honour 'M' flag in RA
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Dec 2017 15:24:29 -0000

Hi Naveen,

> Yes, it would have been the better way.

It’s not too late to set things right. Combining IPv6 ND router discovery
and DHCPv6 in a single, unified service combines the best features of
stateless and stateful autoconfiguration. All it takes is defining a new
IPv6 ND message option.

Plus, it is backwards compatible. If the host sends an RS with a DHCPv6
option, and the router does not recognize the option, the router sends
back an RA with no DHCPv6 option and the host can know that it needs
to do things the old way (i.e., send DHCPv6 Solicit after receiving the RA).
In the other direction, the router will never send an RA with the DHCPv6
option included unless the host first sent an RS with DHCPv6 option.

With a combined autoconfiguration service  like this, the ages-old debate
about SLAAC vs. DHCPv6 goes away, and we truly get the best of both
worlds.

Thanks - Fred

From: Naveen Kottapalli [mailto:naveen.sarma@gmail.com]
Sent: Wednesday, December 13, 2017 3:03 AM
To: Templin, Fred L <Fred.L.Templin@boeing.com>
Cc: v6ops@ietf.org; ipv6@ietf.org
Subject: Re: [v6ops] Windows 10 doesn't honour 'M' flag in RA

Yes, it would have been the better way.  If clients aren't even referring the 'M' bit, what is the use of carrying in RA?

Yours,
Naveen.

On 13 December 2017 at 00:20, Templin, Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>> wrote:
This is why it would be better to have IPv6 ND and DHCPv6 as a unified
stateless/stateful autoconfiguration service. Everything can be done in
a single message exchange (RS/RA with DHCPv6 option) instead of
requiring multiple message exchanges just for the sake of examining
the M/O bits.

Thanks - Fred

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------