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

Fernando Gont <fgont@si6networks.com> Mon, 07 December 2020 08:38 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 B7BB23A1176 for <ipv6@ietfa.amsl.com>; Mon, 7 Dec 2020 00:38:50 -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 LWrMEwv7T_0z for <ipv6@ietfa.amsl.com>; Mon, 7 Dec 2020 00:38:47 -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 EF9B53A0E9B for <ipv6@ietf.org>; Mon, 7 Dec 2020 00:38:44 -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 1FAF0284684; Mon, 7 Dec 2020 08:28:48 +0000 (UTC)
From: Fernando Gont <fgont@si6networks.com>
Subject: Re: Happy St Nicholas Day: Re-Launching the IPv6 ULA registry
To: 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>
Message-ID: <ba98a7a9-cba3-1efb-1139-1b8a2318ae96@si6networks.com>
Date: Mon, 07 Dec 2020 05:28:13 -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: <CAKD1Yr3ptRjewThToEgERUOKwehTwdqNUAq14acc_nHLFqf3bg@mail.gmail.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/ipv6/q1ozRviETM8MdTeQbApdn0rrU3Y>
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: Mon, 07 Dec 2020 08:38:51 -0000

Hi, Lorenzo,

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.


> Therefore, if a pseudo-randomly allocated address conflicts with 
> something in the registry, the registry should be deemed incorrect.

Following the logic of the port number registry, if two organizations 
use the same prefix, the registry could simply note that.

That said, I'm not sure:

1) Whether folks would be compelled to register their blocks.

2) (Partly as a result of #1), the extent to which a registry would be 
of any use.


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?)

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