[v6ops] Re: Dynamic addresses

Gert Doering <gert@space.net> Wed, 14 August 2024 20:58 UTC

Return-Path: <gert@space.net>
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 30456C14F6A1 for <v6ops@ietfa.amsl.com>; Wed, 14 Aug 2024 13:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=space.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4UYsDhwgM54 for <v6ops@ietfa.amsl.com>; Wed, 14 Aug 2024 13:58:07 -0700 (PDT)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA5DAC14F614 for <v6ops@ietf.org>; Wed, 14 Aug 2024 13:58:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1723669087; x=1755205087; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=0E8vLLl+oJK+EyC+VYV+LkazcGEMtG2tMLK/N3mafVI=; b=PvhlJmLfOGXKFw+SR4M9G1nlOBHXDk2RfmXos3/7qlrZazzMh7EwSkQv TlwsAFKUjTg/TbVQoKI2AogDTcSeXK5sisZtdT8oGacFPxhxcJtIWOY9R k4kZHlobyLWSfgmR5rRjl8y2IyIcGmZymYdtRgYMdz8Uu7UeLg9jdxXUN YqU7mnRhWfqk0z/FcAJi++OTW1tp5RnF9ACawGHpL4TicPGALuJQ+MsVl EaUagoxj3I7fPoPKPQAqQIBR/wAJxBiaihMSVem5+hQMlxG/MYGBKrS6K g6uzYUpuJUeuug4c+hZcprnJwp0SSIEdr/cyTO9YDCOWi4RbS9cei1cAj Q==;
X-CSE-ConnectionGUID: Wyb0kzbeSMKffY4NLmaEPA==
X-CSE-MsgGUID: LYK+8L7OTAG8nZ/1mL/35Q==
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Aug 2024 22:58:03 +0200
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 0C87A1803686 for <v6ops@ietf.org>; Wed, 14 Aug 2024 22:58:03 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id E15F0180D79A; Wed, 14 Aug 2024 22:58:02 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id D54AC3C790; Wed, 14 Aug 2024 22:58:02 +0200 (CEST)
Date: Wed, 14 Aug 2024 22:58:02 +0200
From: Gert Doering <gert@space.net>
To: George Michaelson <ggm@algebras.org>
Message-ID: <Zr0aWhkGBBxiQA4k@Space.Net>
References: <20240812142831.22a4f28e@zbook> <DB9PR07MB7771D93917C01A028E30FDEED6852@DB9PR07MB7771.eurprd07.prod.outlook.com> <0d0f35a3-1493-4e4e-8b4a-08f41fac2b2c@gmail.com> <CACyFTPFPRrW5MxZ8yoNPKYWxzaGQO-HnMNpEKR3TCbVpK6hgWg@mail.gmail.com> <20240813065439.061ef59a@zbook> <CACyFTPH+dA9xkCUT98zHr7AYpGyYFuOgOaynhsPjz3iKEuseog@mail.gmail.com> <20240813171637.48ce7cfe@zbook> <CACyFTPGgJsjLtoTegqy34BCSVH+vp_oxbKvBj3vnLaXpiD-vGA@mail.gmail.com> <Zrx7N9IWGeDqIuPf@Space.Net> <CAKr6gn0MYNr+jhjNvnBS6Tv8bi+U_LMN+ynE1Nnp0Qj_cO61kg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="LWecoRQRg/PK5lPc"
Content-Disposition: inline
In-Reply-To: <CAKr6gn0MYNr+jhjNvnBS6Tv8bi+U_LMN+ynE1Nnp0Qj_cO61kg@mail.gmail.com>
Message-ID-Hash: 66LV63KB2NXY72QIQUW5RFGSHOU6SHN2
X-Message-ID-Hash: 66LV63KB2NXY72QIQUW5RFGSHOU6SHN2
X-MailFrom: gert@space.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Daryll Swer <contact=40daryllswer.com@dmarc.ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] Re: Dynamic addresses
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/fVrPP3XmXiwW5t7kru65oYIMk90>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>

Hi,

On Thu, Aug 15, 2024 at 06:19:58AM +1000, George Michaelson wrote:
> Surely before arguing for constant renumbering you should explain
> remediation for the downsides of constant renumbering?
[..]
> Normally I find I agree easily with what you say. I think you are hand
> waving consequences on your own experience with stable addresses as a norm.
> If you have active solutions and live behind a dynamically addressed sub
> prefix of some other delegate it would be useful to share how you make
> inbound ssh work reliably.

I do have a static v6 network at home, which has been static for 
roughly 23 years - so I see the consequences of assuming "addresses
are static", like "addresses are being put into config files all
over the world".  Should I ever cease working for this very ISP, it
will take me months to get my network back into a working shape...

Thus, not assuming stable addresses, and ensuring software copes better
with change, and more automatic, will cause less pain in the long run.

Now, of course I ssh home - from a few bastion hosts, because firewalling,
and I do not expose my home network to "the world".  Making the DNS
involved more dynamic would certainly be doable, but I am lazy.

But, what you and I do, with SSH, is really of no relevance for the 
Internet at large.  99.99% of the end users out there do not know 
what SSH is, or why they would want a stable address - they use devices
that seamlessly roam between wifi and LTE networks, keeping "connections"
active, and all that - whether it's MPTCP underneath, some sort of
VPN that can handle roaming endpoints, or just very short HTTP sessions,
why would they care?  "Spotify keeps streaming when I leave home",
this is a relevant metric.

(This is part of the larger discussion about IPv6 PI, of course, and
why it does not make sense to give every barbershop wifi a PI /48,
visible in global routing - because it does not work, and is not 
*needed* either)


... I do have customer networks that are connected to other ISPs, with
dynamic and semi-static /56s, and I use an Android phone as LTE hotspot
with always-changing /64 on the wifi, so I *do* see where it hurts, 
and where it doesn't.   My Mac Laptop assigning itself a new privacy
address when it roams between "living room" and "office space" wifi
APs - because they have different SSIDs and it assumes "different network,
then" - *this* is breaking my SSH sessions many times a day.  Which is
annoying, because I have to press the hotkey for "please restore my SSH
sessions to the standard set of hosts and reattach screens there"...

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Ingo Lalla,
                                           Karin Schuler, Sebastian Cler
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279