Design Principles of a Unified Address Format for 4v6
draft-chen-softwire-4v6-add-format-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gang Chen , Zhen Cao | ||
| Last updated | 2012-04-14 (Latest revision 2011-10-12) | ||
| 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
There are heated discussion over the unified address format and mapping algorithm. In order to converge the solutions, it is desirable to discuss the requirements and principles for the design. This document tries to propose practical principles for 4v6 deployment. The requirements have been derived from this deployment consideration. Based on that, a unified address format has been proposed for easying 4v6 solution implementation .
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)