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

Simon Johnson commented on MQTT-560:
------------------------------------

I have suggest that the DISCONNECTED return codes are part of the same returnCode table for ease of reference. We need to go through and confirm which are relevant for SN and should we keep them the same value?

> 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
>            Assignee: Simon Johnson
>            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)