1. Register the sub-protocol name "mqtt" with IANA for use with the MQTT3.1.1 specification. 2. Change the body of chapter 6 line 1757 onwards to be normative. If MQTT is transported over a WebSocket [RFC6455] connection, the following conditions apply: • MQTT Control Packets MUST be sent in WebSocket binary data frames. If any other type of data frame is received the recipient MUST close the Network Connection. • A single WebSocket data frame can contain multiple or partial MQTT Control Packets. The receiver MUST NOT assume that MQTT Control Packets are aligned on WebSocket frame boundaries. • The client MUST include "mqtt" in the list of WebSocket Sub Protocols it offers. • The WebSocket Sub Protocol name selected and returned by the server MUST be "mqtt". • The WebSocket URI used to connect the client and server has no impact on the MQTT protocol. 3. Add the following bullet point to 7.1.1 (MQTT Server compliance target) • Chapter 6 (if MQTT is transported over a WebSocket connection) 4. Add the following bullet point to 7.1.2 (MQTT Client compliance target) • Chapter 6 (if MQTT is transported over a WebSocket connection)