Activity Details

The IPv6-Only Network: DNS64/NAT64/464XLAT


ObjectivesAlthough many visible IPv6 deployment metrics show small-percentage prevalence of IPv6 connectivity, the proportion of popular resources that are available to IPv6 clients on a well-connected dual stack network can exceed 50%. Popular content spheres, such as Google, YouTube NetFlix, Yahoo, Wikipedia, and various CDN offer content over IPv6, and for many users, those providers comprise a large percentage of requested content. If we are at the point of getting IPv4 and IPv6 in similar proportions, the question arises as to whether an organization can make the jump to running an IPv6-only network, and delivering IPv4 as a service. Our experience has shown that a well tuned IPv6-Only network can be indistinguishable from a dual-stack or IPv4-only network. This tutorial provides details into how to build DNS64//NAT64/464XLAT networks, reports on experiences from universities that have already deployed and spent time with such networks, and first-hand experiences of an IPv6-Only wireless network in the tutorial.

This tutorial has been delivered at Internet2 Technology Exchange in 2017 and 2018.

Target AudienceNetwork Engineers
Activity Co-ordinator(s)Dorrel Whinery, University of Hawaii System, USA
Expected No. of Participants:25
Seating ArrangementClassroom
Date:Friday 2019-02-22
Time:13:30 - 15:00
Location:Room 101
Trainer(s):TBD
Agenda
1.  The IPv6-Only Network
Although Dual Stack IPv4/IPv6 networks have proven the validity of IPv6 as an operational protocol, and provided experience for network operators, the application of IPv6 to solving the problems for which it has been designed is becoming a relevant and timely goal. This session shows how some current technologies can be used to build a single protocol, IPv6 network, treating IPv4 as a service, simplifying configuration and reducing network resource requirements. This session will discuss real-world configuration details for various common NAT64, DNS64, 464XLAT, as well as CLAT implementations in OS, browsers, or bump-in-the-wire, and feasibility and relevance of deployment.
TOP