Re: [v6ops] RFC7084

Owen DeLong <owen@delong.com> Tue, 10 December 2013 17:37 UTC

Return-Path: <owen@delong.com>
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 151231AE04C; Tue, 10 Dec 2013 09:37:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.992
X-Spam-Level:
X-Spam-Status: No, score=-0.992 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=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 1hp1osSVnxny; Tue, 10 Dec 2013 09:37:57 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 14CEC1ADF4F; Tue, 10 Dec 2013 09:37:57 -0800 (PST)
Received: from [172.25.1.50] (itsaudcal312pc1.ics.usc.edu [68.181.189.124]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id rBAHUXrl031001 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 10 Dec 2013 09:30:34 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com rBAHUXrl031001
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1386696635; bh=oiUy5sSjbOwX76oRPIf7OHo0pr0=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=nwsm0vzFWKtXy6g/6Jj19CW7NO/uWGnqRNdjag6+CMlFyigv8J6WI5vpXve3AS0yR jOnTCeNLd6/bL6XjSIgvm0L047vo7rG9dPQne9N5AjEP13pvoc2xRco253TcbjQApj G64UKPYxkFoaYk9EfDnIfnfHrlSRlEnFGmd14AL8=
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Subject: Re: [v6ops] RFC7084
From: Owen DeLong <owen@delong.com>
In-Reply-To: <7B4820C5-B562-4BE7-8C6A-CBCDABC39728@nominum.com>
Date: Tue, 10 Dec 2013 09:30:33 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A583EFC3-71BB-4962-875C-4AB775D13491@delong.com>
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>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1822)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Tue, 10 Dec 2013 09:30:35 -0800 (PST)
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@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:37:59 -0000

My understanding from reading the various documents is that M = IA_NA, O= everything else. Further, if M=1, O doesn’t really matter.

In no case do I believe that M or O provide any indication about IA_PD.

I agree that it makes no sense for an HG (among others) not to do IA_PD.

Owen

On Dec 10, 2013, at 8:51 AM, Ted Lemon <Ted.Lemon@nominum.com> 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.
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops