Dear Hannes, Hello. Have you had a chance to review these proposed registrations?
The due date is Wednesday April 12th, 2023, as this document is on this week's IESG telechat agenda. Thank you very much for your time. Best regards, David Dong IANA Services Specialist On Thu Apr 06 15:14:01 2023, david.dong wrote: > Dear Hannes, > > As the designated expert for the OAuth Access Token Types, OAuth > Extensions Error and OAuth Parameters registries, can you review the > proposed registration in draft-ietf-oauth-dpop for us? Please see: > > https://datatracker.ietf.org/doc/draft-ietf-oauth-dpop/ > > The due date is Wednesday April 12th, 2023. This document is on next > week's IESG telechat agenda. > > - > First, in the OAuth Access Token Types registry: > > Name: DPoP > Additional Token Endpoint Response Parameters: > HTTP Authentication Scheme(s): DPoP > Change controller: IETF > Specification document(s): [ RFC-to-be ] > > Second, in the OAuth Extensions Error registry: > > Name: invalid_dpop_proof > Usage Location: token error response, resource error response > Protocol Extension: Demonstrating Proof of Possession (DPoP) > Change controller: IETF > Specification document(s): [ RFC-to-be ] > > Name: use_dpop_nonce > Usage Location: token error response, resource error response > Protocol Extension: Demonstrating Proof of Possession (DPoP) > Change controller: IETF > Specification document(s): [ RFC-to-be ] > > Third, in the OAuth Parameters registry: > > Name: dpop_jkt > Parameter Usage Location: authorization request > Change Controller: IETF > Reference: [ RFC-to-be; Section 10 ] > - > > If this registration is OK, when the IESG approves the document for > publication, we'll make the registration at: > > https://www.iana.org/assignments/oauth-parameters/ > > With thanks, > > David Dong > IANA Services Specialist _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
