mqtt message

Subject: [OASIS Issue Tracker] (MQTT-569) Firmware updates

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: mqtt@lists.oasis-open.org
Date: Mon, 16 Nov 2020 18:52:00 +0000 (UTC)

    [ https://issues.oasis-open.org/browse/MQTT-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=78297#comment-78297 ] 

Ian Craggs commented on MQTT-569:
---------------------------------

There is a question of whether MQTT-SN should be able to handle firmware updates, or left to other protocols such as CoAP.Â Simon is investigating CoAP for just this purpose so we hope he will be able to shed some light on the question.

It may be that adding a request/response facility such as that in MQTT 5.0 would be sufficient.Â

> Firmware updates
> ----------------
>
>                 Key: MQTT-569
>                 URL: https://issues.oasis-open.org/browse/MQTT-569
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Ian Craggs
>            Priority: Major
>
> The question of how to achieve firmware updates is very important to solve.Â Using CoAP is one approach.
> If we add a request/response feature as in MQTT 5.0, would that suffice?



--
This message was sent by Atlassian Jira
(v8.3.3#803004)