The file URI Scheme
draft-kerwin-file-scheme-05

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Matthew Kerwin 
Last updated 2013-07-03
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)
Network Working Group                                          M. Kerwin
Internet-Draft                                                       QUT
Intended status: Standards Track                               July 2013
Expires: January 05, 2013

                          The file URI Scheme
                      draft-kerwin-file-scheme-05

Abstract

   This document specifies the file Uniform Resource Identifier (URI)
   scheme that was originally specified in [RFC1738].  The purpose of
   this document is to keep the information about the scheme on
   standards track, since [RFC1738] has been made obsolete.

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 December 03, 2013.

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
   carefully, as they describe your rights and restrictions with respect
   to this document.

Kerwin                  Expires December 03, 2013               [Page 1]
Internet-Draft                 File Scheme                     July 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  History . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Conventions and Terminology . . . . . . . . . . . . . . .   4
   2.  Scheme Definition . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Implementation Notes  . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Hierarchical Structure  . . . . . . . . . . . . . . . . .   6
     3.2.  Relative file paths . . . . . . . . . . . . . . . . . . .   6
     3.3.  Drives, drive letters, mount points, file system root . .   7
     3.4.  UNC File Paths  . . . . . . . . . . . . . . . . . . . . .   8
     3.5.  Namespaces  . . . . . . . . . . . . . . . . . . . . . . .   9
     3.6.  Character sets and encodings  . . . . . . . . . . . . . .   9
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   8.  Author's Address  . . . . . . . . . . . . . . . . . . . . . .  11

Kerwin                  Expires December 03, 2013               [Page 2]
Internet-Draft                 File Scheme                     July 2013

1.  Introduction

   URIs were previously defined in [RFC1738], which was updated by
   [RFC3986].  Those documents also specify how to define schemes for
   URIs.

   The first definition for many URI schemes appeared in [RFC1738].
   Because that document has been made obsolete, this document copies
   the file URI scheme from it to allow that material to remain on
   standards track.

1.1.  History

   This section is non-normative.

   The file URI scheme was first defined in [RFC1630], which, being an
   informational RFC, does not specify an Internet standard.  The
   definition was standardised in [RFC1738], and the scheme was
   registered with the Internet Assigned Numbers Authority (IANA)
   [IANA-URI-Schemes]; however the latter definition omitted certain
   language included by former that clarified aspects such as:

   o  the use of slashes to donate boundaries between directory levels
      of a hierarchical file system;

   o  the requirement that client software convert the file URI into a
      file name in the local file name conventions;

   o  a justification for defining the scheme.

   The Internet draft [I-D.draft-hoffman-file-uri] was written in an
   effort to keep the file URI scheme on standards track when [RFC1738]
   was made obsolete, but that draft expired in 2005.  It enumerated
   concerns arising from the various, often conflicting implementations
   of the scheme.  It serves as the basis of this document.
Show full document text