attachment
Hi,<br><br>Vendors and standards editors who need to register new URI schemes<br>- please read and use the IANA registration template from IETF BCP 35 <br>(RFC 7595).<br><br>Cheers,<br>- Ira<br><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></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, Jun 19, 2015 at 6:24 PM<br>Subject: [apps-discuss] BCP 35, RFC 7595 on Guidelines and Registration Procedures for URI Schemes<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:apps-discuss@ietf.org">apps-discuss@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>
BCP 35<br>
RFC 7595<br>
<br>
Title: Guidelines and Registration Procedures for<br>
URI Schemes<br>
Author: D. Thaler, Ed.,<br>
T. Hansen,<br>
T. Hardie<br>
Status: Best Current Practice<br>
Stream: IETF<br>
Date: June 2015<br>
Mailbox: <a href="mailto:dthaler@microsoft.com">dthaler@microsoft.com</a>,<br>
<a href="mailto:tony%2Burireg@maillennium.att.com">tony+urireg@maillennium.att.com</a>,<br>
<a href="mailto:ted.ietf@gmail.com">ted.ietf@gmail.com</a><br>
Pages: 19<br>
Characters: 42897<br>
Obsoletes: RFC 4395<br>
See Also: BCP 35<br>
<br>
I-D Tag: draft-ietf-appsawg-uri-scheme-reg-06.txt<br>
<br>
URL: <a href="https://www.rfc-editor.org/info/rfc7595" rel="noreferrer" target="_blank">https://www.rfc-editor.org/info/rfc7595</a><br>
<br>
DOI: <a href="http://dx.doi.org/10.17487/RFC7595" rel="noreferrer" target="_blank">http://dx.doi.org/10.17487/RFC7595</a><br>
<br>
This document updates the guidelines and recommendations, as well as<br>
the IANA registration processes, for the definition of Uniform<br>
Resource Identifier (URI) schemes. It obsoletes RFC 4395.<br>
<br>
This document is a product of the Applications Area Working Group Working Group of the IETF.<br>
<br>
<br>
BCP: This document specifies an Internet Best Current Practices for the<br>
Internet Community, and requests discussion and suggestions for<br>
improvements. Distribution of this 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/listinfo/ietf-announce</a><br>
<a href="https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" rel="noreferrer" target="_blank">https://mailman.rfc-editor.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/search</a><br>
For downloading RFCs, see <a href="https://www.rfc-editor.org/rfc.html" rel="noreferrer" target="_blank">https://www.rfc-editor.org/rfc.html</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>
apps-discuss mailing list<br>
<a href="mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/apps-discuss" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
</div><br>