They may also appear in lower or mixed case as "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in thisĭocument are to be interpreted as described in when theyĪppear in ALL CAPS. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", Specification incorporates such restrictions into media type It may be desirable to restrict the use of media types to specificĮnvironments or to prohibit their use in other environments.
#XSECTION 4.8 REGISTRATION#
The media type specificationĪnd registration procedure is now a separate document, to make it Initially done in, but the procedure defined there was Hindrance to interoperability, the original procedure provedĮxcessively restrictive and had to be generalized. As media types are used in newĮnvironments in which the proliferation of media types is not a Likelihood of interoperability when the capabilities of the remote To limit the number of possible media types, to increase the In this mail environment, there is a need Registering media types for use in the context of the asynchronous The media type registration process was initially defined for The location of the media type registry managed by these procedures This document specifies the criteria for media type registrations andĭefines the procedures to be used to register media types ( Section 5)Īs well as media type structured suffixes ( Section 6) in the InternetĪssigned Numbers Authority (IANA) central registry. Such values are defined in a reasonably orderly, well-specified, and Optionally, media types can define companion data, known asĪ registration process is needed for these labels, so that the set of Of a top-level type and a subtype, which is further structured into The mechanism used to label such content is a media type, consisting Including but not limited to HTTP and MIME, areĬapable of carrying arbitrary labeled content. Recent Internet protocols have been carefully designed to be easilyĮxtensible in certain areas. RFC 6838 Media Type Registration January 2013 10. Structured Syntax Suffix Registration Template. Structured Syntax Suffix Registration Procedures. Usage and Implementation Non-Requirements. Requirements Specific to XML Media Types. Canonicalization and Format Requirements. RFC 6838 Media Type Registration January 2013ġ. The Trust Legal Provisions and are provided without warranty asįreed, et al. Include Simplified BSD License text as described in Section 4.e of
#XSECTION 4.8 CODE#
Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal
#XSECTION 4.8 HOW TO#
Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained atĬopyright (c) 2013 IETF Trust and the persons identified as the Further information onīCPs is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This memo documents an Internet Best Current Practice. Registration of media types for use in HTTP, MIME, and other Internet This document defines procedures for the specification and Media Type Specifications and Registration Procedures Internet Engineering Task Force (IETF) N. RFC 6838: Media Type Specifications and Registration Procedures
0 kommentar(er)
