• IPB194: Naval Gazing at NAT in IPv6 Podcast:Download(87.9MB) |Embed EdHorley TomCoffeen NickBuraglio Ed, Nick, and Tom discuss the need for Network Address Translation v6 to v6 (NAT66). • While Network Prefix Translation (NPTv6) exists, its limitations make it insufficient for real-world business needs. • They also highlight that without a standardized NAT66, the market is forcing vendors to implement their own, hindering widespread IPv6 adoption. • Episode Links: IPv6-to-IPv6 Network Address Translation (NAT66) RFC 6296: IPv6-to-IPv6 Network Prefix Translation Explore our podcasts Join Our Slack Chat all things networking, cloud and security in the Packet Pushers Slack community. • It’s free and open to everyone. • Get Our Weekly Content Summary The free Packet Capture newsletter lists every podcast, video and blog we published that week.
Article Summaries:
- Ed, Nick, and Tom argue that the absence of a standardized Network Address Translation v6 (NAT66) is a key barrier to widespread IPv6 deployment. While Network Prefix Translation (NPTv6) is available, its constraints-such as limited address‑translation flexibility and compatibility issues-make it inadequate for many business environments. The panel notes that, in the current market, vendors are forced to develop proprietary NAT66 solutions, creating fragmentation and slowing adoption. They call for an industry‑wide standard to streamline implementation and accelerate the transition to IPv6.
Sources: