February 5, 2008 8:11 AM PST

ICANN turns on next-gen IP addresses

The great migration from Internet Protocol version 4 to IPv6 has officially begun, after the Internet Corporation for Assigned Names and Numbers added the first addresses to its root servers that conform to the new version.

On Monday, ICANN, which maintains the Internet's addressing systems, said it had for the first time added IPv6 addresses to the appropriate files and databases on six of the world's 13 root server networks--the systems containing the authoritative databases that form a master list of all top-level domain names. Before ICANN did this, those who were using IPv6 had no choice but to run it alongside IPv4, because the root server networks accommodated only IPv4.

"IPv6 will be an essential part (of) our future, and support in the root servers is essential to the growth, stability, and reliability of the public Internet," said the chairman of ICANN's Internet service and connectivity provider constituency, Tony Holmes. "The ISP community welcomes this development as part of the continuing evolution of the public Internet."

Almost all IP addresses currently use the fourth version of the protocol, IPv4, but the length of those addresses limits their number of permutations to around four billion. As more people become connected to the Internet and as more devices are manufactured that can themselves intelligently connect to the Internet, that number is rapidly becoming insufficient.

Businesses are now being urged to start migrating to the sixth version of the Internet protocol--IPv6. Because it uses a longer string of characters, this version makes it possible to have more than 340 trillion trillion trillion possible unique addresses. IPv6 has already been in use for a while in large corporations, where many employees need to be hooked up to a semiprivate network, but ICANN's latest move marks the start of the wider migration.

David Conrad, ICANN's vice president of research, said the addition of IPv6 addresses for the root servers "enhances the end-to-end connectivity for IPv6 networks, and furthers the growth of the global interoperable Internet."

Plan now for shift to IPv6 access
Jay Daley, director of IT for Nominet, the not-for-profit company that runs the .uk registry, said the onus was now on those companies running large Web sites to make the transition to IPv6.

"IPv6 and IPv4 don't interact. If you have an IPv6 client, it can't reach an IPv4 server anywhere," said Daley. "If you really want to see take-up of IPv6, we need the people who run high-volume Web sites to switch over to providing both IPv6 and IPv4 access to them. There are very few sites out there that do that."

Daley explained that all operating systems and most enterprise equipment now supports IPv6 "quite happily," but some low-cost consumer-grade equipment and some applications do not yet support it.

IT managers, said Daley, need to "start planning for how the Web services that they provide will be accessible over IPv6."

"They need to consider using IPv6 when they need any new addresses internally," said Daley. "They must also make sure that they do a repetitive audit over the next few years to make sure their equipment and software supports IPv6. People might be sitting there thinking 'Why do I need to do this?' But it may soon be extremely difficult to get hold of any more IPv4 addresses. It is imperative to ensure you don't suddenly find yourself in a crunch and all of a sudden have to make shift to IPv6 without planning."

Daley also warned that, because IPv4 addresses are now "close to running out," such addresses are likely to become significantly more expensive in the near future.

David Meyer of ZDNet UK reported from London.

See more CNET content tagged:
IPv6, IPv4, address, IP, IP address


Join the conversation!
Add your comment
What is the big push for intra-company network devices to support IPv6 addresses? I thought the plan for IPv6 included routers that could NAT from IPv4 to v6 so we could still use v4 networks interally if we wanted?
Posted by PorkchopXL (1 comment )
Reply Link Flag
IP6 ready is a tough questions to answer.

I guess that the big push is at the time when the IPv4 will be phased out. The related software and hardware (including networking sw & hw) have to be compatible with IPv6.

BTW, if your company has no interaction among other company. That's fine. You can use NAT to solve all the problem. But, if your company like my company running a FTP server and we need to access other company FTP servers for file exchange. That is another story.

That is if our company partner FTP servers has changed to IP6, I mean pure IP6 address scheme, no IPv4 address at all. Then, for those users who need to access this pure IP6 FTP server their PC must have been IP6 ready to recognize the partner IP6 address.

In this case, the software and hardware lie on the path between my company users and our company partner FTP servers must have been somewhat IP6 ready to enable the network connection works. For example, the FTP client as well as the OS must know the IPv6 address in order to build the FTP network connection.
Posted by ithinker (1 comment )
Link Flag
Translation... what's wrong with translation?
If enough IPv4 to IPv6 translation servers were set up, there would be no such problem.

The current problem only resides because of the lack of IPv4 to IPv6 translation servers.

Consider them like NAT servers translating one address scheme to another address scheme. If the number of translation servers were properly set up, the transition would be smooth.

It's because of the lack of such translation servers that we have the current problems.

That said... what part should ICANN play in ensuring that there are enough properly implemented translation/NAT servers?

Posted by wbenton (522 comments )
Reply Link Flag

Join the conversation

Add your comment

The posting of advertisements, profanity, or personal attacks is prohibited. Click here to review our Terms of Use.

What's Hot



RSS Feeds

Add headlines from CNET News to your homepage or feedreader.