Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

IPv4 is OVER. Really. So quit relying on it in new protocols, sheesh

Internet Architecture Board grabs stake, eyes coffin: 'Still not dead? Let's fix that'

Well, that took a while. Eighteen years after the IETF brought us IPv6 as an answer to then-looming-now-upon-us IPv4 address exhaustion, the Internet Architecture Board says: no more.

Getting IPv6 into the field has been a long, slow slog. According to Google, IPv6 carries just 14.6 per cent of search requests to the web giant.

Since the v4 address pool is pretty much exhausted, the IAB says people writing new standards and protocols need to focus on IPv6 “without being dependent on IPv4.”

“The IETF as well as other standards development organizations need to ensure that their standards do not assume IPv4,” the IAB said in a statement on Monday.

Grudgingly, the board – which is an IETF oversight committee – acknowledges that dual-stack implementations and backwards-compatible connectivity “will be needed for some time.”

However, in the faint hope that carriers and ISPs will give up their put-it-off-with-a-really-big-NAT, the IAB wants the IETF and other standards writers to embark on what could be the Internet's biggest ever documentation rewrite: “We recommend that existing standards be reviewed to ensure they will work with IPv6, and use IPv6 examples.”

Good luck with that. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like