Martin Duke has entered the following ballot position for draft-ietf-oauth-access-token-jwt-12: 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-oauth-access-token-jwt/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- (2.1) "...can use any signing algorithm." I presume there ought to be some qualifiers on allowed algorithms? (4) and (5) "This specification does not provide a mechanism for identifying a specific key as the one used to sign JWT access tokens." I don't understand; there's a key ID right there in the token header? (4) I presume it's important that any resouree server rejection of the token should be constant-time. Is this somewhere in the RFC tree, or do we need to explicitly say it here and/or in Security Considerations? _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
