[DNSOP] [Errata Verified] RFC8552 (6551)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 19 April 2021 21:14 UTC

Return-Path: <wwwrun@rfc-editor.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 9BF6A3A40F6; Mon, 19 Apr 2021 14:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 Ou9X2wq9NWvq; Mon, 19 Apr 2021 14:14:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CEA93A276C; Mon, 19 Apr 2021 14:14:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5055CF407B1; Mon, 19 Apr 2021 14:14:22 -0700 (PDT)
To: VirtualJMills@GMail.com, dcrocker@bbiw.net
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: warren@kumari.net, iesg@ietf.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210419211422.5055CF407B1@rfc-editor.org>
Date: Mon, 19 Apr 2021 14:14:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/oFTmQ4iMu_E2dO203pGqDdmeUfs>
Subject: [DNSOP] [Errata Verified] RFC8552 (6551)
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, 19 Apr 2021 21:14:36 -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/eid6551

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

Reported by: Jason Mills <VirtualJMills@GMail.com>
Date Reported: 2021-04-19
Verified by: Warren Kumari (Ops AD) (IESG)

Section: 4

Original Text
-------------
RFC 8552                      DNS AttrLeaf                    March 2019


4.  IANA Considerations

   IANA has established the "Underscored and Globally Scoped DNS Node
   Names" registry.  This section describes the registry, the
   definitions, the initial entries, the use of_ta and _example, and the
   use of [RFC8126] as guidance for expert review.  IANA has also
   updated the "Enumservices Registrations" registry with a pointer to
   this document.

Corrected Text
--------------
RFC 8552                      DNS AttrLeaf                    March 2019


4.  IANA Considerations

   IANA has established the "Underscored and Globally Scoped DNS Node
   Names" registry.  This section describes the registry, the
   definitions, the initial entries, the use of _ta and _example, and the
   use of [RFC8126] as guidance for expert review.  IANA has also
   updated the "Enumservices Registrations" registry with a pointer to
   this document.

Notes
-----
"the use of_ta and _example" is missing a single whitespace before `_ta`, corrected it should read:

"the use of _ta and _example"

--------------------------------------
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