IPv6 and Training

The integration of IPv6 must be preceded by training. It’s impossible to execute or even plan an IPv6 transition plan without thoroughly understanding IPv6. Since the initial integration of IPv6 within core infrastructure will provide the building blocks for all other integrations and transitions throughout the entire network, the value of proper IPv6 implementation by trained personnel should not be underestimated. The training phase of an IPv6 integration plan should provide a detailed overview that relevant staff members can master to understand the basics of IPv6 and how it interacts with IPv4 in both dual-stack and tunnel environments. Training should occur well in advance of all other integration phases and, at a minimum, it should address the design, implementation, configuration, and maintenance of IPv6 networks.

Key points:

1. Integration of IPv6 must be preceded by training.
2. Training is key to developing IPv6 operational capability.
3. At a minimum training should address design, implementation, configuration, and maintenance.
4. Train for all aspects of IT.

Basic IPv6 Training – Everyone & Operations
IPv6 Advanced Networking
IPv6 for Enterprise Architects
IPv6 for System Administrators
Application Developer Sessions on IPv6 Coding

11 Things You Should Be Doing

IPv6 is coming whether you and your organization have adequately planned for it or not. Below are 11 things your agency or enterprise should be doing today to meet government mandates or gain a competitive advantage.

1. Create a Training Plan

2. Understand How IPv6 affects your Organization

3. Establish an IPv6 Transition Team or Office

4. Take Inventory of your Equipment and Necessary Upgrades

5. Identify any Software or Application Issues

6. Draft an IPv6 Impact Analysis

7. Establish an IPv6 Transition Plan

8. Evaluate your Existing ISP

9. Set up a IPv6 Test Environment

10. Devise and Implement a Security Policy

11. Develop an IPv6 Procurement Strategy and Policy

Best Practices for Conducting an IPv6 Inventory

  • Gather information about all your IPv4 devices Servers, network equipment, firewalls, desktops and look at applications that ride on that equipment
  • Determine if devices are capable of running IPv6
  • Look at the operating system software they run and then compare to vendor specifications
  • Establish a core team of project managers as most of the data gathering will need to be done manually
  • The Cisco IPv6 Scorecard (available through World Wide Technology), can help gather some of this information

Why is IPv4 so bad?

It’s unanimous: The current Internet Protocol, IPv4, is inadequate for the surging demand for Internet connectivity across every aspect of the global economy. Primarily, it’s because the structure of IPv4 addresses limits how many can be created, but there are security, workload, architecture, and mobile-device-compatibility issues as well.

Today’s IP addresses consist of four numeric sequences separated by periods, like this: 201.65.2.57. That is a 32-bit IP address (four sequences contains 8 bits). Because of the proliferation of IP addresses through the bi-level architecture that assigns IP numbers (to a network and the hosts on that network), the 32-bit addressing schema of Internet Protocol version 4 holds the distinct possibility that those four billion addresses will soon be exhausted.

IPv6 has many benefits

Even after all of the arguments for an IPv6 upgrade are spelled out, the fact of the matter is that IPv4 is being phased out. Any forward-looking enterprise must convert to IPv6 if it wants to maintain a secure, optimized connection to the Internet. It not only allows for practically limitless IP addresses, but it offers remarkable more capability in these areas:

  • Addressing and Routing
  • Security
  • Administrative Workload
  • Support for mobile devices
  • Sophisticated peer-to-peer communication tools