[v6ops] Re: Dynamic addresses
Daryll Swer <contact@daryllswer.com> Wed, 14 August 2024 15:30 UTC
Return-Path: <contact@daryllswer.com>
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 26890C14F60B for <v6ops@ietfa.amsl.com>; Wed, 14 Aug 2024 08:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, 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=daryllswer.com
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 mbYzxjQe0jJh for <v6ops@ietfa.amsl.com>; Wed, 14 Aug 2024 08:30:46 -0700 (PDT)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CBCEC14F5E7 for <v6ops@ietf.org>; Wed, 14 Aug 2024 08:30:44 -0700 (PDT)
Received: by mail-pl1-x631.google.com with SMTP id d9443c01a7336-201d5af11a4so9290335ad.3 for <v6ops@ietf.org>; Wed, 14 Aug 2024 08:30:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=daryllswer.com; s=google; t=1723649443; x=1724254243; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DgRMtI7RhImcAEnwjTAwzBtUNCyUNHyB8EfpVfZGuqo=; b=jCNkpqu7hFabnDTykEh18+fOO7TCAGRDBkscx3bOJQy9LGk2QEXf/oKw94fWlfnr+y G7h9avUXLqk0x1YWvhNXzOe14jVNiz3wIjodO8aaTo9zKlzqlQpHvo/u6nMMdnEQbLTW RVip3KkNv0Bff+l7gug/qrXDKAZhFGL126/t8jnH0YYbjoeJnfma0+EcHPPKS6Y4YJ7L nYx9N8X6DQobhuj7J0eIE4+yKkt5cAt4jXUvQDNYV6TXCOqxlj7x5kh4UPtcgThQZylj xHO8Piww1Xu0K8SkjR/vUesAhJbIDtIMlreesN2OZ2kHvF29EP2IcOVrBPJ3YDN1IB8a etzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723649443; x=1724254243; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DgRMtI7RhImcAEnwjTAwzBtUNCyUNHyB8EfpVfZGuqo=; b=C56LzHJA7JdkRErAnXFZ+1rTO6H+nI50IVggjw4GQgxYdGYIr2LnoDISt9L5WchaNP AhWs82suZ8uWTJ8xRwzWmSMEiDhJa23IVJfRoVhI9rhXOYby+ghAfEKEYeeUNe3Z6FIG zzXlQ9slh0U9UyyF32goiALuhpPmr27big8gtMZr9qtSDzYRtlDxB53BBKZOG35rS00Y OLTfJuvbLIIjOTJCS09XJvfURwhdB1lYre00qEwLwu/vMSYh5XTMd19BIwhMMBq6cymJ 6tDV6KLn/0r8bSZ1cGPPzY9YotcA2Bx5LghaKNl6QfSqSZ6ZYRUCOSkbSmE+94JOANRW pQng==
X-Forwarded-Encrypted: i=1; AJvYcCXS4a54BtDTWeqQ+2uoMAmUmbLQ0lX752xA0pTgNVqkwCq3g5iefclkQ18EzbtmSoaqL/KGPlgcoS72TOAH+Q==
X-Gm-Message-State: AOJu0YzJrf3pCamGY7LkOor/GhbtEx61DAo95VX2zxtEuUVkrziYT1fV pAseA0RPa6Xa/9wxYz4mGk4wd0rE1yvUNFmAnJfxu7tq73i85ovSFNYmr9FSYjSO8PHxenYGYY5 Y+Gg=
X-Google-Smtp-Source: AGHT+IEuGgqtp66oGMFX8MWEwDVNnRm5WTjQ57d2Cc1chw4tPG2xbnhpPVWdGTLBGK7L81MkpgD3SQ==
X-Received: by 2002:a17:903:40cb:b0:1fc:5820:8940 with SMTP id d9443c01a7336-201d63b4d2cmr34184275ad.20.1723649443010; Wed, 14 Aug 2024 08:30:43 -0700 (PDT)
Received: from mail-pj1-f49.google.com (mail-pj1-f49.google.com. [209.85.216.49]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-201cd1c9b92sm30833255ad.277.2024.08.14.08.30.42 for <v6ops@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 14 Aug 2024 08:30:42 -0700 (PDT)
Received: by mail-pj1-f49.google.com with SMTP id 98e67ed59e1d1-2d1ecfe88d7so3916518a91.3 for <v6ops@ietf.org>; Wed, 14 Aug 2024 08:30:42 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCXFuxoS2V/TevPcvsQkWawZWFjq193BNkKipPD/xLaFBeWsMFXT4L58s0Q7lnqEXe/iKcqw1uVd76gqeyezdQ==
X-Received: by 2002:a17:90a:3dc1:b0:2cf:28c1:4cc2 with SMTP id 98e67ed59e1d1-2d3aaa7aae5mr4078548a91.3.1723649442245; Wed, 14 Aug 2024 08:30:42 -0700 (PDT)
MIME-Version: 1.0
References: <d16406c6-e5d9-4aa4-a16e-7513d04d6b07@gmail.com> <DB9PR07MB777164E663505AA86537EB1DD6852@DB9PR07MB7771.eurprd07.prod.outlook.com> <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> <CACyFTPHNiyVJOu695sP+o6PBBeWmggRag-hvzZ6A1XH4LMgfLw@mail.gmail.com> <CAN-Dau23h-ohjVSMWy3X58aufe2Sk2UwZCXbOqq-70EtiAThGQ@mail.gmail.com>
In-Reply-To: <CAN-Dau23h-ohjVSMWy3X58aufe2Sk2UwZCXbOqq-70EtiAThGQ@mail.gmail.com>
From: Daryll Swer <contact@daryllswer.com>
Date: Wed, 14 Aug 2024 21:00:06 +0530
X-Gmail-Original-Message-ID: <CACyFTPGav6XDnSJoB98EjE-bmm3o3jnUfTz9zZUvwKum_Mjfsg@mail.gmail.com>
Message-ID: <CACyFTPGav6XDnSJoB98EjE-bmm3o3jnUfTz9zZUvwKum_Mjfsg@mail.gmail.com>
To: David Farmer <farmer=40umn.edu@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b8fdcb061fa668c2"
Message-ID-Hash: DCCGLM4TTVYCI4XZD2HHKL3N5JK4JK42
X-Message-ID-Hash: DCCGLM4TTVYCI4XZD2HHKL3N5JK4JK42
X-MailFrom: contact@daryllswer.com
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: "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/NEppuvBkRheFMH6jxgJJu9CDGqM>
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>
David All addresses are dynamic; they will change. It is a question of over what > period and of whom or what triggers that change. Or, looking at it from > another angle, addresses are never permanent; they will eventually change. > I mean, you aren't wrong here. Of course. The point is, changing every few hours/day makes no sense. This is the key point you highlighted: > paying someone to prevent a disruption intentionally caused by them is > considered extortion. But still, “change” for static v4 addresses is rare, typically, when you pay a residential broadband provider for a v4 static, it stays static for years (10+ years even) no problem. But yet, with abundance of IPv6, I can barely get it to stay static for 5 hours on MOST residential ISPs. Very few ISPs are BCOP-690 compliant. mDNS provides more than just the link-local addresses. Various DNS-SD > proxies enable mDNS to operate beyond a single link. As far as I know, they achieve this with non-RFC compliant behaviour (Cisco Meraki has a similar approach, as well IIRC), but I could be wrong. Inter-VLAN mDNS is an issue that I actually wanted to look into, perhaps, we can discuss this off-channel, if you are interested David. *--* Best Regards Daryll Swer Website: daryllswer.com <https://mailtrack.io/l/7d56da72f88c56d06e02d2206c5d463dbb035e01?url=https%3A%2F%2Fwww.daryllswer.com&u=2153471&signature=feef939ce7f3a16e> On Wed, 14 Aug 2024 at 19:52, David Farmer <farmer=40umn.edu@dmarc.ietf.org> wrote: > > > On Wed, Aug 14, 2024 at 04:53 Daryll Swer <contact= > 40daryllswer.com@dmarc.ietf.org> wrote: > >> Gert Doering >> >> There some good arguments for dynamic prefixes >>> >> No there isn't. >> > > All addresses are dynamic; they will change. It is a question of over what > period and of whom or what triggers that change. Or, looking at it from > another angle, addresses are never permanent; they will eventually change. > > people should stop putting explicit IPv6 addresses into places (which will >>> inevitably cause headaches when changing ISP) >> >> NPTv6 to the rescue for non-renumbering across static ISP PDs that >> changes when ISP *itself* is changed (rather than prefix within the same >> ISP). I'm pretty confident people do not change ISPs per 6 hours or per 24 >> hours etc, as is the case with the lease time on the dynamic prefixes to >> begin with. >> > > Yes, reasonable periods of stability are necessary for both addresses and > prefixes. All changes should be coordinated with the users or scheduled to > occur when they cause as little disruption as possible. > > So actually having better support for automatic DNS registration/discovery >>> (mDNS and friends) and just making SoHo networks renumber automatically and >>> properly is a worthwile goal. >> >> >> Not sure what you mean, mDNS and friends, does not care about changing >> GUA or ULA prefixes, it operates on link-local addressing and does not work >> inter-VLAN anyway (without hacking using mDNS Repeaters/Proxies because >> link-local) — maybe I missed something here. >> > > mDNS provides more than just the link-local addresses. Various DNS-SD > proxies enable mDNS to operate beyond a single link. > > I do agree that those 0.001% of people that SSH into their home >>> servers will hate SSHs dying on a renumbering event >> >> >> Are you a gamer, Gert? Because many end-users are (myself included), and >> if the games they play use IPv6 and works P2P native (we intend to have >> IPv6 for every layer 7 application, I hope), RIP (literally) to the player, >> when the genius ISPs flip the prefix on a live-session — same impact as the >> SSH example. >> >> Do we really need to create a list of everyday applications (beyond the >> so called 0.001% SSH users) that'd be impacted by >> dynamic/ever-changing 24/7 prefixes? I'm sure you got the point. >> > > Again, addresses and prefixes are not permanent; they inevitably change > for one reason or another. They should not be changed haphazardly or too > frequently, and these modifications should occur smoothly, aiming to > minimize disruption, usually with some overlap between the old and new > addresses or prefixes. > > However, the idea that addresses should not change is IPv4-centric > thinking. IPv6 was architected with the idea that addresses are meant to be > changed with minimal disruption. What is unacceptable is ISPs deliberately > disrupting addresses or prefixes to differentiate service tiers; paying > someone to prevent a disruption intentionally caused by them is considered > extortion. > > Thanks >
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 The Multach's
- [v6ops] Re: Dynamic addresses Jatin
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 Timothy Winters
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 The Multach's
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 Timothy Winters
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 Daryll Swer
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 Ted Lemon
- [v6ops] Dynamic addresses Brian E Carpenter
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Brian E Carpenter
- [v6ops] Re: Dynamic addresses The Multach's
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Ted Lemon
- [v6ops] Re: Dynamic addresses Marco Moock
- [v6ops] Re: Dynamic addresses Ted Lemon
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Ted Lemon
- [v6ops] Re: Dynamic addresses Gert Doering
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses David Farmer
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses David Farmer
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Brian E Carpenter
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Brian Candler
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Brian Candler
- [v6ops] Re: Dynamic addresses David Farmer
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Tim Chown
- [v6ops] Re: Dynamic addresses Gert Doering
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Gert Doering
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Erik Auerswald
- [v6ops] Re: Dynamic addresses George Michaelson
- [v6ops] Re: v6ops Digest, Vol 168, Issue 29 Daryll Swer
- [v6ops] Re: Dynamic addresses N.Leymann
- [v6ops] Re: Dynamic addresses Marco Moock
- [v6ops] Re: Dynamic addresses Brian E Carpenter
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Marco Moock
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Marco Moock
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Tim Chown
- [v6ops] Re: Dynamic addresses Gert Doering
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses David Farmer
- [v6ops] Re: Dynamic addresses Marco Moock
- [v6ops] Re: Dynamic addresses David Farmer
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses N.Leymann
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Gert Doering
- [v6ops] Re: Dynamic addresses Brian E Carpenter
- [v6ops] Re: Dynamic addresses Daryll Swer
- [v6ops] Re: Dynamic addresses Ted Lemon
- [v6ops] Re: Dynamic addresses David Farmer