[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (MQTT-194) Status of chapter 6 Using WebSocket as a network transport. is unclear
[ http://tools.oasis-open.org/issues/browse/MQTT-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Banks updated MQTT-194: ------------------------------ Proposal: Register the subrpotocol name "mqtt" with IANA for use with the MQTT3.1.1 specifcation. 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. was: 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 WebSocket Protocol Name MUST be the MQTT Protocol Name concatenated with the ASCII representation of the MQTT Protocol Version number. Non Normative comment: For MQTT v3.1.1, this will be "MQTT4". • The WebSocket URI used to connect the client and server has no impact on the MQTT protocol. > Status of chapter 6 Using WebSocket as a network transport. is unclear > ---------------------------------------------------------------------- > > Key: MQTT-194 > URL: http://tools.oasis-open.org/issues/browse/MQTT-194 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: core > Reporter: Andrew Banks > > It is not clear if chapter 6 Using WebSocket as a network transport. is part of the normative specification. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]