…ord keeper. The Protocol field in the IP header [ RFC791 and MIME media types [ RFC6838 ] are two examples of such coordinations. The IETF selects an IANA Functions Operator (IFO) for protocol parameters defined by the IETF. In the contract between the IETF and the current IFO (I…

… Media Type Definition This registration is done using the template defined in [RFC6838] and following [RFC4855]. Type name: video Subtype name: FFV1 Required parameters: None. Optional parameters: These parameters are used to signal the capabilities of a receiver implementation.…

…ng material. The content of this media type is not active (see Section 4.6 of [ RFC6838 ), but it governs how a Client might interact with an Oblivious Gateway Resource . The security implications of processing it are described in Section 6.1 ; privacy implications are described …

…: o URI and URI-Reference from [ RFC3986 ], o type-name and subtype-name from [ RFC6838 ], o media-query-list from [ W3C.REC-css3-mediaqueries-20120619 ], and o Language-Tag from [ RFC5646 ]. 1.2 . Conformance and Error Handling The requirements regarding conformance and error ha…

…included: URI and URI-Reference from [RFC3986] type-name and subtype-name from [RFC6838] media-query-list from [W3C.REC-css3-mediaqueries-20120619] , and Language-Tag from [RFC5646] 1.2. Conformance and Error Handling The requirements regarding conformance and error handling high…

…: o URI and URI-Reference from [ RFC3986 ], o type-name and subtype-name from [ RFC6838 ], o media-query-list from [ W3C.REC-css3-mediaqueries-20120619 ], and o Language-Tag from [ RFC5646 ]. 1.2 . Conformance and Error Handling The requirements regarding conformance and error ha…

…Media Type Definition This registration is done using the template defined in [ RFC6838 ] and following [ RFC4855 ]. Type name: video Subtype name: VP8 Required parameters: None. Optional parameters: Westin, et al. Expires March 12, 2016 [Page 22] Internet-Draft RTP Payload Forma…

…. [ MIME-SPEC ] refers to [ RFC2045 ], [ RFC2046 ], [ RFC2047 ], [ RFC2049 ], [ RFC6838 ], and [ RFC4289 ]. [ SMIMEv2 ] refers to [ RFC2311 ], [ RFC2312 ], [ RFC2313 ], [ RFC2314 ], and [ RFC2315 ]. [ SMIMEv3 ] refers to [ RFC2630 ], [ RFC2631 ], [ RFC2632 ], [ RFC2633 ], [ RFC26…

…Media Types" registry [ IANA.MediaTypes ] in the manner described in RFC 6838 [ RFC6838 ], which can be used to indicate that the content is a JWS or JWE using the JWS Compact Serialization or the JWE Compact Serialization. This section also registers the "application/ jose+json"…

…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; …

…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; …

…s for Identifying Languages, http://www.ietf.org/rfc/rfc5646.txt , IETF, 2009. [RFC6838] N. Freed, J. Klensin, T. Hansen Media Type Specifications and Registration Procedures, http://www.ietf.org/rfc/rfc6838.txt , IETF, 2013. [RNG] ISO/IEC 19757-2 Document Schema Definition Langu…

…scheme is not coupled with a specific protocol nor with a specific media type [ RFC6838 ]. See Section 3 for a discussion of operations that can be performed on the object identified by a file URI. 1.1 . Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL"…

…his 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…

…scheme is not coupled with a specific protocol nor with a specific media type [ RFC6838 ]. See Section 3 for a discussion of operations that can be performed on the object identified by a file URI. 1.1 . Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL"…