Benjamin Kaduk has entered the following ballot position for draft-ietf-regext-rdap-sorting-and-paging-18: 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: ---------------------------------------------------------------------- Thanks for the updates in the -18; they look good with one exception: In Section 2.4, I strongly recommend using the word "encode" (and "encoding") instead of "encrypt" (and "encryption") -- it is good to reserve the term "encrypt" for a procedure that applies cryptographic protection. Part of why we are anti-recommending base64 for this usage is because it does not provide cryptographic protection, so it is surprising to use the word "encrypt" to describe it. _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
