RFC 6147 on DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
rfc-editor@rfc-editor.org Wed, 27 April 2011 23:34 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F442E087F; Wed, 27 Apr 2011 16:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.029
X-Spam-Level:
X-Spam-Status: No, score=-102.029 tagged_above=-999 required=5 tests=[AWL=-0.029, 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KD7F102lt6+9; Wed, 27 Apr 2011 16:34:01 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 866CCE0838; Wed, 27 Apr 2011 16:33:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 71572E0784; Wed, 27 Apr 2011 16:33:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6147 on DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
From: rfc-editor@rfc-editor.org
Message-Id: <20110427233347.71572E0784@rfc-editor.org>
Date: Wed, 27 Apr 2011 16:33:47 -0700
Cc: behave@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 23:34:01 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6147
Title: DNS64: DNS Extensions for Network
Address Translation from IPv6 Clients to
IPv4 Servers
Author: M. Bagnulo, A. Sullivan,
P. Matthews, I. van Beijnum
Status: Standards Track
Stream: IETF
Date: April 2011
Mailbox: marcelo@it.uc3m.es,
ajs@shinkuro.com,
philip_matthews@magma.ca, iljitsch@muada.com
Pages: 32
Characters: 75103
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-behave-dns64-11.txt
URL: http://www.rfc-editor.org/rfc/rfc6147.txt
DNS64 is a mechanism for synthesizing AAAA records from A records.
DNS64 is used with an IPv6/IPv4 translator to enable client-server
communication between an IPv6-only client and an IPv4-only server,
without requiring any changes to either the IPv6 or the IPv4 node,
for the class of applications that work through NATs. This document
specifies DNS64, and provides suggestions on how it should be
deployed in conjunction with IPv6/IPv4 translators. [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