Re: [DNSOP] Last Call: <draft-ietf-dnsop-no-response-issue-14.txt> (A Common Operational Problem in DNS Servers - Failure To Communicate.) to Best Current Practice

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 16 December 2019 09:42 UTC

Return-Path: <stephane@laperouse.bortzmeyer.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 2EF01120121 for <dnsop@ietfa.amsl.com>; Mon, 16 Dec 2019 01:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 ruCpHPkjAUQz for <dnsop@ietfa.amsl.com>; Mon, 16 Dec 2019 01:42:21 -0800 (PST)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fe27:3d3f]) (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 DDAD2120112 for <dnsop@ietf.org>; Mon, 16 Dec 2019 01:42:20 -0800 (PST)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id 4D67DA029B; Mon, 16 Dec 2019 10:42:18 +0100 (CET)
Received: by godin (Postfix, from userid 1000) id 099AAEC0B0D; Mon, 16 Dec 2019 10:39:45 +0100 (CET)
Date: Mon, 16 Dec 2019 10:39:45 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: dnsop@ietf.org
Message-ID: <20191216093945.GA14658@laperouse.bortzmeyer.org>
References: <157559763911.16433.13149772616705852561.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <157559763911.16433.13149772616705852561.idtracker@ietfa.amsl.com>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 18.04 (bionic)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/LlHh7_RjyYby1j4_rnvrfkAH6dM>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-no-response-issue-14.txt> (A Common Operational Problem in DNS Servers - Failure To Communicate.) to Best Current Practice
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, 16 Dec 2019 09:42:22 -0000

On Thu, Dec 05, 2019 at 06:00:39PM -0800,
 The IESG <iesg-secretary@ietf.org> wrote 
 a message of 53 lines which said:

> The IESG has received a request from the Domain Name System Operations WG
> (dnsop) to consider the following document: - 'A Common Operational Problem
> in DNS Servers - Failure To Communicate.'
>   <draft-ietf-dnsop-no-response-issue-14.txt> as Best Current Practice

I just tested the dig commands against NSD and Knot. No problem for
NSD but Knot has a discrepancy:

8.1.4 "Testing Unknown Opcodes"

expect: status: NOTIMP

But:

% dig +noedns +noad +opcode=15 +norec +header-only @2001:678:f::1  

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> +noedns +noad +opcode=15 +norec +header-only @2001:678:f::1
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: RESERVED15, status: FORMERR, id: 58770
;; flags: qr; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; Query time: 24 msec
;; SERVER: 2001:678:f::1#53(2001:678:f::1)
;; WHEN: Mon Dec 16 10:28:49 CET 2019
;; MSG SIZE  rcvd: 12

Do we agree that Knot is wrong and the draft is right? Or is FORMERR
acceptable?