[IPv6]Re: Why not add loopback semantics to 2001:db8::/32?
Michael Richardson <mcr+ietf@sandelman.ca> Tue, 02 December 2025 17:54 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipv6@mail2.ietf.org
Delivered-To: ipv6@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 35BEC940A930; Tue, 2 Dec 2025 09:54:06 -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 U2_NIV0KskcA; Tue, 2 Dec 2025 09:54:05 -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)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D24D3940A928; Tue, 2 Dec 2025 09:54:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 3151638039; Tue, 02 Dec 2025 12:54:05 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id VcHQU-ry3fic; Tue, 2 Dec 2025 12:54:04 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1764698044; bh=/BMXEIfh8nAUEED95YHKOMrlK1yPqxjWjjtjg9WRcIk=; h=From:To:Subject:In-Reply-To:References:Date:From; b=u5XZvGtvCuM9meNfilP98nJ9jBi6eRLYUM+l0ovW2P2nGVoT7wZtEqBnPdfxWDCG0 SlqX6UTSBViZTjJVbfgc19BWt4sh0iZdecUmisfkTi7cFPsWqDbU6ICQcipnJB+xwm o38eWG02gpoExHqpNG7AmSW0L2PURCHdmvonqYGtEic/pJAXNmpEbg6fYmEZuO4sXq QhyQDYoyGvwsBX/0SDk+Q7XDmjEHDKlHWUsCO3Fd+7CmkPp2zlW+buiKyQOwG1A/lT c9dlqIfb79paIQxF+dZjjyZ1sDiZBTDWVcRDuIEhP415Y+aiQTQF9xXR/Au9SgiPsB gJe5u0ZV8ASTg==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4750F38038; Tue, 02 Dec 2025 12:54:04 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 434DF180; Tue, 02 Dec 2025 12:54:04 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mark Smith <markzzzsmith@gmail.com>, 6man WG <ipv6@ietf.org>, v6ops list <v6ops@ietf.org>
In-Reply-To: <CAO42Z2wRTfcKkoG8z_5JZM0FMpWimkni9-uR6RToTeFD8P-HPg@mail.gmail.com>
References: <CAO42Z2wRTfcKkoG8z_5JZM0FMpWimkni9-uR6RToTeFD8P-HPg@mail.gmail.com>
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:54:04 -0500
Message-ID: <29754.1764698044@obiwan.sandelman.ca>
Message-ID-Hash: NOPOAQV3RC5H7BSL5GBQO7DM4PPJMXLS
X-Message-ID-Hash: NOPOAQV3RC5H7BSL5GBQO7DM4PPJMXLS
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.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: [IPv6]Re: Why not add loopback semantics to 2001:db8::/32?
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/e9Qf9kthFK4vtI9fdCeZHbwd_wE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>
Mark Smith <markzzzsmith@gmail.com> wrote:
> If a /96 ended up being the choice, then I've thought I'd use
> 2001:db8::/32 for any host-local loopback testing, since it too would
> satisfy the scenarios that 1::/32 would.
No, that would be confusing.
A useful sanity check on junior administrators is that they didn't use
2001:db8: anywhere.
If they did it means that they didn't understand the example.
(or their LLM didn't)
If we use it here, then we'll have an exception to that rule.
--
Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
- [IPv6]Why not add loopback semantics to 2001:db8:… Mark Smith
- [IPv6]Re: Why not add loopback semantics to 2001:… Michael Richardson
- [IPv6]Re: Why not add loopback semantics to 2001:… Brian E Carpenter
- [IPv6]Re: Why not add loopback semantics to 2001:… Templin (US), Fred L
- [IPv6]Re: Why not add loopback semantics to 2001:… Brian E Carpenter
- [IPv6]Re: Why not add loopback semantics to 2001:… David Farmer
- [IPv6]Re: [v6ops] Re: Why not add loopback semant… Nick Buraglio
- [IPv6]Re: [v6ops] Why not add loopback semantics … Owen DeLong
- [IPv6]Re: [v6ops] Why not add loopback semantics … Mark Smith
- [IPv6]Re: [v6ops] Re: Why not add loopback semant… Daryll Swer