W3C home > Mailing lists > Public > uri@w3.org > November 1999

BCP 35, RFC 2717 on Registration Procedures for URL Scheme Names

From: Daniel LaLiberte <liberte@w3.org>
Date: Fri, 12 Nov 1999 09:21:56 -0500 (EST)
Message-ID: <14380.8836.340595.582195@alceste.w3.org>
To: uri@w3.org
Forwarded Text ----
 To: IETF-Announce: ;
 Subject: BCP 35, RFC 2717 on Registration Procedures for URL Scheme Names
 Cc: rfc-ed@ISI.EDU
 Date: Mon, 08 Nov 1999 09:00:39 -0800
 From: RFC Editor <rfc-ed@ISI.EDU>
 A new Request for Comments is now available in online RFC libraries.
         BCP 35        
         RFC 2717
         Title:	    Registration Procedures for URL Scheme Names
         Author(s):  R. Petke, I. King
         Status:     Best Current Practice
 	Date:       November 1999
         Mailbox:    rpetke@wcom.net, iking@microsoft.com
         Pages:      10
         Characters: 19780
 	Updates/Obsoletes/See Also: None  
         I-D Tag:    draft-ietf-urlreg-procedures-08.txt
         URL:        ftp://ftp.isi.edu/in-notes/rfc2717.txt
 This document defines the process by which new URL scheme names are
 This document is a product of the Uniform Resource Locator
 Registration Procedures Working Group of the IETF.
 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
 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.echo 
 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
 Below is the data which will enable a MIME compliant Mail Reader 
 implementation to automatically retrieve the ASCII version
 of the RFCs.
 Content-Type: text/plain
 Content-ID: <991108085519.RFC@RFC-EDITOR.ORG>
 DOC-ID: rfc2717
End Forwarded Text ----
Received on Friday, 12 November 1999 09:21:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:01 UTC