Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)

Ted Lemon <> Sat, 13 February 2021 02:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6C3C03A1206 for <>; Fri, 12 Feb 2021 18:13:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id H5ubeNbnLj6e for <>; Fri, 12 Feb 2021 18:13:37 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::729]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5BC6F3A1204 for <>; Fri, 12 Feb 2021 18:13:37 -0800 (PST)
Received: by with SMTP id j3so1507665qkk.9 for <>; Fri, 12 Feb 2021 18:13:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=H0e3YwleIZUUxGzbI3dGUstoWMbpTP1sKO4z3CLssZI=; b=OQiSXdLM+yfqEpHI5RmJ0LnENx5fOFX+fraMtklRJi7iX15FE5y473PI/NLZoktfAK TJYPVVkZhDUNXMuQIHCwMCRxGsap3HN9dJx2po1MEHZUWGoDZntIhCmFweeFif5Epf8y KLugA20MbaXzaHm96J7xq5sZrJ0iKx/l6q4wZT+7aOkIQE43hhi1m51ccMRIKkZtiocl fGhp4cvBrruLpbde/USAvfk1VLMY2E2oMdRG+xlmOWmwU2bkWa9/Ba4hkeOIX8Gi7kEm Bg3wzyfVPKkO1WBPoJeYrEBY7kq67lEhCaFqdqMJSx2/xhSPgKgZixlf2hu/WJpwhwiL BZ2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=H0e3YwleIZUUxGzbI3dGUstoWMbpTP1sKO4z3CLssZI=; b=f5y3+U1uOhLqYZdOpGQH6qy0etYdIBgJkkdQ0aBc9zww4AiTfBcVwmR/9uvsJ+cf1K gCmtIfau/rfH7SZs3hVEvC+ASa+mJAGvYUZGiIthNU150NUxZBI+/GG0JKm9n8EB5lw8 iouvHmDWawCGg8oNM34e7Vr9D4NvMTg5oSoDhE29vaBGTKjzAgU7K7qRgKJ/6AO95agY 30VuF/TxFKoh72KtgFd+Zrtxnt0yXnVFW3CLq3HjACaz0mE516Ae6kTCQ20THESDrfPW VQxZb4nUd2JSaD5T+MPGYvl2S6x0XIGjyaZ6TDhTc0fI3svFn2NOMdzWqLrWVk0k830i tU/A==
X-Gm-Message-State: AOAM532cPUoK83u/3s4y0MtTPPLxeJRpGGqb4QHzwTpymZtaKPPxMIhz LK2MA+VaN1ugS/F/LZo90yaharkfx6N5lw==
X-Google-Smtp-Source: ABdhPJz81wgbASqpwgnZkgieDDHCWOaiapTnTCj2A6GXOS9yFXN1nom5jCPJl69NWoNxiYEwRS/sKA==
X-Received: by 2002:ae9:f309:: with SMTP id p9mr1893360qkg.111.1613182415026; Fri, 12 Feb 2021 18:13:35 -0800 (PST)
Received: from ( []) by with ESMTPSA id s136sm7255081qka.106.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Feb 2021 18:13:34 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
From: Ted Lemon <>
In-Reply-To: <>
Date: Fri, 12 Feb 2021 21:13:33 -0500
Cc: Fernando Gont <>, IPv6 Operations <>, "" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <>
To: Fred Baker <>
X-Mailer: Apple Mail (2.3654.
Archived-At: <>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 13 Feb 2021 02:13:39 -0000

On Feb 12, 2021, at 8:55 PM, Fred Baker <> wrote:
>> On Feb 12, 2021, at 4:04 PM, Ted Lemon <> wrote:
>> Global scope is “you can forward it to the default route.”
> No. Global scope, per the RFC  you're quoting, is "Global scope, for uniquely identifying interfaces anywhere in the Internet.”

If you’re referring to RFC 4007, and talking about unicast addresses, then the document is unequivocal on this point: an address is either global or link-local. Those are the only two options. I think here “global” means “there is no context in which this address is, by definition, out of scope.”

I agree that there’s a terminology question here, and perhaps that is a problem to solve, but I don’t see any way to solve it. I think the following things are all true:

ULA addresses are, in principle, VALID in any scope.

They are not, in principle, UNIQUE to a particular link: it’s entirely possible to have two instances of the same ULA referring to different interfaces connected to different links.

In principle, the set of all networks which can route a packet to a particular instance of a ULA /48 MUST be DISJOINT from the set of all networks which can route a packet to some other instance of that ULA /48.

In practice, the randomness of ULAs gives us some reasonable assurance that the principle will hold.

However, users of ULAs that are routed beyond an individual site had better have some policies and procedures in place to make sure that this is true.

Internet backbone routers should never accept BGP advertisements for ULA prefixes.

Sites connecting to the Internet should never, by default, route ULAs northbound of their connection to their ISP.

The last four lines are points of practice, not points of definition of terms.

But the bottom line is that if the term “global” is confusing as it applies to ULAs, it shouldn’t be that hard to clarify what we mean by global.