URL scheme
Click on the red underlined text to get to the source
... URLs. URLs are designated by including a "<scheme>:"
and then a "<scheme-specific-part>". Many URL schemes are already
defined, however, new schemes may need to be defined in the future in
order to accommodate new Internet protocols ...
... registration process is needed to ensure that the names of all such
new schemes are guaranteed not to collide. Further, the registration
process ensures that URL schemes intended for wide spread, public use
are developed in an orderly, well-specified, and public manner.
...
... This document defines the registration procedures to be followed when
new URL schemes are created. A separate document, RFC 2718(-> 4395),
...
... created. A separate document, RFC 2718(-> 4395),
Guidelines for URL Schemes [2], provides guidelines for the creation
of new URL schemes ...
... URL Schemes [2], provides guidelines for the creation
of new URL schemes. The primary focus of this document is on the
<scheme> portion of new URL schemes, referred to as the "scheme name"
...
... of new URL schemes. The primary focus of this document is on the
<scheme> portion of new URL schemes, referred to as the "scheme name"
throughout this document.
...
... URL Scheme Name Registration Trees ...
...
In order to increase the efficiency and flexibility of the URL scheme
name registration process, the need is recognized for multiple
...
... registration procedure to accommodate the different natural
requirements for URL schemes. For example, a scheme that will be
recommended for wide support and implementation by the Internet
community requires a more complete review than a scheme intended to
...
...
The first step in registering a new URL scheme name is to determine
which registration tree the scheme should be registered in.
...
... The IETF tree is intended for URL schemes of general interest to the
Internet community. The tree ...
... Internet community. The tree exists for URL schemes that require a
substantive review and approval process. It is expected that
applicability statements ...
... applicability statements for particular applications will be
published from time to time that recommend implementation of, and
support for, URL schemes that have proven particularly useful in
those contexts.
...
... Registration in the IETF tree requires publication of the URL scheme
syntax and semantics in either an Informational or Standards Track
...
... syntax and semantics in either an Informational or Standards Track
RFC. In general, the creation of a new URL scheme requires a
Standards Track RFC. An Informational RFC may be employed for
registration ...
... Standards Track RFC. An Informational RFC may be employed for
registration only in the case of a URL scheme which is already in
wide usage and meets other standards set forth in RFC 2718(-> 4395), such as
...
... RFC is suitable in any given case, and may either recommend changes
to such document prior to publication, or reject it for publication.
An Informational RFC purporting to describe a URL scheme shall not be
published without IESG approval. This is a departure from practice
...
... 2026, for the purpose of
ensuring that the registration of URL schemes shall serve the best
interests of the Internet community.
...
...
An analysis of the security issues inherent in the new URL scheme is
REQUIRED. (This is in accordance with the basic requirements for all
...
... quality of the specification. RFC publication of alternative tree
URL schemes is encouraged but not required. Material may be
published as an Informational RFC by sending it to the RFC Editor
(please follow the instructions to RFC authors, RFC 2223 ...
...
All new URL schemes SHOULD follow the Guidelines for URL Schemes, set
forth in RFC 2718(-> 4395) ...
...
All new URL schemes SHOULD follow the Guidelines for URL Schemes, set
forth in RFC 2718(-> 4395) [2 ...
...
An analysis of the security issues inherent in the new URL scheme is
encouraged. Regardless of what security analysis is or is not
...
... be identified by a unique prefix, which must be established in the
same fashion as a URL scheme name in the IETF tree, except that the
...
... must be documented for each alternative tree, and must be consistent
for all URL scheme names created in that tree.
...
...
While the template in section 6 of this document is intended to apply
to URL scheme names in the IETF tree, it is also offered as a
...
...
The owner of a URL scheme registered in an alternative tree and
documented by an Informational RFC may pass responsibility for the
...
...
The IESG may reassign responsibility for a URL scheme registered in
an alternative tree and documented by an Informational RFC. The most
...
...
The following issues should be addressed when documenting a new URL
scheme:
...
...
URL scheme name.
URL scheme ...
... URL scheme name.
URL scheme syntax. This should be expressed in a clear and
concise manner. The use of ABNF is encouraged. Please refer to
...
... identify it.
Applications and/or protocols which use this URL scheme name.
Including references to documentation which defines the
applications and/or protocols cited is especially useful.
...
... Author/Change controller.
Applications and/or protocols which use this URL scheme name.
...
... security vulnerabilities of a
protocol may change over time. Consequently, claims as to the
security properties of a registered URL scheme may change as well.
As new vulnerabilities are discovered, information about such
...
... that users are not misled as to the true security properties of a
registered URL scheme.
...
... Masinter, L., Alvestrand, H., Zigmond, D. and R. Petke, "Guidelines for new URL Schemes", RFC 2718(-> 4395), November 1999. ...