[media-types] Re: application/client-authentication+jwt regi stration request for draft-ietf-oauth-rfc7523bis

Dear Media Types,

Note that the contact was changed from me to the OAuth working group in the latest draft (which was published to address AD feedback from Deb Cooley).  You can find the updated registration request at https://www.ietf.org/archive/id/draft-ietf-oauth-rfc7523bis-07.html#name-registry-contents, which contains this contact entry:


  *   Person & email address to contact for further information: IETF OAuth Working Group <[email protected]>

                                                                Thanks,
                                                                -- Mike

From: Brian Campbell <[email protected]>
Sent: Monday, March 9, 2026 4:39 PM
To: [email protected]; [email protected]; Deb Cooley <[email protected]>
Subject: [media-types] application/client-authentication+jwt registration request for draft-ietf-oauth-rfc7523bis

Hello IANA, media-types list participants, & respective DEs,

The https://datatracker.ietf.org/doc/draft-ietf-oauth-rfc7523bis/ document is moving into AD review and the AD (Deb, who is cc'd) recently asked about the status of the anticipated media type registration therein. To be honest, the timing and initiation of the registration request procedures remain somewhat mysterious to me. And I am painfully aware of my recent commentary on the larger topic of JWT's use of media types https://mailarchive.ietf.org/arch/msg/oauth/IRYjOn88hDh-Rk1i9R-fIyznMnA/ followed shortly by this request for registration of a +jwt media type. But, trusting the process and apologizing for any breach of etiquette on my part, I am requesting review/consideration/processing of the below media type registration request copied from https://datatracker.ietf.org/doc/html/draft-ietf-oauth-rfc7523bis-06#section-7.1.1

Thank you,
Brian



   *  Type name: application
   *  Subtype name: client-authentication+jwt
   *  Required parameters: n/a
   *  Optional parameters: n/a
   *  Encoding considerations: binary; A client authentication JWT is a
      JWT; JWT values are encoded as a series of base64url-encoded
      values (some of which may be the empty string) separated by period
      ('.') characters.
   *  Security considerations: See Section 6 of this specification
   *  Interoperability considerations: n/a
   *  Published specification: Section 4 of this specification
   *  Applications that use this media type: Applications that use this
      specification
   *  Fragment identifier considerations: n/a
   *  Additional information:
         Magic number(s): n/a
         File extension(s): n/a
         Macintosh file type code(s): n/a
   *  Person & email address to contact for further information:
      Michael B.  Jones, [email protected]<mailto:[email protected]>
   *  Intended usage: COMMON
   *  Restrictions on usage: none
   *  Author: Michael B.  Jones, [email protected]<mailto:[email protected]>
   *  Change controller: IETF
   *  Provisional registration?  No

CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited.  If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]