[_16k4]

Is the intent to get class E routed on the public internet, or just make it available in private networks?

I've seen docker configs squatting on chunks of class E space for the local bridge interface, presumably because Linux takes it, and it doesn't usually clash with the landmines in rfc 1918 space.

I know of at least one company using class E as the new 8/8 ;)

[schoen]

We're interested in routing it on the public Internet, although I also know that some people are using it internally and that one of the two older public proposals about this suggested that it might be better as new private address space.

One way that I've been thinking about the reachability issue is by analogy to

https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-g...

Many organizations used 1.1.1.1 as a test address (in addition to other uses of 1/8), so once Cloudflare started working to get a public service up there, it had to perform various reachability tests and also set up a way for people to report problems. This is apparently an ongoing process to this day, but Cloudflare's hard work helped make reachability that was initially patchy get asymptotically better. I think we can much do the same with other previously unassigned address ranges.