Uses cases for MAP-T
draft-maglione-softwire-map-t-scenarios-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Roberta Maglione , Wojciech Dec | ||
| Last updated | 2013-05-09 (Latest revision 2012-11-05) | ||
| RFC stream | (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
Softwire working group is currently discussing both encapsulation and translation based stateless IPv4/IPv6 solutions in order to be able to provide IPv4 connectivity to customers in an IPv6 only environment. The purpose of this document is to describe some use cases that would take advantage of a translation based solution, by highlighting the operational benefits that a translation based approach would allow.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)