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

[Mark Smith <[e-mail]>]

On Thu, 10 Dec 2020, 04:21 David Farmer, <farmer=[e-mail]>
wrote:

> First, please don't do this. As has been said, it is unnecessary and will,
> unfortunately, lead some people to make erroneous conclusions. You are
> trying to coordinate something that was intended to be uncoordinated, and
> therefore you are trying to make ULA into something it wasn't intended to
> be.
>
> If you insist on doing this, please don't call it a Registry; that will
> imply it is something akin to the RIRs and that will lead people to make
> the erroneous conclusions I referred to. Furthermore, calling it a
> Registry raises the questions like; Is it mandatory to register your ULA
> prefix? Does the registry represent all ULA prefixes?
>

It cannot.

Per RFC 7084, SOHO/residential CPE are to automatically generate ULA-Ls for
local use by default for internal use, regardless of if global IPv6
connectivity isn't available.

So unless CPE were updated to register their ULA-Ls with this service, it
will never record all ULA-Ls, and actually will only be a record of a tiny
number of them.

I think ANIMA networks do the same sort of thing, so it will be missing
those ULA-Ls too.

Regards,
Mark.


> Possible words to use for this; Diary, Catalog, Journal, Ledger, Log, just
> don't call it a Registry. Furthermore, clearly, statie use is optional and
> by definition it is incomplete,
>
> Thanks
>
> On Sat, Dec 5, 2020 at 5:19 PM Nico Schottelius <
> [e-mail]> wrote:
>
>>
>> Good morning,
>>
>> we have just launched a ULA registry [0] as part of our IPv6 advent
>> calander [1]. While the reception, openness and opinions of whether or
>> not there should be a ULA registry at all differ, a ULA registry has
>> been requested multiple times from our customers in the past.
>>
>> The source code of the ULA registry is fully Open Source and can be
>> found on [2]. It currently operates using the fd00::/8 subnet, whereas
>> draft-hain-ipv6-ulac-02 [3] suggests that RFC4193 should be followed for
>> that subnet and fc00::/8 should have been taken for a ULA registry.
>>
>> However the original SixXS database records [4] on which we based our
>> work operatios in fd00::/8 and according to wikipedia [5] there is no
>> consensus over fc00::/8 in the IETF.
>>
>> Speaking for ungleich, we do not use ULA ourselves, however our users
>> do. In this regard our position is somewhat neutral with the focus of
>> "enable users to move forward with IPv6".
>>
>> However in the spirit of collaboration and finding a consensus for a ULA
>> registration, we could imagine phasing in fc00::/8 as the default prefix
>> for generating new prefixes while keeping the historic information of
>> the previously registered prefixes that originally came from SixXS.
>>
>> Looking forward to your feedback.
>>
>> Best regards from the snowy mountains in Switzerland,
>>
>> Nico
>>
>> [0] https://ula.ungleich.ch/
>> [1] https://ungleich.ch/u/advent-calendar/06/
>> [2] https://code.ungleich.ch/ungleich-public/ipv6ula
>> [3] https://tools.ietf.org/html/draft-hain-ipv6-ulac-02
>> [4] https://www.sixxs.net/tools/grh/ula/list/
>> [5] https://en.wikipedia.org/wiki/Unique_local_address
>>
>> --
>> Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> [e-mail]
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>
>
> --
> ===============================================
> David Farmer               Email:[e-mail]
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: [phone]
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [e-mail]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>