Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a- Service
RFC 8585, “Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a- Service”, is an Informational document published in May 2019 by J. Palet Martinez, H. M.-H. Liu, M. Kawashima. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8585 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8584 Framework for Ethernet VPN Designated Forwarder Election Extensibility
- RFC 8586 Loop Detection in Content Delivery Networks
- RFC 8583 Diameter Load Information Conveyance
- RFC 8587 NFS Version 4.0 Trunking Update
- RFC 8582 Diameter Overload Rate Control
- RFC 8588 Personal Assertion Token Extension for Signature-based Handling of Asserted information using toKENs
- RFC 8581 Diameter Agent Overload and the Peer Overload Report
- RFC 8589 The 'leaptofrogans' URI Scheme