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

Bob Hinden <bob.hinden@gmail.com> Wed, 13 December 2017 16:45 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 8D0B4127077; Wed, 13 Dec 2017 08:45:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, 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 z6lLVZhOPCVy; Wed, 13 Dec 2017 08:45:53 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 824C1126D0C; Wed, 13 Dec 2017 08:45:53 -0800 (PST)
Received: by mail-wm0-x230.google.com with SMTP id 64so6369596wme.3; Wed, 13 Dec 2017 08:45:53 -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=zBbl1NwMWzear1xG0mC3Sza2wSECM0KOrUOuBCwKTXo=; b=RcDClaBgLfLhyF0hVxBQwg6qIepONHzTvyLYl2BNjPswUxmAmwftJ6vsV8MHOfH7ok 8g6GIWiGj/9c+/tIn3Q/raJdPSrGsMG8L0l3Fbe/qCETwbMywySDOzIwamAvGpGGFkSN hkaX7vrfI+lFFbPjf4oFWZO2E7L8PslbUn6UtAmRRR5OVSYxvdYiPgMwoVBbV0JK/4tW gcg1+6qOwVB0K62AQohAj3vbnDLhPH5yu7RIc7vurXsBoRzyQuScxIzqLYRLNYOj7j7s FrR3gKmG3Xo6ZMPuypXqxoNduE5hoKAWNn8GXP0hL+shPfkPGQ6TjeYQqB8SRYyLV+05 ArEw==
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=zBbl1NwMWzear1xG0mC3Sza2wSECM0KOrUOuBCwKTXo=; b=iX/mxIyYjD0WUuPOLsC7wG8GfBOAtteMcO/k+zlVZB1yPNUDWiENO6xNR7AgF/Cuho /xGz4Zjc7UXYxM2WnUSyiN4wVYG7ShY94xB0W+Oj3uwunLBDItt8qYo5KSDxmRdoKJR6 3ihJ80TkoxDfS0VE6V3Zb06deD+rBp4qI1gz2dgCslA4g+NZRkKv0dkD00pd1yCjRSGM 4ucUk0T3Gd7RAezrQqQZF+4a1EaJ+AQfMEsSfpxkTRgB3l7LDCTgVkpjk21phpUfAazZ r0GXXeZORJCr9JMSXmx7rrCW5HPX31jmN8ACR4xeEdaJHK3ufxvkJmsePnhYZQUFOjjH bBfA==
X-Gm-Message-State: AKGB3mIk58GQIwDCbUIldMFVM+bXQ2CA1LbfF1pZOV6Lb7LhL4T1jHk5 p5r9YnLMDKQzCasg+3fScHs=
X-Google-Smtp-Source: ACJfBovXBg5M48EvTomUa91wagvIDsu9vyeiLUjlB/sYN73z6YdCpV6e/FQ3FP7GGqAzcnTbFy84HA==
X-Received: by 10.28.26.139 with SMTP id a133mr2458931wma.90.1513183551972; Wed, 13 Dec 2017 08:45:51 -0800 (PST)
Received: from ?IPv6:2601:647:4d01:db10:90c2:513b:e253:d64f? ([2601:647:4d01:db10:90c2:513b:e253:d64f]) by smtp.gmail.com with ESMTPSA id j13sm2269640wre.55.2017.12.13.08.45.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Dec 2017 08:45:51 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <0B00C5CB-9806-4215-B616-D9BE51196FAD@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C0F48051-A8CD-4208-97DD-296856C70214"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 13 Dec 2017 08:45:46 -0800
In-Reply-To: <21FDCF40-8598-4CEE-9778-0E648697A9E9@fugue.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Tim Chown <Tim.Chown@jisc.ac.uk>, "v6ops@ietf.org" <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
To: Ted Lemon <mellon@fugue.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>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/4GzVA566GahatsawBD3aKOv89ro>
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 16:45:55 -0000

Ted,

The actual text from Section 4.2. "Router Advertisement Message Format” in RFC4861 is:

      M              1-bit "Managed address configuration" flag.  When
                     set, it indicates that addresses are available via
                     Dynamic Host Configuration Protocol [DHCPv6].

                     If the M flag is set, the O flag is redundant and
                     can be ignored because DHCPv6 will return all
                     available configuration information.

      O              1-bit "Other configuration" flag.  When set, it
                     indicates that other configuration information is
                     available via DHCPv6.  Examples of such information
                     are DNS-related information or information on other
                     servers within the network.

        Note: If neither M nor O flags are set, this indicates that no
        information is available via DHCPv6.

I think the protocol specification is clear.

Bob




> On Dec 13, 2017, at 8:03 AM, Ted Lemon <mellon@fugue.com> wrote:
> 
> On Dec 13, 2017, at 7:29 AM, Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
>> A ‘hint’ was the consensus.
> 
> A 'hint' was the vote.   I don't believe that it was a consensus.   As Naveen points out, the current solution is technically invalid.   It would be better not to have the 'M' bit than to have it be a hint.
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------