The following errata report has been submitted for RFC9537,
"Redacted Fields in the Registration Data Access Protocol (RDAP) Response".

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

--------------------------------------
Type: Technical
Reported by: James Gould <[email protected]>

Section: 4.2

Original Text
-------------
The "postPath" member MUST be set when the redacted field does exist
in the redacted response for the Redaction by Empty Value Method
(Section 3.2), the Redaction by Partial Value Method
(Section 3.3), and the Redaction by Replacement Value Method
(Section 3.4).

Corrected Text
--------------
The "postPath" member MAY be set when the redacted field does exist
in the redacted response for the Redaction by Empty Value Method
(Section 3.2), the Redaction by Partial Value Method
(Section 3.3), and the Redaction by Replacement Value Method
(Section 3.4).

Notes
-----
The “postPath” member is an OPTIONAL member and this MUST can provide 
confusion.  The intent of this sentence was to outline which of the path 
members (“prePath”, “postPath”, and “replacementPath”) to use when using path 
expressions and not to conflict with the OPTIONAL definition.  All of the path 
expression members are defined as OPTIONAL in the RFC, so this MUST needs be 
changed to a MAY to correct the confusion.

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC9537 (draft-ietf-regext-rdap-redacted-16)
--------------------------------------
Title               : Redacted Fields in the Registration Data Access Protocol 
(RDAP) Response
Publication Date    : March 2024
Author(s)           : J. Gould, D. Smith, J. Kolker, R. Carney
Category            : PROPOSED STANDARD
Source              : Registration Protocols Extensions
Stream              : IETF
Verifying Party     : IESG

_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to