[regext] [Technical Errata Reported] RFC9083 (7093)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 17 August 2022 13:29 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
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 8A0DDC14F720 for <regext@ietfa.amsl.com>; Wed, 17 Aug 2022 06:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id jNd0iz5OV4Uo for <regext@ietfa.amsl.com>; Wed, 17 Aug 2022 06:29:01 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBF8AC14CF0C for <regext@ietf.org>; Wed, 17 Aug 2022 06:29:01 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 6675FEEA39; Wed, 17 Aug 2022 06:29:01 -0700 (PDT)
To: shollenbeck@verisign.com, andy@hxr.us, superuser@gmail.com, francesca.palombini@ericsson.com, galvin@elistx.com, ietf@antoin.nl
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: <20220817132901.6675FEEA39@rfcpa.amsl.com>
Date: Wed, 17 Aug 2022 06:29:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/D3AYphuFLw9qJheVlkcdkg4Qs7Y>
Subject: [regext] [Technical Errata Reported] RFC9083 (7093)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 17 Aug 2022 13:29:05 -0000

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

You may review the report below and at:

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

Section: 4.1

Original Text
The data structure named "rdapConformance" is an array of strings,
each providing a hint as to the specifications used in the construction
of the response.

Corrected Text
The data structure named "rdapConformance" is an array of strings,
each identifying a registered specification used in the construction
of the response.

The original text uses the word "hint", which some people have interpreted to mean "not normative" and/or "can be ignored". This misinterpretation will likely cause significant misunderstanding of the technical specification and might result in faulty implementations if not corrected. The intention and meaning of this sentence is more clearly specified with the corrected text, noting that the array of string identifiers is directly associated with the set of specifications used to construct an RDAP response.

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. 

RFC9083 (draft-ietf-regext-rfc7483bis-05)
Title               : JSON Responses for the Registration Data Access Protocol (RDAP)
Publication Date    : June 2021
Author(s)           : S. Hollenbeck, A. Newton
Category            : INTERNET STANDARD
Source              : Registration Protocols Extensions
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG