The 'file' URI Scheme
draft-kerwin-file-scheme-10
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Matthew Kerwin
|
|
Last updated |
|
2014-03-06
|
|
Replaced by |
|
RFC 8089, RFC 8089
|
|
Stream |
|
(None)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Independent Submission M. Kerwin
Internet-Draft QUT
Intended status: Standards Track March 7, 2014
Expires: September 8, 2014
The 'file' URI Scheme
draft-kerwin-file-scheme-10
Abstract
This document specifies the file Uniform Resource Identifier (URI)
scheme that was originally specified in RFC 1738. The purpose of
this document is to keep the information about the scheme on
standards track, since RFC 1738 has been made obsolete, and to
promote interoperability by addressing disagreements between various
implementations.
Note to Readers
This draft should be discussed on its github project page [github].
Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 11, 2014.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Kerwin Expires September 8, 2014 [Page 1]
Internet-Draft 'file' URI March 2014
carefully, as they describe your rights and restrictions with respect
to this document.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. History . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Conventions and Terminology . . . . . . . . . . . . . . . 4
2. Scheme Definition . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Components . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Encoding and Character Set Considerations . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. Implementation Notes . . . . . . . . . . . . . . . . . . . . 8
5.1. Leading Slash . . . . . . . . . . . . . . . . . . . . . . 8
5.2. Hierarchical Structure . . . . . . . . . . . . . . . . . 9
5.3. Absolute and relative file paths . . . . . . . . . . . . 9
5.4. Drive Letters . . . . . . . . . . . . . . . . . . . . . . 10
5.5. UNC File Paths . . . . . . . . . . . . . . . . . . . . . 11
5.5.1. Historical Issues with UNC File Paths . . . . . . . . 12
5.6. Namespaces . . . . . . . . . . . . . . . . . . . . . . . 12
5.7. Media Type . . . . . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
6.1. URI Scheme Name . . . . . . . . . . . . . . . . . . . . . 13
6.2. Status . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.3. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . 13
6.4. URI Scheme Semantics . . . . . . . . . . . . . . . . . . 13
6.5. Encoding Considerations . . . . . . . . . . . . . . . . . 13
6.6. Applications/Protocols That Use This URI Scheme Name . . 13
6.7. Interoperability Considerations . . . . . . . . . . . . . 14
6.8. Security Considerations . . . . . . . . . . . . . . . . . 14
6.9. Contact . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.10. Author/Change Controller . . . . . . . . . . . . . . . . 14
6.11. References . . . . . . . . . . . . . . . . . . . . . . . 14
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative References . . . . . . . . . . . . . . . . . . 15
8.2. Informative References . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17
Kerwin Expires September 8, 2014 [Page 2]
Internet-Draft 'file' URI March 2014
1. Introduction
The 'file' URI scheme has historically had little or no
interoperability between platforms. Further, implementers on a
single platform have often disagreed on the syntax to use for a
Show full document text