Re: Happy St Nicholas Day: Re-Launching the IPv6 ULA registry

Fernando Gont <fgont@si6networks.com> Tue, 08 December 2020 01:10 UTC

Return-Path: <fgont@si6networks.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 34E0C3A0DE5 for <ipv6@ietfa.amsl.com>; Mon, 7 Dec 2020 17:10:34 -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 xMt16QSpwo8N for <ipv6@ietfa.amsl.com>; Mon, 7 Dec 2020 17:10:29 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.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 7F9BE3A0DE2 for <ipv6@ietf.org>; Mon, 7 Dec 2020 17:10:25 -0800 (PST)
Received: from [192.168.1.5] (unknown [190.179.27.231]) (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 66731284686; Tue, 8 Dec 2020 01:10:19 +0000 (UTC)
Subject: Re: Happy St Nicholas Day: Re-Launching the IPv6 ULA registry
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Nico Schottelius <nico.schottelius@ungleich.ch>
Cc: IPv6 List <ipv6@ietf.org>
References: <87r1o3deni.fsf@ungleich.ch> <CAKD1Yr3ptRjewThToEgERUOKwehTwdqNUAq14acc_nHLFqf3bg@mail.gmail.com> <ba98a7a9-cba3-1efb-1139-1b8a2318ae96@si6networks.com> <8c60bbd0-1789-0cc5-bdd3-60382638952d@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <b4c361e0-b451-8d9e-1092-de953ad6f2d5@si6networks.com>
Date: Mon, 07 Dec 2020 21:50:03 -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: <8c60bbd0-1789-0cc5-bdd3-60382638952d@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/eCtwkwfhLVZvSM1Us85xBpc7I48>
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: Tue, 08 Dec 2020 01:10:40 -0000

Hello, Brian,

On 7/12/20 17:20, Brian E Carpenter wrote:
>> On 6/12/20 21:42, Lorenzo Colitti wrote:
>>> Nico,
>>>
>>> This seems a bit misguided for several reasons.
>>>
>>> First, registries are supposed to be authoritative databases, but the
>>> RFC specifies that ULA addresses are generated pseudo-randomly.
>>
>> Strictly speaking, there exist registries that are not authoritative --
>> e.g., think of the registered ports in the port number registry.
> 
> That's not a useful analogy. Those ports need to be registered because
> they are potentially used across the open Internet.

I'm not sure that's the case (i.e., that all registerd ports are used in 
the open Internet).  That said, I was simply pointing out that such 
registry does have "conflicts" -- i.e., same port used by multiple 
protocols/apps.


> ULAs are by
> definition not used across the open Internet. Therefore, they don't
> need a registry.

Agreed on this one.



>> That said, I'm not sure:
>>
>> 1) Whether folks would be compelled to register their blocks.
> 
> I'm sure: no.


I, for one, wouldn't :-)



>> That aside, in a way the whole point of randomizing the ULA prefix is
>> that results statistically unique. So, provided folks do follow the
>> advice in the ULA spec (I for one have *not :-) in a number of
>> occasions), there shouldn't be much of a need to actually register ULA
>> prefixes... (if the prefixes are unique... who cares who uses what?)
> 
> Sorry, but I don't think "statistically unique" is a well-defined term.
> The property of a ULA prefix is that there is a very low probability
> of collision if two ULA networks are merged. (For the details, see
> https://tools.ietf.org/html/rfc4193#section-3.2.3).

Thanks for pointing this --. I stand corrected.

(Must say, anyway, that things like " Globally unique prefix (with high 
probability of uniqueness)." leads to some confusion).

Possibly dumb question, since I wasn't there: what was the reason for 
carving ULAs out of the GUA space?  -- i.e., not updating the addressing 
architecture, and marking the ULA block as something other than GUA.

Thanks!

Regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492