[dnsext] [Errata Verified] RFC6672 (5298)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 03 August 2023 13:40 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4F6DC151700; Thu, 3 Aug 2023 06:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.866
X-Spam-Level:
X-Spam-Status: No, score=-5.866 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_PASS=-0.001, 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 q6Kh46fuhR9T; Thu, 3 Aug 2023 06:40:29 -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 F088DC1522C2; Thu, 3 Aug 2023 06:40:28 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id C109EE7299; Thu, 3 Aug 2023 06:40:28 -0700 (PDT)
To: pieter.lexis@powerdns.com, scott.rose@nist.gov, wouter@nlnetlabs.nl
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: evyncke@cisco.com, iesg@ietf.org, dnsext@ietf.org, iana@iana.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230803134028.C109EE7299@rfcpa.amsl.com>
Date: Thu, 03 Aug 2023 06:40:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/RUNhXGngbz-e3iKPfXsMXa1ER6w>
Subject: [dnsext] [Errata Verified] RFC6672 (5298)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Aug 2023 13:40:32 -0000

The following errata report has been verified for RFC6672,
"DNAME Redirection in the DNS". 

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

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Pieter Lexis <pieter.lexis@powerdns.com>
Date Reported: 2018-03-2
Verified by: Eric Vyncke (IESG)

Section: 5.3.4.2

Original Text
-------------
   ;; Header: QR AA RCODE=3(NXDOMAIN)
   ;; OPT PSEUDOSECTION:
   ; EDNS: version: 0, flags: do; udp: 4096

   ;; Question
   cee.example.com. IN A
   ;; Authority
   bar.example.com. NSEC dub.example.com. A DNAME
   bar.example.com. RRSIG NSEC [valid signature]

Corrected Text
--------------
   ;; Header: QR AA RCODE=3(NXDOMAIN)
   ;; OPT PSEUDOSECTION:
   ; EDNS: version: 0, flags: do; udp: 4096

   ;; Question
   cee.example.com. IN A
   ;; Authority
   bar.example.com. NSEC dub.example.com. A DNAME RRSIG NSEC
   bar.example.com. RRSIG NSEC [valid signature]

Notes
-----
The NSEC record in the original text would in no case be valid as it denies it's own existence and the existence of the RRSIG, while the text indicates that " the validator can see that it is a BOGUS reply from an attacker that collated existing records from the DNS to create a confusing reply". This indicates that NSEC and RRSIG should be set in the NSEC bitmap

Edit: Thread - https://www.ietf.org/mail-archive/web/dnsext/current/msg13879.html

--------------------------------------
RFC6672 (draft-ietf-dnsext-rfc2672bis-dname-26)
--------------------------------------
Title               : DNAME Redirection in the DNS
Publication Date    : June 2012
Author(s)           : S. Rose, W. Wijngaards
Category            : PROPOSED STANDARD
Source              : DNS Extensions
Area                : Internet
Stream              : IETF
Verifying Party     : IESG