Hi Hannes (cc: ace WG), Following up on this request; as the designated expert for the OAuth Parameters registry, can you review the proposed registration in draft-ietf-ace-key-groupcomm-17 for us? Please see:
https://datatracker.ietf.org/doc/draft-ietf-ace-key-groupcomm/ The due date is November 2nd. If this 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 Sr. Specialist On Thu Oct 19 22:29:20 2023, david.dong wrote: > Dear Hannes Tschofenig (cc: ace WG), > > As the designated expert for the OAuth Parameters registry, can you > review the proposed registration in draft-ietf-ace-key-groupcomm-17 > for us? Please see: > > https://datatracker.ietf.org/doc/draft-ietf-ace-key-groupcomm/ > > The due date is November 2nd. > > If this 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 Sr. Specialist > > On Thu Oct 19 22:09:03 2023, david.dong wrote: > > Third, in the OAuth Parameters registry in the OAuth Parameters > > registry group located at: > > > > https://www.iana.org/assignments/oauth-parameters/ > > > > two new parameters will be registered as follows: > > > > Name: sign_info > > Parameter Usage Location: client-rs request, rs-client response > > Change Controller: IETF > > Reference: [ RFC-to-be ] > > > > Name: kdcchallenge > > Parameter Usage Location: rs-client response > > Change Controller: IETF > > Reference: [ RFC-to-be ] > > > > As this also requests registrations in an Expert Review or > > Specification Required (see RFC 8126) registry, we will initiate the > > required Expert Review via a separate request. This review must be > > completed before the document's IANA state can be changed to "IANA > > OK." _______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
