Re: [v6ops] Reused deprecated prefix (0200::/7)

[George Michaelson <[e-mail]>]

On Sun, May 23, 2021 at 7:48 PM Александр Иванов <[e-mail]> wrote:
>
> Hello, v6ops maillist members,
>
> I want to talk about the 0200::/7 prefix, which is officially deprecated (RFC4048), but actually used from 2017 to now.
>
> There's a project called Yggdrasil Network - a self-arranging encrypted IPv6 network (https://yggdrasil-network.github.io/) which utilizes this deprecated prefix ...and its network already has members that use it for business purposes.
>
> How do you think about allocating that prefix as a software-routed global unicast address? A future RFC can be merged with draft-horley-v6ops-expand-doc-00.
>
> I highly appreciate any feedback and help for new to the IETF.
>
> Regards,
> ~ Alexander Ivanov, Russia

Please bear in mind that repurposing of experimental or narrow-use
delegations direct from IANA into global public routed space, with
potential to become something shared or used by independent
ASN/entities invites questions around what nature of registry function
needs to exist for this range, and also brings the question of global
unicast address management (which is delegated into the RIR process)
to the surface.

I think that needs to be respected, proposing this block of addresses
goes into a changed state:

  * What is the impact on the RIR system? Is this decision something
which should be part of global address policy?
  * What is the impact on the agreement between the IAB and the RIR
regarding management of global unicast address space?
  * If this invokes distribution of subspaces, what community
obligations regarding registration are being done? Where is the Whois,
RDAP and related information?

For like cases, this has usually led to one, or all of the RIR taking
service obligations on board to host a facility.

cheers

-George (I work in APNIC, but I don't work in address policy contexts)