Re: [DNSOP] [dns-operations] dnsop-any-notimp violates the DNS standards

bert hubert <bert.hubert@netherlabs.nl> Mon, 16 March 2015 15:22 UTC

Return-Path: <ahu@xs.powerdns.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DBE11A8854 for <dnsop@ietfa.amsl.com>; Mon, 16 Mar 2015 08:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZuGxVffDOUNt for <dnsop@ietfa.amsl.com>; Mon, 16 Mar 2015 08:22:40 -0700 (PDT)
Received: from xs.powerdns.com (xs.powerdns.com [IPv6:2001:888:2000:1d::2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22BC61A8833 for <dnsop@ietf.org>; Mon, 16 Mar 2015 08:22:40 -0700 (PDT)
Received: from ahu by xs.powerdns.com with local (Exim 4.71) (envelope-from <ahu@xs.powerdns.com>) id 1YXWqk-0003tl-Je; Mon, 16 Mar 2015 16:22:38 +0100
Date: Mon, 16 Mar 2015 16:22:38 +0100
From: bert hubert <bert.hubert@netherlabs.nl>
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
Message-ID: <20150316152238.GA14111@xs.powerdns.com>
References: <20150309110803.4516.qmail@cr.yp.to> <20150309151812.GA14897@xs.powerdns.com> <20150316142350.GB26918@xs.powerdns.com> <5506EE5D.3000408@redbarn.org> <20150316150510.GA21645@xs.powerdns.com> <2CD99057-F799-4288-A0CE-19C7A4A8B1D4@nominet.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <2CD99057-F799-4288-A0CE-19C7A4A8B1D4@nominet.org.uk>
User-Agent: Mutt/1.5.20 (2009-06-14)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/GI_OuI6_sJrYU5UzWWF3feWcq34>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] [dns-operations] dnsop-any-notimp violates the DNS standards
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 16 Mar 2015 15:22:41 -0000

On Mon, Mar 16, 2015 at 03:16:08PM +0000, Ray Bellis wrote:

> Hypothetically, if you're using one of those funky NoSQL-style backends
> where RRs are looked up in a key-value store directly from a (QNAME,
> QTYPE) tuple I can see how supporting QTYPE == ANY would be tricky.

At DNS query rates, you could just query purely based on the name as the
key. You'd have to do so anyhow to determine what kind of NXDOMAIN/NOERROR
response to generate!

Or are we going to flatten that distinction too to ease implementation?

	Bert