[regext] [Technical Errata Reported] RFC8521 (6310)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 19 October 2020 17:51 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F8213A0FE8 for <regext@ietfa.amsl.com>; Mon, 19 Oct 2020 10:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[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 BJSue08rkfKD for <regext@ietfa.amsl.com>; Mon, 19 Oct 2020 10:51:20 -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 B2ECD3A0FFD for <regext@ietf.org>; Mon, 19 Oct 2020 10:51:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 43DC0F40714; Mon, 19 Oct 2020 10:51:16 -0700 (PDT)
To: shollenbeck@verisign.com, andy@arin.net, superuser@gmail.com, barryleiba@computer.org, ietf@antoin.nl, galvin@elistx.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: shollenbeck@verisign.com, regext@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20201019175116.43DC0F40714@rfc-editor.org>
Date: Mon, 19 Oct 2020 10:51:16 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/ybsXJ9VFjj7SaNL7N7egMKjezFI>
Subject: [regext] [Technical Errata Reported] RFC8521 (6310)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2020 17:51:27 -0000

The following errata report has been submitted for RFC8521,
"Registration Data Access Protocol (RDAP) Object Tagging".

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

--------------------------------------
Type: Technical
Reported by: Scott Hollenbeck <shollenbeck@verisign.com>

Section: 4

Original Text
-------------
RDAP responses that contain values described in this document MUST
   indicate conformance with this specification by including an
   rdapConformance [RFC7483] value of "rdap_objectTag_level_0".  The
   information needed to register this value in the "RDAP Extensions"
   registry is described in Section 5.2.

   The following is an example rdapConformance structure with the
   extension specified.

             "rdapConformance" :
             [
               "rdap_level_0",
               "rdap_objectTag_level_0"
             ]

Corrected Text
--------------
RDAP responses that contain values described in this document MUST
   indicate conformance with this specification by including an
   rdapConformance [RFC7483] value of "rdap_objectTag".  The
   information needed to register this value in the "RDAP Extensions"
   registry is described in Section 5.2.

   The following is an example rdapConformance structure with the
   extension specified.

             "rdapConformance" :
             [
               "rdap_level_0",
               "rdap_objectTag"
             ]

Notes
-----
The value of the rdapConformance tag MUST match the value in the IANA registry, which is "rdap_objectTag".

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8521 (draft-ietf-regext-rdap-object-tag-05)
--------------------------------------
Title               : Registration Data Access Protocol (RDAP) Object Tagging
Publication Date    : November 2018
Author(s)           : S. Hollenbeck, A. Newton
Category            : BEST CURRENT PRACTICE
Source              : Registration Protocols Extensions
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG