W3C home > Mailing lists > Public > public-ietf-w3c@w3.org > July 2015

Fwd: BCP 35, RFC 7595 on Guidelines and Registration Procedures for URI Schemes

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 15 Jul 2015 16:12:44 +0200
To: public-ietf-w3c <public-ietf-w3c@w3.org>
Message-Id: <E7301A0E-AA2F-4385-8FAC-7058FC0F2CE3@mnot.net>
FYI.


> Begin forwarded message:
> 
> From: rfc-editor@rfc-editor.org
> Subject: BCP 35, RFC 7595 on Guidelines and Registration Procedures for URI Schemes
> Date: 20 June 2015 12:24:22 am GMT+2
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: drafts-update-ref@iana.org, apps-discuss@ietf.org, rfc-editor@rfc-editor.org
> Reply-To: ietf@ietf.org
> Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/q9SH6d_2Ma47HTynktPIaNeQ4Qs>
> 
> A new Request for Comments is now available in online RFC libraries.
> 
>        BCP 35        
>        RFC 7595
> 
>        Title:      Guidelines and Registration Procedures for 
>                    URI Schemes 
>        Author:     D. Thaler, Ed.,
>                    T. Hansen,
>                    T. Hardie
>        Status:     Best Current Practice
>        Stream:     IETF
>        Date:       June 2015
>        Mailbox:    dthaler@microsoft.com, 
>                    tony+urireg@maillennium.att.com, 
>                    ted.ietf@gmail.com
>        Pages:      19
>        Characters: 42897
>        Obsoletes:  RFC 4395
>        See Also:   BCP 35
> 
>        I-D Tag:    draft-ietf-appsawg-uri-scheme-reg-06.txt
> 
>        URL:        https://www.rfc-editor.org/info/rfc7595
> 
>        DOI:        http://dx.doi.org/10.17487/RFC7595
> 
> This document updates the guidelines and recommendations, as well as
> the IANA registration processes, for the definition of Uniform
> Resource Identifier (URI) schemes.  It obsoletes RFC 4395.
> 
> This document is a product of the Applications Area Working Group Working Group of the IETF.
> 
> 
> BCP: 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-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  https://www.ietf.org/mailman/listinfo/ietf-announce
>  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/rfc.html
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 

--
Mark Nottingham   https://www.mnot.net/
Received on Wednesday, 15 July 2015 14:13:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 15 July 2015 14:13:13 UTC