Technical Summary
This document defines procedures for the specification and
registration of media types for use in HTTP, MIME and other Internet
protocols.
Working Group Summary
The document was developed by seasoned experts in media types,
and was preceded by significant discussion. The process has been
mostly smooth, but for a great deal of wordsmithing and then picking
nits in the smithed words. That process could go on forever, and
sometimes seems to.
Document Quality
The document updates media type registration procedures based on
experience since the publication of RFC4288. The procedures created
there and in its antecedent have been around for a long time; this
document merely refines them. The aforementioned wordsmithing
has given us a solid document.
Personnel
Murray Kucherawy is the Document Shepherd.
Barry Leiba is the responsible Area Director.
RFC Editor notes:
Three items...
---------------------------------------------------------------------
Section 3.1
OLD
The first procedure is used for registering registrations from IETF
Consensus documents
NEW
The first procedure is used for registrations from IETF
Consensus documents
---------------------------------------------------------------------
Small clarification in Section 5.2; replace the whole section thus:
NEW
Media types registered in the standards tree by the IETF itself MUST
be reviewed and approved by the IESG as part of the normal standards
process. Approval of the RFC will constitute all required review, and
IANA will register the requested media type on that basis.
Standards tree registrations by recognized standards bodies
as well as registrations in the vendor and personal tree are
submitted directly to the IANA, unless other arrangements were made
as part of a liaison agreement. Registration requests can be sent to
iana@iana.org. A web form for registration requests is also available:
http://www.iana.org/cgi-bin/mediatypes.pl
In either case posting the registration to the media-types@iana.org list
for review prior to submission is strongly encouraged.
---------------------------------------------------------------------
Any BCP 78 issues have to be addressed in a different document, so:
Section 6, bullet 2, last sentence:
OLD:
The template may also be submitted in some other
form (as part of another document or as a stand-alone document),
but the contents will be treated as an "IETF Contribution" under
the guidelines of BCP 78 [RFC5378].
NEW:
The template may also be submitted in some other
form, e.g., as part of another document or as a stand-alone
document.
---------------------------------------------------------------------