attachment
<div dir="ltr"><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><br></div></div></div></div>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername"></b> <span dir="ltr"><<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>></span><br>Date: Fri, Feb 17, 2017 at 11:36 PM<br>Subject: [art] RFC 8089 on The "file" URI Scheme<br>To: <a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>, <a href="mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a><br>Cc: <a href="mailto:drafts-update-ref@iana.org">drafts-update-ref@iana.org</a>, <a href="mailto:art@ietf.org">art@ietf.org</a>, <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br><br><br>A new Request for Comments is now available in online RFC libraries.<br>
<br>
<br>
RFC 8089<br>
<br>
Title: The "file" URI Scheme<br>
Author: M. Kerwin<br>
Status: Standards Track<br>
Stream: IETF<br>
Date: February 2017<br>
Mailbox: <a href="mailto:matthew.kerwin@qut.edu.au">matthew.kerwin@qut.edu.au</a><br>
Pages: 19<br>
Characters: 36893<br>
Updates: RFC 1738<br>
<br>
I-D Tag: draft-ietf-appsawg-file-<wbr>scheme-16.txt<br>
<br>
URL: <a href="https://www.rfc-editor.org/info/rfc8089" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>info/rfc8089</a><br>
<br>
DOI: 10.17487/RFC8089<br>
<br>
This document provides a more complete specification of the "file"<br>
Uniform Resource Identifier (URI) scheme and replaces the very brief<br>
definition in Section 3.10 of RFC 1738.<br>
<br>
It defines a common syntax that is intended to interoperate across<br>
the broad spectrum of existing usages. At the same time, it notes<br>
some other current practices around the use of file URIs.<br>
<br>
This document is a product of the ART Area General Application Working Group Working Group of the IETF.<br>
<br>
This is now a Proposed Standard.<br>
<br>
STANDARDS TRACK: This document specifies an Internet Standards Track<br>
protocol for the Internet community, and requests discussion and suggestions<br>
for improvements. Please refer to the current edition of the Official<br>
Internet Protocol Standards (<a href="https://www.rfc-editor.org/standards" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>standards</a>) for the<br>
standardization state and status of this protocol. Distribution of this<br>
memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/ietf-announce</a><br>
<a href="https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" rel="noreferrer" target="_blank">https://mailman.rfc-editor.<wbr>org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href="https://www.rfc-editor.org/search" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>search</a><br>
For downloading RFCs, see <a href="https://www.rfc-editor.org/retrieve/bulk" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>retrieve/bulk</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>. Unless<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
Association Management Solutions, LLC<br>
<br>
<br>
______________________________<wbr>_________________<br>
art mailing list<br>
<a href="mailto:art@ietf.org">art@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/art" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/art</a><br>
</div><br></div>