RFC 8585: Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a-Service
In plain English — editorial summary, not part of the RFC
This document specifies the IPv4 service continuity requirements for IPv6 Customer Edge (CE) routers that are provided either by the service provider or by vendors who sell through the retail market. Specifically, this document extends the basic requirements for IPv6 CE routers as described in RFC 7084 to allow the provisioning of IPv6 transition services for the support of IPv4-as-a-Service (IPv4aaS) by means of new transition mechanisms. The document only covers IPv4aaS, i.e., transition technologies for delivering IPv4 in IPv6-only access networks. IPv4aaS is necessary because there aren't sufficient IPv4 addresses available for every possible customer/ device. However, devices or applications in the customer Local Area Networks (LANs) may be IPv4-only or IPv6-only and still need to communicate with IPv4-only services on the Internet.
Document record
- Document ID
- RFC8585
- Published
- May 2019
- Authors
- J. Palet Martinez; H. M.-H. Liu; M. Kawashima
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8468IPv4, IPv6, and IPv4-IPv6 Coexistence: Updates for the IP Performance Metrics (IPPM) FrameworkCurrent
November 2018
- RFC 8215Local-Use IPv4/IPv6 Translation PrefixCurrent
August 2017
- RFC 9313Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)Current
October 2022
- RFC 9386IPv6 Deployment StatusCurrent
April 2023
- RFC 7757Explicit Address Mappings for Stateless IP/ICMP TranslationCurrent
February 2016
- RFC 7756Stateless IP/ICMP Translation for IPv6 Internet Data Center Environments (SIIT-DC): Dual Translation ModeCurrent
February 2016
- RFC 7755SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center EnvironmentsCurrent
February 2016
- RFC 6782Wireline Incremental IPv6Current
November 2012
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?