Clarifying registry procedures for the Websockets sub-protocol registry
draft-hardie-rfc6455-iana-clarification-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Ted Hardie 
Last updated 2016-03-21
Stream (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          T. Hardie
Internet-Draft                                            March 20, 2016
Updates: RFC6455 (if approved)
Intended status: Best Current Practice
Expires: September 21, 2016

Clarifying registry procedures for the Websockets sub-protocol registry
               draft-hardie-rfc6455-iana-clarification-00

Abstract

   This document clarifies the instructions to IANA for the sub-protocol
   registry set up for 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 of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents 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 September 21, 2016.

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.

Hardie                 Expires September 21, 2016               [Page 1]
Internet-Draft         RFC6455 IANA clarification             March 2016

1.  Introduction

   [RFC6455]  section 11.5 sets up a Subprotocol Name Registry at IANA
   and directs IANA to use First Come First Serve registration
   procedures as set out in [RFC5226].

2.  Clarified instructions

   The tokens registered in the Websockets sub-protocol registry created
   by RFC 6445 Section 11.5 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 1.9 of RFC 6445.

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.

5.  Acknowledgements

   Takeshi Yoshino, Anne Van Kesteren, Julian Reshke, and Alexey
   Melnikov reviewed this update.

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>.

Author's Address

   Ted Hardie

   Email: ted.ietf@gmail.com

Hardie                 Expires September 21, 2016               [Page 2]