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-374) Disconnect Return Codes - question

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

Ken Borgendale commented on MQTT-374:

The descriptions were updated in wd11.  These return codes do not represent enforcement of the specification, but are return codes for use by implementations to give information to the session partner.  

MQTT does not define message rate limits, connection rate limits, connection time limits, or the banning of clients.  However these are valid things for an implementations to do.  We also do not define the return code 0x83 (Implementation specific error) other than in the list of acceptable return codes.

> Disconnect Return Codes - question
> -------------------------------------------
>                 Key: MQTT-374
>                 URL: https://issues.oasis-open.org/browse/MQTT-374
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Assignee: Ken Borgendale
>            Priority: Minor
>             Fix For: 5, wd11
> At - 2546 Table 3.13 – Disconnect Return Code value
> Is this intentional?
> Outside the table, I don't see any explanations for (not a complete list):
> 150 0x96 Message rate too high
> 151 0x97 Quota exceeded
> 159 0x9F Connection rate exceeded
> 160 0xA0 Maximum connect time

This message was sent by Atlassian JIRA

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