[regext] Fwd: [Editorial Errata Reported] RFC7483 (5666)

Andrew Newton <andy@hxr.us> Fri, 22 March 2019 10:27 UTC

MIME-Version: 1.0
References: <20190322102252.4EC0AB80141@rfc-editor.org>
In-Reply-To: <20190322102252.4EC0AB80141@rfc-editor.org>
From: Andrew Newton <andy@hxr.us>
Date: Fri, 22 Mar 2019 06:27:12 -0400
Message-ID: <CAAQiQRewKPeNZfB6cGmweorT4fNVM1yYUSct8NjH31f39wniTA@mail.gmail.com>
To: Registration Protocols Extensions <regext@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/03DUy0AoS5TwJNfhuPxrdp3TH2o>
Subject: [regext] Fwd: [Editorial Errata Reported] RFC7483 (5666)
Precedence: list

---------- Forwarded message ---------
From: RFC Errata System <rfc-editor@rfc-editor.org>
Date: Fri, Mar 22, 2019 at 6:23 AM
Subject: [Editorial Errata Reported] RFC7483 (5666)
To: <andy@arin.net>, <shollenbeck@verisign.com>, <ben@nostrum.com>,
<aamelnikov@fastmail.fm>, <adam@nostrum.com>, <olaf@nlnetlabs.nl>,
<superuser@gmail.com>
Cc: <andy@hxr.us>, <weirds@ietf.org>, <rfc-editor@rfc-editor.org>


The following errata report has been submitted for RFC7483,
"JSON Responses for the Registration Data Access Protocol (RDAP)".

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

--------------------------------------
Type: Editorial
Reported by: Andrew Newton <andy@hxr.us>

Section: 3

Original Text
-------------
handle:           DNRs and RIRs have registry-unique identifiers that
                     may be used to specifically reference an object
                     instance.  The semantics of this data type as found
                     in this document are to be a registry-unique
                     reference to the closest enclosing object where the
                     value is found.  The data type names "registryId",
                     "roid", "nic-handle", "registrationNo", etc., are
                     terms often synonymous with this data type.  In
                     this document, the term "handle" is used.  The term
                     exposed to users by clients is a presentation issue
                     beyond the scope of this document.

Corrected Text
--------------
handle:           DNRs and RIRs have registry-unique identifiers that
                     may be used to specifically reference an object
                     instance.  The semantics of this data type as found
                     in this document are to be a registry-unique
                     reference to the closest enclosing object where the
                     value is found.  The data type names "registryId",
                     "roid", "nic-handle", "registrationNo", etc., are
                     terms often synonymous with this data type.  In
                     this document, the term "handle" is used.  The term
                     exposed to users by clients is a presentation issue
                     beyond the scope of this document. This value is a
                     simple string.

Notes
-----
All uses of handle in section 5 call "handle" out as being a string,
but if a reader were to only read section 3 they would not know it.

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.

--------------------------------------
RFC7483 (draft-ietf-weirds-json-response-14)
--------------------------------------
Title               : JSON Responses for the Registration Data Access
Protocol (RDAP)
Publication Date    : March 2015
Author(s)           : A. Newton, S. Hollenbeck
Category            : PROPOSED STANDARD
Source              : Web Extensible Internet Registration Data Service
Area                : Applications
Stream              : IETF
Verifying Party     : IESG

[regext] Fwd: [Editorial Errata Reported] RFC7483… Andrew Newton