An Internet Draft by John Curran (Chairman of ARIN) titled "An Internet Transition Plan" sets out some dates that may be of use within large organizations to establish internal deadlines:
http://www.ietf.org/internet-drafts/draft-jcurran-v6transitionplan-02.txt An Internet Transition Plan John Curran January 30, 2008
The following press release was issued by ARIN:
http://www.arin.net/media/releases/070521-v6-resolution.pdf ARIN Board Advises Internet Community on Migration to IPv6 21 May 2007
The US Government’s Office of Management and Budget (OMB) issued this memo dictating IPv6 compliance within the US Federal Government’s networks by June 30th 2008:
http://www.whitehouse.gov/omb/memoranda/fy2005/m05-22.pdf MEMORANDUM FOR THE CHIEF INFORMATION OFFICERS August 2, 2005
For reference, some major tectonic shifts have already occurred: IPv6 addresses and connectivity were added to the root nameservers on February 8th, 2008:
http://www.iana.org/reports/2008/root-aaaa-announcement.html IPv6 Addresses for the Root Servers 29 January 2008
Internet Corporation for Assigned Names and Numbers (ICANN) followed with its own announcement:
http://www.icann.org/announcements/announcement-04feb08.htm IPv6 Address Added for Root Servers in the Root Zone Addition enhances end-to-end connectivity for IPv6 networks 4 February 2008
Why is this significant? After ICANN and IANA made these announcements, the root nameservers started including IPv6 addresses to queries for addresses and the like. That means that every time a web address, or email is sent and a query touches the root nameservers, there is a potential of an IPv6 address being returned. Today most enterprise and ISP systems will ignore that IPv6 address. At Hurricane Electric, all DNS nameservers are IPv6 enabled and addressable from IPv6 capable networks.
Why create an IPv6 plan when the OMB date turned out to be a soft date and the IPv4 exhaustion dates are just projections?
The value of setting deadlines and creating timelines is to help people within your organization plan accordingly.
For example, be sure to take into account your organization's capital expenditure cycle for core equipment such as routers and firewalls. Often assets such as routers and firewalls are only replaced every 3 to 7 years.
IPv6 at Hurricane Electric © 2008 http://he.net/
Page 5 of 9 April 2008