IPv6 Addressing of IPv6/IPv4 Translators
draft-thaler-behave-translator-addressing-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dave Thaler | ||
| Last updated | 2009-08-27 (Latest revision 2009-07-06) | ||
| Replaced by | draft-ietf-behave-translator-addressing | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-behave-translator-addressing | |
| 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 IPv6/IPv4 translators, as well as other types of proxies and gateways (e.g., for DNS) used in IPv6/IPv4 scenarios.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)