The 'file' URI Scheme
draft-kerwin-file-scheme-09

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Matthew Kerwin 
Last updated 2013-12-10
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                       December 11, 2013
Expires: June 14, 2014

                         The 'file' URI Scheme
                      draft-kerwin-file-scheme-09

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 resolving 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 June 14, 2014.

Copyright Notice

   Copyright (c) 2013 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 June 14, 2014                 [Page 1]
Internet-Draft                 'file' URI                  December 2013

   carefully, as they describe your rights and restrictions with respect
   to this document.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  History . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Conventions and Terminology . . . . . . . . . . . . . . .   4
   2.  Scheme Definition . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Components  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Implementation Notes  . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Leading Slash . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Hierarchical Structure  . . . . . . . . . . . . . . . . .   8
     3.3.  Absolute and relative file paths  . . . . . . . . . . . .   8
     3.4.  Drive Letters . . . . . . . . . . . . . . . . . . . . . .   9
     3.5.  UNC File Paths  . . . . . . . . . . . . . . . . . . . . .   9
       3.5.1.  Historical Issues with UNC File Paths . . . . . . . .  11
     3.6.  Namespaces  . . . . . . . . . . . . . . . . . . . . . . .  11
   4.  Encoding and Character Set Considerations . . . . . . . . . .  11
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     6.1.  URI Scheme Name . . . . . . . . . . . . . . . . . . . . .  12
     6.2.  Status  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     6.3.  URI Scheme Syntax . . . . . . . . . . . . . . . . . . . .  12
     6.4.  URI Scheme Semantics  . . . . . . . . . . . . . . . . . .  12
     6.5.  Encoding Considerations . . . . . . . . . . . . . . . . .  12
     6.6.  Applications/Protocols That Use This URI Scheme Name  . .  13
     6.7.  Interoperability Considerations . . . . . . . . . . . . .  13
     6.8.  Security Considerations . . . . . . . . . . . . . . . . .  13
     6.9.  Contact . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.10. Author/Change Controller  . . . . . . . . . . . . . . . .  13
     6.11. References  . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  15

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
   particular filesystem.  This document attempts to resolve those
   problems, and define a standard scheme which is interoperable between
   different extant and future implementations.  Additionally, it aims
   to ease implementation by conforming to a general syntax that allows
   existing URI parsing machinery to parse 'file' URIs.
Show full document text