Stateless Address Mapping for IPv4 Residual Deployment (4rd)
draft-despres-softwire-4rd-addmapping-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Xiaohong Deng , Jacni Qin , Simon Perreault , Rémi Després | ||
| Last updated | 2012-02-03 (Latest revision 2011-09-22) | ||
| Replaced by | draft-despres-softwire-4rd-u | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-despres-softwire-4rd-u | |
| 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 a mechanism, the 4rd address mapping, for service providers to offer residual deployment of the IPv4 service across IPv6-only domains. Ease of operation and scalability are due to this address mapping being stateless (no per customer states). IPv4 address sharing is based on exclusive port sets assigned to customers, these sets being algorithmically derived from bits used as port-set identifiers. Features include support of shared IPv4 addresses, same routes for IPv4 as for IPv6, and compatibility with both provider aggregatable and provider-independent IPv4 prefixes. The whole 4rd address mapping or part of it can be used combined with various tunneling and double-translation methods. It can also be used either alone or in parallel with stateful mechanisms used for their flexibility where necessary.
Authors
Xiaohong Deng
Jacni Qin
Simon Perreault
Rémi Després
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)