registration
Click on the red underlined text to get to the source
... character sets, and access methods without any changes to the basic
protocol. A registration process is needed, however, to ensure that
the set of such values is developed in an orderly, well-specified,
and public manner.
...
...
This document defines registration procedures which use the Internet
Assigned Numbers Authority (IANA) as a central registry ...
...
Historical Note: The registration process for media types was
initially defined in the context ...
... Media Type Registration ...
... media type or types starts with the
construction of a registration proposal. Registration may occur in
several different registration trees ...
... starts with the
construction of a registration proposal. Registration may occur in
several different registration trees, which have different
...
... registration proposal. Registration may occur in
several different registration trees, which have different
requirements as discussed below. In general, the new registration
proposal ...
... registration trees, which have different
requirements as discussed below. In general, the new registration
proposal is circulated and reviewed in a fashion appropriate to the
tree involved. The media type ...
... acceptable. The following sections describe the requirements and
procedures used for each of the different registration trees.
...
... Registration Trees and Subtype Names ...
...
In order to increase the efficiency and flexibility of the
registration process, different structures of subtype names may be
registered to accomodate the different natural requirements ...
... Internet Community or a subtype that is used to
move files associated with proprietary software. The following
subsections define registration "trees", distinguished by the use of
faceted names (e.g., names of the form "tree ...
... tree is intended for types of general interest to the
Internet Community. Registration in the IETF tree requires approval
...
... tree requires approval
by the IESG and publication of the media type registration as some
form of RFC.
...
... IETF itself. Modification or alteration of the
specification requires the same level of processing (e.g. standards
track) required for the initial registration.
...
...
A registration may be placed in the vendor tree by anyone who has
need to interchange files associated with the particular product.
...
... vendor tree by anyone who has
need to interchange files associated with the particular product.
However, the registration formally belongs to the vendor or
organization producing the software or file format ...
...
Registrations in the vendor tree will be distinguished by the leading
facet "vnd.". That may be followed, at the discretion of the
...
... vendor tree will be distinguished by the leading
facet "vnd.". That may be followed, at the discretion of the
registration, by either a media type name from a well-known producer ...
... ietf-types 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 ...
... products that are not distributed commercially may be registered in
the personal or vanity tree. The registrations are distinguished by
the leading facet "prs.".
...
...
The owner of "personal" registrations and associated specifications
is the person or entity making the registration ...
... registrations and associated specifications
is the person or entity making the registration, or one to whom
responsibility has been transferred as described below.
...
... ietf-types list for
review is strongly encouraged to improve the quality of those
specifications. Registrations in the personl tree may be submitted
directly to the IANA ...
...
For convenience and symmetry with this registration scheme, media
type names with "x." as the first facet may be used for the same
purposes for which names starting ...
...
However, with the simplified registration procedures described above
for vendor and personal trees ...
... Additional Registration Trees ...
... with the advice and consent of the IESG, create new top-level
registration trees. It is explicitly assumed that these trees may be
created ...
... media types
specific to the sciences they cover. In general, the quality of
review of specifications for one of these additional registration
trees is expected to be equivalent to that which IETF would give to
registrations ...
... additional registration
trees is expected to be equivalent to that which IETF would give to
registrations in its own tree. Establishment of these new trees will
...
... Registration Requirements ...
...
Media type registration proposals are all expected to conform to
various requirements laid out in the following sections. Note that
...
... 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.
...
... Media types must function as an actual media format: Registration of
things that are better thought of as a transfer encoding, as a
...
...
This requirement applies regardless of the registration tree
involved.
...
...
These requirements apply regardless of the registration tree
involved.
...
... All registered media types must employ a single, canonical data
format, regardless of registration tree.
...
... tree and
must at a minimum be referenced by, if it isn't actually included in,
the media type registration proposal itself.
...
... not be publically available for media types registered in the vendor
tree, and such registration proposals are explicitly permitted to
include only a specification of which software and version produce or
...
... process such media types. References to or inclusion of format
specifications in registration proposals is encouraged but not
required.
...
...
Format specifications are still required for registration in the
personal tree, but may be either published as RFCs or otherwise
...
... Some media types involve the use of patented technology. The
registration of media types involving patented technology is
specifically permitted. However, the restrictions set forth in RFC
...
...
These recommendations apply regardless of the registration tree
involved.
...
... has not been 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
...
... tree be secure or completely free from risks. Nevertheless, all
known security risks must be identified in the registration of a
media type, again regardless of registration tree ...
...
The security considerations section of all registrations is subject
to continuing evaluation and modification, and in particular may be
...
... made for originators to specify arbitrary actions in an
unrestricted fashion which may then have devastating
effects. See the registration of the
application/postscript media type ...
... attack or else violates a recipient's
privacy in some way. Again, the registration of the
application/postscript media type ...
... limit the number of possible media types and resulted in a
registration process with a significant hurdle and delay for those
registering media types.
...
... However, the need for "common" media types does not require limiting
the registration of new media types. If a limited set of media types
...
... media type is NOT
a requirement for registration. If, however, a media type is
explicitly intended for limited use, this should be noted in its
...
... media type is
explicitly intended for limited use, this should be noted in its
registration.
...
... media type proposals and "publish" them as part
of the media types registration tree itself.
...
... Other than in the IETF tree, the registration of a data type does not
imply endorsement, approval, or recommendation by IANA ...
... through the IETF standards process. This is too difficult and too
lengthy a process for the convenient registration of media types.
...
... Registration Procedure ...
... process, but rather an administrative procedure intended to allow
community comment and sanity checking without excessive time delay.
For registration in the IETF tree, the normal IETF ...
... on the ietf-types list (as described in the next subsection) as a
first step. For registrations in the vendor or personal tree, the
...
... interoperability or security considerations. The
submitter may submit a revised registration, or withdraw the
registration completely, at any time.
...
... submitter may submit a revised registration, or withdraw the
registration completely, at any time.
...
... IANA Registration ...
... media types
and has obtained approval that is necessary, the author may submit
the registration request to the IANA, which will register the media
type ...
... IANA, which will register the media
type and make the media type registration available to the community.
...
... Comments on Media Type Registrations ...
... of the media type if possible. Submitters of comments may request
that their comment be attached to the media type registration itself,
and if IANA approves of this the comment will be made accessible in
...
... IANA approves of this the comment will be made accessible in
conjunction with the type registration itself.
...
...
Media type registrations will be posted in the anonymous FTP
directory "ftp://ftp.isi.edu/in-notes/iana/assignments/media-types ...
... tree in response
to a communication from the IESG stating that a given registration
has been approved. Vendor and personal types will be registered by
...
... IANA to conduct a comprehensive security review of
media type registrations. Nevertheless, IANA has the
authority ...
... IANA, the author may request
a change to its definition. The descriptions of the different
registration trees above designate the "owners" of each type of
registration. The change request follows the same procedure as the
...
... registration trees above designate the "owners" of each type of
registration. The change request follows the same procedure as the
registration request:
...
... registration. The change request follows the same procedure as the
registration request:
...
... media type. The most
common case of this will be to enable changes to be made to types
where the author of the registration has died, moved out of contact
or is otherwise unable to make changes that are important to the
community.
...
... Registration Template ...
... 2046draft defines an initial set of access types, but allows for the
registration of additional access types to accommodate new retrieval
mechanisms.
...
... Registration Requirements ...
... Registration Procedure ...
... IANA Registration ...
... IANA will register the access
type and make the registration available to the community. The
specification of the access type must also be published as an RFC.
...
...
Access type registrations will be posted in the anonymous FTP
directory "ftp://ftp.isi.edu/in-notes/iana/assignments/access-types/" ...
... access type reviewer and
forwarded by the reviewer to the IANA for registration, or in
response to a communication from the IESG that an access type ...
... IANA Procedures for Transfer Encoding Registration ...
... There is no need for a special procedure for registering Transfer
Encodings with the IANA. All legitimate transfer encoding
registrations must appear as a standards-track RFC, so it is the
IESG's ...
...
Transfer encoding registrations will be posted in the anonymous FTP
directory "ftp://ftp.isi.edu/in-notes/iana/assignments/transfer-
...