RFC 7936 on Clarifying Registry Procedures for the WebSocket Subprotocol Name Registry

rfc-editor@rfc-editor.org Tue, 19 July 2016 14:33 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D7B12E147 for <ietf-announce@ietfa.amsl.com>; Tue, 19 Jul 2016 07:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 TpP-xlbqWhNQ for <ietf-announce@ietfa.amsl.com>; Tue, 19 Jul 2016 07:33:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9543E12D93C for <ietf-announce@ietf.org>; Tue, 19 Jul 2016 07:01:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 77979B80E1A; Tue, 19 Jul 2016 07:01:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7936 on Clarifying Registry Procedures for the WebSocket Subprotocol Name Registry
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160719140132.77979B80E1A@rfc-editor.org>
Date: Tue, 19 Jul 2016 07:01:32 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/YJuaI-Wf7xZeNpBlznT3rkQdZMg>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 19 Jul 2016 14:33:49 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7936

        Title:      Clarifying Registry Procedures for the 
                    WebSocket Subprotocol Name Registry 
        Author:     T. Hardie
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2016
        Mailbox:    ted.ietf@gmail.com
        Pages:      3
        Characters: 4873
        Updates:    RFC 6455

        I-D Tag:    draft-hardie-rfc6455-iana-clarification-03.txt

        URL:        https://www.rfc-editor.org/info/rfc7936

        DOI:        http://dx.doi.org/10.17487/RFC7936

This document clarifies the instructions to IANA for the subprotocol
registry set up for WebSockets in RFC 6455.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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/retrieve/bulk

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