IPv6 Multihoming without Network Address Translation
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 22
- 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.
- Publication Date
- 2014-03-01
- Status Note
- Informational
- DOI
10.17487/RFC7157- Link
- https://doi.org/10.17487/RFC7157
- Author(s)
- Ole TrøanDavid MilesSatoru MatsushimaTadahisa OkimotoDan Wing
- Keyword(s)
- NPTv6
Latest version of IETF RFC 7157
Document Versions — IETF RFC 7157
-
▶ IETF RFC 7157 (2014-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 4191 [Active*]
- IETF RFC 4861 [Active*]
- IETF RFC 6296 [Active*]
- IETF RFC 6724 [Active*]
- IETF RFC 6731 [Active*]
- RFC7078 — RFC7078 EXTERNAL
Bibliographic Reference(s)
- The Broadband Forum, "TR-069, CPE WAN Management Protocol v1.1", Version: Issue 1 Amendment 2, December 2007, < http://www.broadband-forum.org/technical/download/ TR-069_Amendment-2.pdf >. EXTERNAL
- The Broadband Forum, "TR-124, Functional Requirements for Broadband Residential Gateway Devices", Issue: 2, May 2010, < http://www.broadband-forum.org/technical/download/ TR-124_Issue-2.pdf >. EXTERNAL
- IETF RFC 3022 [Active*]
- IETF RFC 3442 [Active*]
- IETF RFC 3582 [Active*]
- IETF RFC 3646 [Active*]
- IETF RFC 4116 [Active*]
- IETF RFC 4218 [Active*]
- IETF RFC 4960 [Superseded*]
- IETF RFC 5206 [Superseded*]
- IETF RFC 5220 [Active*]
- IETF RFC 5245 [Superseded*]
- IETF RFC 5533 [Active*]
- IETF RFC 6106 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7157.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7157, IPv6 Multihoming without Network Address Translation. Available at https://doi.org/10.17487/RFC7157
Snippet:
IETF RFC 7157, IPv6 Multihoming without Network Address Translation. Available at https://doi.org/10.17487/RFC7157
HTML (ISO 690 compliant)
Preview:
IETF RFC 7157, IPv6 Multihoming without Network Address Translation. Available at https://doi.org/10.17487/RFC7157
Snippet:
<span class="citation"><cite>IETF RFC 7157</cite>, IPv6 Multihoming without Network Address Translation. Available at <a href="https://doi.org/10.17487/RFC7157" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7157</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7157, IPv6 Multihoming without Network Address Translation
doi: 10.17487/RFC7157
url: https://doi.org/10.17487/RFC7157
doi: 10.17487/RFC7157
url: https://doi.org/10.17487/RFC7157
Snippet:
<li> <cite id="bib-rfc7157">IETF RFC 7157</cite>, IPv6 Multihoming without Network Address Translation <span class="doi">10.17487/RFC7157</span> </li>
Referenced By
- IETF RFC 7368 [Active*]
- IETF RFC 8028 [Active*]