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

Michael Sweet <msweet@msweet.org> Wed, 26 November 2025 18:20 UTC

Return-Path: <msweet@msweet.org>
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 0258E913B472; Wed, 26 Nov 2025 10:20:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=msweet.org
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 jX9TK-Pqa-Ig; Wed, 26 Nov 2025 10:20:05 -0800 (PST)
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 9825A913B46C; Wed, 26 Nov 2025 10:20:05 -0800 (PST)
Received: from smtpclient.apple (cbl-66-186-76-47.vianet.ca [66.186.76.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.msweet.org (Postfix) with ESMTPSA id A606980444; Wed, 26 Nov 2025 18:19:58 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.msweet.org A606980444
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=msweet.org; s=default; t=1764181199; bh=84OwECMEOiNKjMDG9OulZohpVH9+8O2Jmf9DTF8PiEk=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=BfXN4E7pWv40iRXSbyJFbkjiULquH/tAMzbYOpIVESo6/TZinPTf5zGhG3I0suGV0 4Xfp2PI1+XZj5zQrS8X0BGW9RWPwReuU502e9n6ll/Vqd72X44rU3YkmEP2MqlOfIu JMFuoqqE6ExbY3jDFltJGiyP40p2JqrI4yURrJqM=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.4\))
From: Michael Sweet <msweet@msweet.org>
In-Reply-To: <CAO42Z2ykz37BOKpxxHVhwGKzQfTCLokbcU7wCg9-SDWoK+ahhg@mail.gmail.com>
Date: Wed, 26 Nov 2025 13:19:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1FCD4A72-65B5-40D4-AEBA-A7EB1CE3FA6F@msweet.org>
References: <CAO42Z2wmCYvqpCGn6LxLW0otHS0kqmS6jGXkXqLtcKhPJn9eMQ@mail.gmail.com> <38F85990-939F-47AA-9A04-24EEC29E4F41@gmail.com> <CAO42Z2ykz37BOKpxxHVhwGKzQfTCLokbcU7wCg9-SDWoK+ahhg@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
X-Mailer: Apple Mail (2.3864.300.41.1.4)
Message-ID-Hash: QQXHNWRQB5RCS45VGHIXAT7FQZW5R6LM
X-Message-ID-Hash: QQXHNWRQB5RCS45VGHIXAT7FQZW5R6LM
X-MailFrom: msweet@msweet.org
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
CC: Ole Trøan <otroan.ietf@gmail.com>, Gert Doering <gert@space.net>, Geoff Huston <gih902@gmail.com>, IPv6 <ipv6@ietf.org>, IPv6 Operations <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [IPv6]Re: [v6ops] New draft: "The IPv6 Loopback Address Prefix"
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/yXIGg9wQRQNXUbjSEtkaswJcg7Y>
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>

Ole,

> On Nov 26, 2025, at 12:52 PM, Mark Smith <markzzzsmith@gmail.com> wrote:
> 
> Hi Ole,
> 
> On Thu, 27 Nov 2025 at 00:18, Ole Trøan <otroan.ietf@gmail.com> wrote:
>> 
>> Mark,
>> 
>> Since the loopback address is of link-local scope you can already do this with multiple loopback interfaces.
>> ::1%loop0
>> ::1%loop1
>> 
> 
> That's interesting.
> 
> One thing I think worth avoiding is having to use loopback addresses
> with zone IDs to minimise the amount of typing since these addresses
> may be commonly typed in manually.

One other thing, and something that has been a sore spot for IoT devices like printers forever, is that relying on using zone/scope IDs doesn't work for services that use URIs.  The old URI WG and somewhat more recently 6man have tried extending URIs to support IPv6 addresses with zone/scope IDs three different ways (mainly for link-local addresses but really for any address whose routing depends on it) and have failed.

There isn't a lot we can do for link-local addresses (there we have to rely on mDNS hostnames), but for loopback addresses things *should* Just Work if every loopback interface has a unique address and not "::1%ZONEID".

________________________
Michael Sweet