Network Working Group
Internet Engineering Task Force (IETF)                         T. Hardie
Request for Comments: 7936                                     July 2016
Updates: RFC6455 (if approved)
Intended status: 6455
Category: Standards Track
Expires: December 3, 2016
ISSN: 2070-1721

                     Clarifying registry procedures Registry Procedures
              for the Websockets sub-protocol registry
               draft-hardie-rfc6455-iana-clarification-03 WebSocket Subprotocol Name Registry

Abstract

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

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list  It represents the consensus of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid the IETF community.  It has
   received public review and has been approved for a maximum publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of six months this document, any errata,
   and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 3, 2016.
   http://www.rfc-editor.org/info/rfc7936.

Copyright Notice

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

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) 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.

1.  Introduction

   [RFC6455] section

   Section 11.5 of [RFC6455] sets up a WebSocket Subprotocol Name
   Registry at IANA and directs IANA to use First Come First Serve
   registration procedures as set out in [RFC5226].  The reuse of this
   registry by other protocols has indicated that some clarification of
   the instructions to IANA would be useful.

2.  Clarified instructions Instructions

   The tokens registered in the Websockets sub-protocol registry WebSocket Subprotocol Name Registry
   created by RFC 6455 Section 11.5 of RFC 6455 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 section Section 1.9 of RFC 6455.

3.  Security Considerations

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

4.  IANA Considerations

   This document is, in its entirety, a clarification of the registry
   policy for the Websockets sub-protocol name registry. WebSocket Subprotocol Name Registry.  As part of this
   clarification, IANA is requested to list has listed both this document and RFC 6455 as
   references for the Websockets sub-protocol registry. WebSocket Subprotocol Name Registry.  In addition,
   IANA is requested to include has included the following note under the registry's
   Registration Procedures: "Please see Section 2 of RFC
   XXXX, 7936, which
   clarifies that registrations which differ from existing registrations
   only by case will be refused."

5.  Acknowledgements

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

6.  Normative References

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

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

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: ted.ietf@gmail.com