44/8

Mon Jul 22 19:15:23 UTC 2019

I think the Class E block has been covered before.  There were two reasons to not re-allocate it.

1.      A lot of existing code base does not know how to handle those addresses and may refuse to route them or will otherwise mishandle them.

2.      It was decided that squeezing every bit of space out of the v4 allocations only served to delay the desired v6 deployment.

This is my recollection and might be flawed.

Steven Naslund
Chicago IL

>Whatever happened to the entire class E block? I know it's reserved for future use, but sounds like that future is now given that we've exhausted all existing >allocations.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190722/997a43b1/attachment.html>