Mahesh Jethanandani has entered the following ballot position for draft-ietf-oauth-security-topics-27: 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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-oauth-security-topics/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for writing this document. Just a couple of comments. Using lowercase "not" together with an uppercase RFC2119 keyword is not acceptable usage. Found: "not RECOMMENDED" The IANA review of this document seems to not have concluded yet. Found terminology that should be reviewed for inclusivity; see https://www.rfc-editor.org/part2/#inclusive_language for background and more guidance: * Term "masterthesis"; alternatives might be "active", "central", "initiator", "leader", "main", "orchestrator", "parent", "primary", "server" * Term "man"; alternatives might be "individual", "people", "person" * Term "he"; alternatives might be "they", "them", "their" * Term "traditional"; alternatives might be "classic", "classical", "common", "conventional", "customary", "fixed", "habitual", "historic", "long-established", "popular", "prescribed", "regular", "rooted", "time-honored", "universal", "widely used", "widespread" * Term "native"; alternatives might be "built-in", "fundamental", "ingrained", "intrinsic", "original" _______________________________________________ OAuth mailing list -- oauth@ietf.org To unsubscribe send an email to oauth-le...@ietf.org
