[IPv6]Re: Call for adoption: draft-kumari-ipv6-loopback-02 (Ends 2026-08-05)

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 21 July 2026 15:25 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 70B5511B828E8 for <ipv6@mail2.ietf.org>; Tue, 21 Jul 2026 08:25:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784647538; bh=WfAamsuTb7eowRcGbsh/bM5vhlI2Yo5AuLGmg5r2dWc=; h=From:To:Subject:In-Reply-To:References:Date; b=SD9YH4DS1b8QD0E00YHHEWvGDTLRIT4jSeekufEbC2+nu60SMTXIXliaBhwgoGBb8 B5dN6s4MqOGinJRFglVErF6CCd7MXY81BPDZN+aJRDv57OekcL+JDJzyYSYVSqyyIC Sfor2vtm4ei3MhKjNgLqyFgtV5selMcPjktwZTXE=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 rJZB2R0AZqAz for <ipv6@mail2.ietf.org>; Tue, 21 Jul 2026 08:25:38 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (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 020D811B828B2 for <ipv6@ietf.org>; Tue, 21 Jul 2026 08:25:30 -0700 (PDT)
Received: from dyas.sandelman.ca (nat64-44.users.meeting.ietf.org [31.130.238.68]) by relay.sandelman.ca (Postfix) with ESMTPS id 438DD1F46E for <ipv6@ietf.org>; Tue, 21 Jul 2026 15:25:29 +0000 (UTC)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 82819A076D for <ipv6@ietf.org>; Tue, 21 Jul 2026 11:25:28 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ipv6@ietf.org
In-Reply-To: <178456714107.192650.13444847527691372817@dt-datatracker-d4d6ff9d9-ql5mb>
References: <178456714107.192650.13444847527691372817@dt-datatracker-d4d6ff9d9-ql5mb>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 29.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 21 Jul 2026 17:25:28 +0200
Message-ID: <1017859.1784647528@dyas>
Message-ID-Hash: WS6WX6KLORFHU6FZIMBRPK3QROM4H5JW
X-Message-ID-Hash: WS6WX6KLORFHU6FZIMBRPK3QROM4H5JW
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: Call for adoption: draft-kumari-ipv6-loopback-02 (Ends 2026-08-05)
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xmDGF4Xv8U5Au5HqHHrZDj6DYlg>
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>

I have read kumari-ipv6-loopback, and I support adoption.
I agree with others that the name should probably be "hostlocal"
(which is akin to 'localhost'...)

I have noticed how v4 (docker!) uses 127.0.1.1, within 127.0.0.0/8,
and I never noticed that all of ::/96 wasn't equally useable.
In practice, I've regularly changed the prefix-length ("netmask") of lo, and
I've run services on ::2, ::3, ::4...

I am not convinced that ::/96, (with ::/128 understood to be cutout), can not
work, but that's a discussion for post-adoption.

The IANA special purpose registry is at
https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml
Generally that means something within: 2001::/23 as per RFC2928, and amended
later on.   2001:db8::/32 (Documentation Prefix) is there.

If this prefix will be within 2001::/23, then let's make sure that:
a) it's easy to type.
b) it's quite visually distinct from 2001:db8:  so that humans seeing it
   for the first time are minimally surprised.

I won't start a beauty contest here on that, I have many ideas.
I would like some variation of the above two points to be included in the
IANA Considerations.

(I'm reminded of: "Why is prisoner.iana.org attacking me?")

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*