On Mon, May 6, 2019, 11:08 PM Ronald F. Guilmette <[email protected]> wrote:
> >Impossible. It's disabled in the stack, hard-coded as a martian or a > bogon, > >can't even configure it, name it. > > Sounds like a software problem. > > If your software doesn't do what you want it to do, that's hardly ARIN's > responsibility. > The trick is: this is virtually *every* piece of network software ever written that behaves this way. There was an initiative in March this year, by Paul Wouters I think, to allow use of 240/4, 224/4, 0/8, 127/8 etc. All of those are forbidden now by hard code in Linux, Windows and pretty much any switch firmware. I encourage you to follow the proceedings of Netdev 0x13 in Prague this year. Look up something like "IPv4 unicast extensions" or "IPv4 unicast expansions". While ARIN may not be (directly) responsible for this mess, it is the reality it ultimately happens to be a part of. -- Töma
_______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
