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

Mark Smith <markzzzsmith@gmail.com> Tue, 25 November 2025 23:17 UTC

Return-Path: <markzzzsmith@gmail.com>
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 ABE68909A7D8 for <ipv6@mail2.ietf.org>; Tue, 25 Nov 2025 15:17:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level:
X-Spam-Status: No, score=-0.599 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, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HF1n-F52VoHj for <ipv6@mail2.ietf.org>; Tue, 25 Nov 2025 15:17:43 -0800 (PST)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A9906909A6CE for <ipv6@ietf.org>; Tue, 25 Nov 2025 15:17:00 -0800 (PST)
Received: by mail-pg1-x52f.google.com with SMTP id 41be03b00d2f7-bc274b8ab7dso4380577a12.3 for <ipv6@ietf.org>; Tue, 25 Nov 2025 15:17:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764112620; x=1764717420; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=hCdY9nxyM1hwbA4cDEo1HzjRy9FmH987J31yt6k0CzI=; b=gnu8gZmkOF2YPelKALsQ4xEtcogDisMKSZyPweWWJYiR/aYLvvyPkpSn+9mXEjQ79o XADFN/YNKLJku1v6aE1DNkeCkR6PN4CkaAzytUS4v4sHcaGMseWNvtNzjskTBNONe4Dj 9/+uSr/Nlp5A3j+RuDk70ILIvPJi9XKC+xTaKuNTrKZoBj4lnEwubt88ZF6LWBagLxJw n2heliaHAD3W1ycWTpPlG31jkAjR4megHv2up6qptMTq5bjOJX2IxHEMqA8RncRAtwFK hmQSzkgeM2HeANsjOsFRWxtPhQXhzJVEGJbJ4FWsfrwucydq1yS0mk9l7TZUrQ7HTVSX rwcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764112620; x=1764717420; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=hCdY9nxyM1hwbA4cDEo1HzjRy9FmH987J31yt6k0CzI=; b=kyhQubMTCx733BcqR2HicvSy1tnixAL3RkBNtgfPrqhXsZq1yR1AZFJcYCJRbP2CU8 ohNSQda6ru//dg08etsiS7jY+kIqavUHNesft3iY5QXchkTQzvWClD9nnsvbgPzegWG2 cAlN5ccx2R8tebk4hRF31cLlMs5rkc5acOjKJPS2tzLOWmZVToeg4dDLR/FKOgbMDiQJ EyDDnM+qiMA7fze3By95pIUyGCWf81S8bCZB3THqdMGMYwknzGtxEM2VC+BiGUooLkny pkhY3EESscUmKG+ormsP8RcH9ltDaTiiBs38zzxUSZHwldqxJFUJaZFyoCVcwvQcwG9+ 3Q8w==
X-Gm-Message-State: AOJu0YyEW5jCaO4ZGMhD6NYqPugAJNoJd5fxMHuVKOa2jZPTon/tM31P FklsNPM8H0ltsFDUVfhDz+eidu8wrk4Z7+OV3tYyocTkM2/fQZ7o6NDYcTcV5to/BgIVxqLRH/h 6vlF+DQYX7VcDfi8C5xfHa4t8eqbe3YI=
X-Gm-Gg: ASbGncvPo8yrqrqa+yrkzl0DXwI74r/2VEmwXvpwCiHTOqF42y9vK48U+484dpTshLU DBVWaOlnv8hI4/VadI7n8D6F+3YZTuX8cryD4GtejxRJZDuazaqMrkGa00TEDndl3CtpBddmakI Di+NVKqYIUVr6aSvg0LpO5RMWQ/Prn1lPZdM1X6B7PkKpVqBE9fklNhHkJqKxKxT8SP3yi4Uwxn zmdFVWbSsxBjSFOYKClGZ5UcUAxTw4IKq8Su182uGKkZ6a3FJ/SxDcjgQY/U8de3OJQp70=
X-Google-Smtp-Source: AGHT+IFwMVePUU+YdWnIt00QGWJgeLe/gq0smkOiToncECa6kj8hS/e5lc9L1JV+wpTWQa0eFQLwjej7xBxoiRpKf+4=
X-Received: by 2002:a05:7022:923:b0:119:e56c:18a6 with SMTP id a92af1059eb24-11c9d712787mr10776217c88.14.1764112619495; Tue, 25 Nov 2025 15:16:59 -0800 (PST)
MIME-Version: 1.0
References: <CAHw9_i+b=uZozstCAm1Kr52Pj-_Y_aCndHc0e703rMUr9va=iA@mail.gmail.com>
In-Reply-To: <CAHw9_i+b=uZozstCAm1Kr52Pj-_Y_aCndHc0e703rMUr9va=iA@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 26 Nov 2025 10:16:33 +1100
X-Gm-Features: AWmQ_blBmTx4K_mHJIh3n2W1OgFYawJyOLLl0Ys8J8380VhIOaBe9WF0aZOzBEg
Message-ID: <CAO42Z2xsGuZ+5V8SadxRRkeeL7owm35F9MO8owAcWwfi9Q6nFw@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: Y46YTVRHC2N6TFLDOB7A7Q3SUTMJJWZ4
X-Message-ID-Hash: Y46YTVRHC2N6TFLDOB7A7Q3SUTMJJWZ4
X-MailFrom: markzzzsmith@gmail.com
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: IPv6 <ipv6@ietf.org>, IPv6 Operations <v6ops@ietf.org>, Geoff Huston <gih902@gmail.com>
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/Iq3JzA8bLuCgVw9Gc3DUhRXtnjY>
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>

Hello,

On Wed, 26 Nov 2025 at 04:40, Warren Kumari <warren@kumari.net> wrote:
>
> Dear 6MAN and V6OPS,
>
> Geoff Huston and I have just submitted draft-kumari-ipv6-loopback - "The IPv6 Loopback Address Prefix"
>
> We believe that it is within the 6MAN charter ("The 6man working group is responsible for the maintenance, upkeep, and advancement of the IPv6 protocol specifications and addressing architecture."), but I have CCed V6OPS as well, as it is clearly operational as well.
>
> Abstract:
> "This document updates the IP Version 6 Address Architecture to define the IPv6 address prefix ::/32 as the Loopback address prefix."
>
> Basically, this document expands the single loopback address ::1/128 into a prefix.
>
> Yes, we are aware that there have been some previous discussions[0] on the need (or lack thereof!) of a loopback prefix in IPv6, but we believe that they are worth revisiting.
>
> There are a number of situations in which having more than a single address is helpful; an obvious example of this is Dockers/k8s use of 127.0.0.11 for the DNS resolver, SPAM RBL use of the last octet on 127.0.0.x to encode the type of SPAM. It is also relatively common it use this for inter-service communication in container environments.
>
> It is also a common practice to bind different services to different addresses in the IPv4 loopback space to allow for scaling (avoiding the "Port already in use" issue), testing, etc.  Yes, these can be somewhat emulated with ULAs and / or additional interfaces and scopes, but they are all more complicated, and much more likely to result in leakage or collision.
>
> Another, more recent example is the ICANN Public Comment on "Name Collision IPv6 Research Study" and proposed use of ::ffff:7f00:3535 [1] - if there was a loopback prefix this would have been a better option[2]
>

I fully agree that there is a need for a larger loopback prefix. I
also fully agree that /32 is the Goldilocks size.

"A Larger Loopback Prefix for IPv6"
https://datatracker.ietf.org/doc/draft-smith-v6ops-larger-ipv6-loopback-prefix/04/

Regards,
Mark.


>
> We expect a fairly robust discussion :-),
> W
>
> [0]: I know I've seen them, but I quick search of my mail was unable to find these — the authors are more than happy to link to previous documents, etc.
>
> [1]: See long threads on 6MAN https://mailarchive.ietf.org/arch/msg/ipv6/-HrYFMwHhsUWYxSXsFIkLpF_Qgk/ and V6OPS.
>
> [2]: Solving the technical concerns, but not necessarily the policy ones.
>
> _______________________________________________
> v6ops mailing list -- v6ops@ietf.org
> To unsubscribe send an email to v6ops-leave@ietf.org