[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=59726#comment-59726 ] Ian Craggs commented on MQTT-250: --------------------------------- To have MQTT work on sensor networks, or on datagram protocols like UDP, not all the features of MQTT-SN are needed. The issues related to datagram protocols are: - MQTT packet retries. These became optional in 3.1.1. They are essential in unreliable network protocols - QoS - 1: multicast or connectionless publish - server/gateway discovery - advertise, searchgw, gwinfo packets partly related (probably create separate issues for these): - sleeping clients (power saving) - topic registration (reducing network usage) Separate issues, not related to datagram protocols: - nacks on all operations - server initiated disconnects - server initiated pings - updating the will message at any point > 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 > Priority: Critical > > 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]