IPv6 Addressing of IPv4/IPv6 Translators

Document Type Replaced Internet-Draft (behave WG)
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
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
plain text pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-behave-address-format
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Christian Huitema (huitema@microsoft.com)
Congxiao Bao (congxiao@cernet.edu.cn)
Marcelo Bagnulo (marcelo@it.uc3m.es)
Mohamed Boucadair (mohamed.boucadair@orange-ftgroup.com)
Xing Li (xing@cernet.edu.cn)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)