Re: Ephemeral addressing [was Re: 64share v2]

Philip Homburg <> Wed, 11 November 2020 13:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EAECD3A10D2 for <>; Wed, 11 Nov 2020 05:09:08 -0800 (PST)
X-Quarantine-ID: <JZazjD0jMXbY>
X-Virus-Scanned: amavisd-new at
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -1.622
X-Spam-Status: No, score=-1.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.276, 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 JZazjD0jMXbY for <>; Wed, 11 Nov 2020 05:09:07 -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 36F5B3A0A47 for <>; Wed, 11 Nov 2020 05:09:07 -0800 (PST)
Received: from (localhost [::ffff:]) by with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1kcprv-0000GNC; Wed, 11 Nov 2020 14:08:59 +0100
Message-Id: <>
Subject: Re: Ephemeral addressing [was Re: 64share v2]
From: Philip Homburg <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <038A830C-E024-42C6-917E-E6FF57829A1C@employees.or g> <> <> <> <> <> <>
In-reply-to: Your message of "Wed, 11 Nov 2020 13:03:16 +0100 ." <>
Date: Wed, 11 Nov 2020 14:08:58 +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: Wed, 11 Nov 2020 13:09:09 -0000

> Let me rename this thread as this opens a much larger issue.  While
> being able to rapidly reconfigure an end-user network using the
> layer3 primitives in 6man, I don't think it's worth solving unless
> also the upper layer problems are solved.  
> - How do TCP connections
> survive a renumbering event?
> - How do applications get notified to
> reconnect?
>- Do all applications have to change as a result? Or
> use a different transport layer?
> - What happens with DNS configuration?
> Are you assuming everyone has DNS-SD deployed and working?
> - What
> about other configuration? Static addresses for example?
> Good luck I say...  Until then I suggest that we continue (to
> pretend) that addresses must be long-lived.

My reality is that many addresses are short lived. Not because addresses
on a single link change often, but because mobile devices regularly connect
to new links.

Static addresses are similar to old unix systems where you have recompile
the kernel and reboot for each new piece of hardware that gets added to a
system. Modern systems were forced to evolve because users expect to 
plug in USB devices, connect bluetooth devices, etc.

Does the world wait until the IETF solves renumbering? No. Just like the
world switched to NAT long before the IETF recognized there was such a
thing, most modern application deployments are essentially an overlay

Applications use https to connect to the cloud, session identifiers are 
stored in cookies. Short sessions and short timeouts make renumber event
transparent to the application.

Can TCP survive a renumber event? Yes, MPTCP should be able to that.

How do applications get notified. The IETF and the Open Group failed to 
create APIs for that. So every OS creates its own ad-hoc mechanisms.

DNS support dynamic updates.

But what we do at the transport layer may not be relevant. So we can focus
on making the network layer work. 

Or just stick to static prefixes.