RFC 4288:Media Type Specifications and Registratio...
RFC-Ref

requirement


Click on the red underlined text to get to the source

... within several different registration trees that have different requirements, as discussed below. In general, a new registration proposal is circulated and reviewed in a fashion appropriate to the tree ...
... tree involved. The media type is then registered if the proposal is acceptable. The following sections describe the requirements and procedures used for each of the different registration trees. ...


... registration process, different structures of subtype names may be registered to accommodate the different natural requirements for, e.g., a subtype that will be recommended for wide support and implementation by the Internet community ...


... Registration Requirements ...
... Media type registration proposals are all expected to conform to various requirements laid out in the following sections. Note that requirement specifics sometimes vary depending on the registration tree ...
... various requirements laid out in the following sections. Note that requirement specifics sometimes vary depending on the registration tree, again as detailed in the following sections. ...
... Functionality Requirement ...
... media type. This requirement applies regardless of the registration tree involved. ...
... Naming Requirements ...
... discouraged. These requirements apply regardless of the registration tree involved. ...
... All subtypes of multipart and message MUST conform to the syntax rules and other requirements specified in [RFC2046]. ...
... Parameter Requirements ...
... Canonicalization and Format Requirements ...
... Security Requirements ...
... have not been assessed". There is absolutely no requirement that media types registered in any tree ...
... Requirements specific to XML media types ...
... There are a number of additional requirements specific to the registration of XML media types ...
... registration of XML media types. These requirements are specified in [RFC3023]. ...
... Encoding Requirements ...
... Usage and Implementation Non-requirements ...
... Therefore, universal support and implementation of a media type is NOT a requirement for registration. However, if a media type is ...
... Publication Requirements ...


... Provided that the media type meets all of the relevant requirements and has obtained whatever approval is necessary, the author may submit the registration request ...
... Area Director(s), will review the registration to make sure it meets the requirements set forth in this document. Registrations ...
... Registrations that do not meet these requirements will be returned to the submitter for revision. ...


... Registrations in the standards tree MUST satisfy the additional requirement that they originate from the IETF itself or from another standards body recognized as such by the IETF ...


... Security requirements for media type registrations are discussed in Section 4.6. ...


... Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. ...


... clarified. o The rules and requirements for constructing security considerations sections have been extended and clarified. ...
... registry. o The basic registration requirements for the various top-level types have been moved from RFC 2046draft to this document. ...



Google
Web
RFC-Ref