Stateless 4Via6 Address Sharing
draft-dec-stateless-4v6-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Wojciech Dec , Rajiv Asati , DENG Hui | ||
| Last updated | 2012-04-16 (Latest revision 2011-10-14) | ||
| 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 presents an overview of the characteristics of stateless 4V6 solutions, alongside a assessment of the issues attributes. The impact of translated or mapped tunnel transport modes is also presented in the broader context of other industry standard reference architectures and existing deployments.
Authors
Wojciech Dec
Rajiv Asati
DENG Hui
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)