Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44)
Metadata
- Publisher
- IETF
- Doc Type
- Experimental
- Pages
- 33
- Abstract
- In customer sites having IPv4-only Customer Premises Equipment (CPE), Teredo (RFC 4380, RFC 5991, RFC 6081) provides last-resort IPv6 connectivity. However, because it is designed to work without the involvement of Internet Service Providers, it has significant limitations (connectivity between IPv6 native addresses and Teredo addresses is uncertain; connectivity between Teredo addresses fails for some combinations of NAT types). 6a44 is a complementary solution that, being based on ISP cooperation, avoids these limitations. At the beginning of 6a44 IPv6 addresses, it replaces the Teredo well-known prefix, present at the beginning of Teredo IPv6 addresses, with network-specific /48 prefixes assigned by local ISPs (an evolution similar to that from 6to4 to 6rd (IPv6 Rapid Deployment on IPv4 Infrastructures)). The specification is expected to be complete enough for running code to be independently written and the solution to be incrementally deployed and used. This document defines an Experimental Protocol for the Internet community.
- Publication Date
- 2012-10-01
- Status Note
- Experimental
- DOI
10.17487/RFC6751- Link
- https://doi.org/10.17487/RFC6751
- Author(s)
- Rémi DesprésBrian E. CarpenterDan WingSheng Jiang
- Keyword(s)
- Coexistence, Interworking, Tunnel, Encapsulation, LISP
Latest version of IETF RFC 6751
Document Versions — IETF RFC 6751
-
▶ IETF RFC 6751 (2012-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 792 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2460 [Superseded*]
- IETF RFC 4291 [Active*]
Bibliographic Reference(s)
- de Saint-Exupery, A., "Wind, Sand and Stars", Chapter III (The Tool), 1939. EXTERNAL
- Yamaguchi, J., Shirasaki, Y., Miyakawa, S., Nakagawa, A., and H. Ashida, "NAT444 addressing models", Work in Progress, July 2012. EXTERNAL
- Carpenter, B. and S. Jiang, "Legacy NAT Traversal for IPv6: Simple Address Mapping for Premises Legacy Equipment (SAMPLE)", Work in Progress, June 2010. EXTERNAL
- Despres, R., "Rapid Deployment of Native IPv6 Behind IPv4 NATs (6rd+)", Work in Progress, July 2010. EXTERNAL
- IETF RFC 1918 [Active*]
- IETF RFC 2827 [Active*]
- IETF RFC 3053 [Active*]
- IETF RFC 3056 [Active*]
- IETF RFC 3068 [Superseded*]
- IETF RFC 3704 [Active*]
- IETF RFC 4193 [Active*]
- IETF RFC 4380 [Active*]
- IETF RFC 4443 [Active*]
- IETF RFC 5245 [Superseded*]
- IETF RFC 5569 [Active*]
- IETF RFC 5626 [Active*]
- IETF RFC 5969 [Active*]
- IETF RFC 5991 [Active*]
- IETF RFC 6081 [Active*]
- IETF RFC 6145 [Superseded*]
- IETF RFC 6324 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6751.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 6751, Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44). Available at https://doi.org/10.17487/RFC6751
Snippet:
IETF RFC 6751, Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44). Available at https://doi.org/10.17487/RFC6751
HTML (ISO 690 compliant)
Preview:
IETF RFC 6751, Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44). Available at https://doi.org/10.17487/RFC6751
Snippet:
<span class="citation"><cite>IETF RFC 6751</cite>, Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44). Available at <a href="https://doi.org/10.17487/RFC6751" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6751</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6751, Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44)
doi: 10.17487/RFC6751
url: https://doi.org/10.17487/RFC6751
doi: 10.17487/RFC6751
url: https://doi.org/10.17487/RFC6751
Snippet:
<li> <cite id="bib-rfc6751">IETF RFC 6751</cite>, Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44) <span class="doi">10.17487/RFC6751</span> </li>
Referenced By
- IETF RFC 7059 [Active*]