[BEHAVE] RFC 6052 on IPv6 Addressing of IPv4/IPv6 Translators
rfc-editor@rfc-editor.org Fri, 29 October 2010 05:34 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0880B3A6A26; Thu, 28 Oct 2010 22:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.096
X-Spam-Level:
X-Spam-Status: No, score=-102.096 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B+aPxamoiUOY; Thu, 28 Oct 2010 22:34:33 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id E11243A6A09; Thu, 28 Oct 2010 22:32:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B2232E072F; Thu, 28 Oct 2010 22:34:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20101029053442.B2232E072F@rfc-editor.org>
Date: Thu, 28 Oct 2010 22:34:42 -0700
Cc: behave@ietf.org, rfc-editor@rfc-editor.org
Subject: [BEHAVE] RFC 6052 on IPv6 Addressing of IPv4/IPv6 Translators
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 05:34:37 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6052
Title: IPv6 Addressing of IPv4/IPv6 Translators
Author: C. Bao, C. Huitema,
M. Bagnulo, M. Boucadair,
X. Li
Status: Standards Track
Stream: IETF
Date: October 2010
Mailbox: congxiao@cernet.edu.cn,
huitema@microsoft.com,
marcelo@it.uc3m.es,
mohamed.boucadair@orange-ftgroup.com,
xing@cernet.edu.cn
Pages: 18
Characters: 41849
Updates: RFC4291
I-D Tag: draft-ietf-behave-address-format-10.txt
URL: http://www.rfc-editor.org/rfc/rfc6052.txt
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]
This document is a product of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC