Re: [DNSOP] Priming query transport selection

Jim Reid <jim@rfc1035.com> Wed, 13 January 2010 20:34 UTC

Return-Path: <jim@rfc1035.com>
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 3DCBA3A67FC for <dnsop@core3.amsl.com>; Wed, 13 Jan 2010 12:34:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level:
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=-0.900, 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 skEHrnlOrwjC for <dnsop@core3.amsl.com>; Wed, 13 Jan 2010 12:34:54 -0800 (PST)
Received: from hutch.rfc1035.com (hutch.rfc1035.com [195.54.233.70]) by core3.amsl.com (Postfix) with ESMTP id 551153A68A6 for <dnsop@ietf.org>; Wed, 13 Jan 2010 12:34:54 -0800 (PST)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jim) by hutch.rfc1035.com (Postfix) with ESMTPSA id A588D154283D; Wed, 13 Jan 2010 20:34:49 +0000 (GMT)
Message-Id: <631E7931-47D4-4AAF-B2C6-62DA6DA5A4CA@rfc1035.com>
From: Jim Reid <jim@rfc1035.com>
To: Alex Bligh <alex@alex.org.uk>
In-Reply-To: <D9CCEA0D18D9D5B457A90853@Ximines.local>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 13 Jan 2010 20:34:49 +0000
References: <201001131823.o0DINxYv068180@stora.ogud.com> <555CFB98-BB21-4AD4-9D4A-3AF3BD98E4B2@rfc1035.com> <D9CCEA0D18D9D5B457A90853@Ximines.local>
X-Mailer: Apple Mail (2.936)
Cc: dnsop@ietf.org
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: Wed, 13 Jan 2010 20:34:55 -0000

On 13 Jan 2010, at 20:01, Alex Bligh wrote:

>> An EDNS0 ignorant resolver MUST issue the priming query over UDP.
>
> I presume you mean DNSSEC ignorant.

That's implicit. The language was in Olafur's original text BTW...

If a resolver doesn't speak EDNS0, it can't set the DO bit. Which  
means the authoritative server isn't supposed to send back DNSSEC- 
related RRs. Unless the resolver explicitly queries for those RRtypes.  
Which seems unlikely, particularly in the context of a priming query.  
It would be very odd for a DNS implementation to be DNSSEC-aware and  
not support EDNS0. Then again, the DNS is full of all sorts of  
weirdness and bizarre implementations.