[art] RFC 8089 on The "file" URI Scheme

rfc-editor@rfc-editor.org Sat, 18 February 2017 04:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 669FF129704; Fri, 17 Feb 2017 20:36:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b9FvhW9GmDja; Fri, 17 Feb 2017 20:36:10 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74098129463; Fri, 17 Feb 2017 20:36:10 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6954BB812CD; Fri, 17 Feb 2017 20:36:10 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170218043610.6954BB812CD@rfc-editor.org>
Date: Fri, 17 Feb 2017 20:36:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/tGmjEiDwfXuRTIrTmXr0Y9U3620>
Cc: drafts-update-ref@iana.org, art@ietf.org, rfc-editor@rfc-editor.org
Subject: [art] RFC 8089 on The "file" URI Scheme
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2017 04:36:11 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8089

        Title:      The "file" URI Scheme 
        Author:     M. Kerwin
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2017
        Mailbox:    matthew.kerwin@qut.edu.au
        Pages:      19
        Characters: 36893
        Updates:    RFC 1738

        I-D Tag:    draft-ietf-appsawg-file-scheme-16.txt

        URL:        https://www.rfc-editor.org/info/rfc8089

        DOI:        10.17487/RFC8089

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

It defines a common syntax that 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.

This document is a product of the ART Area General Application Working Group Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC