The following errata report has been verified for RFC9083, "JSON Responses for the Registration Data Access Protocol (RDAP)".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7094 -------------------------------------- Status: Verified Type: Technical Reported by: Scott Hollenbeck <[email protected]> Date Reported: 2022-08-17 Verified by: Murray Kucherawy (IESG) Section: 2.1 Original Text ------------- If The Registry of the Moon desires to express information not found in this specification, it might select "lunarNIC" as its identifying prefix and insert, as an example, the member named "lunarNIC_beforeOneSmallStep" to signify registrations occurring before the first moon landing and the member named "lunarNIC_harshMistressNotes" that contains other descriptive text. Consider the following JSON response with JSON names, some of which should be ignored by clients without knowledge of their meaning. { "handle" : "ABC123", "lunarNIC_beforeOneSmallStep" : "TRUE THAT!", "remarks" : [ { "description" : [ "She sells sea shells down by the sea shore.", "Originally written by Terry Sullivan." ] } ], "lunarNIC_harshMistressNotes" : [ "In space,", "nobody can hear you scream." ] } Figure 2 Corrected Text -------------- If The Registry of the Moon desires to express information not found in this specification, it might select "lunarNIC_level_0" as its identifying prefix and insert, as an example, the member named "lunarNIC_level_0_beforeOneSmallStep" to signify registrations occurring before the first moon landing and the member named "lunarNIC_level_0_harshMistressNotes" that contains other descriptive text. Consider the following JSON response with JSON names, some of which should be ignored by clients without knowledge of their meaning. { "handle" : "ABC123", "lunarNIC_level_0_beforeOneSmallStep" : "TRUE THAT!", "remarks" : [ { "description" : [ "She sells sea shells down by the sea shore.", "Originally written by Terry Sullivan." ] } ], "lunarNIC_level_0_harshMistressNotes" : [ "In space,", "nobody can hear you scream." ] } Figure 2 Notes ----- The original text uses the string identifier "lunarNIC" as the prefix for an example extension. This is inconsistent with the example given in Section 4.1, where "lunarNIC_level_0" is used as an example of a registered identifier for an RDAP extension. This inconsistency can lead implementers to believe that the registered identifier and the extension prefix can be inconsistent, when the intent of the specification is that they should be consistent. This inconsistency can cause significant misunderstanding of the technical specification and might result in faulty implementations if not corrected. Changing the examples in Section 2.1 aligns the text with the example in Section 4.1, demonstrating that the extension prefix and the registered identifier should be one and the same. -------------------------------------- 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 _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
