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

rfc-editor@rfc-editor.org Fri, 19 June 2015 22:27 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C3A71B2B77; Fri, 19 Jun 2015 15:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2OGFqQnHj4k; Fri, 19 Jun 2015 15:27:16 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id C79541B2B74; Fri, 19 Jun 2015 15:27:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B2549180092; Fri, 19 Jun 2015 15:24:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 35, RFC 7595 on Guidelines and Registration Procedures for URI Schemes
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150619222422.B2549180092@rfc-editor.org>
Date: Fri, 19 Jun 2015 15:24:22 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/q9SH6d_2Ma47HTynktPIaNeQ4Qs>
Cc: drafts-update-ref@iana.org, apps-discuss@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jun 2015 22:27:18 -0000

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