….17487/RFC6386 , November 2011 , < https://www.rfc-editor.org/info/rfc6386 > . [RFC6838] Freed, N. , Klensin, J. , and T. Hansen , "Media Type Specifications and Registration Procedures" , BCP 13 , RFC 6838 , DOI 10.17487/RFC6838 , January 2013 , < https://www.rfc-editor.org/info…
…on that was successfully secured. string mediaType A media type as defined in [ RFC6838 ]. Securing mechanism specifications SHOULD provide integrity protection for any information referenced by a URL that is critical to validation. Mechanisms that can achieve this protection are…
…tached file. FileMediaType 0x4660 mand. Media type of the file following the [@!RFC6838] format. FileData 0x465C mand. The data of the file. FileUID 0x46AE mand. not 0 Unique ID representing the file, as random as possible. FileReferral 0x4675 A binary value that a track/codec ca…
…o not support 64-bit numbers. 9.3. Media Types Registry The Internet media type RFC6838 ("MIME type") for a single encoded CBOR data item is "application/cbor" as defined in the "Media Types" registry IANA.media-types Type name: application Subtype name: cbor Required parameters:…
…e Specifications and Registration Procedures ”, BCP 13 , RFC 6838, DOI 10.17487/RFC6838 , January 2013. [BCP178] Saint-Andre, P., Crocker, D., and M. Nottingham, “ Deprecating the "X-" Prefix and Similar Constructs in Application Protocols ”, BCP 178 , RFC 6648, DOI 10.17487/RFC6…
…o not support 64-bit numbers. 9.3. Media Types Registry The Internet media type RFC6838 ("MIME type") for a single encoded CBOR data item is "application/cbor" as defined in the "Media Types" registry IANA.media-types Type name: application Subtype name: cbor Required parameters:…
…o not support 64-bit numbers. 9.3. Media Types Registry The Internet media type RFC6838 ("MIME type") for a single encoded CBOR data item is "application/cbor" as defined in the "Media Types" registry IANA.media-types Type name: application Subtype name: cbor Required parameters:…
… 11 defines no formal (optional/required) parameters for this registered type * RFC6838 sect. 4.2.1 defines the common usage of a "charset" parameter as a "required" one (which isn't the case here) * RFC6838 sect. 4.2.1 defines that "charset" should not be used if the inner paylo…
…e Specifications and Registration Procedures ”, BCP 13 , RFC 6838, DOI 10.17487/RFC6838 , January 2013. [BCP178] Saint-Andre, P., Crocker, D., and M. Nottingham, “ Deprecating the "X-" Prefix and Similar Constructs in Application Protocols ”, BCP 178 , RFC 6648, DOI 10.17487/RFC6…
… 11 defines no formal (optional/required) parameters for this registered type * RFC6838 sect. 4.2.1 defines the common usage of a "charset" parameter as a "required" one (which isn't the case here) * RFC6838 sect. 4.2.1 defines that "charset" should not be used if the inner paylo…
← Previous
Page 6