Re: [dns-dir] draft-ietf-behave-nat64-discovery-heuristic-13

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 19 February 2013 13:47 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dns-dir@ietfa.amsl.com
Delivered-To: dns-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F33321F8CFB for <dns-dir@ietfa.amsl.com>; Tue, 19 Feb 2013 05:47:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level:
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 zlZmM42+DL8E for <dns-dir@ietfa.amsl.com>; Tue, 19 Feb 2013 05:47:04 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 9B42B21F8D02 for <dns-dir@ietf.org>; Tue, 19 Feb 2013 05:47:04 -0800 (PST)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 490E08A031; Tue, 19 Feb 2013 13:47:03 +0000 (UTC)
Date: Tue, 19 Feb 2013 08:47:02 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Message-ID: <20130219134702.GB22289@mx1.yitter.info>
References: <4518F39EB578034D8C99A9B7776CDBA34C673A@xmb-aln-x04.cisco.com> <20130212192356.GF8091@mx1.yitter.info> <0370390A-9855-4F41-8E1F-05FDA9A875D6@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0370390A-9855-4F41-8E1F-05FDA9A875D6@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dns-dir@ietf.org
Subject: Re: [dns-dir] draft-ietf-behave-nat64-discovery-heuristic-13
X-BeenThere: dns-dir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF DNS directorate discussion list <dns-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-dir>, <mailto:dns-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dns-dir>
List-Post: <mailto:dns-dir@ietf.org>
List-Help: <mailto:dns-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-dir>, <mailto:dns-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2013 13:47:05 -0000

On Tue, Feb 19, 2013 at 08:09:20AM -0500, Ralph Droms wrote:

> One more question: draft-cheshire-dnsext-special-names-03 is in
> ready to publish, waiting in cluster C83.

Oh, interesting.  I thought maybe that document had submerged because
of how it impinges on the relationship with ICANN.  But if it's going
to get published, then. . . 

>  Did you consider section
> 5, Domain Name Reservation Considerations, of that document;
> specifically, although draft-cheshire-dnsext-special-names-03 has
> not yet been published, is it worth the effort to answer the
> questions in section 5?

. . . yes, it is, and no, I didn't consider them.  Note that this
particular name doesn't have any implications for the root zone,
though it does require IANA action to register the name in .arpa.
Here are the answers, in any case:

1.  No, although this is a name in .arpa and therefore is sort of
already marked as special.

2.  Yes.  Any application attempting to perform NAT64 discovery will
query the name.

3.  Yes, to the extent the API or library is affected by NAT64.

4.  No.

5.  No.

6.  This name has effects for operators of NAT64/DNS64, but otherwise
is just another .arpa name.

7.  The registry for .arpa is held at IANA, and only IANA needs to
take action here.

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com