Type name: application

Subtype name: oauth-authz-req+jwt

Required parameters: n/a

Optional parameters: n/a

Encoding considerations: binary; A Request Object 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 10 of RFC 9101

Interoperability considerations: n/a

Published specification: Section 4 of RFC 9101

Applications that use this media type: Applications that use
  Request Objects to make an OAuth 2.0 Authorization Request

  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:
  Nat Sakimura, nat&nat.consulting

Intended usage: COMMON

Restrictions on usage: none

Author: Nat Sakimura, nat&nat.consulting

Change controller: IETF

Provisional registration?  No