RFC 8880: Special Use Domain Name 'ipv4only.arpa'
In plain English — editorial summary, not part of the RFC
NAT64 (Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers) allows client devices using IPv6 to communicate with servers that have only IPv4 connectivity. The specification for how a client discovers its local network's NAT64 prefix (RFC 7050) defines the special name 'ipv4only.arpa' for this purpose. However, in its Domain Name Reservation Considerations section (Section 8.1), that specification (RFC 7050) indicates that the name actually has no particularly special properties that would require special handling. Consequently, despite the well-articulated special purpose of the name, 'ipv4only.arpa' was not recorded in the Special-Use Domain Names registry as a name with special properties. This document updates RFC 7050. It describes the special treatment required and formally declares the special properties of the name. It also adds similar declarations for the corresponding reverse mapping names.
Document record
- Document ID
- RFC8880
- Published
- August 2020
- Authors
- S. Cheshire; D. Schinazi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 17
- Also known as
- —
- Updates:
- RFC 7050
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 9872Recommendations for Discovering IPv6 Prefix Used for IPv6 Address SynthesisCurrent
September 2025
- RFC 9313Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)Current
October 2022
- 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
- RFC 6889Analysis of Stateful 64 TranslationCurrent
April 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?