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

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Wed, 11 November 2020 14:31 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F9A63A0C82 for <ipv6@ietfa.amsl.com>; Wed, 11 Nov 2020 06:31:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.622
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D8cZ0Gng7xlt for <ipv6@ietfa.amsl.com>; Wed, 11 Nov 2020 06:31:11 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [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 ietfa.amsl.com (Postfix) with ESMTPS id 68E3C3A0BAD for <ipv6@ietf.org>; Wed, 11 Nov 2020 06:31:11 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1kcr9K-0000GNC; Wed, 11 Nov 2020 15:31:02 +0100
Message-Id: <m1kcr9K-0000GNC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: Ephemeral addressing [was Re: 64share v2]
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <CAD6AjGR-NE_sJ_jp7nAT6OvNkcdE9qoWuGEiiVW7r9YtsQvbbw@mail.gmail.com> <CAKD1Yr0G8PjzE+pULte_AaOi=RHMLyto-YUQerGjQ=iOYnz+iA@mail.gmail.com> <0986B112-2159-4045-87F9-876B58F1D896@employees.org> <CAKD1Yr0h9=7p+n=qnH1o1EHqtPrsaYebgvHciOJpP3=iXgNgKQ@mail.gmail.com> <0C739112-D8EA-42C3-BEFD-88C014D5BCD0@employees.org> <62bc0e56-85b8-42ea-c46b-4f2205dc435f@joelhalpern.com> <28C2E56B-1443-480A-B3D1-82E0F8CC0EC7@employees.org> <aabd41ad-1770-f2ac-77d6-62bfff1992c0@joelhalpern.com> <CC7C2B94-5A05-4682-8367-9072CC201C49@employees.org> <80ed3a3b-6e2c-188f-4c1e-c2ededfbbe0d@joelhalpern.com> <0188AC41-60B0-4BC6-810D-DC59CF9E4FB3@employees.org> <1931a638-64ed-f40e-07a3-67cf1eafb941@joelhalpern.com> <376D6BB0-87E2-42E5-9BC4-F3A2F04FA005@employees.org> <CAD6AjGSr-TPcGo7f9EGgoAahYLQTL68CUSq58LGMgD0=6GmRRg@mail.gmail.com> <8DC674FB-9F90-4C41-A323-62BD62934A12@employees.org> <CAD6AjGTYBs8YbHgCJJG84vgwXK4ZSCm65z6KXvZP9F+LdT_atg@mail.gmail.com> <038A830C-E024-42C6-917E-E6FF57829A1C@employees.or g> <CAD6AjGTQVtJBJ3=aZBsF1WcdSK2k9b1hzeZXM6008w_2vpo6_w@mail.gmail.com> <948ACA2B-E45C-4289-A837-9F2536F20F8F@employees.org> <CAKD1Yr0tDTSH2F4=ZsdMJREy1k6equ9mZV0Au1bJPmKuzxeYVA@mail.gmail.com> <43C449AD-D116-4452-A4F2-79AE5A76539F@employees.org> <m1kcoXQ-0000G1C@stereo.hq.phicoh.net> <267D8461-47EC-443A-98DF-4FE990138B5A@employees.org> <m1kcprv-0000GNC@stereo.hq.phicoh.net> <F39272F7-EBCC-4551-BB42-4014DD437302@employees.org>
In-reply-to: Your message of "Wed, 11 Nov 2020 14:35:39 +0100 ." <F39272F7-EBCC-4551-BB42-4014DD437302@employees.org>
Date: Wed, 11 Nov 2020 15:31:01 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/F7Kp9SA4uZcDMCz3EWdO7xnKPSM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2020 14:31:13 -0000

> Seems to me the world waited. At least the one I'm leaving in did.
> :-) None of the systems I use handle renumbering. Barring a single
> application (mosh).  Most of the building blocks are there, but in
> 20 years of waiting few if any have put them together.  I doubt
> this is deployable in time to avoid users being forced to NAT on
> the edge, to protect themselves from instability in global addressing.
> 
> Are we going to restrict all future IPv6 end-user networks that
> are forced to depend on PA addressing to be client only?

Anything web handles renumbering.

With a bit of scripting you can have a persistent ssh session: restart a new
ssh when the old one fail. Run 'tmux att' on the server side.

Anything running phones handles renumbering, phones constantly switch between
mobile and wifi. 

There are probably a lot more applications that are meant to run on laptops
that can automatically switch to new addresses.