[dnsext] additional section processing for DNAME

JINMEI Tatuya / 神明達哉 <jinmei@isc.org> Fri, 07 January 2011 23:14 UTC

Return-Path: <jinmei@isc.org>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B76313A69CF for <dnsext@core3.amsl.com>; Fri, 7 Jan 2011 15:14:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.6
X-Spam-Level:
X-Spam-Status: No, score=0.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, NO_RELAYS=-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 hMWJA6iH5WCd for <dnsext@core3.amsl.com>; Fri, 7 Jan 2011 15:14:01 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by core3.amsl.com (Postfix) with ESMTP id 44F923A69BC for <dnsext@ietf.org>; Fri, 7 Jan 2011 15:12:54 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 0DCD65F985D; Fri, 7 Jan 2011 23:14:51 +0000 (UTC) (envelope-from jinmei@isc.org)
Received: from jmb.jinmei.org (unknown [IPv6:2001:4f8:3:64:c62c:3ff:fe1f:6c75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 8571D216C3F; Fri, 7 Jan 2011 23:14:49 +0000 (UTC) (envelope-from jinmei@isc.org)
Date: Fri, 07 Jan 2011 15:14:49 -0800
Message-ID: <m2zkrc1f2u.wl%jinmei@isc.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isc.org>
To: scottr.nist@gmail.com, wouter@nlnetlabs.nl
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.1 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Cc: dnsext@ietf.org
Subject: [dnsext] additional section processing for DNAME
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 23:14:01 -0000

Hello,

I have one quick question about draft-ietf-dnsext-rfc2672bis-dname-21.
In its Section 3, the draft states:

   The DNAME RR causes type NS additional section processing.  This
   refers to action at step 6 of the server algorithm outlined in
   section 3.2.

And the "step 6" of section 3.2 is as follows:

   6.  Using local data only, attempt to add other RRs which may be
       useful to the additional section of the query.  Exit.

It's not clear to me what these mean...what's "type NS additional
section processing" (for DNAME RR) in the first place?  Does this
mean, for example, if an authoritative server of "example.com" has the
following DNAME RR:

dname.example.com. DNAME dname.example.org.

and it also happens to have authoritative AAAA or A RRset of
dname.example.org, then the server includes these AAAA/A RRsets in the
additional section?  This doesn't seem to make much sense to me, so I
guess "type NS additional section processing" should mean something
else, but I don't know what it is.

Could you clarify what it is, and what it is for?

Thanks,

(p.s. I spent some time of googling to find the answer myself, and I
noticed this change was introduced in rev 15 of this document around
when there was a WG last call.  So I suspect this is a response to a
last call comment, but I couldn't find the relevant discussion.
Hence this question, at the risk of asking something twice at the same
place)

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.