draft-ietf-appsawg-about-uri-scheme-01.txt   draft-ietf-appsawg-about-uri-scheme-02.txt 
Applications Area WG (APPSAWG) L. Hunt, Ed. Applications Area WG (APPSAWG) L. Hunt, Ed.
Internet-Draft Opera Software, ASA. Internet-Draft Opera Software, ASA.
Intended Status: Standards Track M. Yevstifeyev, Ed. Intended Status: Standards Track M. Yevstifeyev, Ed.
Expires: June 11, 2012 December 9, 2011 Expires: September 4, 2012 March 3, 2012
The "about" URI Scheme The "about" URI Scheme
draft-ietf-appsawg-about-uri-scheme-01 draft-ietf-appsawg-about-uri-scheme-02
Abstract Abstract
This document specifies the "about" URI scheme, that is widely used This document specifies the "about" URI scheme, that 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
skipping to change at page 1, line 41 skipping to change at page 1, line 41
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Copyright and License Notice Copyright and License Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
2. URI Scheme Specification . . . . . . . . . . . . . . . . . . . 3 2. URI Scheme Specification . . . . . . . . . . . . . . . . . . . 3
2.1. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . . 3 2.1. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . . 3
2.2. URI Scheme Semantics . . . . . . . . . . . . . . . . . . . 3 2.2. URI Scheme Semantics . . . . . . . . . . . . . . . . . . . 3
2.2.1. Special-Purpose "about" URIs . . . . . . . . . . . . . 4 2.2.1. Special-Purpose "about" URIs . . . . . . . . . . . . . 3
2.3. Encoding Considerations . . . . . . . . . . . . . . . . . . 4 2.3. Encoding Considerations . . . . . . . . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
4.1. URI Scheme Registration . . . . . . . . . . . . . . . . . . 4 4.1. URI Scheme Registration . . . . . . . . . . . . . . . . . . 4
4.2. A Registry for Registered Tokens . . . . . . . . . . . . . 5 4.2. A Registry for Registered Tokens . . . . . . . . . . . . . 5
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Normative References . . . . . . . . . . . . . . . . . . . 6 5.1. Normative References . . . . . . . . . . . . . . . . . . . 6
5.2. Informative References . . . . . . . . . . . . . . . . . . 7 5.2. Informative References . . . . . . . . . . . . . . . . . . 7
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 7 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
skipping to change at page 3, line 21 skipping to change at page 3, line 21
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. URI Scheme Specification 2. URI Scheme Specification
2.1. URI Scheme Syntax 2.1. URI Scheme Syntax
The "about" URI MUST syntactically conform to the <about-uri> rule The "about" URI MUST syntactically conform to the <about-uri> rule
below, expressed using Augmented Backus-Naur Form (ABNF) [RFC5234]: below, expressed using Augmented Backus-Naur Form (ABNF) [RFC5234]:
about-uri = "about:" about-token [ about-query ] about-uri = "about:" about-token [ about-query ]
about-token = *( unreserved / pct-encoded ) about-token = *pchar
; for the WG discussion: the possible variants are:
; = *pchar or = segment
; = 1*pchar or = segment-nz
; = segment-nz-nc
; this is to be decided by WG.
about-query = "?" query about-query = "?" query
pchar = <as specified in RFC 3986, Appendix A> pchar = <as specified in RFC 3986, Appendix A>
query = <as specified in RFC 3986, Appendix A> query = <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. and <about-query> to the query component of URI.
2.2. URI Scheme Semantics 2.2. URI Scheme Semantics
Generally speaking, the resource a particular "about" URI resolves to Generally speaking, the resource a particular "about" URI resolves to
skipping to change at page 5, line 21 skipping to change at page 5, line 16
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/protocols that use the scheme: "about" URIs are Applications/protocols that use the scheme: "about" URIs are
predominantly used by Web browsers, although they may be used by predominantly used by Web browsers, although they may be used by
other applications. other applications.
Security considerations: see Section 3 of RFC xxxx Security considerations: see Section 3 of RFC xxxx
Contact: IESG <iesg@ietf.org> (on behalf of the IETF) Contact: IETF Applications Area Directors <app-ads@tools.ietf.org>
Author/Change controller: Applications Area IETF Working Group Author/Change controller: IESG <iesg@ietf.org> (on behalf of the
<apps-discuss@ietf.org> IETF)
References: see Section 5 of RFC xxxx References: see Section 5 of RFC xxxx
[RFC Editor: Please replace xxxx with assigned RFC number] [RFC Editor: Please replace xxxx with assigned RFC number]
4.2. A Registry for Registered Tokens 4.2. A Registry for Registered Tokens
IANA is asked to set up a new registry entitled "'about' URI Special IANA is asked to set up a new registry entitled "'about' URI Special
Purpose Tokens" following the guidelines below. Purpose Tokens" following the guidelines below.
 End of changes. 7 change blocks. 
13 lines changed or deleted 8 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/