Possible actions to begin with for entering IPv6 era

Internet Protocol Version 6 (IPv6) is no longer a brand new technology. Internet communication system workers like us would be expected to do well on IPv6 deployment, without doubt.

After Microsoft Windows Vista was delivered, however, we could no longer excuse ourselves procrastinating on IPv6 deployment.

In fact, it would be quite difficult now to find non-IPv6-capable client hosts! From computers with FreeBSD, Linux, Microsoft Windows, Apple (OS X), and mobile phones such as Nokia phones (Symbian OS), Windows Mobile, Google Android, and even to game consoles such as Nintendo Wii, Sony Playstation 3, all of them already support IPv6 right now!

We could have lived in a "Pure IPv6" world today, if the Internet were fully ready for IPv6. What a pity!

I list some possible actions to begin with immediately for entering IPv6 era:

• Assign IPv6 Addresses for Subnets
• Remove Non-IPv6-capable Network Components
• Set a Deadline for Basic IPv6 Packet Delivery Function

Assign IPv6 Addresses for Subnets

We should build up an inventory of our existing IPv4 subnets first. After that, we can assign IPv6 subnet addresses for each of them one after one.

Remove Non-IPv6-capable Network Components

We should consult from our vendors whether our components are ready for IPv6 or not. To build a whole new system, stop using non-IPv6-capable products at all!

Set a Deadline for Basic IPv6 Packet Delivery Function

We can start from small goal, and the most important, setting a deadline for it. The goal could be as small as "IPv6 packets can be successfully exchanged among all subnets". This small goal alone would ensure us the existing functions of IPv4 in the new flavor of IPv6 addressing.

After the basics are done, we can start to implement other IPv6-specific functions, one after one.