Éric Vyncke has entered the following ballot position for draft-ietf-regext-rdap-sorting-and-paging-16: 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-sorting-and-paging/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for the work put into this document. Please find below a couple of non-blocking COMMENT points (but, to be honest, I was close to put a DISCUSS about server performance impact that is not fully addressed in the security section). I hope that this helps to improve the document, Regards, -éric == COMMENTS == -- Section 2.1 -- I find the wording a little confusing in ""totalCount": "Numeric" (OPTIONAL) ... It MUST be provided if and only if ...". While I understand the meaning, would another wording avoid the conflicting "OPTIONAL" <-> "MUST" ? I.e., the "OPTIONAL" could possibly be removed. -- Section 2.2 -- I am concerned that a server having to compute "totalCount" (even if only to return the first 10 entries) may spend a lot of time computing this number in the absence of index... The security section does not offer a definitive answer to this issue IMHO. E.g., I would prefer to allow the server to refuse to serve "totalCount" until the last page (and even). -- Section 2.3 -- Is there a reason why RFC 5952 was not used to represent the IPv6 address ? I am concerned that a server having to sort on client-side selection of properties may have a huge performance impact in the absence of relevant DB indexes.The security section does not offer a definitive answer to this issue IMHO. -- Section 2.3.1 -- Is there a reason for this unusual writing of 'ipV4' (uppercase V) ? -- Section 2.4 -- Suggestion: mention that the cursor value is opaque for the client ? == NITS == -- Section 2.2 -- Is a 'figure' element really required for a single line example ? Should the URI be "https://example.com/rdap/domains?name=*example.com&count=true"; (also applicable to section 2.3) _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
