Testing IPv6 Transition Mechanisms to support IPv6 only networks
The United States Government Office of Management and Budget recently announced a memo that directed all agencies to plan for at least 80% of IP-enabled assets on Federal networks to be IPv6-only by the end of FY 2025. This is the first of what will mostly likely be several announcements about network operators moving to IPv6-only networks. As we move to IPv6-only networks operators are looking for ways to help with the transition customers. The IETF has documented several different protocols for this transition which includes MAP-E, MAP-T, DS-Lite, LW4over6, and 464XLAT. These protocols allow for network operators to roll out IPv6-only networks in pieces instead of all at once.
When deploying new protocols into the network, operators need to ensure that devices can interoperate. Developers of the products need to ensure the network devices they are developing meet the requirements of the standards and the network operators.
Both network operators and developers need testing to ensure transitioning to IPv6 networks will have a low impact on the users. Current testing for both Interoperability and Conformance has shown common issues that the community can learn from including fragmentation, configuration, and protocol complexity that can be avoided. This presentation will present the lessons learned during testing of IPv6-only transition technologies.
Speaker(s):
Timothy Winters, QA Cafe
Views : 603
ipv6
