Use cases for MAP-T
draft-maglione-softwire-map-t-scenarios-05
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Roberta Maglione , Wojciech Dec , Ida Leung , Edwin Mallette | ||
| Last updated | 2015-04-27 (Latest revision 2014-10-24) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
The 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 operational use cases that would benefit from a translation based approach and highlights the operational benefits that a translation based solution would allow.
Authors
Roberta Maglione
Wojciech Dec
Ida Leung
Edwin Mallette
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)