English:
IPv6 Protocol Stack for BSD Development Project - The Objectives And Outcome of The KAME Project
(Interview of Prof. Jun MURAI, WIDE Project Chair)
The history and success of the KAME project
Comments from the core members as the KAME Project concludes
KAME Project Manifest for Completion R&D for IPv6:The new stage focused on Operations and Applications
The announcement of conclusion of the KAME project
Japanese:
http://www.ipv6style.jp/jp/special/kame/20051121/index.shtml
http://www.ipv6style.jp/jp/special/kame/20051121_1/index.shtml
In "The Internet Protocol Journal, September 2005":
http://www.cisco.com/application/pdf/en/us/guest/about/about/c644/ccmigration_09186a00805320df.pdf
Summary
Network Address Translation (NAT) and CIDR did their jobs and
bought the 10 years needed to get IPv6 standards and products developed.
Now is the time to recognize the end to sustainable growth of the
IPv4-based Internet has arrived and that it is time to move on. IPv6 is
ready as the successor, so the gating issue is attitude. When CIOs make
firm decisions to deploy IPv6, the process is fairly straightforward. Staff
will need to be trained, management tools will need to be enhanced,
routers and operating systems will need to be updated, and IPv6-enabled
versions of applications will need to be deployed. All these steps
will take time - in many cases multiple years. The point of this article
has been to show that the recent consumption rates of IPv4 will not be
sustainable from the central pool beyond this decade, so organizations
would be wise to start the process of planning for an IPv6 deployment
now. Those who delay may find that the IANA pool for IPv4 has run
dry before they have completed their move to IPv6. Although that may
not be a problem for most, organizations that need to acquire additional
IPv4 space to continue growing during the transition could be out
of luck.