Welcome:
Login
|
Sign Up
|
About CircleID
Follow:
|
|
|
IPv4 Markets |
Sponsored by |
|
Following on from last year's measurements after World IPv6 Day, the RIPE NCC carried out active measurements on World IPv6 Launch on 6 June 2012. These measurements included latency measurements both on IPv4 and IPv6 from our vantage points to selected hostnames of World IPv6 Launch participants and other dual-stacked parties. We used these measurements to determine the performance of IPv4 versus IPv6 connections.
Contributing to international telecommunications standards, not in the IETF but in a more august and imposing body, the ITU-T, part of the United Nations, was quite an experience. Still called CCITT in those days, it was formal and solemn; everybody was part of and sat with their national delegation, countries were aligned in alphabetical order; nobody spoke out of turn, every word was simultaneously translated in the three official languages of the time and we wore suit and tie.
Declan McCullagh recently opined that the "FBI [and the] DEA warn [that] IPv6 could shield criminals from police." His post was picked-up relatively widely in the past few days, with the headlines adding more hyperbole along the way. So just how real is this threat? Let's take a look.
For two things that would seem to be completely unrelated there is an interesting parallel between IPv6 and DNSSEC. In both cases there is a misalignment of interests between content providers and service?providers. Content providers aren't highly motivated to deploy IPv6 because only a small proportion of users have v6 connectivity and even fewer only have v6. Service providers aren't anxious to deploy IPv6? because there isn't a lot of content on v6, and virtually none exclusively on v6 - so they don't expand the universe of interesting stuff on the web by deploying IPv6. Basically the same things could be said about DNSSEC.
As announced on RIPE Labs we monitored the behaviour of a number of networks that participated in the World IPv6 Launch on 6 June 2012. For that, we looked at the full list of participating organisations as shown on the ISOC website and chose 50 websites from that list. We looked at 'interesting' sites and at geographic distribution. We also tried to find a good mix of networks that had IPv6 switched on already and those that didn't have IPv6 deployed at the time they registered on the ISOC web site.
In recent interviews about World IPv6 Launch I've been asked by several different people whether or not I think there needs to be some kind of a "Flag Day" on which the world all together switches from Internet Protocol version 4 (IPv4) to the version 6 (IPv6). I don't think a flag day is needed. World IPv6 Launch is just the right thing. It's worth looking at some previous flag-type days to get a better sense of why.
World IPv6 Launch kicked off 6 June 2012 at 00:00 UTC. On this day, multitudes of website operators, network operators and home router vendors from all over the world have joined thousands of companies and millions of websites in permanently enabling the next generation Internet. They have done this by turning IPv6 support on by default in (at least some of) their products and services. This is a major milestone in the history of the Internet.
This year, we expect that the RIPE NCC's pool of unallocated IPv4 addresses will reach the "last /8", meaning that we have 16,777,216 IPv4 addresses left in the available pool. At that point it will no longer be possible for RIPE NCC members to obtain the amount of IPv4 addresses they will require to expand their current and future networks. When we hit the last /8, the RIPE NCC will only be able to distribute IPv6 addresses and a one-off allocation of IPv4 address space... Has this caused a last minute rush?
The transition to IPv6 is top of mind for most service providers. Even in places where there are still IPv4 addresses to be had surveys we've run suggest v6 is solidly on the priority list. That's not to say everyone has the same strategy. Depending where you are in the world transition options are different -- in places such as APAC where exhaustion is at hand one of the many NAT alternatives will likely be deployed since getting a significant allocation of addresses is not going to happen and other alternatives for obtaining addresses will prove expensive.
In my previous blog on the topic, I stated that the business case supporting the IPv4 roll-out in the late 90s was the Internet. Although IP depletion will slowly become a reality, the chances are that due to mitigating technologies such as NAT and DNS64, it may take quite a while before organizations in the developed economies will get serious about IPv6. So where should we look to find a business case for IPv6?
A World-Renowned Source for Internet Developments. Serving Since 2002.
