This report should be accepted. The example shown in Figure 33 is described as an "elided example", which means that some response elements have been omitted. However, the example in Figure 32 is also described as an elided example, and it includes an rdapConformance data structure. The two examples should be consistent, and the example in Figure 32 is less likely to confuse a reader.
Scott > -----Original Message----- > From: RFC Errata System <rfc-edi...@rfc-editor.org> > Sent: Wednesday, June 12, 2024 8:55 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 (7986) > > 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/1xCDwdnx1IUo8eajYgx5llsFgjfMUASSCYP0Y3KHFsSMami6TL8 > 2Va45VCyFZvMN7EF710QKGMCX557WnTNuIxuy7w5njLfAs56GE4XGcdH8QI > j9nJCP_NlvqlPYAXlgV00eBEXzPochUlWWr-1jy5-rxFIKc9Y5YDgd4HvjXlO- > uQodIqmtnNjqobfUCHlyoVItV7i1lRcDpGghIs641nZO820h0cRMsTHqT6nvLXq > h9iRwQbZ8UJB8kKio1DcVByVqnfXrux-nRIkDv-_M49qFboPB2DFurC- > yaPuG8ZpM/https%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2Feid7986 > > -------------------------------------- > Type: Technical > Reported by: Gavin Brown <gavin.br...@icann.org> > > Section: 9 > > Original Text > ------------- > The following is an elided example of an entity truncated data. > > { > "objectClassName" : "entity", > "handle" : "ANENTITY", > "roles" : [ "registrant" ], > ... > "entities" : > [ > { > "objectClassName" : "entity", > "handle": "ANEMBEDDEDENTITY", > "roles" : [ "technical" ], > ... > }, > ... > ], > "networks" : > [ > ... > ], > ... > "remarks" : > [ > { > "title" : "Data Policy", > "type" : "object truncated due to unexplainable reason", > "description" : > [ > "Some of the data in this object has been removed." > ], > "links" : > [ > { > "value" : "https://secure- > web.cisco.com/1HYtu9grs5WCFmxh4rv6fCaFDMPppkrjwHyUcRf8IL6jP93bR_ > Vuy1w2txz3oe3Sspu_3qHXO__eu9EoTHLFT3WpbrG8eh-McKeOo8kob- > TBlrwGGI505YHI4VXcf-MkFeUGKj0AYFz2onzDODGAc5yU6QO11FW406KE- > g8DWI0UIILG--AiB0ul5rg-rslIDtlwVob15DAB5zQAEraX5Ecie7neVzzPZE- > BiSpPsirTmu1TYHeMEAzm- > aAgzUDvho1FZmVjWCue_JhAvh_i4A3HBIHFz1KOR4hjqRaqXU9M/https%3A > %2F%2Fexample.net%2Fhelp", > "rel" : "alternate", > "type" : "text/html", > "href" : "https://secure- > web.cisco.com/1Qtuhudhy7fIcu3yJw8CkJPgAeGs_jneFL0vsiGbvHBn7LYPO9R > MAoi1Tb-kifURs- > cLkKlG4wr95MfCe06jfJCj3V0yo8SDKM4UGc11GQnCmKQ1Tu5i77Yxrf- > 3G8Y8ViRC8KSz9gB7YPbozff7pCMprSe6a69kuNcRqpOrlzK- > 0B12HpDD34eiD2O6FPut_F2RQyGYHHAnoA8f5s_sS1ZaBCs0LHvTb8btxtKV- > YDtP2HZy- > 4rgnsO1KZHoWV9qmZ90EV0w2yPJ0JcXxeaQM5WF0oR2MNNwWmDUDFHl > BAw/https%3A%2F%2Fwww.example.com%2Fdata_policy.html" > } > ] > } > ] > } > > > Corrected Text > -------------- > The following is an elided example of an entity truncated data. > > { > "rdapConformance" : > [ > "rdap_level_0" > ], > "objectClassName" : "entity", > "handle" : "ANENTITY", > "roles" : [ "registrant" ], > ... > "entities" : > [ > { > "objectClassName" : "entity", > "handle": "ANEMBEDDEDENTITY", > "roles" : [ "technical" ], > ... > }, > ... > ], > "networks" : > [ > ... > ], > ... > "remarks" : > [ > { > "title" : "Data Policy", > "type" : "object truncated due to unexplainable reason", > "description" : > [ > "Some of the data in this object has been removed." > ], > "links" : > [ > { > "value" : "https://secure- > web.cisco.com/1HYtu9grs5WCFmxh4rv6fCaFDMPppkrjwHyUcRf8IL6jP93bR_ > Vuy1w2txz3oe3Sspu_3qHXO__eu9EoTHLFT3WpbrG8eh-McKeOo8kob- > TBlrwGGI505YHI4VXcf-MkFeUGKj0AYFz2onzDODGAc5yU6QO11FW406KE- > g8DWI0UIILG--AiB0ul5rg-rslIDtlwVob15DAB5zQAEraX5Ecie7neVzzPZE- > BiSpPsirTmu1TYHeMEAzm- > aAgzUDvho1FZmVjWCue_JhAvh_i4A3HBIHFz1KOR4hjqRaqXU9M/https%3A > %2F%2Fexample.net%2Fhelp", > "rel" : "alternate", > "type" : "text/html", > "href" : "https://secure- > web.cisco.com/1Qtuhudhy7fIcu3yJw8CkJPgAeGs_jneFL0vsiGbvHBn7LYPO9R > MAoi1Tb-kifURs- > cLkKlG4wr95MfCe06jfJCj3V0yo8SDKM4UGc11GQnCmKQ1Tu5i77Yxrf- > 3G8Y8ViRC8KSz9gB7YPbozff7pCMprSe6a69kuNcRqpOrlzK- > 0B12HpDD34eiD2O6FPut_F2RQyGYHHAnoA8f5s_sS1ZaBCs0LHvTb8btxtKV- > YDtP2HZy- > 4rgnsO1KZHoWV9qmZ90EV0w2yPJ0JcXxeaQM5WF0oR2MNNwWmDUDFHl > BAw/https%3A%2F%2Fwww.example.com%2Fdata_policy.html" > } > ] > } > ] > } > > > 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 33 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
