Re: A6/DNAME usage guidelines and limits

Carl Perry <caperry@edolnx.net> Wed, 03 April 2002 20:43 UTC

Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15203 for <dnsext-archive@lists.ietf.org>; Wed, 3 Apr 2002 15:43:11 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.35 #1) id 16srOE-000GaY-00 for namedroppers-data@psg.com; Wed, 03 Apr 2002 12:29:54 -0800
Received: from caperry-pc1.isot.com ([208.27.64.66] helo=southern-star-ranch.com) by psg.com with smtp (Exim 3.35 #1) id 16srOD-000GaS-00 for namedroppers@ops.ietf.org; Wed, 03 Apr 2002 12:29:53 -0800
Received: (qmail 20451 invoked by uid 500); 3 Apr 2002 21:59:42 -0000
Date: Wed, 03 Apr 2002 15:59:42 -0600
From: Carl Perry <caperry@edolnx.net>
To: namedroppers@ops.ietf.org
Subject: Re: A6/DNAME usage guidelines and limits
Message-ID: <20020403155942.A30198@onramp.southern-star-ranch.com>
Reply-To: Carl Perry <caperry@edolnx.net>
References: <20020402164751.E19210@connect.com.au>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-md5"; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20020402164751.E19210@connect.com.au>; from nathanj@optimo.com.au on Tue, Apr 02, 2002 at 04:47:51PM +1000
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

On Tue, Apr 02, 2002 at 04:47:51PM +1000, Nathan Jones wrote:
> AAAA Synthesis
> 
>    [RFC2874] discusses making a transition from AAAA to A6 by automatically
>    generating AAAA records from A6 records. Such AAAA synthesis should be
>    viewed as an integral part of DNS support for IPv6, rather than purely
>    a transition mechanism. 
> 
>    A nameserver that offers recursive DNS resolution SHOULD be able to
>    generate AAAA records in response to AAAA queries. This allows devices
>    and other hosts to use a lightweight stub resolver that does not need
>    to know about A6.

I think this is the way to go.  A6 is a good idea, in general.  However,
having the resolver on a client have to perform multiple queries to get
a single name resolved is not a good idea.  End-points in the DNS tree
should be able to ask DNS server/cache systems to provide them an AAAA
answer to a name.  The server/cache should be able to handle AAAA and
A6, and convert A6 records to AAAA responses accordingly.  This gives
the ability for "easy" address renumeration, and a thinner client
resolver profile.  In short, it's the best of both worlds.

-- 
	-Carl Perry
	caperry@edolnx.net

"Deliver yesterday, code today, think tomorrow."