NAT66: IPv6-to-IPv6 NAT
www.ietf.org › old › 2009There will be IPv6 NAT, and the IETF cannot do anything to prevent it Therefore, we have two choices… Refuse to document IPv6 NAT, don’t offer advice about how to do it Some vendors will simply build IPv4 NA(P)Ts with longer addresses Others will try to make improvements, causing inconsistency Document an IPv6 NAT mechanism (such as NAT66)
NAT66: IPv6-to-IPv6 NAT
https://www.ietf.org/old/2009/proceedings/08nov/slides/behave-14.…NAT66 -- BEHAVE WG, IETF 73 Motivations for NAT66 A few facts.. There is demand from enterprise network operators for IPv6 NAT Vendors are implementing IPv6 NAT products to meet that demand There will be IPv6 NAT, and the IETF cannot do anything to prevent it Therefore, we have two choices… Refuse to document IPv6 NAT, don’t offer advice about how to do it
IPv6-to-IPv6 Network Prefix Translation - Wikipedia
https://en.wikipedia.org/wiki/IPv6-to-IPv6_Network_Prefix_TranslationIPv6-to-IPv6 Network Prefix Translation (NPTv6 or NAT66) is an specification for IPv6 to achieve the address-independence at the network edge, similar to network address translation (NAT) in Internet Protocol version 4. It has fewer architectural problems than traditional IPv4 NAT; it is for example stateless and preserves the reachability attributed to the end-to-end principle. However, the method may not translate embedded IPv6 addresses properly (IPsec can be impacted), and s…
IPv6-to-IPv6 Network Address Translation (NAT66)
tools.ietf.org › id › draft-mrw-nat66-00IPv6-to-IPv6 Network Address Translation (NAT66) draft-mrw-nat66-00.txt Abstract. This document describes a stateless, transport-agnostic IPv6-to-IPv6 Network Address Translation (NAT66) function that provides the address independence benefit associated with IPv4-to-IPv4 NAT (NAT44) while minimizing, but not completely eliminating, the problems associated with NAT44.