…webp' Media Type This section contains the media type registration details per [RFC6838]. 6.1.1. Registration Details Type name: image Subtype name: webp Required parameters: N/A Optional parameters: N/A Encoding considerations: Binary. The Base64 encoding [RFC4648] should be use…

…p' Media Type This section contains the media type registration details as per [RFC6838]. 2.1. Registration Details Media type name: image Media subtype name: webp Required parameters: N/A Zern Expires 26 March 2022 [Page 2] Internet-Draft WebP Image Format Media Type Registratio…

…This information is modeled after that specified for the "Media Types" registry RFC6838 ; if in doubt, the provisions of this registry should be applied analogously. Key Identifier: The key (conforming to suffix-key in Section 4.1 Registration Status: "Provisional" or "Permanent"…

… "Media Types" registry [ IANA.MediaTypes ] in the manner described in RFC 6838 RFC6838 ], which can be used to indicate that the content is a JWT. o Type name: application o Subtype name: jwt o Required parameters: n/a o Optional parameters: n/a o Encoding considerations: 8bit; …

…istering party. 2.5 . URI Fragment Identifiers Media type definitions (as per [ RFC6838 ]) SHOULD specify the fragment identifier syntax(es) to be used with them; other specifications MUST NOT define structure within the fragment identifier, unless they are explicitly defining on…

… "Media Types" registry [ IANA.MediaTypes ] in the manner described in RFC 6838 RFC6838 ], which can be used to indicate that the content is a JWT. o Type name: application o Subtype name: jwt o Required parameters: n/a o Optional parameters: n/a o Encoding considerations: 8bit; …

…. IANA Considerations This specification defines two new Internet media types [ RFC6838 ]. 6.1 . application/problem+json Type name: application Subtype name: problem+json Required parameters: None Optional parameters: None; unrecognized parameters should be ignored Encoding cons…

… "Media Types" registry [ IANA.MediaTypes ] in the manner described in RFC 6838 RFC6838 ], which can be used to indicate that the content is a CWT. 9.2.1 . Registry Contents o Type name: application o Subtype name: cwt o Required parameters: N/A o Optional parameters: N/A o Encod…

… CBOR Object Signing and Encryption (COSE) [ RFC9052 ]. It uses content types [ RFC6838 ] to distinguish between the data types of unsecured documents conforming to [ VC-DATA-MODEL-2.0 ] and the data types of secured documents conforming to [ VC-DATA-MODEL-2.0 ]. JSON Web Signatu…

…he "Media Types" registry IANA.MediaTypes ] in the manner described in RFC 6838 RFC6838 ], which can be used to indicate that the content is a JWK or a JWK Set, respectively. o Type Name: application o Subtype Name: jwk+json o Required Parameters: n/a o Optional Parameters: n/a o…

…nce indicates a certificate chain. IANA has registered the following media type RFC6838 Type name: application Subtype name: cose-x509 Required parameters: N/A Optional parameters: usage Can be absent to provide no further information about the intended meaning of the order in th…

…type-name>" where <type-name> and <subtype-name> are defined in Section 4.2 of [RFC6838] . Leading and trailing whitespace is also omitted. Textual content values along with parameters and subparameters can be located using the IANA "Media Types" registry. Applications SHOULD pro…

…ons that wish to register media types. The document describing that mechanism [ RFC6838 ] provides somewhat more information about the general approach. 6.4 . Completing the Template A template for defining and registering a URN namespace is provided in Appendix A . This section …

…7049 CBOR October 2013 7.3 . Media Type ("MIME Type") The Internet media type [ RFC6838 ] for CBOR data is application/cbor. Type name: application Subtype name: cbor Required parameters: n/a Optional parameters: n/a Encoding considerations: binary Security considerations: See Se…

…t/form-data This section is the media type registration using the template from RFC6838 ]. Type name: multipart Subtype name: form-data Required parameters: boundary Optional parameters: none Encoding considerations: Common use is BINARY. In limited use (or transports that restri…