Robert Wilton has entered the following ballot position for draft-ietf-regext-rdap-partial-response-13: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-partial-response/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Hi, Thank you for this document. I have two minor comments: 2.1.2. Representing Subsetting Links "value": "https://example.com/rdap/domains?name=*nr.com &fieldSet=afieldset", Should "afieldset" be "anotherfieldset"? 5. Negative Answers Each request including an empty or unsupported "fieldSet" value MUST produce an HTTP 400 (Bad Request) response code. Optionally, the response MAY include additional information regarding the negative answer in the HTTP entity body. Given the solution suggests that subsetting metadata may be included in positive responses, it might be helpful to also include similar metadata in negative responses. I.e. rather than just stating that a fieldSet is invalid, perhaps there should be a recommendation that the response include the list of possible valid values that fieldSet may take? Regards, Rob _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
