Re: [v6ops] M/O flags and PD

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 30 October 2015 14:45 UTC

Return-Path: <Fred.L.Templin@boeing.com>
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 1B9201A1BC2 for <v6ops@ietfa.amsl.com>; Fri, 30 Oct 2015 07:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 vLAyINgF5UEw for <v6ops@ietfa.amsl.com>; Fri, 30 Oct 2015 07:45:20 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (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 D6CFA1A1A98 for <v6ops@ietf.org>; Fri, 30 Oct 2015 07:45:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t9UEjLFF026076; Fri, 30 Oct 2015 09:45:21 -0500
Received: from XCH-BLV-406.nw.nos.boeing.com (xch-blv-406.nw.nos.boeing.com [130.247.25.162]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t9UEjB4U025409 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 30 Oct 2015 09:45:11 -0500
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.14]) by XCH-BLV-406.nw.nos.boeing.com ([169.254.6.161]) with mapi id 14.03.0235.001; Fri, 30 Oct 2015 07:45:09 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Gert Doering <gert@space.net>, Tore Anderson <tore@fud.no>
Thread-Topic: [v6ops] M/O flags and PD
Thread-Index: AQHREuB/Fp3T7dBlRUqAWJXhaLg8yZ6EG6UAgAAI8oCAAAL2gIAACYkAgAADHYD//+h2UA==
Date: Fri, 30 Oct 2015 14:45:08 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832F348D8@XCH-BLV-504.nw.nos.boeing.com>
References: <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> <20151030073854.GZ70452@Space.Net> <20151030091055.2b050875@echo.ms.redpill-linpro.com> <20151030082131.GC70452@Space.Net> <20151030095538.20544d0a@echo.ms.redpill-linpro.com> <20151030090647.GG70452@Space.Net>
In-Reply-To: <20151030090647.GG70452@Space.Net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/9gsH6mvlyyJpELD9TIgwFnShsDY>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "jinmei@wide.ad.jp" <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 14:45:22 -0000

Hi Gert,

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Gert Doering
> Sent: Friday, October 30, 2015 2:07 AM
> To: Tore Anderson
> Cc: v6ops@ietf.org; jinmei@wide.ad.jp
> Subject: Re: [v6ops] M/O flags and PD
> 
> Hi,
> 
> On Fri, Oct 30, 2015 at 09:55:38AM +0100, Tore Anderson wrote:
> > * Gert Doering <gert@space.net>
> >
> > > Yes, but that is the point - "typical routers" do not need to
> > > *listen* to RAs, because that's not required for their job.  They
> > > will speak a routing protocol, and not default-route, etc.
> >
> > Who is listening for RAs or not seems to me to be besides the point. It
> > boils down to this: If you are about to originate an RA to a link, and
> > know that there is information available in DHCPv6 on said link, you
> > should set set the M or O flag. Otherwise you're supplying false
> > information by indicating that there is no information available in
> > DHCPv6.
> 
> No, the point I was trying to made is: conceptually, DHCPv6 PD is happening
> outside RA.  RA is "information to hosts", PD is "done by routers".
> 
> But I already agreed that this is not written down anywhere, but my
> interpretation on how this can all make sense.
> 
> [..]
> > > As I said, boundaries between "hosts" and "router" are less than clear
> > > today - but this is my interpretation on how these have come into place.
> >
> > Indeed. Thus I believe claims like <hosts don't request prefixes> or
> > <routers don't process RAs> can't be considered true (unless a node can
> > be both simultaneously).
> 
> We had this discussion in the context of the CPE spec - a CPE is a
> router (obviously), but for acquiring its management IPv6 address and
> for being talked to on the management address, it's very obviously a
> host as well.  So of course a node can be both.

Right, and it is fine for a host to act as a requesting router from the
standpoint of DHCPv6 PD but then use the delegated prefix for its
own multi-addressing purposes rather than to provision addresses
for other hosts.

Thanks - Fred
fred.l.templin@boeing.com

> 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