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

vendor


Click on the red underlined text to get to the source

... Vendor Tree ...
... The vendor tree is used for media types associated with commercially available products. "Vendor ...
... vendor tree is used for media types associated with commercially available products. "Vendor" or "producer" are construed as equivalent and very broadly in this context ...
... A registration may be placed in the vendor tree by anyone who needs to interchange files associated with the particular product. However, the registration ...
... to interchange files associated with the particular product. However, the registration formally belongs to the vendor or organization producing the software or file format being registered. ...
... Registrations in the vendor tree will be distinguished by the leading facet "vnd.". That may be followed, at the discretion of the registrant, by either a media subtype ...
... While public exposure and review of media types to be registered in the vendor tree is not required, using the ietf-types@iana.org mailing list ...
... mailing list for review is strongly encouraged to improve the quality of those specifications. Registrations in the vendor tree may be submitted directly to the IANA. ...
... However, with the simplified registration procedures described above for vendor and personal trees, it should rarely, if ever, be necessary to use unregistered ...


... specified as completely as possible when media types are registered in the vendor or personal trees. ...
... JPEG. Similar behavior is encouraged for media types registered in the vendor or personal trees but is not required. ...
... The specifications of format and processing particulars may or may not be publicly available for media types registered in the vendor tree, and such registration proposals are explicitly permitted to ...
... standards Tree. A similar analysis for media types registered in the vendor or personal trees is encouraged but not required. However, regardless of what security analysis ...
... standards tree by the IETF itself MUST be published as RFCs. RFC publication of vendor and personal media type proposals is encouraged but not required. In all ...
... media types that do require a substantive review and approval process in a recognized standards body. The vendor and personal trees exist for those media types that ...


... Registrations in the vendor and personal tree should be submitted directly to the IANA ...


... IESG stating that a given registration has been approved. Vendor and personal types will be registered by the IANA automatically and without any formal approval ...


... media types, registered prior to 1996, would, if registered under the guidelines in this document, be placed into either the vendor or personal trees. Reregistration of those types to reflect the appropriate trees ...



Google
Web
RFC-Ref