4 ms·
I'd support this for optional private deploy where you get to control and manage what was already using that space and conflicts are a local thing to deal with.
by zamadatix 5y ago
I'd support this for optional private deploy where you get to control and manage what was already using that space and conflicts are a local thing to deal with. I can't say I'm in support of the chaos that is expecting billions of internet endpoints to stay out of space that was permanently reserved for other use and expecting anything useful to come out of of the rubble. 1.1.1.0/24 was bad enough and that didn't even have the same standing or blast radius as 127/8 sans 127/16.
I've seen lots of 127/8 use for "next hop self" tunneling on network gear and of course lots of 127/8 use for local communication. You'd have better luck getting people to finish going to IPv6 than convincing everyone to change 20 year old configurations to new ones so someone else can deploy new stuff in the old space.
It's also interesting all 3 chose to represent themselves as being under the sole backing group of "IPv4 Unicast Extensions Project". I'm not sure if they either couldn't find support or didn't seek it such as with previous RFC's by the offers (e.g. stuff around bufferbloat). Either way it's disappointing to see standards track RFCs that haven't first sought/demonstrated wider opinion and support.
- dtaht 5y agoWe have been at this, technically, for years and has been discussed in multiple forums prior to now. It's a done project for me (my primary focus is bufferbloat), as all the technical work I could do is complete and the core patches for 240/4, and 0/8 and zeroth in the linux kernel and BSD. The internet drafts are now submitted for consideration for standards track. If they fail to gain support, the existing and future usages of these ipv4 spaces will remain unstandardized.