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

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 07 November 2019 12:13 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 9F895120143 for <regext@ietfa.amsl.com>; Thu, 7 Nov 2019 04:13:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id sJEIS1JP3FL3 for <regext@ietfa.amsl.com>; Thu, 7 Nov 2019 04:13:39 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BEED12006F for <regext@ietf.org>; Thu, 7 Nov 2019 04:13:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1D07AF40718; Thu, 7 Nov 2019 04:13:20 -0800 (PST)
To: shollenbeck@verisign.com, andy@arin.net, barryleiba@computer.org, aamelnikov@fastmail.fm, adam@nostrum.com, 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: <20191107121320.1D07AF40718@rfc-editor.org>
Date: Thu, 07 Nov 2019 04:13:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/x66zSilgRBSUmlcblND6q4FPUhs>
X-Mailman-Approved-At: Thu, 07 Nov 2019 11:42:06 -0800
Subject: [regext] [Technical Errata Reported] RFC8521 (5896)
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: Thu, 07 Nov 2019 12:13:41 -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:

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

Section: 3

Original Text
The bootstrap service registry for the RDAP service provider space is represented using the structure specified in Section 3 of RFC 7484 [RFC7484].

Corrected Text
The bootstrap service registry for the RDAP service provider space is based on the structure specified in Section 3 of RFC 7484 [RFC7484].

The registry structure specific in RFC 8521 includes an additional contact information field that does not appear in the structure defined in RFC 7484. So, the 8521 registry is not "represented using the structure specified in Section 3 of RFC 7484". It extends the structure with the addition of the contact field.

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