Registration Tree
Click on the red underlined text to get to the source
... registration proposal. Registration may occur
within several different registration trees that have different
requirements, as discussed below. In general, a new registration
proposal ...
... acceptable. The following sections describe the requirements and
procedures used for each of the different registration trees.
...
... Registration Trees and Subtype Names ...
... 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.
...
...
This requirement applies regardless of the registration tree
involved.
...
... The combination of these names serves to uniquely identify the media
type, and the format of the subtype name identifies the registration
tree. Both type and subtype names are case-insensitive.
...
...
These requirements apply regardless of the registration tree
involved.
...
... All registered media types MUST employ a single, canonical data
format, regardless of registration tree.
A precise and openly available specification of the format of each
...
... subject to continuing evaluation.
These recommendations apply regardless of the registration tree
involved.
...
... done, all descriptions of security issues MUST be as accurate as
possible regardless of registration tree. In particular, a statement
that there are "no security issues associated with this type" MUST
...
... registration of a
media type, again regardless of registration tree.
The security considerations ...
... media type proposals and
"publish" them as part of the media types registration tree itself.
As stated previously, standards tree ...
... IANA, the owner may
request a change to its definition. The descriptions of the
different registration trees above designate the "owners" of each
type of registration. The same procedure that would be appropriate
...