idnits 2.17.1 draft-hardie-rfc6455-iana-clarification-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 01, 2016) is 2883 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Hardie 3 Internet-Draft June 01, 2016 4 Updates: RFC6455 (if approved) 5 Intended status: Standards Track 6 Expires: December 3, 2016 8 Clarifying registry procedures for the Websockets sub-protocol registry 9 draft-hardie-rfc6455-iana-clarification-03 11 Abstract 13 This document clarifies the instructions to IANA for the sub-protocol 14 registry set up for Websockets in RFC 6455. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on December 3, 2016. 33 Copyright Notice 35 Copyright (c) 2016 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 1. Introduction 50 [RFC6455] section 11.5 sets up a Subprotocol Name Registry at IANA 51 and directs IANA to use First Come First Serve registration 52 procedures as set out in [RFC5226]. The reuse of this registry by 53 other protocols has indicated that some clarification of the 54 instructions to IANA would be useful. 56 2. Clarified instructions 58 The tokens registered in the Websockets sub-protocol registry created 59 by RFC 6455 Section 11.5 are matched using case-sensitive string 60 match. IANA is, however, instructed to decline registrations in the 61 registry which differ only as to case, in order to minimize potential 62 confusion among different registered versions. For other useful 63 advice on avoiding collision, registrants are encouraged to consult 64 the non-normative section 1.9 of RFC 6455. 66 3. Security Considerations 68 This document describes an update to registry policy, not a protocol. 70 4. IANA Considerations 72 This document is, in its entirety, a clarification of the registry 73 policy for the Websockets sub-protocol name registry. As part of 74 this clarification, IANA is requested to list both this document and 75 RFC 6455 as references for the Websockets sub-protocol registry. In 76 addition, IANA is requested to include the following note under the 77 registry's Registration Procedures: "Please see Section 2 of RFC 78 XXXX, which clarifies that registrations which differ from existing 79 registrations only by case will be refused." 81 5. Acknowledgements 83 Takeshi Yoshino, Anne Van Kesteren, Julian Reshke, Barry Leiba, and 84 Alexey Melnikov reviewed this update. Harald Alvestrand acted as 85 document shepherd. 87 6. Normative References 89 [RFC6455] Fette, I. and A. Melnikov, "The WebSocket Protocol", 90 RFC 6455, DOI 10.17487/RFC6455, December 2011, 91 . 93 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 94 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 95 DOI 10.17487/RFC5226, May 2008, 96 . 98 Author's Address 100 Ted Hardie 102 Email: ted.ietf@gmail.com