[rfc-dist] BCP0115 RFC 4395 on Guidelines and Registration Procedures for New URI Schemes
rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Tue, 14 February 2006 02:08 UTC
From: "rfc-editor at rfc-editor.org"
Date: Mon, 13 Feb 2006 18:08:17 -0800
Subject: [rfc-dist] BCP0115 RFC 4395 on Guidelines and Registration Procedures for New URI Schemes
Message-ID: <200602140208.k1E28Hvq013604@nit.isi.edu>
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 at maillennium.att.com, hardie at qualcomm.com, LMM at 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 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 unlimited distribution. 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 ... --ec0fca45c4ebdaf9a53a958d4158ebbd 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 at maillennium.att.com, hardie at qualcomm.com, LMM at 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 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 unlimited distribution. 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 ...
- [rfc-dist] BCP0115 RFC 4395 on Guidelines and Reg… rfc-editor@rfc-editor.org