Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

O. Troan, Ed.
D. Miles
S. Matsushima
T. Okimoto
D. Wing

Stream:

IETF

Source:

v6ops (ops)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7157

Discuss this RFC: Send questions or comments to the mailing listv6ops@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7157

Abstract

Network Address and Port Translation (NAPT) works well for conservingglobal addresses and addressing multihoming requirements because anIPv4 NAPT router implements three functions: source addressselection, next-hop resolution, and (optionally) DNS resolution. ForIPv6 hosts, one approach could be the use of IPv6-to-IPv6 NetworkPrefix Translation (NPTv6). However, NAT and NPTv6 should beavoided, if at all possible, to permit transparent end-to-endconnectivity. In this document, we analyze the use cases ofmultihoming. We also describe functional requirements and possiblesolutions for multihoming without the use of NAT in IPv6 for hostsand small IPv6 networks that would otherwise be unable to meetminimum IPv6-allocation criteria. We conclude that DHCPv6-basedsolutions are suitable to solve the multihoming issues described inthis document, but NPTv6 may be required as an intermediate solution.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.