CurrentPROPOSED STANDARDIETF stream

RFC 6052: IPv6 Addressing of IPv4/IPv6 Translators

In plain English — editorial summary, not part of the RFC

This document discusses the algorithmic translation of an IPv6 address to a corresponding IPv4 address, and vice versa, using only statically configured information. It defines a well-known prefix for use in algorithmic translations, while allowing organizations to also use network-specific prefixes when appropriate. Algorithmic translation is used in IPv4/IPv6 translators, as well as other types of proxies and gateways (e.g., for DNS) used in IPv4/IPv6 scenarios. [STANDARDS-TRACK]

Document record

Document ID
RFC6052
Published
October 2010
Authors
C. Bao; C. Huitema; M. Bagnulo; M. Boucadair; X. Li
Status
PROPOSED STANDARD
Stream
IETF
Area
tsv
Pages
18
Also known as
Updates:
RFC 4291

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6052-ipv6-addressing-of-ipv4-ipv6-translators