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

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

I have analyzed all the MQTT 5.0 reason codes, with my conclusions in the following table.

|*Reason Code - Decimal*|*Reason Code - Hex*|*MQTT*
*3.1.1*|*Name*|*Packets*|*Comments*|
|0|0x00|Â|Success|CONNACK, PUBACK, PUBREC, PUBREL, PUBCOMP, UNSUBACK, AUTH|Re-use|
|0|0x00|only|Connection accepted|CONNACK|Re-use (as âSuccessâ)|
|0|0x00|both|Granted QoS 0Â|SUBACK|Re-use|
|1|0x01|both|Granted QoS 1|SUBACK|Re-use|
|1|0x01|only|Connection Refused, unacceptable protocol version|CONNACK|Use 0x84 - unsupported protocol version|
|2|0x02|both|Granted QoS 2|SUBACK|Re-use|
|2|0x02|only|Connection Refused, identifier rejected|CONNACK|Use 0x85 - client identifier not valid|
|3|0x03|only|Connection Refused, server unavailable|CONNACK|Use 0x88 - server unavailable|
|4Â|0x04|Â|Disconnect with Will MessageÂ|DISCONNECT|Re-use. This is sent by the client to request a will message be sent.|
|4|0x04|only|Connection Refused, bad user name or password|CONNACK|Use 0x86 - bad user name or password|
|5|0x05|only|Connection Refused, not authorized|CONNACK|Use 0x87 - not authorized|
|16Â|0x10|Â|No matching subscribers|PUBACK, PUBREC|Re-use - should we add a reason code field to the PUBREC, PUBREL, PUBCOMP packets?|
|17|0x11|Â|No subscription existed|UNSUBACK|Re-use|
|24|0x18|Â|Continue authentication|AUTH|Reuse in MQTT-SN auth exchange|
|25|0x19|Â|Re-authenticate|AUTH|Reuse in MQTT-SN auth exchange|
|128|0x80|Â|Unspecified error|CONNACK, PUBACK, PUBREC, SUBACK, UNSUBACK, DISCONNECT|Re-use|
|128|0x80|only|Failure|SUBACK|Re-use (as unspecified error)|
|129|0x81|Â|Malformed packet|CONNACK
DISCONNECT|Re-use|
|130|0x82|Â|Protocol error|CONNACK
DISCONNECT|Re-use|
|131|0x83|Â|Implementation specific error|CONNACK, PUBACK, PUBREC, SUBACK, UNSUBACK, DISCONNECT|Re-use|
|132|0x84|Â|Unsupported Protocol Version|CONNACK|Re-use|
|133|0x85|Â|Client identifier not valid|CONNACK|Re-use|
|134|0x86|Â|Bad user name or password|CONNACK|Re-use|
|135|0x87|Â|Not authorized|CONNACK, PUBACK, PUBREC, SUBACK, UNSUBACK, DISCONNECT|Re-use|
|136|0x88|Â|Server unavailable|CONNACK|Re-use|
|137|0x89|Â|Server busy|CONNACK
DISCONNECT|Re-use|
|138|0x8A|Â|Banned|CONNACK|Re-use|
|139|0x8B|Â|Server shutting down|DISCONNECT|Re-use|
|140|0x8C|Â|Bad authentication method|CONNACK
DISCONNECT|Re-use|
|141|0x8D|Â|Keep alive timeout|DISCONNECT|Re-use|
|142|0x8E|Â|Session taken over|DISCONNECT|Re-use|
|143|0x8F|Â|Topic filter invalid|SUBACK, UNSUBACK, DISCONNECT|Re-use|
|144|0x90|Â|Topic name invalid|CONNACK, PUBACK, PUBREC, DISCONNECT|Re-use|
|145|0x91|Â|Packet identifier in use|PUBACK, PUBREC, SUBACK, UNSUBACK|Re-use|
|146|0x92|Â|Packet identifier not found|PUBREL, PUBCOMP|Re-use if reason code added to PUBREL, PUBCOMP|
|147|0x93|Â|Receive maximum exceeded|DISCONNECT|Re-use? Receive maximum is always 1 in MQTT-SN|
|148|0x94|Â|Topic alias invalid|DISCONNECT|Re-use|
|149|0x95|Â|Packet too large|CONNACK
DISCONNECT|Re-use|
|150|0x96|Â|Message rate too high|DISCONNECT|Re-use|
|151|0x97|Â|Quota exceeded|CONNACK, PUBACK, PUBREC, SUBACK, DISCONNECT|Re-use|
|152|0x98|Â|Administrative action|DISCONNECT|Re-use|
|153|0x99|Â|Payload format invalid|PUBACK, PUBREC, DISCONNECT|MQTT 5 only. Transparent gateway only.|
|154|0x9A|Â|Retain not supported|CONNACK
DISCONNECT|MQTT 5 only. Transparent gateway only.|
|155|0x9B|Â|QoS not supported|CONNACK
DISCONNECT|MQTT 5 only. Transparent gateway only.|
|156|0x9C|Â|Use another server|CONNACK
DISCONNECT|Re-use|
|157|0x9D|Â|Server moved|CONNACK
DISCONNECT|Re-use|
|158|0x9E|Â|Shared subscription not supported|SUBACK
DISCONNECT|MQTT 5 only. Transparent gateway only.|
|159|0x9F|Â|Connection rate exceeded|CONNACK
DISCONNECT|Re-use|
|160|0xADÂ|Â|Maximum connect time|DISCONNECT|Re-use|
|161|0xA1|Â|Subscription Identifiers not supportedÂ|SUBACK, DISCONNECT|MQTT 5 only. Transparent gateway only.|
|162|0xA2|Â|Wildcard Subscription not supported|SUBACK, DISCONNECT|MQTT 5 only. Transparent gateway only.|

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