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

Bob Hinden <bob.hinden@gmail.com> Wed, 13 December 2017 21:43 UTC

Return-Path: <bob.hinden@gmail.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 E7A7E126D73; Wed, 13 Dec 2017 13:43:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 weEb_le_AROf; Wed, 13 Dec 2017 13:43:32 -0800 (PST)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F364512704B; Wed, 13 Dec 2017 13:43:31 -0800 (PST)
Received: by mail-pf0-x235.google.com with SMTP id j28so2079970pfk.8; Wed, 13 Dec 2017 13:43:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=YAMLiS5BErtR6umb+60F3azxbZ4FGHRRTmC3Xhd31w4=; b=Tsr7eYjO9PR+gf1lqvjBJe87J/dzPC8e7wGS63Z2rmj+3I8/Pu2W1qKD+RvLTkYmfX pOnaJ8Bs4JN4b/1qGB56IRKeQh/uCctPqzKnJXfxe7ITUk5dIBD3gyliF35duyLgHRHx pd8c986XWnY1N66ETtpH90H4ZnamNqcLLDpI7L/eKGvcFSe1pl8vZqkCdvNxisc+KMNE ZE9KiJFIMy09WAvxz22G1oAhLobvnyvYY44JGIW4NTRiHKfwhPLU2X5YxTEsccQRr63O LUtSqDUeJwkR4etPWo/3TCTbT9nhysei640fMe1UE8MlTc41IwVPe85inC8jcB05YWLr 265w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=YAMLiS5BErtR6umb+60F3azxbZ4FGHRRTmC3Xhd31w4=; b=YkM1XsnM3lIUPW0nwPWEjnCJPGlerBhqL6489/3MXJBH9JxHyjNAtQ1T+i8qb+/62Y dilQRu+THct+YaokM9TqLJGqmmivHCXoPz+Bj8t5kiYrUmfVyQFQN/Aof+vNw+fD60rq yhyazMqu8DuOjGzw1VzZaB1PJ1TtM5H1pcIqYWvNukQsm804o3LS+XkHhzBrjy9pqK3b mYy2UsyRhlC6I2d570MzC0UQ8t3vobd5Iw+PkmAsWpQP91iaP+c1YueyNUk7n0wCTDOJ pram8YTwif2rEhslWIBkx33xQwGT8WhrD57sN151tSG0nHgkPV6m2evR2nLDsNRG8fuR 1glQ==
X-Gm-Message-State: AKGB3mKksyN1Xx8cJgPkgDHkkN7fFnAZrOr/OsURdPBcDG9fApbHft12 VS/ljO4rxCwbAxr8YjUBYqw=
X-Google-Smtp-Source: ACJfBot7pjWOmtYDSCc/N/6KE0gJfhXA0DgKzZlbtsabQVw71di3+UKgv0IqVujdkEveUlmY7V64Jw==
X-Received: by 10.99.124.24 with SMTP id x24mr6470695pgc.196.1513201411569; Wed, 13 Dec 2017 13:43:31 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id z23sm4428634pgc.2.2017.12.13.13.43.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Dec 2017 13:43:29 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <E9CDFC94-72B5-46A7-AE8B-2C2B2FBF435E@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_098534B7-E197-4DB3-BC1B-1DFB55E961A1"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 13 Dec 2017 13:43:27 -0800
In-Reply-To: <F8345142-BDC9-4E9D-ABDB-B17F15EF210F@google.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, "v6ops@ietf.org list" <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
To: james woodyatt <jhw@google.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> <F8345142-BDC9-4E9D-ABDB-B17F15EF210F@google.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/sFNYp1w2-XfroxfVtcAWS_xg6qo>
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 21:43:34 -0000

James,

> On Dec 13, 2017, at 12:27 PM, james woodyatt <jhw@google.com> wrote:
> 
> On Dec 13, 2017, at 11:34, Simon Hobson <linux@thehobsons.co.uk> wrote:
>> 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 ?
> 
> Put another way, "are there really professionally managed networks?”
> 
> Worth noting: the point is that the “Note:” in RFC 4861 cited previously in the thread asserts that M=0&O=0 is a signal to all hosts on the link that “no information is available via DHCPv6,” which is really only true while *all* the routers on the link are consistently sending that signal. It stops being true as soon as one or more of the routers on the link contradict the signal, and it continues to not be true until all the contradicting routers expire their valid lifetimes. On a “professionally managed network,” there might never be any contradicting routers on the link at any time, and in that case the Note correctly describes how the protocol works. In other cases, however, it remains a little less than clear.
> 
> So, I ask again: are there really professionally managed networks?

Yes.  The common definition of professional is that you get paid to do a job.  How well you do it is another matter :-)

To you point, I think there are networks where all of the routers are configured correctly.

Bob