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

Mark Smith <markzzzsmith@gmail.com> Wed, 06 January 2021 19:46 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 907AC3A1188; Wed, 6 Jan 2021 11:46:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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.998, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BkONk5ccEK6K; Wed, 6 Jan 2021 11:46:50 -0800 (PST)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16E883A1102; Wed, 6 Jan 2021 11:46:50 -0800 (PST)
Received: by mail-ot1-x32a.google.com with SMTP id d8so4116581otq.6; Wed, 06 Jan 2021 11:46:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=a0KX+rMiBdbGde6DZlSiPYYZyPtyoAQSf5pMHGhu6ng=; b=gRjfRqPbTPH9DS3l7benl8KLf7OZGN0P9+cF5SZIv320DDX376qyUBl7yNX2wJ9+jL 9JDbXgpD/8qnEtIWGpURdLFMyfit6lls9LtYIX0FYBxuVMMAcYznST/d0NcrV9n7n/9q gu1wRA5eEvFz/BqmcUXNjQjhp0+7J+Z8OUYO4ThfpoEd681gnXYfj4WCMpyG1XqLoMzP RgZW+9RIME9LnvL2deCXKUaBFZb18LDf68MB8Q/GV1q+1t24g4ZuryEX08F0RKGEZsLm oFmPUXKJk0BP6v2rhFhaMkjHQx160JXlmY+dWmLC91vYJkjJBaNsXPgmsqqpXAB5OV5R iO0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=a0KX+rMiBdbGde6DZlSiPYYZyPtyoAQSf5pMHGhu6ng=; b=QiwKAiecDysgafJjZVJrM4vuPYsj4malu6BZlZPK1y8jC7N6254wIf0cAeplaSQaOK Mkifx2TDEe0qG53SsEHrPzgxkOuJhuOEQNxZV6XOxGAvbP2g16t40tl/ziSlvGBu3mZh k41gK6rSdX3QDVexriPbPwhcPzxC2cv0LGNtoHwz+Bbw470Mo9cyT10z8SAQDFxTzuPk s1b6RwuFRgWewaAyBwhL02UjDK3hFPCYj7yY5chvjH8Q1F6cNPDtb6r6QFV9bGU3Vv+n xiaYyysvkwQK3jTsYOWyNHGIOPNrJeU4ZfuD2oyJYEKQBcjVtPvs8owPdYrO1JA1trR8 NADQ==
X-Gm-Message-State: AOAM531XHMZqA1MY6Y8ml4rf0G1yvszaq4i9ZlgyHeErqWILtrAF8udC L+y5lpmTGaz0DqssHFMYzQD6JTnyAj7fh6of1V8=
X-Google-Smtp-Source: ABdhPJz7e0bY7uqnU4rhILeeIOXzWZVK74LZJimeR72vkb30Nx973X6Ba/xEyTS697ReCwwYLF2ebh2cSB38wTMl+fw=
X-Received: by 2002:a9d:602:: with SMTP id 2mr4305378otn.153.1609962409393; Wed, 06 Jan 2021 11:46:49 -0800 (PST)
MIME-Version: 1.0
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <CAN-Dau344H7xgD0Q_O54c=R08zFRFjToO8BHt=ssauxgEH7ynA@mail.gmail.com> <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com>
In-Reply-To: <EFF2CF9D-147B-4E7F-9080-633A24FDA666@fugue.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 7 Jan 2021 06:46:22 +1100
Message-ID: <CAO42Z2xmP1CFWsDKQJ35wuNjjdZdyimZN=5j2h9rGbcZjkeHZA@mail.gmail.com>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
To: Ted Lemon <mellon@fugue.com>
Cc: David Farmer <farmer=40umn.edu@dmarc.ietf.org>, Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0bY0VakcSB2Iqnnh5v_H5uLkBN0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 19:46:52 -0000

On Wed, 6 Jan 2021 at 23:18, Ted Lemon <mellon@fugue.com> wrote:
>
> On Jan 5, 2021, at 11:38 PM, David Farmer <farmer=40umn.edu@dmarc.ietf.org> wrote:
>
> I think this is the right direction the previous draft indirectly defined a new scope "non-global", I much prefer explicitly defining a new local scope.
>
>
> Actually, I think you’ve got it right here: the scope is “non-global.”

I







>
> I would add something like the following to better define the relationship between the three scopes;
>
> The boundary of the link-local scope is strongly defined, limiting the extent of the link-local scope to an individual link. However, in contrast, the boundary of the local scope is weakly defined, it is amorphous and imprecise. In some instances, the extent of the local scope can be a single site, in other instances, a group of unrelated sites, a single organization, or even a cooperating group of organizations. Furthermore, the extent of an individual instance of the local scope doesn't necessarily remain constant, it may expand or contract over time as the local situation dictates, for example when two organizations merge. Nevertheless, the extent of the local scope doesn’t encompass the entirety of the Internet which the global scope does.
>
>
> There is at least one obvious problem with this definition: the term “local.” ULAs aren’t really local, despite the name. Using the name “local” is what leads to this confusion. Consider this taxonomy:
>
> GUA: “valid everywhere on the internet scope”
> ULA: “not valid everywhere scope”
> LLA: “valid only on this link scope”
>
> Of course these names are awkward, but I hope they are clarifying. A ULA is “not valid everywhere.” That’s really all you can say about it. You can’t put a ULA prefix in a global routing domain. You can put it in a site routing domain. You can put it in a multi-site routing domain. You can not route it at all. All these uses are valid.
>
> So I don’t really object to your text, but I do object to the name “local.” How about “explicit”? That is, the scope of a ULA is explicit, in the sense that it must be _made_ explicit by the user(s) of the ULA? If that doesn’t work, I’m sure we can come up with a more agreeable term, but please let it not be “local.” Sorry to be a sticky wicket. :)
>

I think "local" is close to, if not the right word.

I consider anything that is non-global or smaller than global to be "local".

I think "local" is a word that has the word's user's perspective and
the context of its use as part of its semantics. The perspective and
context defines what the "local" domain boundary is, and it is
possible that different people might have different definitions,
although they'll probably be pretty similar. People have their own
local perspective on the definition of the word "local" ;-)

When I'm at home, my "local" network is my home network.

When I'm at work, my "local" network is the ISP I work at's network. I
don't consider our customers' home networks "local" though, even
though they're all part of the network with the same AS number.

Some examples of "local" outside of networking.

I go for walks around my local neighbourhood. I ride my bike around
the local neighbourhood. As I can ride further than I can walk, my
local neighbourhood in the context of being on my bike is a greater
geographical area than my local neighbourhood when I walk.



> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------