[media-types] Re: [IANA #1443287] application/explicit -registration-response+jwt registration request

Thanks for the approval, Darrel.

You're right that I made a cut-and-paste error between the two registrations in my requests.  Good catch!

The descriptions are correct at https://openid.net/specs/openid-federation-1_0.html#name-media-type-registration.

                                                                Best wishes,
                                                                -- Mike

From: Darrel Miller <[email protected]>
Sent: Saturday, February 21, 2026 1:28 PM
To: [email protected]
Cc: [email protected]; Darrel Miller <[email protected]>
Subject: [media-types] Re: [IANA #1443287] application/explicit-registration-response+jwt registration request

We can approve the  application/explicit-registration-response+jwt registration, but the description below seems to be from the Trust Mark Status Response.

Darrel
________________________________
From: Amanda Baber via RT <[email protected]<mailto:[email protected]>>
Sent: Friday, February 20, 2026 9:24 PM
Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; Darrel Miller <[email protected]<mailto:[email protected]>>
Subject: [IANA #1443287] application/explicit-registration-response+jwt registration request

Hi Darrel,

Sending a reminder for this OpenID request from February 4th. #2 of 2.

thanks,
Amanda

On Wed Feb 04 18:38:54 2026, amanda.baber wrote:
> Hi Darrel,
>
> This is #2 of 2 from OpenID.
>
> thanks,
> Amanda
>
> =====
>
> Name: Michael B Jones
>
> Email: [email protected]<mailto:[email protected]>
>
> Media type name: application
>
> Media subtype name: explicit-registration-response+jwt
>
> Required parameters: n/a
>
> Optional parameters: n/a
>
> Encoding considerations: binary
>
> A Trust Mark Status Response is a signed 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 18 of
> https://openid.net/specs/openid-federation-1_0.html
>
> Interoperability considerations: n/a
>
> Published specification: Section 15.8 of
> https://openid.net/specs/openid-federation-1_0.html
>
> Applications which use this media: Applications that use
> https://openid.net/specs/openid-federation-1_0.html
>
> Fragment identifier considerations: n/a
>
> Restrictions on usage: none
>
> Provisional registration? (standards tree only): No
>
> Additional information:
>
> 1. Deprecated alias names for this type: N/A
> 2. Magic number(s): N/A
> 3. File extension(s): N/A
> 4. Macintosh file type code: N/A
> 5. Object Identifiers: N/A
>
> General Comments: The OpenID Federation 1.0 specification is in the
> 14-day OpenID Foundation-wide voting period for approval as an OpenID
> Final Specification. It would be ideal for the registration to occur
> before the specification becomes final on February 17, 2026.
>
> Person to contact for further information:
>
> 1. Name: Michael B Jones
> 2. Email: [email protected]<mailto:[email protected]>
>
> Intended usage: COMMON
>
> Author/Change controller: OpenID Foundation Artifact Binding Working
> Group - [email protected]<mailto:[email protected]>

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