Thanks for the review, Mahesh!
I fixed the usage of "man", "he", and "traditional" in this PR:
https://github.com/oauthstuff/draft-ietf-oauth-security-topics/pull/99
The term "mastertheses" needs to remain as-is, as it appears only in a
URL(!)
The term "native" is commonly used to describe a specific type of apps,
see https://datatracker.ietf.org/doc/html/rfc8252, and I'd therefore
like to keep it as-is
-Daniel
Am 12.05.24 um 07:31 schrieb Mahesh Jethanandani via Datatracker:
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 tohttps://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 tooauth-le...@ietf.org
_______________________________________________
OAuth mailing list -- oauth@ietf.org
To unsubscribe send an email to oauth-le...@ietf.org
