Re: [DNSOP] About draft-ietf-dnsop-extended-error

Viktor Dukhovni <ietf-dane@dukhovni.org> Tue, 14 November 2017 08:47 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2BBD126FB3 for <dnsop@ietfa.amsl.com>; Tue, 14 Nov 2017 00:47:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 sIvSaei4PV1v for <dnsop@ietfa.amsl.com>; Tue, 14 Nov 2017 00:47:30 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE3E2128D3E for <dnsop@ietf.org>; Tue, 14 Nov 2017 00:47:26 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id DFDE27A330A; Tue, 14 Nov 2017 08:47:25 +0000 (UTC)
Date: Tue, 14 Nov 2017 08:47:25 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: dnsop@ietf.org
Message-ID: <20171114084725.GP3322@mournblade.imrryr.org>
Reply-To: dnsop@ietf.org
References: <20171112012835.GA16257@laperouse.bortzmeyer.org> <alpine.DEB.2.11.1711131236140.14243@grey.csi.cam.ac.uk> <yblmv3psjmk.fsf@wu.hardakers.net> <20171114073227.GO3322@mournblade.imrryr.org> <3b429f8e-1046-e70d-ab9f-0ac4ba735232@time-travellers.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <3b429f8e-1046-e70d-ab9f-0ac4ba735232@time-travellers.org>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/VK49db4oXAZbUrsBDLyRmlMCIvA>
Subject: Re: [DNSOP] About draft-ietf-dnsop-extended-error
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 14 Nov 2017 08:47:32 -0000

On Tue, Nov 14, 2017 at 07:56:00AM +0000, Shane Kerr wrote:

> > And indeed unlike actual errors, there is nothing one could possibly
> > add in the form extended "error" diagnostics when returning a NODATA
> > or NXDomain response, these non-error conditions don't require any
> > additional context to aid problem resolution.
> 
> Be careful when you say "nothing ... possibly". ;)
> 
> For example, you could have something like:
> 
> RCODE: SUCCESS (NODATA)
> Extended code: ERRBLACKLIST
> Explanation: "Client blacklisted for IPv6 queries"

Well, once we're in the "lying with DNS" business, we hardly need
to restrict extended diagnostics to errors, we can equally contemplate
them for policy-based answers that don't reflect the authoritative
zone content... :-8

-- 
	Viktor.