Re: [v6ops] DHCPv6 PD route injection

Mikael Abrahamsson <swmike@swm.pp.se> Tue, 14 November 2017 05:00 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95713128AA1 for <v6ops@ietfa.amsl.com>; Mon, 13 Nov 2017 21:00:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 VYniksFsbucx for <v6ops@ietfa.amsl.com>; Mon, 13 Nov 2017 21:00:12 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 953AC1286C7 for <v6ops@ietf.org>; Mon, 13 Nov 2017 21:00:12 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 46C96B2; Tue, 14 Nov 2017 06:00:10 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1510635610; bh=UAlrxxmevn/R9O0I22u03ardq1RhdUHjwXNdw68mnbM=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=emwUKcjW1chvBpdT+Njw/zMLrCc7iVNUv2CUJ6w5RcAI/alxmjsY2aldrWxSAbMOL 75MmERUrKv76elDMZp7InNE0xlF9pgEDGlw4kkzCWtePFsu9/ziNa9PeC4XctNQO49 JLoB3Jaq1UvfWG8hiDJql1O57YpKp6PITAYYfqG0=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 40218AF; Tue, 14 Nov 2017 06:00:10 +0100 (CET)
Date: Tue, 14 Nov 2017 06:00:10 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
cc: v6ops@ietf.org
In-Reply-To: <6a7622ee-3517-b874-5ab9-80a7bff865ea@gmail.com>
Message-ID: <alpine.DEB.2.20.1711140555290.16389@uplift.swm.pp.se>
References: <be9724f5-2ff5-d90c-2749-ecae2c628b78@si6networks.com> <207f040a-7fe2-9434-e7a5-f546b26fdf63@strayalpha.com> <CAKD1Yr26NK2osApYZBm8Yd=0X7xcetrxojp6=JHOEAu9BB0q8A@mail.gmail.com> <8ca59610-2d25-2be4-9d2c-9b1a75fd3ace@si6networks.com> <E67105A3-396B-403C-B741-E9E01CFB5CE7@employees.org> <862687c9-c107-53a8-288a-29049097b0e1@acm.org> <AM5PR0701MB2836C00EA1AAC73E7E63F583E02B0@AM5PR0701MB2836.eurprd07.prod.outlook.com> <CAO42Z2xacRco7ne7biQ93so0k-x4xSnM2jzoB13-sdVRLshQDQ@mail.gmail.com> <CAKD1Yr0Zz6Jxg_ZuEbBkMhBdEaZKOrtx-eUns7KWi9v-5PDBzg@mail.gmail.com> <CAO42Z2xqwRH94dw=XJf5mt3STdDcTYmB_i1NbXP46shdJQeaPA@mail.gmail.com> <FC485644-826F-469A-92B5-45A8F9048F35@employees.org> <ef6666c1-8c14-7b1d-5782-9b0119232d32@gmail.com> <alpine.DEB.2.20.1711140413290.16389@uplift.swm.pp.se> <c95f0a3c-cdc1-0fad-b470-267cba6c25bd@gmail.com> <alpine.DEB.2.20.1711140428510.16389@uplift.swm.pp.se> <6a7622ee-3517-b874-5ab9-80a7bff865ea@gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/w4_BYxF5shGrHEAdqvnm2bYkOa4>
Subject: Re: [v6ops] DHCPv6 PD route injection
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 14 Nov 2017 05:00:14 -0000

On Tue, 14 Nov 2017, Alexandre Petrescu wrote:

> There is a need to send route updates only if there is a Relay.  When 
> there is a Relay the Server has a GUA.

Commonly, but not necessarily, and also irrelevant to the problem at hand.

> This makes wonder whether in cellular networks the PGW needs to do route 
> injection (route updates) during DHCPv6-PD.

It needs to install the delegated prefix into its RIB/FIB. If it needs to 
tell anyone else about it is a different problem, and it depends on the 
setup. If there is a covering larger prefix statically routed to it then 
it doesn't need to tell anyone else. There is no requirement for the PGW 
to use a routing protocol, but nothing in the architecture that precludes 
it from doing so.

PGW is a router, and in this case for PD it can be either a relay or a 
DHCPv6 server, perhaps with a diameter backend. Depends on how you define 
it, is a DHCPv6-PD delegating router asking Diameter what prefix to 
assign, actually a relay or a server? I don't think it matters anyway, it 
ends up the same thing.

Nontheless, there is no fundamentally different about this, to any other 
situation with a PPPoE terminating BNG for instance.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se