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://www.rfc-editor.org/errata/eid7985 -------------------------------------- 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
