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

Philip Homburg <> Mon, 30 November 2020 15:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1922E3A0E9E for <>; Mon, 30 Nov 2020 07:54:29 -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 fMBjpax0eWBR for <>; Mon, 30 Nov 2020 07:54:27 -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 C42433A0E8C for <>; Mon, 30 Nov 2020 07:54:26 -0800 (PST)
Received: from (localhost [::ffff:]) by with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1kjlVK-0000K4C; Mon, 30 Nov 2020 16:54:18 +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 "Mon, 30 Nov 2020 15:37:29 +0100 ." <>
Date: Mon, 30 Nov 2020 16:54:16 +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: Mon, 30 Nov 2020 15:54:37 -0000

> Right, so can you know describe how the network, hosts and applications
> are supposed to deal with flash renumbering? Including servers in
> that network.
> Specification, implementation and deployment status?
> I'm drilling down on this to see if we can get a common understanding
> of what the IETF gaps are, and what the implementation and deployment
> gaps are.  (Not making any assumption that the IETF would ever
> recommend an ephemeral addressing model of course.)

- DHCPv6 PD: there is a little bit, I think DOCSIS requires the CPE to poll
  the upstream router
- I still plan to read the HNCP spec one day, but I assume it has support for
  with drawing prefixes and annoucing new ones. 
- We can assume that routers get the new prefix from HNCP and use RA to
  renumber hosts.

- hosts get a new SLAAC prefix using RA, the old SLAAC prefix will be marked
- DHCPv6 has a way to inform hosts, but it doesn't seem widely implemented.

- applications have to use short flows and detect broken connections. Many
  applications can do that, but certainly not all
- for applications that use TCP and want to keep the connection, we could use
- QUIC will be seen as a path forward 

- by and large servers don't have to anything special. Servers just receive
  requests, it doesn't matter to the server what address is used to reach the
- For a service, we probably need to update directory information:
  - DNS has an update mechanism. A daemon on the host could detect address
    changes and update. There doesn't seem to be a standard notification
    mechanism at the operating system level. 
  - Torrents use DHTs. This would require OS specific code to detect the 
    change and then the torrent process can update the DHT.