RFC 8215: Local-Use IPv4/IPv6 Translation Prefix
In plain English — editorial summary, not part of the RFC
This document reserves the IPv6 prefix 64:ff9b:1::/48 for local use within domains that enable IPv4/IPv6 translation mechanisms.
Document record
- Document ID
- RFC8215
- Published
- August 2017
- Authors
- T. Anderson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8512A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)Current
January 2019
- RFC 6782Wireline Incremental IPv6Current
November 2012
- RFC 8115DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 PrefixesCurrent
March 2017
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 9229IPv4 Routes with an IPv6 Next Hop in the Babel Routing ProtocolCurrent
May 2022
- RFC 6384An FTP Application Layer Gateway (ALG) for IPv6-to-IPv4 TranslationCurrent
October 2011
- RFC 6052IPv6 Addressing of IPv4/IPv6 TranslatorsCurrent
October 2010
- RFC 8219Benchmarking Methodology for IPv6 Transition TechnologiesCurrent
August 2017
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?