Personal Tree
Click on the red underlined text to get to the source
... While public exposure and review of media types to be registered in
the personal tree is not required, using the ietf-types list for
review is strongly encouraged to improve the quality of those
...
... review is strongly encouraged to improve the quality of those
specifications. Registrations in the personal tree may be submitted
directly to the IANA.
...
... registration procedures described above
for vendor and personal trees, it should rarely, if ever, be
necessary to use unregistered experimental ...
... media types are registered
in the vendor or personal trees.
Parameter names have the syntax as media type names ...
... Format specifications are still required for registration in the
personal tree, but may be either published as RFCs or otherwise
deposited with the IANA. The deposited specifications will meet the
...
... media types registered
in the vendor or personal trees is encouraged but not required.
However, regardless of what security analysis has or has not been
...
... substantive review and approval process in a recognized standards
body. The vendor and personal trees exist for those media types that
do not require such a process. It is expected that applicability
statements ...
... Registrations in the vendor and personal tree should be submitted
directly to the IANA, ideally after first posting to the
...
... prefix.
o Types registered in the personal tree MUST either provide a format
specification or a pointer to one.
...
... 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 is encouraged but not required.
...