IETF Logo Mail Archive

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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 13 December 2017 19:41 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 2AA87127AD4; Wed, 13 Dec 2017 11:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 HFTdjv0EChLv; Wed, 13 Dec 2017 11:41:16 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 38BE5126E7A; Wed, 13 Dec 2017 11:41:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id vBDJfFdb040849; Wed, 13 Dec 2017 12:41:15 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id vBDJfBDG040804 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 13 Dec 2017 12:41:11 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 13 Dec 2017 11:41:10 -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 11:41:10 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org list" <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
Thread-Topic: [v6ops] Windows 10 doesn't honour 'M' flag in RA
Thread-Index: AQHTc3ids/3rysN/2UOtzik0uog6BqNADGWAgAGf3HSAAAE2IA==
Date: Wed, 13 Dec 2017 19:41:10 +0000
Message-ID: <5a503a3d1fcd43e882c782b6b9031e79@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> <alpine.DEB.2.20.1712131225280.8884@uplift.swm.pp.se> <CANFmOtkKcq8fkms5op1WftLmGok003UcMt4Y+0+3BLcE_myO0Q@mail.gmail.com> <F2F31353-9641-4670-8152-0DF1B184451E@jisc.ac.uk> <21FDCF40-8598-4CEE-9778-0E648697A9E9@fugue.com> <0B00C5CB-9806-4215-B616-D9BE51196FAD@gmail.com> <CANFmOtk4x86YDwuezZO_VzFn4RT41PZiZKL+mrFvRSPP4WkyFw@mail.gmail.com> <aa71c96d-0829-5b6b-19e7-27834dce565e@gmail.com> <D1717655-A8E7-4595-A35E-142F4A8AADD7@thehobsons.co.uk>
In-Reply-To: <D1717655-A8E7-4595-A35E-142F4A8AADD7@thehobsons.co.uk>
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/AB4vr5CPD4aSS6DUzHMKbw1uuPk>
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 19:41:18 -0000

Hi,

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Simon Hobson
> Sent: Wednesday, December 13, 2017 11:35 AM
> To: v6ops@ietf.org list <v6ops@ietf.org>; IPv6 List <ipv6@ietf.org>
> Subject: Re: [v6ops] Windows 10 doesn't honour 'M' flag in RA
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> > Well, the "Note:" does leave an open question. How does the person (or
> > automaton) configuring the router that sends the RA know that no
> > information is available via DHCPv6? It is entirely possible that
> > DHCPv6 is available on another box, and the person configuring the
> > the router doesn't know it. So these flags are intrinsically unreliable
> > and can only be hints; it's *necessary* that hosts are allowed to
> > ignore them and look for DHCPv6 anyway.
> 
> I keep hearing this argument time and time again, but cannot reconcile it with any professionally managed network. Are there really
> professionally managed networks where the guys responsible for the routers (intrinsically tied in with the network config) don't talk
> to the guys running DHCP servers (intrinsically tied in with the network config) ?
> Put another way, are there really networks where two different groups "do their own thing" without agreeing between themselves
> how the network is supposed to work ?

A unified SLAAC/DHCPv6 service would reconcile the ambiguity.

Thanks - Fred

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

v2.23.0 | Report a Bug | By Email