Deployment Considerations for Public 4over6
draft-wu-softwire-public4over6-deployment-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Peng Wu , Qi Sun | ||
| Last updated | 2013-01-10 (Latest revision 2012-07-09) | ||
| 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
Public 4over6 is a stateful transition mechanism which assigns public IPv4 address to CPE/host and uses IPv4-in-IPv6 tunnel. It doesn't involve CGN as in DS-lite and reduces the mapping scale on the Concentrator to per-subscriber level. This document describers deployment models for Public 4over6, and the deployment considerations of the Public 4over6 architecture.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)