Hacker News new | past | comments | ask | show | jobs | submit login

I doubt anything containing 0.0.0.1 is advertised in China (it's definitely not outside of China). Looks like an address someone would use to indicate an error condition.

... which is just another example of the zillions of cases that would have to be dealt with.

Sure, each one is probably quite easy. But the sheer number of them is huge, and many of them will only be uncovered after they fail, setting off a frantic search for the retired guy with the source code.

With Y2K there was a combination of self-interest and hysteria that motivated organizations to tackle it. With this, it's harder to make that case because IPv6 is here already. I'm sure very few of those applications with hardcoded 0.0.0.0/8 are IPv6-ready, but everyone else can move ahead with IPv6 and those old apps will keep working for years to come. Unleashing 172.0.52.7 as someone's residential IP address will result in seemingly random failures that cause headaches for the ISP, application developers, and corporate IT departments. It'll be a very unpopular idea.




My principal reason for proposing that 127 be reduced to a /16 instead of a /8 was to help unwind the kubernetes hairball.

I have no idea to what extent 0/8 is being used today. I do see quite a bit of 240/4 in private networks. It's a shame that last may never be publically allocated.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: