RFC 9083, "JSON Responses for the Registration Data Access Protocol (RDAP)", June 2021

Errata ID: 7985
Status: Rejected
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Gavin Brown
Date Reported: 2024-06-12
Rejected by: Orie Steele
Date Rejected: 2024-06-13

Section 6 says:

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!"
  ]
}

It should say:

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.

Report New Errata