OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (MQTT-270) SN Feature: server initiated disconnects

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

Ken Borgendale commented on MQTT-270:

My list of disconnect reason codes:
- Protocol error (a violation of a MUST in the spec)
- Text field character encoding error (might just violate the SHOULD)
- Topic name of topic filter not valid (the provider can have more stringent requirements than MQTT)
- System topic name or topic filter not valid (specific $ topic check)
- Websocket packet type not valid (must be binary)
- Timeout (no messages within keep alive time)
- Not authorized 
- Client quota exceeded (might be temporary)
- Message too big (probably requires admin action, should have been prevented by discovery)
- Message rate too high (might be temporary)
- Server capacity limit (might be temporary)
- Server (or client) terminating (try another server or try later)
- Disconnect due to administrative action 
- Server (or client) error
- Function not supported

While some of these are more likely in the server to client direction, almost all of them make sense in the client to server direction.  It makes sense to group the reason codes by the actions we thing the receiver can do before retrying.

A number of these errors also occurs on CONNACK, PUBACK, PUBREC, PUBCOM, SUBACK, and UNSUBACK.  It would make sense to have a single set of reason codes values.  We can then have a table of all return codes and suggestions of what applications and humans can do when they see such an error.

> SN Feature: server initiated disconnects
> ----------------------------------------
>                 Key: MQTT-270
>                 URL: https://issues.oasis-open.org/browse/MQTT-270
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 3.1.1
>            Reporter: Ian Craggs
>            Assignee: Ian Craggs
> MQTT-SN allows the server to send a disconnect packet to a client. This is much nicer behaviour, for example in the case that a server is shutting down. A reason could also be transmitted with the disconnect packet, so that the client had some idea of when to attempt to reconnect. 

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]