Shimmed IPv4/IPv6 Address Network Translation Interface (SHANTI)
draft-carpenter-shanti-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Brian E. Carpenter | ||
| Last updated | 2007-11-07 | ||
| 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
There is a pragmatic need for a packet-level translation mechanism between IPv4 and IPv6, for scenarios where no other mode of IPv4 to IPv6 interworking is possible. The mechanism defined here uses a shim in both the translator and the IPv6 host to mitigate the problems introduced by stateless translation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)