IPv6 Addressing of IPv4/IPv6 Translators
draft-ietf-behave-translator-addressing-00
| Document | Type |
Replaced Internet-Draft
(behave WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Huitema , Congxiao Bao , Marcelo Bagnulo , Mohamed Boucadair , Xing Li | ||
| Last updated | 2009-08-27 (Latest revision 2009-08-22) | ||
| Replaces | draft-thaler-behave-translator-addressing | ||
| Replaced by | RFC 6052 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-behave-address-format | |
| Consensus boilerplate | Unknown | ||
| 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 discusses how an individual IPv6 address can be algorithmically translated to a corresponding IPv4 address, and vice versa, using only statically configured information. This technique is used in IPv4/IPv6 translators, as well as other types of proxies and gateways (e.g., for DNS) used in IPv4/IPv6 scenarios.
Authors
Christian Huitema
Congxiao Bao
Marcelo Bagnulo
Mohamed Boucadair
Xing Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)