The debates are raging over whether or not we should migrate to IPv6. The strongest argument is the enormous address space that will allow for everyone and everything to have a unique public address, many addresses actually. It is often said that the shortage of public IPv4 addresses has limited our capabilities because it led to the pervasive use of private addressing, Network Address Translation (NAT) and Port Address Translation (PAT). Though these technologies remain critical, they are often regarded as stop-gap measures, and they sometimes create problems. In some circles, NAT has acquired a very bad name. But is that a fair perspective of the technology? Let's review the positives and negatives.
February 4th 2008 will be the day the repotting of the internet finally starts. A milestone of sorts for some people who spent a good part of the last five years getting us this far. It should now be finally possible for a IPv6 only device to have a chance to communicate on the Internet. Indeed, today, IPv6 address information is not included in most root DNS servers. Some good write-ups are already appearing on the subject covering the relevance of this development... Why get excited as there are practically no IPv6 only devices yet, some will bemoan. Well, one can hear a distant rumbling of such devices coming, alongside the mobile internet...
Wide-Area Data Services (WDS), aka "WAN Optimization" is becoming the most effective way to improve application performance while reducing network traffic. In scenarios where there is significant network latency that would otherwise render many applications unusable, WDS can deliver almost LAN-like speed. Where bandwidth constraints exist and there is no practical or economical option, WDS can help reduce network traffic, allowing you to postpone or avoid circuit upgrades altogether. The technology provides the ability to centralize applications and servers, furthering the cost savings on hardware, software licensing, maintenance and the operation of a distributed architecture.
There have been quite a number of recent articles about various IPv6 issues. Thus the question: how far along is the actual IPv6 deployment? This is a quick-and-dirty survey that focuses mainly on the content provider side. What domains were surveyed? Alexa offers country depended TopSites listings. Domains listed are frequently visited by users from that country, not necessarily hosted there...
The Time Square Ball bringing in 2008 had more than 9,500 LED bulbs displaying 16 million colours while consuming power equivalent to about ten toasters. This compares to 600 incandescent and halogen bulbs adorning last year's Ball. Easy to forget that most mobile devices used by Time Square revelers were behind IPv4 NAT's and that always on applications such as Instant Messaging, Push e-mail, VoIP or location based services tend to be electricity guzzlers. It so happens that applications that we want always to be reachable have to keep sending periodic keepalive messages to keep the NAT state active...
There are discussions starting within the Regional Internet Registries (RIRs) about the creation of trading market in IPv4 addresses as we approach the inevitable exhaustion of unallocated addresses. The view being put forward is basically "this is likely to happen anyway and by discussing it now, we can ensure it happens in an orderly way". When I first heard this idea I was a bit surprised. The RIRs are policy based bodies and so a shift to a trading market appears to be an abandonment of that policy base. However I have been partly corrected on that.
We know that the Internet is running out of IPv4 addresses and that some in our community check twice a day Mat Ford's doomsday clock or spend an hour once a week reading the tea leaves based on Geoff Huston's exhaustive data compiled at Potaroo. Like with global warming, there is still a school of thought out there arguing that this running out of IP addresses is just fear mongering and that we are not really running out of IPv4 addresses as a NATted world is more than adequate to run the Internet for the foreseeable future. We know that the Internet is running out of AS...
May 6th 2007: ARIN board of trustees passes a resolution advising the Internet community that migration to a new version of the internet protocol, IPv6, will be necessary to allow continued growth of the internet. June 29th 2007, Puerto Rico: ICANN Board resolution states that: The Board further resolves to work with the Regional Internet Registries and other stakeholders to promote education and outreach, with the goal of supporting the future growth of the Internet by encouraging the timely deployment of IPv6. Oct 26th 2007 at the RIPE 55 meeting in Amsterdam... Nov 15th 2007: IGF meeting, Rio de Janeiro... This is but a small sample of the fast growing visibility IPv6 acquired this year, 2007.
I joined the ICANN board during the December 2004 ICANN meeting in Cape Town. I served for a three year term and stepped down at this last meeting in Los Angeles and didn't run for another term... Before joining ICANN, I thought that ICANN was the only part of the Internet that wasn't really working. I knew that there must be a better way to do what ICANN does, but I couldn't be bothered to figure it out. I'd agree with people who said things like, "it should just be distributed" or "it should just be first come first serve" or "we should just get rid of it." People from ICANN would say, "it's more complicated than that" or "at this point that would be impossible." After being part of the process for three years, I find myself saying those same things...
I hear this has been all over the network operator lists, so here it is for the rest of us. With apologies to Don McLean...