IPv6 Multihoming without Network Address Translation
RFC 7157, “IPv6 Multihoming without Network Address Translation”, is an Informational document published in March 2014 by O. Troan, D. Miles, S. Matsushima, T. Okimoto, D. Wing. The canonical text is published by the RFC Editor.
Abstract
Network Address and Port Translation (NAPT) works well for conserving global addresses and addressing multihoming requirements because an IPv4 NAPT router implements three functions: source address selection, next-hop resolution, and (optionally) DNS resolution. For IPv6 hosts, one approach could be the use of IPv6-to-IPv6 Network Prefix Translation (NPTv6). However, NAT and NPTv6 should be avoided, if at all possible, to permit transparent end-to-end connectivity. In this document, we analyze the use cases of multihoming. We also describe functional requirements and possible solutions for multihoming without the use of NAT in IPv6 for hosts and small IPv6 networks that would otherwise be unable to meet minimum IPv6-allocation criteria. We conclude that DHCPv6-based solutions are suitable to solve the multihoming issues described in this document, but NPTv6 may be required as an intermediate solution.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 7157 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7156 Diameter Support for Proxy Mobile IPv6 Localized Routing
- RFC 7158 The JavaScript Object Notation Data Interchange Format
- RFC 7155 Diameter Network Access Server Application
- RFC 7159 The JavaScript Object Notation Data Interchange Format
- RFC 7154 IETF Guidelines for Conduct
- RFC 7160 Support for Multiple Clock Rates in an RTP Session
- RFC 7153 IANA Registries for BGP Extended Communities
- RFC 7161 Proxy Mobile IPv6 Multicast Handover Optimization by the Subscription Information Acquisition through the LMA