Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?

Philip Homburg <> Fri, 27 November 2020 09:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6E5963A157C for <>; Fri, 27 Nov 2020 01:58:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mlukvOWpyCU8 for <>; Fri, 27 Nov 2020 01:58:25 -0800 (PST)
Received: from ( [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 367423A157A for <>; Fri, 27 Nov 2020 01:58:23 -0800 (PST)
Received: from (localhost [::ffff:]) by with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1kiaW6-0000IFC; Fri, 27 Nov 2020 10:58:14 +0100
Message-Id: <>
Subject: Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?
From: Philip Homburg <>
References: <> <>
In-reply-to: Your message of "Thu, 26 Nov 2020 19:32:04 +0100 ." <>
Date: Fri, 27 Nov 2020 10:58:13 +0100
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 27 Nov 2020 09:58:28 -0000

> > DHCPv6 has a very complex model. There can be multiple relays and multiple
> > DHCP servers. So a downstream router first has to collect offers and then
> > select one.
> Its hard to see what you could remove. A RA solution would likely
> have to be implemented with some sort of database backend like
> RADIUS. That something isnt specified, doesnt make it simple.

Radius is an optional feature. Yes, you can use it if for example you have
static prefixes, but you can just as well have a pool of prefixes on the

For SLAAC, a router also needs to know what prefix to use. You could use radius
for that, but I assume that local configuration is more likely.

> > Worse, we have trouble tying a DHCP PD to link state.
> The goal of PD is _not_ to tie it to link state. I would expect
> that goal to be general regardless of wire-representation.

I think this is the key change we should make is to avoid renumbering problems.
The downstream router has to actively verify that the prefix is still valid.

> > RA has the advantage that all information can be in a single RA, ensuring
> > consistency. We can also add mechanisms that the downstream node quickly
> > and reliably notices flash renumbering independent of link state.
> It might be worth noting that  RAs do not guarantee all information
> in a single RA. It can be split across multiple messages or come
> from different sources.

So that is something we should work out. I.e., specify that related information
has to go in a single message. Maybe a bit that says this a point-to-point
link. Maybe a counter to allow the host to verify that all parts have been

> Lets ask the question differently. Would RS/RA be a good protocol
> for address assignment?

RA is widely used for SLAAC. Though SLAAC has a few renumbering issues.

On the other hand, in the mode DHCPv6 PD is commonly used, it is a bad protocol.