[regext] [Editorial Errata Reported] RFC7483 (5666)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 22 March 2019 10:23 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 669FC130DE7 for <regext@ietfa.amsl.com>; Fri, 22 Mar 2019 03:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fz2xMqILH8Dh for <regext@ietfa.amsl.com>; Fri, 22 Mar 2019 03:23:00 -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 8B922126C01 for <weirds@ietf.org>; Fri, 22 Mar 2019 03:23:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4EC0AB80141; Fri, 22 Mar 2019 03:22:52 -0700 (PDT)
To: andy@arin.net, shollenbeck@verisign.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, olaf@nlnetlabs.nl, superuser@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: andy@hxr.us, weirds@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190322102252.4EC0AB80141@rfc-editor.org>
Date: Fri, 22 Mar 2019 03:22:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/2mTP_PVkcGl3Ycaw04LF6QP6TCI>
X-Mailman-Approved-At: Fri, 22 Mar 2019 03:44:34 -0700
Subject: [regext] [Editorial Errata Reported] RFC7483 (5666)
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: Fri, 22 Mar 2019 10:23:03 -0000
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] [Editorial Errata Reported] RFC7483 (566… RFC Errata System
- Re: [regext] [Editorial Errata Reported] RFC7483 … Hollenbeck, Scott