Hi Med,
Thanks for your review. I merged your nit, and opened
https://github.com/oauth-wg/draft-ietf-oauth-rfc8725bis/issues/68 for
the issue you raised.
Best,
Yaron
------ Original Message ------
From "Mohamed Boucadair via Datatracker" <[email protected]>
To "The IESG" <[email protected]>
Cc [email protected]; [email protected];
[email protected]; [email protected]
Date 20/08/2026 10:17:46
Subject Mohamed Boucadair's No Objection on
draft-ietf-oauth-rfc8725bis-09: (with COMMENT)
Mohamed Boucadair has entered the following ballot position for
draft-ietf-oauth-rfc8725bis-09: 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-rfc8725bis/
----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
Hi Yaron, Dick, and Mike,
Thank you for the effort out into this BCP refresh.
# I only reviewed the diff vs. RFC8725. I found the changes well-articulated
with clear reasoning, overall.
# “reasonable” limits
The document argues for implementations to use “reasonable” limits and provides
examples of such “reasonable” values. The document is silent about how these
implementations should expose configuration knobs for those who deploy to
actually adjust these values.
Likewise, for auditing and management purposes, these implementations should
expose the actual limits put into affect.
# (nit) “Existing BCP” won’t age as soon as this draft will be published as
RFC. I sent you a PR to fix this:
https://github.com/oauth-wg/draft-ietf-oauth-rfc8725bis/pull/67
Cheers,
Med
_______________________________________________
OAuth mailing list -- [email protected]
To unsubscribe send an email to [email protected]
