Protocol Action: 'IPv6 Addressing of IPv4/IPv6 Translators' to Proposed Standard

The IESG <> Mon, 30 August 2010 13:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0803A3A6811; Mon, 30 Aug 2010 06:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.228
X-Spam-Status: No, score=-102.228 tagged_above=-999 required=5 tests=[AWL=0.371, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id I2IMXjS7oR1K; Mon, 30 Aug 2010 06:51:28 -0700 (PDT)
Received: from [] (localhost []) by (Postfix) with ESMTP id A597C3A6822; Mon, 30 Aug 2010 06:51:27 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'IPv6 Addressing of IPv4/IPv6 Translators' to Proposed Standard
X-Test-IDTracker: no
Message-ID: <20100830135127.14760.89557.idtracker@localhost>
Date: Mon, 30 Aug 2010 06:51:27 -0700
Cc: Internet Architecture Board <>, behave mailing list <>, behave chair <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 30 Aug 2010 13:51:30 -0000

The IESG has approved the following document:
- 'IPv6 Addressing of IPv4/IPv6 Translators'
  <draft-ietf-behave-address-format-10.txt> as a Proposed Standard

This document is the product of the Behavior Engineering for Hindrance
Avoidance Working Group.

The IESG contact persons are David Harrington and Lars Eggert.

A URL of this Internet Draft is:

Technical Summary

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.

Working Group Summary

This document represents the WG consensus that accommodates
different approaches for the different scenarios Behave was 
chartered to solve.

Document Quality

This document is not a protocol, but there are implementations in
progress, e.g.
Several vendors are actively implementing the specification.
Special reviewers are listed in the document's acknowledgement section.


Who is the Document Shepherd for this document?  Dave Thaler
Who is the Responsible Area Director?  David Harrington
The document doesn't require IANA experts. 

RFC Editor Note

  Please be sure IPv6 hex addresses are represented in lowercase hex, as per draft-ietf-6man-text-representation.