[v6ops] public prefixes on loopback

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 04 December 2025 02:38 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 5AEA5950542F for <v6ops@mail2.ietf.org>; Wed, 3 Dec 2025 18:38:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level:
X-Spam-Status: No, score=-2.8 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_LOW=-0.7, 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 AHMCANeMpJxL for <v6ops@mail2.ietf.org>; Wed, 3 Dec 2025 18:38:47 -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 DC7819505427 for <v6ops@ietf.org>; Wed, 3 Dec 2025 18:38:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 3A52D18017 for <v6ops@ietf.org>; Wed, 03 Dec 2025 21:38:42 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id WoQra-pJRclG for <v6ops@ietf.org>; Wed, 3 Dec 2025 21:38:41 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1764815921; bh=eUbFClLZ5aqYyAY09kMQwjXoLJy+vAmF9O1nufyJqnc=; h=From:To:Subject:Date:From; b=iDCv75pYRvMPzPsDCc4zmqImyRb4sfimJiOV8QBtKR2B1Pctg5r5TrheCKxPhXx+y lcM0Ca+FCfy49PYAhJuroXzVCHHHJWdbYX39RRNPBtj/9Kt4O8AfT7PXdrGzSYfZRb tujensWBDloRC+HqCGTOx1SJcN9Ru9XfwbCgfcKCHelZSLXAoCh/7i2sNN2WVw3QjB eI3yNuUGIi8raQm1dnoYqIjNcNnhzvarkDhgsRc2xty6NJbCpXD3pLxyu0ZOSylQmn i44jh+wPKi1NO1tVlBlR5prhalYBKauLXrTc5dwx1cmNMTGy3aXEai4nG/p9Dru9en BOPub8tPcQ0Aw==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 18AB818015 for <v6ops@ietf.org>; Wed, 03 Dec 2025 21:38:41 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 14C101B3 for <v6ops@ietf.org>; Wed, 03 Dec 2025 21:38:41 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: v6ops list <v6ops@ietf.org>
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: Wed, 03 Dec 2025 21:38:41 -0500
Message-ID: <19038.1764815921@obiwan.sandelman.ca>
Message-ID-Hash: LH2HWRNF7N54N2NXNR5Z7YGVZ5VE4H6Q
X-Message-ID-Hash: LH2HWRNF7N54N2NXNR5Z7YGVZ5VE4H6Q
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] public prefixes on loopback
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/f0ehxHiCOh0R33Wp4Dq4H2pSguY>
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>

Owen DeLong <owen=40delong.com@dmarc.ietf.org> wrote:
    > I’m still trying to comprehend a testing scenario that would require
    > this where GUA or ULA wouldn’t be a better choice. Loopback semantics
    > imply addresses that are identical across all machines,
    > quasi-automatically configured, and not routable outside of host
    > scope.

{same mis-comprehension for me too, but:}

    > This is not to be confused with virtual interface semantics
    > (which loopback interfaces iare frequently (ab)used for in IPv4) where
    > a routable address is assigned to non-physical interface to facilitate
    > reachability regardless of which subset of physical interfaces remain
    > up. (e.g. the use of configured routable “loopback” addresses on
    > routers to terminate iBGP sessions).

1. I really wish this practice had a good name, and did not involve the word
   "loop" or "back".  Because of the confusion.

2. The IETF has no really good descriptions of the above practice.
   (Why do *I* even know about it is a question... Like I always knew this?)
   I'm guessing it must be in routing-platform vendor training materials.

Maybe someone has some pointers to good material?
Again, as I said in another email, it would really be nice to be able to cite
this exact operational "pro-tip"

Owen, you write **ab** used in that somewhat cynical way, so you think that
maybe this is sometimes a wrong practice?
One could put the address on a "dummy" interface or other such thing.  Is it really different on any platforms?

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