Re: [DNSOP] [Ext] Re: Processing error codes in draft-ietf-dnsop-extended-error-10

Wes Hardaker <wjhns1@hardakers.net> Mon, 30 September 2019 23:09 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 7CEE312008F for <dnsop@ietfa.amsl.com>; Mon, 30 Sep 2019 16:09:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 hgkBnzEldvyK for <dnsop@ietfa.amsl.com>; Mon, 30 Sep 2019 16:09:24 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED1AA120077 for <dnsop@ietf.org>; Mon, 30 Sep 2019 16:09:23 -0700 (PDT)
Received: from localhost (unknown [10.0.0.3]) by mail.hardakers.net (Postfix) with ESMTPA id 38BA022DB9; Mon, 30 Sep 2019 16:09:23 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: "dnsop\@ietf.org" <dnsop@ietf.org>
References: <CAMOjQcEtDBR29yKmOTvnx-7B7SmC9pox_kzOCKs4jBMQr1VSTA@mail.gmail.com> <yblblv15wv0.fsf@w7.hardakers.net> <6419da25-924e-8d54-0700-48a4cd6d4d34@icann.org>
Date: Mon, 30 Sep 2019 16:09:23 -0700
In-Reply-To: <6419da25-924e-8d54-0700-48a4cd6d4d34@icann.org> (Paul Hoffman's message of "Mon, 30 Sep 2019 21:40:33 +0000")
Message-ID: <yblimp92xgc.fsf@w7.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rCmn0K6J4N3rvT4GQ-texlNKphM>
Subject: Re: [DNSOP] [Ext] Re: Processing error codes in draft-ietf-dnsop-extended-error-10
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 30 Sep 2019 23:09:26 -0000

Paul Hoffman <paul.hoffman@icann.org> writes:

> Saying "SHOULD NOT" without helping the reading understand the
> implications is dangerous and will lead to lack of
> interoperability. Either this document specifies the exact places
> where an EDE can change the processing of the RCODE, or the current
> MUST NOT wording is correct.

Did you read the new replacement sentence?

      Applications MUST continue to follow requirements from applicable
      specs on how to process RCODEs no matter what EDE values is also
      received.

Is that sufficient?

> Some folks (apparently including the document authors) want to be be
> able to use the presence of an EDE to change the way resolvers act.

Not sure why you think the authors think that.  We've (I think all) been
arguing "this is for debugging".  I do push back on unnecessary MUSTs a
lot of the time, but I think the above text is better and still uses
strong language and indicates precedence goes to other specs.

-- 
Wes Hardaker
USC/ISI