The following errata report has been rejected 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/eid7985 -------------------------------------- Status: Rejected Type: Technical Reported by: Gavin Brown <gavin.br...@icann.org> Date Reported: 2024-06-12 Rejected by: Orie Steele (IESG) 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. --VERIFIER NOTES-- 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. -------------------------------------- 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
