draft-ietf-appsawg-about-uri-scheme-05.txt   draft-ietf-appsawg-about-uri-scheme-06.txt 
Applications Area WG (APPSAWG) S. Moonesamy, Ed. Applications Area WG (APPSAWG) S. Moonesamy, Ed.
Internet-Draft Internet-Draft
Intended Status: Informational Intended Status: Informational
Expires: November 30, 2012 May 29, 2012 Expires: December 5, 2012 June 3, 2012
The "about" URI Scheme The "about" URI Scheme
draft-ietf-appsawg-about-uri-scheme-05 draft-ietf-appsawg-about-uri-scheme-06
Abstract Abstract
This document specifies the "about" URI scheme, which is widely used This document describes the "about" URI scheme, which is widely used
by web browsers and some other applications to designate access to by web browsers and some other applications to designate access to
their internal resources, such as settings, application information, their internal resources, such as settings, application information,
hidden built-in functionality, and so on. hidden built-in functionality, and so on.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 2, line 12 skipping to change at page 2, line 12
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. URI Scheme Specification . . . . . . . . . . . . . . . . . . . 2 2. URI Scheme Specification . . . . . . . . . . . . . . . . . . . 2
2.1. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . . 2 2.1. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . . 2
2.2. URI Scheme Semantics . . . . . . . . . . . . . . . . . . . 2 2.2. URI Scheme Semantics . . . . . . . . . . . . . . . . . . . 3
2.2.1. Well-known "about" URIs . . . . . . . . . . . . . . . . 3 2.2.1. Well-known "about" URIs . . . . . . . . . . . . . . . . 3
2.3. Encoding Considerations . . . . . . . . . . . . . . . . . . 3 2.3. Encoding Considerations . . . . . . . . . . . . . . . . . . 3
3. "about:blank" . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. "about:blank" . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5.1. URI Scheme Registration . . . . . . . . . . . . . . . . . . 4 5.1. URI Scheme Registration . . . . . . . . . . . . . . . . . . 4
5.2. A Registry for Well-known Tokens . . . . . . . . . . . . . 4 5.2. A Registry for Well-known Tokens . . . . . . . . . . . . . 4
5.2.1. Registration procedure . . . . . . . . . . . . . . . . 5 5.2.1. Registration procedure . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . 6 6.2. Informative References . . . . . . . . . . . . . . . . . . 6
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 6 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
This document specifies the "about" Uniform Resource Identifier (URI) This document describes the "about" Uniform Resource Identifier (URI)
scheme. The "about" URI scheme is currently widely used by Web scheme. The "about" URI scheme is currently widely used by Web
browsers to designate access to their internal resources such as browsers to designate access to their internal resources such as
settings, application information, so called "Easter eggs" (i.e. settings, application information, so called "Easter eggs" (i.e.
hidden feature or joke in an application). hidden feature or joke in an application).
2. URI Scheme Specification 2. URI Scheme Specification
2.1. URI Scheme Syntax 2.1. URI Scheme Syntax
The "about" URI syntactically conforms to the <about-uri> rule below, The "about" URI syntactically conforms to the <about-uri> rule below,
expressed using Augmented Backus-Naur Form (ABNF) [RFC5234]: expressed using Augmented Backus-Naur Form (ABNF) [RFC5234]:
about-uri = "about:" about-token [ about-query ] about-uri = "about:" about-token [ about-query ] [ about-fragment ]
about-token = *pchar about-token = *pchar
about-query = "?" query about-query = "?" query
pchar = <as specified in RFC 3986, Appendix A> about-fragment = "#" fragment
query = <as specified in RFC 3986, Appendix A> pchar = <as specified in RFC 3986, Appendix A>
query = <as specified in RFC 3986, Appendix A>
fragment = <as specified in RFC 3986, Appendix A>
In terms of RFC 3986, <about-token> part corresponds to <hier-part>, In terms of RFC 3986, <about-token> part corresponds to <hier-part>,
and <about-query> to the query component of URI. <about-query> to the query component and <about-fragment> to the
fragment component of the URI.
2.2. URI Scheme Semantics 2.2. URI Scheme Semantics
The resource which a particular "about" URI references is denoted by The resource which a particular "about" URI references is denoted by
<about-token> part of the URI. The <about-query> specifies <about-token> part of the URI. The <about-query> specifies
additional information about its handling and/or the information that additional information about its handling and/or the information that
should be returned by the resource which the URI references. should be returned by the resource which the URI references.
It is impossible to specify a binding between all the possible tokens It is impossible to specify a binding between all the possible tokens
and the semantics of "about" URIs that would contain such tokens. and the semantics of "about" URIs that would contain such tokens.
Therefore the resource referenced by the URI is generally considered Therefore the resource referenced by the URI is generally considered
as specific to a Web browser implementation. as specific to a Web browser implementation.
skipping to change at page 3, line 30 skipping to change at page 3, line 34
<about-token> part. It is recommended that such URIs be handled in <about-token> part. It is recommended that such URIs be handled in
accordance with the specification referenced in the Well-known token accordance with the specification referenced in the Well-known token
registry (see Section 5.2). registry (see Section 5.2).
Well-known "about" URIs are intended to be registered when there is a Well-known "about" URIs are intended to be registered when there is a
need to codify the behavior of particular <about-token>. need to codify the behavior of particular <about-token>.
2.3. Encoding Considerations 2.3. Encoding Considerations
"about" URIs are subject to encoding rules defined in RFC 3986 "about" URIs are subject to encoding rules defined in RFC 3986
[RFC3986]. For the sake of simplicity, "about" IRIs [RFC3987] are [RFC3986].
not permitted.
3. "about:blank" 3. "about:blank"
This document defines one well-known token: "blank". The URI This document defines one well-known token: "blank". The URI
"about:blank" refers to a resource represented in the browser by a "about:blank" refers to a resource represented in the browser by a
blank page. blank page.
4. Security Considerations 4. Security Considerations
Security considerations for URIs are discussed in Section 7 of RFC Security considerations for URIs are discussed in Section 7 of RFC
skipping to change at page 4, line 25 skipping to change at page 4, line 28
Status: Permanent Status: Permanent
URI scheme syntax: see Section 2.1 of RFC xxxx URI scheme syntax: see Section 2.1 of RFC xxxx
URI scheme semantics: see Section 2.2 of RFC xxxx URI scheme semantics: see Section 2.2 of RFC xxxx
URI scheme encoding considerations: see Section 2.3 of RFC xxxx URI scheme encoding considerations: see Section 2.3 of RFC xxxx
Applications that use the scheme: "about" URIs are predominantly Applications that use the scheme: "about" URIs are predominantly
Web browsers. used by Web browsers.
Security considerations: see Section 4 of RFC xxxx Security considerations: see Section 4 of RFC xxxx
Contact: IETF Applications Area Directors <app-ads@tools.ietf.org> Contact: IETF Applications Area Directors <app-ads@tools.ietf.org>
Author/Change controller: IESG <iesg@ietf.org> (on behalf of the Author/Change controller: IESG <iesg@ietf.org> (on behalf of the
IETF) IETF)
References: see Section 5 of RFC xxxx References: see Section 5 of RFC xxxx
skipping to change at page 4, line 47 skipping to change at page 4, line 50
5.2. A Registry for Well-known Tokens 5.2. A Registry for Well-known Tokens
This document creates the '"about" URI Well-known Tokens' registry. This document creates the '"about" URI Well-known Tokens' registry.
The registry entries consist of three fields: Well-known Token, The registry entries consist of three fields: Well-known Token,
Description and Reference. The Well-known Token field has to conform Description and Reference. The Well-known Token field has to conform
to <about-token> production defined in Section 2.1. The initial set to <about-token> production defined in Section 2.1. The initial set
of assignments is as follows: of assignments is as follows:
+------------------+------------------------------------+-----------+ +--------------+------------------------------------+-------------+
| Special-Purpose | Description | Reference | | Well-known | Description | Reference |
| Token | | | | Token | | |
+------------------+------------------------------------+-----------+ +------------------+--------------------------------+-------------+
| blank | Used in "about" URIs to refer to | RFC xxxx | | blank | Used in "about" URIs to refer to | RFC xxxx |
| | blank page. | | | | blank page | |
+------------------+------------------------------------+-----------+ +--------------+------------------------------------+-------------+
5.2.1. Registration procedure 5.2.1. Registration procedure
The registration policy for this registry is "First Come First The registration policy for this registry is "First Come First
Served" as described in RFC 5226 [RFC5226]. The registrant of the Served" as described in RFC 5226 [RFC5226]. The registrant of the
token should provide the information mentioned in the following token should provide the information mentioned in the following
registration template: registration template:
o Registered Token: The desired special-purpose token to be used in o Registered Token: The desired Well-known token to be used in
"about" URIs. "about" URIs.
o Intended usage: A short description of how "about" URIs with the o Intended usage: A short description of how "about" URIs with the
registered token is handled including information about the registered token is handled including information about the
referenced resource. referenced resource.
o Contact/Change controller: Person (including contact information) o Contact/Change controller: Person (including contact information)
authorized to change this registration. authorized to change this registration.
o Specification: A stable reference to a document which specifies o Specification: A stable reference to a document which specifies
skipping to change at page 6, line 11 skipping to change at page 6, line 15
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for
Syntax Specifications: ABNF", STD 68, RFC 5234, January Syntax Specifications: ABNF", STD 68, RFC 5234, January
2008. 2008.
6.2. Informative References 6.2. Informative References
[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource
Identifiers (IRIs)", RFC 3987, January 2005.
[RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
Registration Procedures for New URI Schemes", BCP 35, Registration Procedures for New URI Schemes", BCP 35,
RFC 4395, February 2006. RFC 4395, February 2006.
Appendix A. Acknowledgments Appendix A. Acknowledgments
This document has been formed from the draft initially authored by This document has been formed from the draft initially authored by
Lachlan Hunt and Joseph Holsten. Additionally, the contributions of Lachlan Hunt and Joseph Holsten. Additionally, the contributions of
Frank Ellermann and Alexey Melnikov are gratefully acknowledged. Frank Ellermann and Alexey Melnikov are gratefully acknowledged.
Barry Leiba and Murray Kucherawy deserve a special credit for Barry Leiba and Murray Kucherawy deserve a special credit for
 End of changes. 14 change blocks. 
23 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/