Murray Kucherawy has entered the following ballot position for draft-ietf-regext-rdap-sorting-and-paging-17: 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: ---------------------------------------------------------------------- I support Roman's DISCUSS point about resolving the JSONPath reference. I'm working the chartering of the proposed "jsonpath" working group, so I'm happy to contribute to resolving this. And a "thank you" to the document shepherd for including this in the writeup. Another possible option is to cite draft-goessner-dispatch-jsonpath, marking it as "work in progress", though I think that's still tricky because we don't know for sure that changes produced by the proposed working group will be fully backward-compatible with what this document requires. I also support Ben's DISCUSS point about multi-sorts. Section 1: A totally minor nit, but I think the reference to RFC 7230 should be up where HTTP is first used. Section 2.2: The ABNF here reminds me that string literals in ABNF are case-insensitive (RFC 5234, Section 2.3). Just wanted to check that "COUNT=fAlSe" is fine here, for example. _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
