Code change:
12. <del> This document specifies no IANA actions. </del> <ins> 12.1. This specification requests registration of the following Claims in the IANA "JSON Web Token Claims" registry [@IANA.JWT] established by [@!RFC7519]. Claim Name: "status" Claim Description: Reference to a status list containing up-to- date status information on the JWT. Change Controller: IETF Specification Document(s): [[ (#jwt-referenced-token) of this specification ]] Claim Name: "status_list" Claim Description: A status list containing up-to-date status information on multiple other JWTs encoded as a bitarray. Change Controller: IETF Specification Document(s): [[ (#jwt-status-list-claim-format) of this specification ]] 12.2. This section requests registration of the following media types [@RFC2046] in the "Media Types" registry [@IANA.MediaTypes] in the manner described in [@RFC6838]. To indicate that the content is an JWT-based Status List: Type name: application * Subtype name: statuslist+jwt * Required parameters: n/a * Optional parameters: n/a * Encoding considerations: binary; A JWT-based Status List 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 (#Security) of [[ this specification ]] * Interoperability considerations: n/a * Published specification: [[ this specification ]] * Applications that use this media type: Applications using [[ this specification ]] for updated status information of tokens * Fragment identifier considerations: n/a * Additional information: * File extension(s): n/a * Macintosh file type code(s): n/a * Person & email address to contact for further information: Paul Bastian, paul.bastian@posteo.de * Intended usage: COMMON * Restrictions on usage: none * Author: Paul Bastian, paul.bastian@posteo.de * Change controller: IETF * Provisional registration?  No To indicate that the content is an CWT-based Status List: Type name: application * Subtype name: statuslist+cwt * Required parameters: n/a * Optional parameters: n/a * Encoding considerations: binary * Security considerations: See (#Security) of [[ this specification ]] * Interoperability considerations: n/a * Published specification: [[ this specification ]] * Applications that use this media type: Applications using [[ this specification ]] for updated status information of tokens * Fragment identifier considerations: n/ a * Additional information: * File extension(s): n/a * Macintosh file type code(s): n/a * Person & email address to contact for further information: Paul Bastian, paul.bastian@posteo.de * Intended usage: COMMON * Restrictions on usage: none * Author: Paul Bastian, paul.bastian@posteo.de * Change controller: IETF * Provisional registration?  No </ins>

Related discussion:
text: IANA Consideration to register JWT Claim names and media types URL
Propose and as media types
same for jwt types?
Note that JWT values are actually media types URL which is a little odd sometimes but that's how it is - so you don't need anything different in terms of registration for a jwt type b/c it is a media type. And the JWT BCP does recommend explicit typing using URL for better or worse, which would suggest that be registered. But it and would also probably have utility in places like HTTP and headers so would make sense to register both. There are some media-type-registration requests in SD-JWT that could be borrowed from URL or you can look at entries in the registry URL