[DNSOP] [Errata Verified] RFC8552 (7066)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 29 January 2024 18:41 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 21258C151540; Mon, 29 Jan 2024 10:41:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.659
X-Spam-Level:
X-Spam-Status: No, score=-6.659 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, 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 pxx1NHpf9Le3; Mon, 29 Jan 2024 10:41:22 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 2919BC14F6BC; Mon, 29 Jan 2024 10:41:22 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 11BF53E8CF; Mon, 29 Jan 2024 10:41:22 -0800 (PST)
To: bernie@ietf.hoeneisen.ch, dcrocker@bbiw.net
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: warren@kumari.net, iesg@ietf.org, dnsop@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240129184122.11BF53E8CF@rfcpa.amsl.com>
Date: Mon, 29 Jan 2024 10:41:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yGGR69hPKQiSQJb31GDUUj22Ta0>
Subject: [DNSOP] [Errata Verified] RFC8552 (7066)
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: Mon, 29 Jan 2024 18:41:26 -0000

The following errata report has been verified for RFC8552,
"Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves". 

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

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

Reported by: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
Date Reported: 2022-08-02
Verified by: Warren Kumari (Ops AD) (IESG)

Section: 4.1.2.

Original Text
-------------
          | URI        | _dccp                 | [RFC7566]     |

Corrected Text
--------------
         | URI        | _dccp                 | [RFC4340]     |

Notes
-----
Wrong reference. RFC7566 does not even mention "dccp". 

Note that this also has an impact to the IANA registry: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#underscored-globally-scoped-dns-node-names


[ Warren Kumari (Ops AD): Please see the thread for resolution: https://mailarchive.ietf.org/arch/msg/dnsop/WFMXL5dY8sniHwVtkPfcqvWk3nI/

This was added as "part of a list used to "reserve" the names of (transport) protocols, so that constructs like _25._quic.example.com could be constructed where the _name denotes the protocol and not the name of something." . I am requesting that the IANA update the reference to match. ]


--------------------------------------
RFC8552 (draft-ietf-dnsop-attrleaf-16)
--------------------------------------
Title               : Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves
Publication Date    : March 2019
Author(s)           : D. Crocker
Category            : BEST CURRENT PRACTICE
Source              : Domain Name System Operations
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG