Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-01.txt

<mohamed.boucadair@orange-ftgroup.com> Thu, 22 October 2009 11:44 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.com>
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 10CF73A6889 for <behave@core3.amsl.com>; Thu, 22 Oct 2009 04:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 kmkOeRDTMPyr for <behave@core3.amsl.com>; Thu, 22 Oct 2009 04:44:33 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by core3.amsl.com (Postfix) with ESMTP id C10D73A6840 for <behave@ietf.org>; Thu, 22 Oct 2009 04:44:32 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 48C5F248408; Thu, 22 Oct 2009 13:44:41 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 2D4D22380E0; Thu, 22 Oct 2009 13:44:41 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.13]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Thu, 22 Oct 2009 13:44:41 +0200
From: mohamed.boucadair@orange-ftgroup.com
To: Christian Huitema <huitema@microsoft.com>, "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>, "ajs@shinkuro.com" <ajs@shinkuro.com>, "behave@ietf.org" <behave@ietf.org>
Date: Thu, 22 Oct 2009 13:44:39 +0200
Thread-Topic: [BEHAVE] I-D Action:draft-ietf-behave-dns64-01.txt
Thread-Index: AQHKUOZcB4qVxczK40+zVvgdVO4zY5ENo/MAgAFHKICAAUzkUIABPuww
Message-ID: <23132_1256211881_4AE045A9_23132_13404_1_94C682931C08B048B7A8645303FDC9F30781B159F8@PUEXCB1B.nanterre.francetelecom.fr>
References: <20091019180002.1AFBE3A692D@core3.amsl.com> <20091019181555.GC9536@shinkuro.com> <18034D4D7FE9AE48BF19AB1B0EF2729F3EF10EF424@NOK-EUMSG-01.mgdnok.nokia.com> <6B55F0F93C3E9D45AF283313B8D342BA211C9BC9@TK5EX14MBXW652.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA211C9BC9@TK5EX14MBXW652.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
x-tm-as-product-ver: SMEX-8.0.0.1259-5.600.1016-16652.007
x-tm-as-result: No--39.951800-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2009.10.22.110924
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-01.txt
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: Thu, 22 Oct 2009 11:44:34 -0000

Dear Christian, all,

FYI, we have submitted a draft to describe the A64 record for IPv4-mapped IPv6 addresses. An updated version of the draft will be submitted soon

	Title           : A64: DNS Resource Record for IPv4-mapped IPv6 Address
	Author(s)       : M. Boucadair, E. Burgey
	Filename        : draft-boucadair-behave-dns-a64-00.txt
	Pages           : 9
	Date            : 2009-10-18

In this context of IPv4-IPv6 interconnection, several solutions have been proposed.  Some of these solutions require the definition of a new IPv4-mapped IPv6 address [I-D.ietf-behave-address-format] which is used to represent an IPv4-only host in an IPv6 realms and the definition of a new mechanism called DNS64 for synthesizing a AAAA record, representing an IPv4-mapped IPv6 address in the DNS system, from the A record representing the IPv4 address of the IPv4-only host [I-D.ietf-behave-dns64].  This IPv4-mapped IPv6 address, when managed by a translator, is to be considered as "fake" address in a DNS system since it is not necessarily assigned to any host's interface qualified by the associated name.  This document defines a new DNS record type and query type to identify IPv4-mapped IPv6 address [I-D.ietf-behave-address-format] from native IPv6 ones.  The new record type and query type aim at helping the remote party to enforce its policies and avoid NAT64 boxes when possible.  Native addresses are to be preferred.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-boucadair-behave-dns-a64-00.txt


Cheers,
Med

 

-----Message d'origine-----
De : behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la part de Christian Huitema
Envoyé : mercredi 21 octobre 2009 18:40
À : teemu.savolainen@nokia.com; ajs@shinkuro.com; behave@ietf.org
Objet : Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-01.txt

> The draft contains question about multihoming:"In particular, how is 
> the multi-homed host supposed to know that a given AAAA is synthetic?".

Wonder about that too. Isn't the best solution to create a new record type, say A4A6, that would contain the mapped addresses of IPv4 only hosts?

-- Christian Huitema



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************