News for hackers. Stuff that matters.
Re:Unicast Use of the Formerly Reserved 127/8 by mysterydip on Wednesday November 17, 2021 @07:35AM (#29252233)
I honestly don't know why we don't just have "IPv5" which adds an octet to the front of IPv4. Everything on the internet now would be 0.a.b.c.d and everything else would use 1-255.a.b.c.d
Re:Unicast Use of the Formerly Reserved 127/8 by Dagger2 on Wednesday November 17, 2021 @01:13PM (#29256640)
Because that's basically what v6 did. It just added enough octets that we don't need to turn around and do it again immediately afterwards, since deploying new L3 protocols is hard enough as it is without needing to do it twice.
Re:Unicast Use of the Formerly Reserved 127/8 by Denvercoder9 on Wednesday November 17, 2021 @07:45AM (#29252319)
That doesn't solve the fundamental problem of IPv6 adoption: _all_ equipment along a network path needs to be updated to be compatible with the new addresses for them to be usable.
Re:Unicast Use of the Formerly Reserved 127/8 by jffry on Wednesday November 17, 2021 @10:01AM (#29253908)
Yeah, and if we're going to be changing all of the equipment, why not take the time to smooth over some of the other known warts besides address space?

It's my understanding that IPv6 is essentially that, and not just a move to a 128-bit address space

Re:Unicast Use of the Formerly Reserved 127/8 by ajsnigrutin on Wednesday November 17, 2021 @08:26AM (#29252662)
This means changing every piece of network equipment everywhere.

And if you need to change it, why keep all the broken parts of ipv4, if you can fix them (atleast partially), like we did in ipv6?