Clarifying Registry Procedures for the WebSocket Subprotocol Name Registry
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: "IETF-Announce" <email@example.com> Cc: firstname.lastname@example.org, "Harald T. Alvestrand" <email@example.com>, firstname.lastname@example.org, "The IESG" <email@example.com>, firstname.lastname@example.org, email@example.com Subject: Protocol Action: 'Clarifying registry procedures for the Websockets sub-protocol registry' to Proposed Standard (draft-hardie-rfc6455-iana-clarification-03.txt) The IESG has approved the following document: - 'Clarifying registry procedures for the Websockets sub-protocol registry' (draft-hardie-rfc6455-iana-clarification-03.txt) as Proposed Standard This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Alexey Melnikov. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-hardie-rfc6455-iana-clarification/
Technical Summary This document clarifies the instructions to IANA for the sub-protocol registry set up for Websockets in RFC 6455. Working Group Summary The reason for concerns being raised was that the registry is being reused by the RTCWEB WG's datachannel protocol. This is not a WG document, however it was discussed on the HYBI mailing list where RFC 6455 was discussed, as well as on the RTCWEB WG list. There is the HYBI mailing list consensus behind this draft. Document Quality Implementors of WebSocket specification (RFC 6455) commented on this proposal and support it. This document is purely about IANA procedure and it doesn't require any changes to existing implementations. Personnel Harald Alvestrand is the Document Shepherd. Alexey Melnikov is the Responsible Area Director.