Re: [DNSOP] draft-ietf-dnsop-extended-error code options

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 14 November 2017 01:33 UTC

Return-Path: <bortzmeyer@nic.fr>
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 205D5129445 for <dnsop@ietfa.amsl.com>; Mon, 13 Nov 2017 17:33:26 -0800 (PST)
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] 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 AY5PLAOLJWwf for <dnsop@ietfa.amsl.com>; Mon, 13 Nov 2017 17:33:24 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72CF8126E7A for <dnsop@ietf.org>; Mon, 13 Nov 2017 17:33:24 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id E4F4031D12; Tue, 14 Nov 2017 02:33:21 +0100 (CET)
Received: by godin (Postfix, from userid 1000) id 67385EC0BB6; Tue, 14 Nov 2017 02:30:49 +0100 (CET)
Date: Tue, 14 Nov 2017 09:30:49 +0800
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Ray Bellis <ray@bellis.me.uk>
Cc: dnsop@ietf.org
Message-ID: <20171114013049.GA19865@laperouse.bortzmeyer.org>
References: <yblpo9md8fk.fsf@wu.hardakers.net> <CADyWQ+G-e+zqGkFK7vPQdXBDRvyv-Gxw75N1z+A6L8ULR=+izQ@mail.gmail.com> <26DB1BD1-A877-482A-83B3-7A7F673AAB4A@apnic.net> <e9a3bbc4-0c03-b66c-eb2b-a1c1b336424b@bellis.me.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <e9a3bbc4-0c03-b66c-eb2b-a1c1b336424b@bellis.me.uk>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 16.04 (xenial)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zewqnQ93XyzCzbgHGd8vxi2v6X0>
Subject: Re: [DNSOP] draft-ietf-dnsop-extended-error code options
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 01:33:26 -0000

On Mon, Nov 13, 2017 at 08:54:16PM +0800,
 Ray Bellis <ray@bellis.me.uk> wrote 
 a message of 29 lines which said:

> Would it be feasible to reserve a standard RCODE value in the header
> that just means "see extended error"?

First reaction: no. Middleboxes would block these responses, or old
clients would not know what to do with it.