IPs Continue To Dwindle
It's widely known, at least within geekdom, that the number of available IP addresses is on a collision course with the number zero. The depletion of the IPv4 address space, and the necessity of migrating to the next-generation IPv6, has been discussed ad infinitum in geek circles since RFC 2460 was published in December 1998.
That discussion has not always been about the best way to resolve the issue, however. The imminence of IPv4 exhaustion has consistently been denied, and its emergent nature downplayed. Indeed, APNIC Director General Paul Wilson's 2003 statement on the subject — describing depletion predictions as "misinformation" and "rumor", while stating that existing IPv4 would suffice for another twenty years — brings to mind the infamously mis-attributed quote "I think there is a world market for maybe five computers."
That the latter missed the mark by several billion is inconsequential for most of us, but that the former was a dozen over certainly isn't. The timeline that once had decades to go has now dropped into counting by months, and the outlook for meeting the deadline isn't good.
Hence the possibility for some surprise — not that it is happening, but how soon. Though estimates vary considerably, many credible sources place the Internet Assigned Numbers Authority's pool at zero by June 2011 — just over a year from now — with the various regional authorities drying up by early 2012. Some predictions, however, place zero hour before the end of this year.
Meanwhile, nobody is finding encouraging numbers on IPv6 implementation. Decimal points feature prominently in most — figures include 0.15%, 0.2%, 0.238%, 0.403%, and a heartening, but probably skewed, 10% - 13%. Perhaps the Mayans did know a thing or two about 2012...
Even though the numbers are low, work is being done to prepare for the inevitable.
Comcast, one of the largest ISPs in the U.S., will be conducting several IPv6 tests in the near future: 6RD (rapid IPv6 deployment) and CMTS tests are scheduled to begin in June, testers have been selected for a check of fiber-based Ethernet for business beginning "soon", and a trial run of DS-Lite (dual-stack lite) planned for an as-yet unannounced date.
Verizon's packet technology director, Jean McManus, highlighted the importance of the experiment: "As a result of this trial, we can begin to validate our strategy for IPv6 migration for the residential market while maintaining service continuity during the transition."
Justin Ryan is a Contributing Editor for Linux Journal.
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
|Introduction to MapReduce with Hadoop on Linux||Jun 05, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Linux Systems Administrator
- Validate an E-Mail Address with PHP, the Right Way
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Introduction to MapReduce with Hadoop on Linux
- RSS Feeds
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?