Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 25
- Abstract
- Hosts and applications may benefit from learning if an IPv6 address is synthesized and if NAT64 and DNS64 are present in a network. This document analyzes all proposed solutions (known at the time of writing) for communicating whether the synthesis is taking place, what address format was used, and what IPv6 prefix was used by the NAT64 and DNS64. These solutions enable both NAT64 avoidance and local IPv6 address synthesis. The document concludes by recommending the standardization of the approach based on heuristic discovery.
- Publication Date
- 2013-11-01
- Status Note
- Informational
- DOI
10.17487/RFC7051- Link
- https://doi.org/10.17487/RFC7051
- Author(s)
- Jouni KorhonenTeemu Savolainen
- Keyword(s)
- NAT64, DNS64, 464XLAT
Latest version of IETF RFC 7051
Document Versions — IETF RFC 7051
-
▶ IETF RFC 7051 (2013-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2326 [Superseded*]
- IETF RFC 2671 [Superseded*]
- IETF RFC 3261 [Active*]
- IETF RFC 3315 [Superseded*]
- IETF RFC 4566 [Superseded*]
- IETF RFC 4848 [Active*]
- IETF RFC 4861 [Active*]
- IETF RFC 5389 [Superseded*]
- IETF RFC 6052 [Active*]
- IETF RFC 6146 [Active*]
- IETF RFC 6147 [Active*]
- IETF RFC 6724 [Active*]
- IETF RFC 7050 [Active*]
Bibliographic Reference(s)
- 3GPP.TS-24.301.201012 — NAS.24.301 EXTERNAL
- Wing, D., "Learning the IPv6 Prefix of a Network's IPv6/ IPv4 Translator", Work in Progress, October 2009. EXTERNAL
- Korhonen, J. and T. Savolainen, "EDNS0 Option for Indicating AAAA Record Synthesis and Format", Work in Progress, February 2011. EXTERNAL
- Venaas, S., Asaeda, H., SUZUKI, S., and T. Fujisaki, "An IPv4 - IPv6 multicast translator", Work in Progress, December 2010. EXTERNAL
- Boucadair, M. and E. Burgey, "A64: DNS Resource Record for IPv4-Embedded IPv6 Address", Work in Progress, September 2010. EXTERNAL
- Carpenter, B., Jiang, S., and Z. Cao, "Problem Statement for Referral", Work in Progress, February 2011. EXTERNAL
- Boucadair, M., Levis, P., Grimault, J., Savolainen, T., and G. Bajko, "Dynamic Host Configuration Protocol (DHCPv6) Options for Shared IP Addresses Solutions", Work in Progress, December 2009. EXTERNAL
- Korhonen, J. and T. Savolainen, "EDNS0 Option for Indicating AAAA Record Synthesis and Format", Work in Progress, July 2010. EXTERNAL
- Venaas, S., Li, X., and C. Bao, "Framework for IPv4/IPv6 Multicast Translation", Work in Progress, June 2011. EXTERNAL
- IETF RFC 3971 [Active*]
- IETF RFC 4033 [Active*]
- IETF RFC 5507 [Active*]
- IETF RFC 6144 [Active*]
- IETF RFC 6891 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7051.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 7051, Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix. Available at https://doi.org/10.17487/RFC7051
Snippet:
IETF RFC 7051, Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix. Available at https://doi.org/10.17487/RFC7051
HTML (ISO 690 compliant)
Preview:
IETF RFC 7051, Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix. Available at https://doi.org/10.17487/RFC7051
Snippet:
<span class="citation"><cite>IETF RFC 7051</cite>, Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix. Available at <a href="https://doi.org/10.17487/RFC7051" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7051</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7051, Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix
doi: 10.17487/RFC7051
url: https://doi.org/10.17487/RFC7051
doi: 10.17487/RFC7051
url: https://doi.org/10.17487/RFC7051
Snippet:
<li> <cite id="bib-rfc7051">IETF RFC 7051</cite>, Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix <span class="doi">10.17487/RFC7051</span> </li>
Referenced By
- IETF RFC 7225 [Active*]
- IETF RFC 7849 [Active*]
- IETF RFC 8683 [Active*]
- IETF RFC 9872 [Active*]