I'm inclined to reject this report. The example cited in Figure 28 is described in the text as a "common response body", not a complete RDAP response. The error response body is described in the context of a complete RDAP response in Figure 29, which includes an rdapConformance data structure. As such, the examples in the two figures are fine as-is.
Scott > -----Original Message----- > From: RFC Errata System <rfc-edi...@rfc-editor.org> > Sent: Wednesday, June 12, 2024 8:53 AM > To: Hollenbeck, Scott <shollenb...@verisign.com>; a...@hxr.us; > superu...@gmail.com; orie@transmute.industries; gal...@elistx.com; > i...@antoin.nl > Cc: gavin.br...@icann.org; regext@ietf.org; rfc-edi...@rfc-editor.org > Subject: [EXTERNAL] [Technical Errata Reported] RFC9083 (7985) > > Caution: This email originated from outside the organization. Do not click > links > or open attachments unless you recognize the sender and know the content is > safe. > > 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: > https://secure- > web.cisco.com/1W6ZWGNLzPAZgBK9OlCgZpWyokevhvwHqow41x9OXuZnbq > yDqJWNFQA1oqJLn5q1ahY0X9QjBpFnLNACtmO6fQsf_NaEN57rWmU5iaXw > pZMU1JMhup1mGQ5XFXSevNF_PmPD0eKmWC46xwIikDy6qmca1OX5JloD3 > 7OcwZlPxvtlDNKb_MT_MIsH9670N- > WKLIy3Dworq63g5h6JTWVN_JM4Xyt2eSsEQLbrRWFHzM6BBRo4NQi07bhn5 > lFoWEH2rYsHvVIeQK1QZVbwNkotGC2ywFU3NhJ7r4LaygwX118Y/https%3A > %2F%2Fwww.rfc-editor.org%2Ferrata%2Feid7985 > > -------------------------------------- > Type: Technical > Reported by: Gavin Brown <gavin.br...@icann.org> > > Section: 6 > > Original Text > ------------- > This is an example of the common response body. > > { > "errorCode": 418, > "title": "Your Beverage Choice is Not Available", > "description": > [ > "I know coffee has more ummppphhh.", > "Sorry, dude!" > ] > } > > Corrected Text > -------------- > This is an example of the common response body. > > { > "rdapConformance" : > [ > "rdap_level_0" > ], > "errorCode": 418, > "title": "Your Beverage Choice is Not Available", > "description": > [ > "I know coffee has more ummppphhh.", > "Sorry, dude!" > ] > } > > Notes > ----- > RFC 9083 4.1 states that the rdapConformance data structure MUST appear in > the topmost JSON object of RDAP responses. The example error response > provided in Figure 28 should include the rdapConformance property but does > not. > > 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. > > -------------------------------------- > 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 > Stream : IETF > Verifying Party : IESG _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
