RFC 9872: Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis
In plain English — editorial summary, not part of the RFC
On networks providing IPv4-IPv6 translation (RFC 7915), hosts and other endpoints need to know the IPv6 prefix(es) used for translation (the NAT64 prefix (RFC 6052)). This document provides guidelines for NAT64 prefix discovery, specifically recommending obtaining the NAT64 prefix from the Router Advertisement option (RFC 8781) when available.
Document record
- Document ID
- RFC9872
- Published
- September 2025
- Authors
- N. Buraglio; T. Jensen; J. Linkova
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8683Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise NetworksCurrent
November 2019
- 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 8512A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)Current
January 2019
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
- RFC 8219Benchmarking Methodology for IPv6 Transition TechnologiesCurrent
August 2017
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 7051Analysis of Solution Proposals for Hosts to Learn NAT64 PrefixCurrent
November 2013
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?