[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-250) Merge the MQTT 3.1.1 and MQTT-SN 1.2 specifications
[ https://issues.oasis-open.org/browse/MQTT-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58950#comment-58950 ] Richard Coppen commented on MQTT-250: ------------------------------------- Reviewed on TC call 12.02.2015 https://www.oasis-open.org/apps/org/workgroup/mqtt/download.php/55197/OASIS_MQTT_TC_minutes_12022015.pdf > Merge the MQTT 3.1.1 and MQTT-SN 1.2 specifications > --------------------------------------------------- > > Key: MQTT-250 > URL: https://issues.oasis-open.org/browse/MQTT-250 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: futures > Reporter: Allan Stockdill-Mander > > Many features that have been discussed as desirable in MQTT, or assist with its mission to be a lightweight pub/sub messaging transport are available in MQTT-SN, along with it being a binding of a very similar protocol to MQTT on a connectionless transport. > MQTT-SN provides the following on top of standard MQTT features; > Negative ACKs on publishes and subscribes > Server initiated pings > Server initiated disconnects > Ability to update will message data at any point > Topic Registration saves space when sending/receiving on the same topic and allows subscription identification of non wildcard subs. > Will as part of session data > Client controlled timed expiry of session data > (along with other features specifically aimed at sensor networks) > A lot of the above are compelling for the current implementation of MQTT over a connected transport, and essential if MQTT is looking to extend its usefulness in mesh/sensor networks. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]