IETF Logo Mail Archive

[DNSOP] [Editorial Errata Reported] RFC8906 (7689)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 26 October 2023 22:30 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
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 5A63DC17C509 for <dnsop@ietfa.amsl.com>; Thu, 26 Oct 2023 15:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmYYMmgwIEeb for <dnsop@ietfa.amsl.com>; Thu, 26 Oct 2023 15:30:51 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0173EC1705FA for <dnsop@ietf.org>; Thu, 26 Oct 2023 15:30:50 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id DFCF5E7C03; Thu, 26 Oct 2023 15:30:50 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: jsoref@gmail.com, marka@isc.org, ray@isc.org, dnsop@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231026223050.DFCF5E7C03@rfcpa.amsl.com>
Date: Thu, 26 Oct 2023 15:30:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/CyqlRgLuzRCaX_kq0i2KSVHfDPs>
Subject: [DNSOP] [Editorial Errata Reported] RFC8906 (7689)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 26 Oct 2023 22:30:55 -0000

The following errata report has been submitted for RFC8906,
"A Common Operational Problem in DNS Servers: Failure to Communicate".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7689

--------------------------------------
Type: Editorial
Reported by: Josh Soref <jsoref@gmail.com>

Section: 8.2.8

Original Text
-------------
expect: DO=1 to be present if an RRSIG is in the response


Corrected Text
--------------
expect: flag: do to be present if ...

Notes
-----
The same section has `expect: flag: aa to be present`, and when running the suggested command, no `DO=1` is shown, which makes the advice unhelpful.

Sample command:
```
$ dig +nocookie +edns=0 +noad +norec +dnssec soa $zone @$server

; <<>> DiG 9.16.44-Debian <<>> +nocookie +edns +noad +norec +dnssec soa powerdns.com @2600:3c03::f03c:91ff:fe55:e54d
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 45268
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 1232
;; QUESTION SECTION:
;powerdns.com.			IN	SOA

;; Query time: 0 msec
;; SERVER: 2600:3c03::f03c:91ff:fe55:e54d#53(2600:3c03::f03c:91ff:fe55:e54d)
;; WHEN: Thu Oct 26 22:26:44 UTC 2023
;; MSG SIZE  rcvd: 41
```

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC8906 (draft-ietf-dnsop-no-response-issue-23)
--------------------------------------
Title               : A Common Operational Problem in DNS Servers: Failure to Communicate
Publication Date    : September 2020
Author(s)           : M. Andrews, R. Bellis
Category            : BEST CURRENT PRACTICE
Source              : Domain Name System Operations
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email