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

Fernando Gont <fernando@gont.com.ar> Sat, 13 February 2021 00:29 UTC

Return-Path: <fernando@gont.com.ar>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73E213A114C for <v6ops@ietfa.amsl.com>; Fri, 12 Feb 2021 16:29:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Unp_fKVZT0Gk for <v6ops@ietfa.amsl.com>; Fri, 12 Feb 2021 16:29:43 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44F7C3A114A for <v6ops@ietf.org>; Fri, 12 Feb 2021 16:29:42 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:4181:442:5061:d73f] (unknown [IPv6:2800:810:464:2b9:4181:442:5061:d73f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 8E5C9283DA9; Sat, 13 Feb 2021 00:29:39 +0000 (UTC)
To: v6ops@ietf.org
References: <160989494094.6024.7402128068704112703@ietfa.amsl.com> <6fe3a45e-de65-9f88-808d-ea7e2abdcd16@si6networks.com> <F4E00812-E366-4520-AE17-7BB46E28D575@gmail.com> <b2e51a89-e8a7-9ddb-643d-63a98569b03c@si6networks.com> <CB9EA5F4-A241-46A4-A371-B2A1BFB8C72F@fugue.com> <dff93a2e-f4f8-01c9-ce88-c2dbb20a04f1@si6networks.com> <759637FF-77C7-41EA-8671-73988AD48873@fugue.com>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <6ab2d348-6220-6744-9585-1f99e23a7ee0@gont.com.ar>
Date: Fri, 12 Feb 2021 21:29:17 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <759637FF-77C7-41EA-8671-73988AD48873@fugue.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ckY56qT3PjoXjLm7_OYXv2TPS2k>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Feb 2021 00:29:46 -0000

On 12/2/21 21:04, Ted Lemon wrote:
> On Feb 12, 2021, at 6:50 PM, Fernando Gont <fgont@si6networks.com 
> <mailto:fgont@si6networks.com>> wrote:
>> This, in away, is the question that this document somewhat raises:
>>
>> * What's "global scope" anyway?
> 
> Global scope is “you can forward it to the default route.”

That's certainly not the definition of "global" we currently have.

(draft-gont-6man-ipv6-ula-scope points to the relevant places)


Me, I wouldn't use the "default route" in the definition of "global". 
 From a routing pov the default route is simply yet another route, 
albeit with a zero-len mask.

Addresses need to be able to identify the intended sender/recipient. So 
the area where they can do that limit their scope.

Now, if I use fd00:1234:5678:abcd::/64 on my net, and you use the same 
prefix on yours, and both usages are legitimate, then that's an 
indication that the scope of ULAs cannot be global.



>> * And, given what we have right now, either the definition of scope is 
>> flawed (as in the scoped addressing architecture), or ULAs are not 
>> global, or both. :-)
> 
> RFC 4007 has a concept of “interfaces belonging to a zone,” and has a 
> nice diagram with several organizations that we might say is a 
> non-overlapping Venn diagram. But ULAs don’t have to have a 
> non-overlapping Venn diagram. So they are global.

Please define "global". :-)



> And indeed there is no 
> way to automatically determine (without configuration) which zone any 
> given address belongs to. So in effect the only two scopes that can be 
> automatically determined are “link local” and “global.” There can be no 
> other scope, in the sense of a scope that can be automatically determined.
> 
> This doesn’t mean that RFC 4007 is useless, but what it does mean is 
> that when we assign a scope to “ULA,” the only scope that makes sense is 
> “global.”

This is the definition of "scope" and "global scope" from RFC4007:

    [RFC4007] defines the scope of an address as:

       "[the] topological span within which the address may be used as a
       unique identifier for an interface or set of interfaces"

    And defines the "global scope" to be used for:

       "uniquely identifying interfaces anywhere in the Internet"


ULAs can certainly NOT be used in the Internet-wide span, and they 
certainly do not "uniquely identify interfaces anywhere in the Internet".



> So maybe a better question to ask is, why are we discussing this? What 
> problem are we trying to solve?

As per the above, either the definition in the scoped addressing 
architecture is wrong, or flagging ULAs as "global scope" is incorrect.

The problem I'm trying to solve is one of architecture, so to speak.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1