Re: [BEHAVE] using IPv4-mapped DNS/DNS64 resolvers for dual-stack/IPv6-only hosts

Zhen Cao <zehn.cao@gmail.com> Tue, 09 March 2010 03:12 UTC

Return-Path: <zehn.cao@gmail.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 639A53A6820 for <behave@core3.amsl.com>; Mon, 8 Mar 2010 19:12:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 0+t+lBUyDb0u for <behave@core3.amsl.com>; Mon, 8 Mar 2010 19:12:58 -0800 (PST)
Received: from mail-yw0-f173.google.com (mail-yw0-f173.google.com [209.85.211.173]) by core3.amsl.com (Postfix) with ESMTP id 036283A6358 for <behave@ietf.org>; Mon, 8 Mar 2010 19:12:57 -0800 (PST)
Received: by ywh3 with SMTP id 3so1447886ywh.31 for <behave@ietf.org>; Mon, 08 Mar 2010 19:12:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=TP73a6KcnEcWTwUbTDupMWBkWOkO3LEy79KYBerTb0I=; b=bVy+WoFLpT2KQIeYF+TBRMHzRridzOwWq5w8bnDoO4/bRdn6zeE+8ZvqgoGvejD9+1 YkJtEWBx8MGoETnSIGF076caRnfUC7fGgrIQNw+Ajkc6oAi8W7xaxyIf8JjQCaJ3Vtek Yl8F2v8ZzgDmla+s/SPfyEn+qasa2N+c/icYI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=hxUa3gz1O8IpHEzqrs1satTkUqLM+I5I1ge/VnOnX0pr3TLMerLpqCMcSwy0fNSJEG YEByx5sT/gMiObnwMb1M6MNVNA0J+2CTk49e22ikHkcCCLeuWqSRMF8bE46I1bEE5j67 PwdX500w4oa8XmJFcozDDqW8Fm6vqQD1vLqks=
MIME-Version: 1.0
Received: by 10.101.36.14 with SMTP id o14mr119023anj.28.1268104377978; Mon, 08 Mar 2010 19:12:57 -0800 (PST)
In-Reply-To: <13cd01caac1e$0cd62e80$c4f0200a@cisco.com>
References: <AcqsFrQAWo81hYVBRbKSjMqPHFKU+w==> <13cd01caac1e$0cd62e80$c4f0200a@cisco.com>
Date: Tue, 09 Mar 2010 11:12:57 +0800
Message-ID: <c549bac51003081912t13150804s6f252e2d51f6c20a@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: behave@ietf.org
Subject: Re: [BEHAVE] using IPv4-mapped DNS/DNS64 resolvers for dual-stack/IPv6-only hosts
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: Tue, 09 Mar 2010 03:12:59 -0000

Late catch-up with one comment on the approach:

if a dual stack host sends a query to first DNS (::ffff:192.0.2.1) but
fails to get any resultsr, it will failover to the second DNS and
there will be the same problem that traffic will be translated via
NAT64?

Thanks,
Zhen

On Sat, Feb 13, 2010 at 4:00 AM, Dan Wing <dwing@cisco.com> wrote:
> A few weeks ago there was an active thread on BEHAVE and 3Gv6@ietf.org,
> worrying about how a network containing a mix of dual-stack hosts and
> IPv6-only hosts would work.  Ideally, to prevent unnecessary address family
> translation, the dual-stack hosts should use a 'normal' DNS resolver and the
> IPv6-only hosts should use a DNS64 resolver.  However, it is difficult to
> detect if a host is dual-stack or is IPv6-only.
>
> So, I wrote an Internet Draft describing details of several approaches that
> had been discussed on the mailing list, and attempted to provide a list of
> advantages/disadvantages to each.
>
>
> While writing them down, I came up with another approach which uses an
> IPv4-mapped address in the list of IPv6 DNS servers.  An IPv6-only host cannot
> use that address, so it would use the next DNS server on the list; a
> dual-stack host can use such a DNS server.  Details are in:
>
> http://tools.ietf.org/html/draft-wing-behave-dns64-config-02#section-3.1
>
> Please comment on this approach.  For whatever it's worth, the idea seems to
> work.
>
> -d
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>