[v6ops] Re: [IPv6]Re: New draft: "The IPv6 Loopback Address Prefix"

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 02 December 2025 17:31 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: v6ops@mail2.ietf.org
Delivered-To: v6ops@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D9FBF940470A; Tue, 2 Dec 2025 09:31:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kn62JSD_6z8t; Tue, 2 Dec 2025 09:31:26 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 6A6B094046FE; Tue, 2 Dec 2025 09:31:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 4CD6B38038; Tue, 02 Dec 2025 12:31:25 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id iDdrwA3iYe_K; Tue, 2 Dec 2025 12:31:23 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1764696683; bh=rpk5aVulghOEJPD15aUPEM4mkynKWw+6aiDZTvKX0is=; h=From:To:Subject:In-Reply-To:References:Date:From; b=hsQhbhnsHrXx9yt2T5TttSqUcxNIyZIlVPhkEC2wBgiR2SIDewjzdvhfgv0tkQfGv WxZuBynwe6uGgPjagXOkjaELvzkPPTuIREhxSxYJU3b6zYpsCAuszqiCnoFZ6eN4Sc Xj5Z2MW4e+Gtx5c2Ph9naJ2fRAWk5LSOEUXcMiI5ZUB7NHUxxoROjHe4PRiAhR2AGq ud2Q9KD8S1qmKZgMy0YDPJeq1uRLGUl7a44zdHlLSZew6LNLLHhonv+du7qdaF3lPT ogoEGhIHVHrz/v8OP70+1FOURda+27kR0rqwSoI+/yg/E31ZywDcH4HSjoSawa6qkQ DH6dMVBMsf83Q==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4F3EB38036; Tue, 02 Dec 2025 12:31:23 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 4AA83180; Tue, 02 Dec 2025 12:31:23 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Philipp S. Tiesel" <philipp@tiesel.net>, IPv6 <ipv6@ietf.org>, IPv6 Operations <v6ops@ietf.org>
In-Reply-To: <F09C050D-C8F2-45BB-B9E4-A46E02C192FC@tiesel.net>
References: <CAN-Dau15-hFTaejyHqz2xPTR1+srh6YOpz+rQQB-y_KAEBJS=w@mail.gmail.com> <F09C050D-C8F2-45BB-B9E4-A46E02C192FC@tiesel.net>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 02 Dec 2025 12:31:23 -0500
Message-ID: <21865.1764696683@obiwan.sandelman.ca>
Message-ID-Hash: XW7DG4BR4YUVLU36GHOMTWDKC2VA5XR2
X-Message-ID-Hash: XW7DG4BR4YUVLU36GHOMTWDKC2VA5XR2
X-MailFrom: mcr+ietf@sandelman.ca
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [v6ops] Re: [IPv6]Re: New draft: "The IPv6 Loopback Address Prefix"
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/b7O0rBZ0TYCoYD03y-gg1kuqxMI>
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>

{I haven't read all of the threads}

1. I think that the common practice (even, BCP) situation of putting GUAs on the
   loopback interface in order that they be available regardless of which
   interface is up is a different situation than wanting to put multiple ::1

We actually struggled in RFC8994 to explain the above practice, as it was
not, it seems really documented anywhere. (section 6.11)
This is neither here nor there, I think.

2. Those who want ::2, etc. what it, and not a ULA, because it's a form of
   zero-cost discovery.  You create a local convention, like that the local
   (container) DNS server is at [::53]:53.  ULA won't work, because the
   conventions get burnt into your local tools/containers/etc.

::0/48 is wrong, because it includes many other things.

I don't buy that I need to put a /64 on "each" loopback interface.
At that point any convention around ::53 or something is dead, so do
something else.
The notion of allocating 1::/32 has a smell for me.

I would like ULA-C to be useable at some point.  If this document
wants to take fc00::/48, and can do it without opening the ULA-C debate, then
great.  (Or maybe it can open that debate and finish it)

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide