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

Wes Hardaker <wjhns1@hardakers.net> Tue, 14 November 2017 02:02 UTC

Return-Path: <wjhns1@hardakers.net>
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 CF4211200C5 for <dnsop@ietfa.amsl.com>; Mon, 13 Nov 2017 18:02:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_PERMERROR=0.01] 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 pfH-k6XHSCQb for <dnsop@ietfa.amsl.com>; Mon, 13 Nov 2017 18:02:17 -0800 (PST)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B351F128656 for <dnsop@ietf.org>; Mon, 13 Nov 2017 18:02:17 -0800 (PST)
Received: from localhost (unknown [IPv6:2001:67c:1232:144:fd59:400e:83b4:e6de]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 05A2B241E9; Mon, 13 Nov 2017 18:02:14 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Tony Finch <dot@dotat.at>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, dnsop@ietf.org
References: <20171112012835.GA16257@laperouse.bortzmeyer.org> <alpine.DEB.2.11.1711131236140.14243@grey.csi.cam.ac.uk>
Date: Mon, 13 Nov 2017 18:02:11 -0800
In-Reply-To: <alpine.DEB.2.11.1711131236140.14243@grey.csi.cam.ac.uk> (Tony Finch's message of "Mon, 13 Nov 2017 12:36:57 +0000")
Message-ID: <yblmv3psjmk.fsf@wu.hardakers.net>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Ckuo05BzrX982wfLaXSb5-I2Pj8>
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 02:02:19 -0000

Tony Finch <dot@dotat.at> writes:

> Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
>>
>> > It can be included in any error response (SERVFAIL, NXDOMAIN,
>> > REFUSED, etc)
>>
>> It can be argued that NODATA (pseudo rcode, I know) is an "error" as
>> well as NXDOMAIN...
>
> Or, neither of them are errors :-)

We'll remove the restriction in any wording that says it can only be for
errors.  I think there is clear consensus to do so.
-- 
Wes Hardaker
USC/ISI