[OASIS Issue Tracker] (MQTT-560) Error codes need consideration, both quantity and location.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Ian Craggs commented on MQTT-560:
---------------------------------

As suggested in section 2.2 of Miroslav's document, we should adopt all of the MQTT 5.0 reason codes in MQTT-SN so that a transparent gateway can forward any errors it receives on to any MQTT-SN clients.

In addition we will anticipate we will need some MQTT-SN specific reason codes. The range for those should be agreed and reserved with the MQTT TC so that there is no confusion between those for MQTT and those for MQTT-SN.

> Error codes need consideration, both quantity and location.
> -----------------------------------------------------------
>
>                 Key: MQTT-560
>                 URL: https://issues.oasis-open.org/browse/MQTT-560
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Simon Johnson [X]
>            Assignee: Simon Johnson [X]
>            Priority: Minor
>
> We should think about defining common error codes, especially around topicId negotiations. We should also ensure every ACK message type has the ability to report errors (where possible).



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