Re: [v6ops] M/O flags and PD

Gert Doering <gert@space.net> Fri, 30 October 2015 07:38 UTC

Return-Path: <gert@Space.Net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2F1B1A89A5 for <v6ops@ietfa.amsl.com>; Fri, 30 Oct 2015 00:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 1p3guMKLy8gO for <v6ops@ietfa.amsl.com>; Fri, 30 Oct 2015 00:38:57 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (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 41A701A87C1 for <v6ops@ietf.org>; Fri, 30 Oct 2015 00:38:56 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 895D462E91 for <v6ops@ietf.org>; Fri, 30 Oct 2015 08:38:54 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 5497660391 for <v6ops@ietf.org>; Fri, 30 Oct 2015 08:38:54 +0100 (CET)
Received: (qmail 46596 invoked by uid 1007); 30 Oct 2015 08:38:54 +0100
Date: Fri, 30 Oct 2015 08:38:54 +0100
From: Gert Doering <gert@space.net>
To: Tore Anderson <tore@fud.no>
Message-ID: <20151030073854.GZ70452@Space.Net>
References: <20151019195001.22760.2580.idtracker@ietfa.amsl.com> <5AB28826-8E45-461F-AA7B-5D45F218FC18@cisco.com> <20151028113851.530c649d@echo.ms.redpill-linpro.com> <CAJE_bqd1263SaqU61sqqk_4Tne1GzE4_kMUhuLMgY42Cyc6m_A@mail.gmail.com> <5631232E.4020701@gmail.com> <20151029203951.06a4d4fd@envy.fud.no> <39B7C63D-A31A-4F3D-8487-5A9FF917F939@employees.org> <20151030075849.5ad90ed6@echo.ms.redpill-linpro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20151030075849.5ad90ed6@echo.ms.redpill-linpro.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/EI5ghhyb9Uqk0DaPkZyxvs45Jfc>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, ???????????? <jinmei@wide.ad.jp>
Subject: Re: [v6ops] M/O flags and PD
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 30 Oct 2015 07:38:59 -0000

Hi,

On Fri, Oct 30, 2015 at 07:58:49AM +0100, Tore Anderson wrote:
> We can even disregard RFC 7084, as it's not a standard. RFC 4861
> Section 4.2 is where the flags and their meaning is specified. It says,
> and I quote:
[..]
> So DHCPv6-provided configuration is divided into two categories:
> 
> 1) addresses
> 2) other
> 
> The availability of both of these categories of configuration is
> signalled through the M/O flags. Nowhere that I can find is a third
> «other than "other"» category of DHCPv6-provided configuration defined
> or even hinted at.

I do not have RFCs to counter that, but my interpretation is a bit
different.  I see that section of 4861 as traditionally applied to 
*hosts*, while IA_PD traditionally is a *router* function, so out of 
scope for the "host part" of 4861.

Now this gets all muddled together when you have a router that also 
wants an address for itself (= acting as a host for that purpose) or 
a host that wants a prefix (= serving as a router for that prefix).

Conceptually, still, "address for me" is a fairly independent thing
from "prefix for something I serve as a router"...  and 4861/O/M only
seem to cover the "address for me" part.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279