Transition Requirements for IPv6 Customer Edge Routers
draft-palet-v6ops-rfc7084-bis-transition-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jordi Palet Martinez | ||
| Last updated | 2018-04-20 (Latest revision 2017-10-17) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies the transition requirements for an IPv6 Customer Edge (CE) router. Specifically, this document extends the "Basic Requirements for IPv6-only Customer Edge Routers" ([RFC7084]) in order to allow the provisioning of IPv6 transition services for the hosts attached to it. The document covers several transition technologies, either for delivering IPv6 in IPv4-only access networks and specially for delivering IPv4 "as-a-service" 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 able to do so.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)