Use case of IPv6 transition in APONF
draft-sun-aponf-openv6-use-cases-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Chongfeng Xie , Qiong Sun , JF Tremblay | ||
| Last updated | 2015-01-02 (Latest revision 2014-07-01) | ||
| 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
The IPv6 transition has been an ongoing process throughout the world due to the exhaustion of the IPv4 address space. However, this transition leads to costly end-to-end network upgrades and poses new challenges of managing a large number of devices with a variety of transitioning protocols. While IPv6 transition tools exist, there are still new issues exist. Operators may need various types of IPv6 transition technologies depending on performance requirements, deployment scenarios, etc. To address these difficulties, a software defined unifying approach would provide a unified way to deploy IPv6 in a cost-effective, flexible manner. This document describes use cases of IPv6 transition (Openv6) and also requirements in APONF architecture.
Authors
Chongfeng Xie
Qiong Sun
JF Tremblay
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)