Re: [BEHAVE] Happy Eyeballs and DNS64 not sending synthetic AAAA RRs

"Dan Wing" <dwing@cisco.com> Thu, 04 August 2011 20:24 UTC

Return-Path: <dwing@cisco.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 166BE11E8077 for <behave@ietfa.amsl.com>; Thu, 4 Aug 2011 13:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.824
X-Spam-Level:
X-Spam-Status: No, score=-103.824 tagged_above=-999 required=5 tests=[AWL=-1.225, BAYES_00=-2.599, 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 qFI3LkrNei9m for <behave@ietfa.amsl.com>; Thu, 4 Aug 2011 13:24:36 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 4A4A521F8A71 for <behave@ietf.org>; Thu, 4 Aug 2011 13:24:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1808; q=dns/txt; s=iport; t=1312489492; x=1313699092; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=TPoSLfFIlqhnpUC378lN+5AE9qXIqTUVNbyFYabwUPU=; b=Rn/Jfe6WukGC2s4wwqf8bsSKA0vZNQHzhWSuDUV4DwItoLPy/G0GrjKQ EGLYkiuRi1fevhWNOtIwh0msHVlZBD3m4YV+BhwSKP27j7U+zd3blPqzK rbaLHv4Mq/KYB/LPO9smgDVEXnjTVI2v0pAONlbWR0uhIleBsawQ7GGxG 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvkAAI3/Ok6rRDoJ/2dsb2JhbABDmA6BbI1wd4FAAQEBAQIBAQEBBQoBFxA0EAcBAwIJDgECBAEBAScHGQ4VCgkIAQEEARILF4dKBKJiAZ5mhkIEh1qcJQ
X-IronPort-AV: E=Sophos;i="4.67,319,1309737600"; d="scan'208";a="9781867"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-4.cisco.com with ESMTP; 04 Aug 2011 20:24:51 +0000
Received: from dwingWS (sjc-vpn2-56.cisco.com [10.21.112.56]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p74KOomw023430; Thu, 4 Aug 2011 20:24:51 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Andrew Sullivan' <ajs@anvilwalrusden.com>, behave@ietf.org
References: <916CE6CF87173740BC8A2CE443096962A6F825@008-AM1MPN1-037.mgdnok.nokia.com> <5667E655-22FD-483B-872C-73F9B8667EEC@viagenie.ca> <20110804190632.GJ38760@shinkuro.com>
In-Reply-To: <20110804190632.GJ38760@shinkuro.com>
Date: Thu, 04 Aug 2011 13:24:50 -0700
Message-ID: <018201cc52e4$901b9690$b052c3b0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcxS2aXNiP2HDGTDTNOEM2zQM2ExQQACnKmw
Content-Language: en-us
Subject: Re: [BEHAVE] Happy Eyeballs and DNS64 not sending synthetic AAAA RRs
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Aug 2011 20:24:37 -0000

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Andrew Sullivan
> Sent: Thursday, August 04, 2011 12:07 PM
> To: behave@ietf.org
> Subject: Re: [BEHAVE] Happy Eyeballs and DNS64 not sending synthetic
> AAAA RRs
> 
> On Thu, Aug 04, 2011 at 02:37:47PM -0400, Marc Blanchet wrote:
> >
> > I'm not sure I get your point. If we are in a DNS64 scenario, the
> network between host and the NAT64, as well as the host itself,  is
> IPv6-only. Therefore, there is no such "fall back using IPv4".
> >
> 
> Right.  Every now and then someone talks about what happens when you
> use DNS64 in a dual stack environment.  The answer is, "Doctor, it
> hurts when I do this."
> 
> Don't do it.
> 
> I get why people want to make DNS64/NAT64 more robust than it may be
> as defined.  But this is an attractive nuisance: it's never really
> going to work all the way anyway.  (The twisty problems of detecting
> the DNS64 are already illustrating this.)

A nuance to this problem is that some networks will have a mix
of hosts:

  (a) IPv4-only, which use a 'normal' DNS server
  (b) dual stack hosts, which use a 'normal' DNS server
  (c) IPv6-only hosts, which use a DNS64 server so they
      can use a NAT64 to visit IPv4-only servers.

http://tools.ietf.org/html/draft-wing-behave-dns64-config-03 discusses
the pros/cons of a bunch of mechanisms to provide the correct DNS
server to all three of those host types.

I don't know if there is interest in this problem.  (But I find it
an interesting problem.)

-d

> A
> 
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave