Re: [v6ops] M/O flags and PD

Gert Doering <gert@space.net> Fri, 30 October 2015 09:06 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 12B831A87A2 for <v6ops@ietfa.amsl.com>; Fri, 30 Oct 2015 02:06:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 ESPLKSewE_lo for <v6ops@ietfa.amsl.com>; Fri, 30 Oct 2015 02:06:50 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.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 E866A1A879E for <v6ops@ietf.org>; Fri, 30 Oct 2015 02:06:49 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id DCCAF62F0D for <v6ops@ietf.org>; Fri, 30 Oct 2015 10:06:47 +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 8347362E91 for <v6ops@ietf.org>; Fri, 30 Oct 2015 10:06:47 +0100 (CET)
Received: (qmail 52743 invoked by uid 1007); 30 Oct 2015 10:06:47 +0100
Date: Fri, 30 Oct 2015 10:06:47 +0100
From: Gert Doering <gert@space.net>
To: Tore Anderson <tore@fud.no>
Message-ID: <20151030090647.GG70452@Space.Net>
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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="+T+TIFsggo/fsWlW"
Content-Disposition: inline
In-Reply-To: <20151030095538.20544d0a@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/khhapdh8JHBThFLiT62whg0L04g>
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 09:06:52 -0000

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.

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