idnits 2.17.1 draft-kerwin-file-scheme-00.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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 3) being 111 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The abstract seems to contain references ([RFC1738]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 20, 2013) is 3955 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 1738 (Obsoleted by RFC 4248, RFC 4266) Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Kerwin 3 Internet-Draft June 20, 2013 4 Intended status: Standards Track 5 Expires: December 22, 2013 7 The file URI Scheme 8 draft-kerwin-file-scheme-00 10 Abstract 12 This document specifies the file Uniform Resource Identifier (URI) 13 scheme that was originally specified in [RFC1738]. The purpose of 14 this document is to keep the information about the scheme on 15 standards track, since [RFC1738] has been made obsolete. 17 Status of This Memo 19 This Internet-Draft is submitted to IETF in full conformance with 20 the provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress". 32 This Internet-Draft will expire on December 22, 2013. 34 Copyright Notice 36 Copyright (c) 2013 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2. Scheme Definition . . . . . . . . . . . . . . . . . . . . . . 3 53 3. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3.1 Normative References . . . . . . . . . . . . . . . . . . . 3 55 3.2 Informative References . . . . . . . . . . . . . . . . . . 3 56 Author's Address . . . . . . . . . . . . . . . . . . . 3 58 1. Introduction 60 URIs were previously defined in [RFC1738], which was updated by 61 [RFC3986]. Those documents also specify how to define schemes for 62 URIs. 64 The first definition for many URI schemes appeared in [RFC1738]. 65 Because that document has been made obsolete, this document copies 66 the file URI scheme from it to allow that material to remain on 67 standards track. 69 2. Scheme Definition 71 The file URL scheme is used to designate files accessible on a 72 particular host computer. This scheme, unlike most other URL schemes, 73 does not designate a resource that is universally accessible over 74 the Internet. 76 A file URL takes the form: 78 file:/// 80 where is the fully quilified domain name of the system on 81 which the is accessible, and is a hierarchical 82 directory path of the form //... 84 For example, a VMS file 86 DISK$USER:[MY.NOTES]NOTE123456.TXT 88 might become 90 92 As a special case, can be the string "localhost" or the empty 93 string; this is interpreted as `the machine from which the URL is 94 being interpreted'. 96 The file URL scheme is unusual in that it does not specify an 97 Internet protocol or access method for such files; as such, its 98 utility in network protocols between hosts is limited. 100 3. References 102 3.1 Normative References 104 3.2 Informative References 106 [RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform 107 Resource Locators (URL)", RFC 1738, December 1994. 109 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 110 Resource Identifier (URI): Generic Syntax", STD 66, 111 RFC 3986, January 2005. 113 Author's Address 115 Matthew Kerwin 117 Email: matthew@kerwin.net.au