IPv6 Best Practice & Strategies
The following articles are recommended best practice and strategies for the implementation of IPv6.
Eight Security Considerations for IPv6 Deployment
BY DANNY MCPHERSON, VERISIGN CHIEF SECURITY OFFICER
IPv6 represents new territory for most Internet stakeholders, and its roll-out will introduce some unique security challenges. While the following list is by no means comprehensive, it does point to eight considerations and problem areas that the industry will need to address as IPv6 adoption continues. Because we're still in the early stages, the solutions to some of these risks will only come after real-world use leads to proven best practices.
Link: http://verisigninc.com/assets/ipv6-security-considerations.pdf
US Government IPv6 Roadmap (May 2012)
The purpose of this planning guide is to provide United States (U.S.) Federal Government agency leaders with practical and actionable guidance on how to successfully integrate Internet Protocol version 6 (IPv6) throughout their enterprise. This guide has been updated from the original guide published in 2009 to aid in understanding the Federal Government‘s Internet Protocol version 6 (IPv6) history, vision, current goals, and deadlines.
Link: Planning Guide/Roadmap Toward IPv6 Adoption within the U.S. Government
IPv6 Best Current Operational Practices
The IP Best Current Operational Practice (IPBCOP) project will collect the best practices known within the operations community and capture those practices in a series of documents. These “living documents” are peer reviewed by technology experts who actually deploy and manage these environments. We believe the best documentation is when it is based on real-world implementations.
IPv6 Support Required for All IP-Capable Nodes
In April 2012, the IETF released RFC-6540 which recommends the IPv6 support level required for new and upgraded equipment and software. The main recommendations of the document are:
- New IP implementations must support IPv6.
- Updates to current IP implementations should support IPv6.
- IPv6 support must be equivalent or better in quality and functionality when compared to IPv4 support in a new or updated IP implementation.
- New and updated IP networking implementations should support IPv4 and IPv6 coexistence (dual-stack), but must not require IPv4 for proper and complete function.
- Implementers are encouraged to update existing hardware and software to enable IPv6 wherever technically feasible.
Purchasing Guidelines for ICT Equipment (RIPE)
To ensure the smooth and cost-efficient uptake of IPv6 across their networks, it is important that governments and large enterprises specify requirements for IPv6 compatibility when seeking tenders for information and computer technology (ICT) equipment and support. This document is intended to provide a Best Common Practice (BCP) template that can be used by governments or large enterprises when developing tender documents. It can also serve as an aid to those people or organisations interested in tendering for government or enterprise contracts.
Formulating requirements for IPv6 support can be done in several ways. In this document we look at three different options:
Link: http://www.ripe.net/ripe/docs/ripe-501