Re: [dnsext] Fwd: djb on NXDOMAIN/NODATA for non-terminals

Paul Vixie <vixie@isc.org> Tue, 29 March 2011 07: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 CCA713A685D for <dnsext@core3.amsl.com>; Tue, 29 Mar 2011 00:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level:
X-Spam-Status: No, score=-2.381 tagged_above=-999 required=5 tests=[AWL=-0.097, BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
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 pBrsbD-LkGup for <dnsext@core3.amsl.com>; Tue, 29 Mar 2011 00:19:03 -0700 (PDT)
Received: from nsa.vix.com (unknown [IPv6:2001:4f8:3:bb:230:48ff:fe5a:2f38]) by core3.amsl.com (Postfix) with ESMTP id DC13C3A67AC for <dnsext@ietf.org>; Tue, 29 Mar 2011 00:19:02 -0700 (PDT)
Received: from nsa.vix.com (localhost [127.0.0.1]) by nsa.vix.com (Postfix) with ESMTP id 76F04A1059 for <dnsext@ietf.org>; Tue, 29 Mar 2011 07:20:38 +0000 (UTC) (envelope-from vixie@isc.org)
From: Paul Vixie <vixie@isc.org>
To: dnsext@ietf.org
In-Reply-To: Your message of "Mon, 28 Mar 2011 15:44:50 MST." <BANLkTikkx4ndK3TpByptuRdtPGuFztm2yA@mail.gmail.com>
References: <AANLkTimCZVyag8+Pv8zJsah2B-C=h3bPJ=DNVVo3agLc@mail.gmail.com> <34319.1301351478@nsa.vix.com> <BANLkTikkx4ndK3TpByptuRdtPGuFztm2yA@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3; XEmacs 21.4 (patch 22)
Date: Tue, 29 Mar 2011 07:20:38 +0000
Message-ID: <65033.1301383238@nsa.vix.com>
Subject: Re: [dnsext] Fwd: djb on NXDOMAIN/NODATA for non-terminals
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: Tue, 29 Mar 2011 07:19:03 -0000

> Date: Mon, 28 Mar 2011 15:44:50 -0700
> From: Matthew Dempsky <matthew@dempsky.org>
> 
> You're mischaracterizing the argument.  The concern is that servers
> that follow the old behavior are still in widespread use, and suddenly
> changing the interpretation will cause massive backwards compatibility
> problems.

i don't think so.  nobody is querying intersticial names from an rbl so
even if there were millions of rbldnsd servers running on autopilot it
would not have an operational effect.  but there are at best thousands
of rbldnsd servers and none of them are on autopilot.  tinydns may have
a larger installed base, but there are very few empty nonterminals in
the tinydns datasets i have seen.  there just is no "widespread use" of
the "old behaviour".

> Just tie the new behavior to an EDNS option or something.  No one's
> going to protest that.

if it would take a wire protocol change then it's not a clarification
and i don't think anybody would say it was worth adding complexity for.
(not even me.)