Re: [v6ops] RFC7084

Nick Hilliard <nick@inex.ie> Tue, 10 December 2013 17:05 UTC

Return-Path: <nick@inex.ie>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 303071AE222 for <ipv6@ietfa.amsl.com>; Tue, 10 Dec 2013 09:05:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 De-KRkaqVlrs for <ipv6@ietfa.amsl.com>; Tue, 10 Dec 2013 09:05:27 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8DE1AE21E for <ipv6@ietf.org>; Tue, 10 Dec 2013 09:05:26 -0800 (PST)
X-Envelope-To: ipv6@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100::126]) (authenticated bits=0) by mail.netability.ie (8.14.7/8.14.5) with ESMTP id rBAH5IGY009827 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 10 Dec 2013 17:05:18 GMT (envelope-from nick@inex.ie)
X-Authentication-Warning: cheesecake.netability.ie: Host [IPv6:2001:4d68:2002:100::126] claimed to be cupcake.foobar.org
Message-ID: <52A749CE.7020605@inex.ie>
Date: Tue, 10 Dec 2013 17:05:18 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>, Sander Steffann <sander@steffann.nl>
Subject: Re: [v6ops] RFC7084
References: <96747494E3D74D41B20907035DB1E48DC7BB@MOPESMBX03.eu.thmulti.com> <2D09D61DDFA73D4C884805CC7865E611303B0269@GAALPA1MSGUSR9L.ITServices.sbc.com> <96747494E3D74D41B20907035DB1E48DCD72@MOPESMBX03.eu.thmulti.com> <alpine.DEB.2.02.1312100803370.24602@uplift.swm.pp.se> <F92E1B55-C74B-400C-B83E-6B50D175D121@steffann.nl> <7B4820C5-B562-4BE7-8C6A-CBCDABC39728@nominum.com>
In-Reply-To: <7B4820C5-B562-4BE7-8C6A-CBCDABC39728@nominum.com>
X-Enigmail-Version: 1.6
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 10 Dec 2013 16:53:01 -0800
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Dec 2013 17:05:29 -0000

On 10/12/2013 16:51, Ted Lemon wrote:
> On Dec 10, 2013, at 6:08 AM, Sander Steffann <sander@steffann.nl> wrote:
>> As far as I know the M flag is linked only to IA_NA. As far as I can see IA_PD is not linked to the M flag at all.
> 
> There is no agreement on what the M and O bits do.   Some people think M means stateful address management; some think M means IA_NA and O means IA_PD.   RFC 4861 is actually fairly clear, at least to my reading of it, that "M" means IA_NA and IA_PD, and that "O" means stateless DHCPv6, but I've heard people argue vehemently that "M" means _only_ IA_NA, and that "O" means IA_PD, because prefixes aren't addresses.
> 
> So if you believe my reading of RFC 4861, you would set 'M' and expect the HG to get both IA_NA and IA_PD; RFC 7084 makes it clear that _either_ the 'M' or 'O' bit being set triggers the HG to do prefix delegation.
> 
> So if you want to do prefix delegation and not stateful address assignment, set the 'O' bit and _not_ the 'M' bit, even though that contradicts what RFC 4861 says.

<head spins>