[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=83875#comment-83875 ] 

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

My conclusions are:
 * MQTT-SN should adopt all of the MQTT 5.0 reason codes. Some of these will only be used by a transparent gateway if it chooses to forward the MQTT 5.0 reason code to the MQTT-SN client. Where possible, MQTT-SN should re-use the MQTT 5.0 reason code instead of inventing a new one.
 * Create new reason codes if needed, but minimize them. Then we'll ask for these ranges (failure are 0x80 and above, success are below) to be reserved by MQTT.
 * There is some overlap for CONNACK return codes in MQTT 3.1.1 and CONNACK reason codes in MQTT 5.0. An MQTT-SN transparent gateway should translate MQTT 3.1.1 CONNACK return codes into MQTT 5.0 CONNACK reason codes.
 * MQTT 5.0 has reason codes in PUBREC/PUBREL/PUBCOMP packets as well as PUBACK. I propose extending these packets in MQTT-SN to include an optional reason code. This would allow a transparent gateway to forward this information on easily, as well as providing optimized QoS 2 packet flows in the case of error.

> 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)