RFC 7051: Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7051
- Published
- November 2013
- Authors
- J. Korhonen; T. Savolainen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7050Discovery of the IPv6 Prefix Used for IPv6 Address SynthesisUpdated
November 2013
- RFC 8219Benchmarking Methodology for IPv6 Transition TechnologiesCurrent
August 2017
- RFC 8683Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise NetworksCurrent
November 2019
- RFC 6889Analysis of Stateful 64 TranslationCurrent
April 2013
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 8880Special Use Domain Name 'ipv4only.arpa'Current
August 2020
- RFC 9313Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)Current
October 2022
- RFC 9872Recommendations for Discovering IPv6 Prefix Used for IPv6 Address SynthesisCurrent
September 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?