Clarifying Registry Procedures for the WebSocket Subprotocol Name Registry

Internet Engineering Task Force (IETF)                         T. Hardie
Request for Comments: 7936                                     July 2016
Updates: <a href="./rfc6455">6455</a>
Category: Standards Track
ISSN: 2070-1721


                     <span class="h1">Clarifying Registry Procedures</span>
              <span class="h1">for the WebSocket Subprotocol Name Registry</span>

Abstract

   This document clarifies the instructions to IANA for the subprotocol
   registry set up for WebSockets in <a href="./rfc6455">RFC 6455</a>.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc7936">http://www.rfc-editor.org/info/rfc7936</a>.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.








<span class="grey">Hardie                       Standards Track                    [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc7936">RFC 7936</a>             IANA Clarification of <a href="./rfc6455">RFC 6455</a>            July 2016</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ................................................... <a href="#page-2">2</a>
   <a href="#section-2">2</a>. Clarified Instructions ......................................... <a href="#page-2">2</a>
   <a href="#section-3">3</a>. Security Considerations ........................................ <a href="#page-2">2</a>
   <a href="#section-4">4</a>. IANA Considerations ............................................ <a href="#page-2">2</a>
   <a href="#section-5">5</a>. Normative References ........................................... <a href="#page-3">3</a>
   Acknowledgements .................................................. <a href="#page-3">3</a>
   Author's Address .................................................. <a href="#page-3">3</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   <a href="./rfc6455#section-11.5">Section 11.5 of [RFC6455]</a> sets up a WebSocket Subprotocol Name
   Registry at IANA and directs IANA to use First Come First Serve
   registration procedures as set out in [<a href="./rfc5226" title="">RFC5226</a>].  The reuse of this
   registry by other protocols has indicated that some clarification of
   the instructions to IANA would be useful.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Clarified Instructions</span>

   The tokens registered in the WebSocket Subprotocol Name Registry
   created by <a href="./rfc6455#section-11.5">Section 11.5 of RFC 6455</a> are matched using case-sensitive
   string match.  IANA is, however, instructed to decline registrations
   in the registry which differ only as to case, in order to minimize
   potential confusion among different registered versions.  For other
   useful advice on avoiding collision, registrants are encouraged to
   consult the non-normative <a href="./rfc6455#section-1.9">Section 1.9 of RFC 6455</a>.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Security Considerations</span>

   This document describes an update to registry policy, not a protocol.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  IANA Considerations</span>

   This document is, in its entirety, a clarification of the registry
   policy for the WebSocket Subprotocol Name Registry.  As part of this
   clarification, IANA has listed both this document and <a href="./rfc6455">RFC 6455</a> as
   references for the WebSocket Subprotocol Name Registry.  In addition,
   IANA has included the following note under the registry's
   Registration Procedures: "Please see <a href="./rfc7936#section-2">Section 2 of RFC 7936</a>, which
   clarifies that registrations which differ from existing registrations
   only by case will be refused."









<span class="grey">Hardie                       Standards Track                    [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc7936">RFC 7936</a>             IANA Clarification of <a href="./rfc6455">RFC 6455</a>            July 2016</span>


<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Normative References</span>

   [<a id="ref-RFC6455">RFC6455</a>]  Fette, I. and A. Melnikov, "The WebSocket Protocol",
              <a href="./rfc6455">RFC 6455</a>, DOI 10.17487/RFC6455, December 2011,
              <<a href="https://www.rfc-editor.org/info/rfc6455">http://www.rfc-editor.org/info/rfc6455</a>>.

   [<a id="ref-RFC5226">RFC5226</a>]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
              DOI 10.17487/RFC5226, May 2008,
              <<a href="https://www.rfc-editor.org/info/rfc5226">http://www.rfc-editor.org/info/rfc5226</a>>.

Acknowledgements

   Takeshi Yoshino, Anne Van Kesteren, Julian Reshke, Barry Leiba, and
   Alexey Melnikov reviewed this update.  Harald Alvestrand acted as
   document shepherd.

Author's Address

   Ted Hardie

   Email: [email protected]





























Hardie                       Standards Track                    [Page 3]