idnits 2.17.1 draft-yevstifeyev-view-source-uri-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 23, 2011) is 4745 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 4395 (Obsoleted by RFC 7595) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT M. Yevstifeyev 3 Intended Status: Informational April 23, 2011 4 Expires: October 25, 2011 6 The 'view-source' URI Scheme 7 draft-yevstifeyev-view-source-uri-01 9 Abstract 11 This document specifies the 'view-source' Uniform Resource Identifier 12 (URI) scheme, which refers to the source code of resource identified 13 by it. 15 Status of this Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as 23 Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/1id-abstracts.html 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html 36 Copyright and License Notice 38 Copyright (c) 2011 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. URI Scheme Registration Template . . . . . . . . . . . . . . . 2 56 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 57 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 58 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 5.1. Normative References . . . . . . . . . . . . . . . . . . . 4 60 5.2. Informative References . . . . . . . . . . . . . . . . . . 5 61 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 63 1. Introduction 65 This document specifies the 'view-source' Uniform Resource Identifier 66 (URI) scheme. The 'view-source' URIs have long been used by web- 67 browsers to refer to the source code of resource identified by it 68 having mostly semi-formal specifications (such as the article at 69 Microsoft Developer Network libarary [MSDN-VIEW-SOURCE]) and no 70 official record at the IETF. This document is to remove this 71 uncertainty; it gives the formal definition of 'view-source' URI 72 scheme and registers it in the corresponding IANA registry. 74 Generic URI syntax is defined in RFC 3986 [RFC3986]; registration 75 procedures for new URI schemes are described in RFC 4395 [RFC4395]. 77 1.1. Terminology 79 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 80 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 81 document are to be interpreted as described in RFC 2119 [RFC2119]. 83 2. URI Scheme Registration Template 85 This section contains the registration template for 'view-source' URI 86 scheme, as required by RFC 4395 [RFC4395]. 88 o URI Scheme Name: view-source 90 o Status: Provisional 92 o URI Scheme Syntax: The 'view-source' URI takes the form of the 93 rule below, defined in ABNF [RFC5234]: 95 view-source-uri = "view-source:" absolute-URI 97 where the rule is defined in Appendix A of RFC 3986 98 [RFC3986] 100 o URI Scheme Semantics: The application resolving the 'view-source' 101 URI SHALL return the source code of the resource, identified by 102 . Each application implementing the 'view-source' 103 URI scheme is permitted to choose how the source code is displayed. 104 However this specification recommends that it SHOULD be 105 represented in the media type "text/plain" [RFC2046] or "text/html" 106 [RFC2854] and the character encoding "UTF-8" [RFC3629]. 108 Per RFC 4395, not all URI schemes are used to refer to a particular 109 piece of information (a resource), but rather identify the endpoint 110 for establishing connection (for instance, the 'telnet' URI scheme 111 [RFC4248]) or performing other actions (such as sending an e-mail 112 message [RFC5322] using the 'mailto' URI scheme [RFC6068]). 113 Therefore if the 'view-source' URI refers to such URI (e. g. 114 with a 'tel' URI [RFC3966] in the 115 part), such URI SHALL be resolved to the resource of 116 zero length, containing no data, with the media type "text/plain" 117 [RFC2046] and the character encoding "UTF-8" [RFC3629]. 119 This specification does not set any restrictions on how the 120 applications shall resolve such URIs as 121 , i. e. with the 122 "view-source:" prefixed more than once. However it recommends that 123 such URIs SHOULD be resolved to the resource of zero length, 124 containing no data, with the media type "text/plain" [RFC2046] and 125 the character encoding "UTF-8" [RFC3629] 127 o Encoding Considerations: There are no other encoding 128 considerations for 'view-source' URIs not discussed in RFC 3986 129 [RFC3986] 131 o Applications and Protocols that Use this URI Scheme Name: The 132 'view-source' URIs is generally used by web-browsers. However this 133 document does not place the limit on where else they can be used. 135 See Wikipedia's entry on "View-source URI scheme" 136 [WIKI-VIEW-SOURCE] for the up-to-date list of browser support 137 information 139 o Interoperability Considerations: The 'view-source' URI may 140 sometimes refer to the source code that is under certain legal 141 provisions, according to which an individual or a company may not 142 have granted the free access or other actions with regard to it. 143 The users of such information should be careful regarding these 144 matters 146 o Security Considerations: Security considerations for 'view-source' 147 URIs are discussed in Section 3 of this document 149 o Contact: Mykyta Yevstifeyev 151 o Author/Change Controller: IESG 153 o References: See Section 5 of this document 155 3. Security Considerations 157 Generic security considerations for URIs are discussed in Section 7 158 of RFC 3986 [RFC3986]. 160 The 'view-source' URIs may sometimes reveal the information (source 161 code) that is a governmental, trade or other type of secret and, 162 therefore, disclose confidential information. It can also sometimes 163 refer to the source code that is under certain legal provisions, 164 according to which an individual or a company may not have granted 165 the free access or other actions with regard to it. The users of 166 such information should be careful with regard to these matters. 168 4. IANA Considerations 170 IANA is asked to register the 'view-source' URI scheme using the 171 template of Section 2. 173 5. References 175 5.1. Normative References 177 [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 178 Extensions (MIME) Part Two: Media Types", RFC 2046, 179 November 1996. 181 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 182 Requirement Levels", BCP 14, RFC 2119, March 1997. 184 [RFC2854] Connolly, D. and L. Masinter, "The 'text/html' Media 185 Type", RFC 2854, June 2000. 187 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 188 10646", STD 63, RFC 3629, November 2003. 190 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 191 Resource Identifier (URI): Generic Syntax", STD 66, 192 RFC 3986, January 2005. 194 [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for 195 Syntax Specifications: ABNF", STD 68, RFC 5234, January 196 2008. 198 5.2. Informative References 200 [MSDN-VIEW-SOURCE] 201 Microsoft Corporation, "view-source Protocol," Microsoft 202 Developer Network (MSDN). 203 205 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", 206 RFC 3966, December 2004. 208 [RFC4248] Hoffman, P., "The telnet URI Scheme", RFC 4248, October 209 2005. 211 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 212 Registration Procedures for New URI Schemes", BCP 35, 213 RFC 4395, February 2006. 215 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 216 October 2008. 218 [RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' 219 URI Scheme", RFC 6068, October 2010. 221 [WIKI-VIEW-SOURCE] 222 Wikipedia Contributors, "View-source URI scheme," 223 Wikipedia, The Free Encyclopedia, March 2011. 224 226 Author's Addresses 228 Mykyta Yevstifeyev 229 8 Kuzovkov St., flat 25 230 Kotovsk 231 Ukraine 232 EMail: evnikita2@gmail.com