W3C home > Mailing lists > Public > uri@w3.org > February 2006

FW: BCP0115 RFC 4395 on Guidelines and Registration Procedures for NewURI Schemes

From: Larry Masinter <LMM@acm.org>
Date: Tue, 28 Feb 2006 12:42:54 -0800
To: uri@w3.org
Message-id: <001701c63ca7$8cb49e10$bca62099@corp.adobe.com>


-----Original Message-----
From: ietf-announce-bounces@ietf.org On Behalf Of rfc-editor@rfc-editor.org
Sent: Monday, February 13, 2006 6:08 PM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: rfc-editor@rfc-editor.org
Subject: BCP0115 RFC 4395 on Guidelines and Registration Procedures for
NewURI Schemes

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

        BCP 115        
        RFC 4395

        Title:      Guidelines and Registration Procedures for 
                    New URI Schemes 
        Author:     T. Hansen,  T. Hardie, 
                    L. Masinter
        Status:     Best Current Practice
        Date:       February 2006
        Mailbox:    tony+urireg@maillennium.att.com, 
                    hardie@qualcomm.com, 
                    LMM@acm.org
        Pages:      15
        Characters: 31933
        
        I-D Tag:    draft-hansen-2717bis-2718bis-uri-guidelines-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4395.txt

This document provides guidelines and recommendations for the
definition of Uniform Resource Identifier (URI) schemes.  It also
updates the process and IANA registry for URI schemes.  It obsoletes
both RFC 2717 and RFC 2718.  This document specifies an Internet Best
Current Practices for the Internet Community, and requests 
discussion and suggestions for improvements.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
Received on Tuesday, 28 February 2006 20:43:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:36 GMT