PET for IPv6 to IPv4 communication
draft-cui-softwire-pet64-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mingwei Xu , Xing Li , Shengling Wang , Yong Cui , Jianping Wu | ||
| Last updated | 2009-10-19 | ||
| 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
This draft offers a solution using PET for the scenario that an IPv6- only client initiates a communication to an IPv4-only server through IPv6 backbone. In this communication scenario,translation is needed. However, translation work has requirements on the performance (hardware or software) of PET and the size of network that the PET is charge for. This draft introduces the concept of translation preference to express the PET's willing of performing translation according to some policies the network administrators constitute. Through exchanging the Translation preference among PETs, PET framework can decide which PET should act as a translator. In addition, this draft also gives how the PET collaborates with DNS to solve the IPv6-to-IPv4 communication problem.
Authors
Mingwei Xu
Xing Li
Shengling Wang
Yong Cui
Jianping Wu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)