Re: [dnsext] WG opinion on draft : Improvements to DNS Resolvers, for Resiliency, Robustness, and Responsiveness

Brian Dickson <brian.peter.dickson@gmail.com> Wed, 23 February 2011 17:10 UTC

Return-Path: <brian.peter.dickson@gmail.com>
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 EE6463A68C5 for <dnsext@core3.amsl.com>; Wed, 23 Feb 2011 09:10:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 NXY4qdIm12Pq for <dnsext@core3.amsl.com>; Wed, 23 Feb 2011 09:10:16 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id DD4E53A67A1 for <dnsext@ietf.org>; Wed, 23 Feb 2011 09:10:15 -0800 (PST)
Received: by fxm15 with SMTP id 15so5094858fxm.31 for <dnsext@ietf.org>; Wed, 23 Feb 2011 09:11:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=wVvgmMoedhyfuMQXvY+O1AGIephljF5C9o6nJwO650k=; b=SUcTiuYmyRtVQeaClviHzh7jqb6K+WZ+2CzmA+pksxCFD1BEvnOwsSLrtTAaLx70UH dGm5oEkuxBaPvtkBam9lGTsvpiW8unAo4Nx0JN+y4MtxcKnTb5NREYUESgSkroyxq9cV JUb8SpiDYOnXVU4l8s7+ouah8QSiCZ2cgOckI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=iOSrc8zp+wZ2tsCM/dC9xAjEO6IXcpLkKyLBwOuQ4gFVrcwvHIsFLP+sONP5ljYk+/ cfdvtcMhSGrzQ7gbmU/gpdBzZ4KeURb8Iube7Lfd85pFaQwDC/j0dxD/cKGo6ODR2YxI 1Fxl1tcA/3cgGZe+QD0HXetmyLR08lGE13VI0=
MIME-Version: 1.0
Received: by 10.223.114.209 with SMTP id f17mr5335004faq.136.1298479976470; Wed, 23 Feb 2011 08:52:56 -0800 (PST)
Received: by 10.223.107.132 with HTTP; Wed, 23 Feb 2011 08:52:56 -0800 (PST)
In-Reply-To: <82ei6yu3ja.fsf@mid.bfk.de>
References: <4D622624.90303@ogud.com> <BF79BE89-20B2-4897-B07C-1426745C4AA9@verisign.com> <AANLkTinQig=e7wv-3GsXi73p3AKQOsbjE6EzDNMbWWRw@mail.gmail.com> <4D63907A.8010700@nlnetlabs.nl> <82zkpnyt3z.fsf@mid.bfk.de> <22348.1298455916@nsa.vix.com> <82ei6zyqqz.fsf@mid.bfk.de> <39328.1298474414@nsa.vix.com> <82y656u4zb.fsf@mid.bfk.de> <82ei6yu3ja.fsf@mid.bfk.de>
Date: Wed, 23 Feb 2011 12:52:56 -0400
Message-ID: <AANLkTimf7B9J8eHsqeZ6dZ4bhG0it4ttXPKbfBYGataS@mail.gmail.com>
From: Brian Dickson <brian.peter.dickson@gmail.com>
To: Florian Weimer <fweimer@bfk.de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: dnsext@ietf.org
Subject: Re: [dnsext] WG opinion on draft : Improvements to DNS Resolvers, for Resiliency, Robustness, and Responsiveness
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: Wed, 23 Feb 2011 17:10:17 -0000

On Wed, Feb 23, 2011 at 12:19 PM, Florian Weimer <fweimer@bfk.de> wrote:
> * Florian Weimer:
>
>>> nlnetlabs nsd and verisign atlas both understood the spec in this
>>> regard also.
>>
>> Actually, ATLAS sent NXDOMAIN instead of NODATA for existing,
>> non-delegated names with a missing RRset (that is, empty terminals) at
>> one point in the not too-distant past.  I don't remember if they
>> implemented the old BIND behavior, too, but it would be odd to send
>> NXDOMAIN for empty terminals, and NODATA for empty non-terminals.
>
> Off-list, I was told that my terminology is off, which is true.
> Please read "empty RRsets" for "empty terminals".

So, this is an interesting data point, arguably in support of Paul,
because of the following:
- it was clearly broken behavior (really, really broken)
- you won't find a shorter tail than that - the vendor *is* the *only*
user of the software (!!)
- it helps illustrate the difference between NODATA and NXDOMAIN (and
when the latter is the wrong answer)
- wow - see point 1 :-)
- it shows that regardless of deployment scope, there should be
pressure to fix broken deployments, rather than to ankylose (rigidly
anchor, forever) that broken-ness into the specifications (IMHO)

Brian