Re: [dnsext] Failure to add glue MUST cause TC to be set.

Paul Vixie <vixie@isc.org> Sat, 19 February 2011 21:19 UTC

Return-Path: <vixie@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 11FCE3A6FC6 for <dnsext@core3.amsl.com>; Sat, 19 Feb 2011 13:19:52 -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 U7cUikck4yPj for <dnsext@core3.amsl.com>; Sat, 19 Feb 2011 13:19:51 -0800 (PST)
Received: from nsa.vix.com (unknown [IPv6:2001:4f8:3:bb:230:48ff:fe5a:2f38]) by core3.amsl.com (Postfix) with ESMTP id 2BAAE3A6FBE for <dnsext@ietf.org>; Sat, 19 Feb 2011 13:19:51 -0800 (PST)
Received: from nsa.vix.com (localhost [127.0.0.1]) by nsa.vix.com (Postfix) with ESMTP id B21F8A1055 for <dnsext@ietf.org>; Sat, 19 Feb 2011 21:20:25 +0000 (UTC) (envelope-from vixie@isc.org)
From: Paul Vixie <vixie@isc.org>
To: dnsext@ietf.org
In-Reply-To: Your message of "Sun, 20 Feb 2011 08:07:15 +1100." <20110219210716.72943A5602B@drugs.dv.isc.org>
References: <20110219210716.72943A5602B@drugs.dv.isc.org>
X-Mailer: MH-E 8.2; nmh 1.2; XEmacs 21.4 (patch 22)
Date: Sat, 19 Feb 2011 21:20:25 +0000
Message-ID: <11263.1298150425@nsa.vix.com>
Subject: Re: [dnsext] Failure to add glue MUST cause TC to be set.
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: Sat, 19 Feb 2011 21:19:52 -0000

we also need to require that the parent zone contain the addresses of
child glue, since otherwise the parent authority must also be recursive
which is something i think we're trying to move away from.

re:

> We need to make it clear that adding address records here (RFC 1034,
> Section 4.3.2, step 3b) is not optional unlike step 6 where they are
> optional.
> 
>          b. If a match would take us out of the authoritative data,
>             we have a referral.  This happens when we encounter a
>             node with NS RRs marking cuts along the bottom of a
>             zone.
> 
>             Copy the NS RRs for the subzone into the authority
>             section of the reply.  Put whatever addresses are
>             available into the additional section, using glue RRs
>             if the addresses are not available from authoritative
>             data or the cache.  Go to step 4.