[media-types] draft-ietf-oauth-status-list media types review request
Christian Bormann <[email protected]>
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <[email protected]> |
Dear media-types list participants and respective DEs, Our draft https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/ is currently past AD review and we were asked about the status of the requested media types registrations. Would it be possible to get a review on the 2 requested media types? Media Type Registrations: ---- statuslist+jwt: ---- Media type name: application Media subtype name: statuslist+jwt Required parameters: n/a Optional parameters: n/a Encoding considerations: binary statuslist+jwt values are Json Web Tokens (JWTs). See Section 5.1 of [RFC-ietf-oauth-status-list-13] Security considerations: See Section 11 of [RFC-ietf-oauth-status- list-13] Interoperability considerations: n/a Published specification: [RFC-ietf-oauth-status-list-13] Applications which use this media: Applications using status lists for updated status information of tokens 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: Person to contact for further information: 1. Name: Paul Bastian 2. Email: [email protected] Intended usage: COMMON Author/Change controller: IETF ---- statuslist+cwt: ---- Media type name: application Media subtype name: statuslist+cwt Required parameters: n/a Optional parameters: n/a Encoding considerations: binary statuslist+cwt values are CBOR Web Tokens (CWTs). See Section 5.2 of [RFC-ietf-oauth-status-list-13] Security considerations: See Section 11 of [RFC-ietf-oauth-status-list-13] Interoperability considerations: n/a Published specification: [RFC-ietf-oauth-status-list-13] Applications which use this media: Applications using status lists for updated status information of tokens 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: Person to contact for further information: 1. Name: Paul Bastian 2. Email: [email protected] <mailto:[email protected]> Intended usage: COMMON Author/Change controller: IETF ---- Thank you & Best regards, Christian _______________________________________________ media-types mailing list -- [email protected] To unsubscribe send an email to [email protected]