Transition Requirements for IPv6 Customer Edge Routers to support IPv4 as a Service
draft-palet-v6ops-transition-ipv4aas-00

Document Type Replaced Internet-Draft (individual)
Last updated 2018-03-02
Replaced by draft-ietf-v6ops-transition-ipv4aas
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-v6ops-transition-ipv4aas
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-palet-v6ops-transition-ipv4aas-00.txt

Abstract

This document specifies the transition requirements for an IPv6 Customer Edge (CE) router, either provided by the service provider or thru the retail market. Specifically, this document extends the "Basic Requirements for IPv6 Customer Edge Routers" ([RFC7084]) in order to allow the provisioning of IPv6 transition services for the support of IPv4 as a Service (IPv4aaS) by means of new transition mechanisms, which where not available at the time [RFC7084] was published. The document only covers transition technologies for delivering IPv4 in IPv6-only access networks, commonly called IPv4 "as-a-service" (IPv4aaS), as required in a world where IPv4 addresses are no longer available, so hosts in the customer LANs with IPv4-only or IPv6-only applications or devices, requiring to communicate with IPv4-only services at the Internet, are still able to do so.

Authors

Jordi Palet (jordi.palet@theipv6company.com)
Hans Liu (hans.liu@dlinkcorp.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)