Standards Tree
Click on the red underlined text to get to the source
... Standards Tree ...
...
The standards tree is intended for types of general interest to the
Internet community. Registrations ...
... Internet community. Registrations in the standards tree MUST be
approved by the IESG and MUST correspond to a formal publication by a
...
...
Media types in the standards tree are normally denoted by names that
are not explicitly faceted, i.e., do not contain period (".", full
stop) characters.
...
...
The "owner" of a media type registration in the standards tree is
assumed to be the standards body itself. Modification or alteration
of the specification requires the same level of processing (e.g.,
...
... additional
registration trees is expected to be equivalent to registrations in
the standards tree. Establishment of these new trees will be
announced through RFC publication approved by the IESG ...
...
when a media type is registered in the standards tree, and SHOULD be
specified as completely as possible when media types are registered
...
...
New parameters SHOULD NOT be defined as a way to introduce new
functionality in types registered in the standards tree, although new
parameters MAY be added to convey additional information that does
not otherwise change existing functionality. An example of this
...
... A precise and openly available specification of the format of each
media type MUST exist for all types registered in the standards tree
and MUST at a minimum be referenced by, if it isn't actually included
in, the media type registration ...
... part of a standards-track protocol. In addition, other standards
bodies making use of the standards tree may have their own rules
regarding intellectual property that must be observed in their
registrations ...
... An analysis of security issues MUST be done for all types registered
in the standards Tree. A similar analysis for media types registered
in the vendor ...
...
Proposals for media types registered in the standards tree by the
IETF itself MUST be published as RFCs. RFC publication of vendor ...
... registration tree itself.
As stated previously, standards tree registrations for media types
...
... media types.
The standards tree exists for media types that do require a
substantive review and approval process in a recognized standards
...
...
In the case of a registration in the standards tree, this additional
information MAY be provided in the formal specification of the media
type. It is suggested that this be done by incorporating the IANA ...
... IETF
registrations in the standards tree. The posting of an Internet
Draft is a necessary first step, followed by posting to the
ietf-types ...
...
Proposed registrations in the standards tree by other standards
bodies should be communicated to the IESG (at iesg@ietf.org) and to
...
...
Notice of a potential media type registration in the standards tree
MUST be sent to the "ietf-types@iana.org" mailing list ...
...
Media types registered in the standards tree MUST be approved by the
IESG prior to registration ...
... registration is either part of an RFC publication request or
a registration in the standards tree submitted to the IESG, close
coordination between the IANA ...
... IANA will only register media types in the standards tree in
response to a communication from the IESG stating that a given
...
...
Registrations in the standards tree MUST satisfy the additional
requirement that they originate from the IETF ...
... o The unfaceted IETF tree is now called the standards tree, and the
registration rules for this tree ...
... o Ietf-types list review of registrations in the standards tree is
now required rather than just recommended.
...