Re: [DNSOP] Priming query transport selection

Florian Weimer <fweimer@bfk.de> Fri, 15 January 2010 14:24 UTC

Return-Path: <fweimer@bfk.de>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A51C3A6AAB for <dnsop@core3.amsl.com>; Fri, 15 Jan 2010 06:24:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 FKHl7k+LuCTK for <dnsop@core3.amsl.com>; Fri, 15 Jan 2010 06:24:05 -0800 (PST)
Received: from mx01.bfk.de (mx01.bfk.de [193.227.124.2]) by core3.amsl.com (Postfix) with ESMTP id 6B8CB3A6AA4 for <dnsop@ietf.org>; Fri, 15 Jan 2010 06:24:03 -0800 (PST)
Received: from mx00.int.bfk.de ([10.119.110.2]) by mx01.bfk.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1NVn5h-0002Xp-UW; Fri, 15 Jan 2010 14:23:57 +0000
Received: by bfk.de with local id 1NVn5j-0003et-D7; Fri, 15 Jan 2010 14:23:59 +0000
To: Jim Reid <jim@rfc1035.com>
References: <201001131823.o0DINxYv068180@stora.ogud.com> <555CFB98-BB21-4AD4-9D4A-3AF3BD98E4B2@rfc1035.com> <D9CCEA0D18D9D5B457A90853@Ximines.local> <631E7931-47D4-4AAF-B2C6-62DA6DA5A4CA@rfc1035.com> <CDE7E0414BC50C42E4FCC54F@Ximines.local> <E87EE584-97B5-4FE8-B47D-21048A702B51@rfc1035.com> <82ockvfqsi.fsf@mid.bfk.de> <8B0DBD24-B956-4689-92B9-A388D0618059@rfc1035.com>
From: Florian Weimer <fweimer@bfk.de>
Date: Fri, 15 Jan 2010 14:23:59 +0000
In-Reply-To: <8B0DBD24-B956-4689-92B9-A388D0618059@rfc1035.com> (Jim Reid's message of "Fri\, 15 Jan 2010 14\:05\:02 +0000")
Message-ID: <82hbqnfnuo.fsf@mid.bfk.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: dnsop@ietf.org, Alex Bligh <alex@alex.org.uk>
Subject: Re: [DNSOP] Priming query transport selection
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2010 14:24:06 -0000

* Jim Reid:

> On 15 Jan 2010, at 13:20, Florian Weimer wrote:
>
>> DO is rather pointless because the priming response cannot be
>> validated anyway (even if ROOT-SERVERS.NET were secure, which is
>> currently not planned).
>
> It's not pointless. Validating the priming response requires two
> operations. The first of these is checking the signature over the root
> zone's NS RRset. Which won't be returned unless the DO bit is set.
> [Let's avoid the rat-hole of a DNSSEC-aware resolver iteratively
> querying for DNSKEYs, RRSIGs and so on.]

I'm not sure this narrow perspective is helpful.  Given the amount of
work required to validate the priming response (which resolvers aren't
required to do until they see a client query for ./IN/NS, similar to
what happens with all the other NS RRsets), it really doesn't matter
if you send a DO=0 query first, to get the addresses (in the
additional section), and then a DO=1 query, to get the signature on
the NS RRset (in the answer section).

-- 
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99