The file URI Scheme
draft-ietf-appsawg-file-scheme-16

Document Type Active Internet-Draft (appsawg WG)
Last updated 2016-12-21 (latest revision 2016-12-15)
Replaces draft-kerwin-file-scheme
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication May 2016
Document shepherd Dave Crocker
Shepherd write-up Show (last changed 2016-11-12)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
Applications Area Working Group                                M. Kerwin
Internet-Draft                                                       QUT
Updates: 1738 (if approved)                            December 16, 2016
Intended status: Standards Track
Expires: June 19, 2017

                          The file URI Scheme
                   draft-ietf-appsawg-file-scheme-16

Abstract

   This document provides a more complete specification of the "file"
   Uniform Resource Identifier (URI) scheme, replacing the very brief
   definition in Section 3.10 of RFC 1738.

   It defines a common syntax which is intended to interoperate across
   the broad spectrum of existing usages.  At the same time it notes
   some other current practices around the use of file URIs.

Note to Readers (To be removed by the RFC Editor)

   This draft should be discussed on the IETF Applications Area Working
   Group discussion list <apps-discuss@ietf.org>.

Status of This Memo

   This Internet-Draft is submitted 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 19, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Kerwin                    Expires June 19, 2017                 [Page 1]
Internet-Draft                 file-scheme                 December 2016

   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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
   2.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Operations Involving file URIs  . . . . . . . . . . . . . . .   5
   4.  File System Name Encoding . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Differences from Previous Specifications . . . . . .   9
   Appendix B.  Example URIs . . . . . . . . . . . . . . . . . . . .   9
   Appendix C.  Similar Technologies . . . . . . . . . . . . . . . .  10
   Appendix D.  System-Specific Operations . . . . . . . . . . . . .  10
     D.1.  POSIX Systems . . . . . . . . . . . . . . . . . . . . . .  11
     D.2.  DOS- and Windows-Like Systems . . . . . . . . . . . . . .  11
     D.3.  Mac OS X Systems  . . . . . . . . . . . . . . . . . . . .  11
     D.4.  OpenVMS Files-11 Systems  . . . . . . . . . . . . . . . .  11
   Appendix E.  Nonstandard Syntax Variations  . . . . . . . . . . .  11
     E.1.  User Information  . . . . . . . . . . . . . . . . . . . .  12
     E.2.  DOS and Windows Drive Letters . . . . . . . . . . . . . .  12
       E.2.1.  Relative Resolution . . . . . . . . . . . . . . . . .  13
       E.2.2.  Vertical Line Character . . . . . . . . . . . . . . .  13
     E.3.  UNC Strings . . . . . . . . . . . . . . . . . . . . . . .  14
       E.3.1.  file URI with Authority . . . . . . . . . . . . . . .  14
       E.3.2.  file URI with UNC Path  . . . . . . . . . . . . . . .  15
     E.4.  Backslash as Separator  . . . . . . . . . . . . . . . . .  16
   Appendix F.  Collected Nonstandard Rules  . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   A file URI identifies an object (a "file") stored in a structured
Show full document text