From: uri-request at w3.org [mailto:uri-request at w3.org]On Behalf Of Martin
Sent: Tuesday, January 25, 2005 9:20 PM
To: uri at w3.org
Subject: Fwd: STD 66,RFC 3986 on Uniform Resource Identifier (URI):
The URI spec is an IETF Standard! Thanks to all the people who
contributed over the long time this has been in the works!
>To: ietf-announce at ietf.org
>From: rfc-editor at rfc-editor.org
>Date: Tue, 25 Jan 2005 17:32:09 -0800
>Subject: STD 66,RFC 3986 on Uniform Resource Identifier (URI): Generic
e-request at ietf.org?subject=unsubscribe>
>List-Post: <mailto:ietf-announce at ietf.org>
>List-Help: <mailto:ietf-announce-request at ietf.org?subject=help>
e-request at ietf.org?subject=subscribe>
>A new Request for Comments is now available in online RFC libraries.
> STD 66
> RFC 3986
> Title: Uniform Resource Identifier (URI): Generic Syntax
> Author(s): T. Berners-Lee, R. Fielding, L. Masinter
> Status: Standards Track
> Date: January 2005
> Mailbox: timbl at w3.org, fielding at gbiv.com, LMM at acm.org
> Pages: 61
> Characters: 141811
> Updates: 1738
> Obsoletes: 2732, 2396, 1808
> I-D Tag: draft-fielding-uri-rfc2396bis-07.txt
> URL: ftp://ftp.rfc-editor.org/in-notes/rfc3986.txt
>A Uniform Resource Identifier (URI) is a compact sequence of
>characters that identifies an abstract or physical resource. This
>specification defines the generic URI syntax and a process for
>resolving URI references that might be in relative form, along with
>guidelines and security considerations for the use of URIs on the
>Internet. The URI syntax defines a grammar that is a superset of all
>valid URIs, allowing an implementation to parse the common
>components of a URI reference without knowing the scheme-specific
>requirements of every possible identifier. This specification does
>not define a generative grammar for URIs; that task is performed by
>the individual specifications of each URI scheme.
>This is now a Standard Protocol.
>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 "Internet
>Official Protocol Standards" (STD 1) for the standardization state
>and status of this protocol. Distribution of this memo is unlimited.
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST at IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
>help: ways_to_get_rfcs. For example:
> To: rfc-info at RFC-EDITOR.ORG
> Subject: getting rfcs
> help: ways_to_get_rfcs
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>Below is the data which will enable a MIME compliant Mail Reader
>implementation to automatically retrieve the ASCII version
>of the RFCs.
>Content-ID: <050125173042.RFC at RFC-EDITOR.ORG>
>IETF-Announce mailing list
>IETF-Announce at ietf.org