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] Updated: (MQTT-166) 3.10.1 Fixed Header - malformed? (4)

     [ http://tools.oasis-open.org/issues/browse/MQTT-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Banks updated MQTT-166:

Remove lines 430-431 in Chapter 2 , which deal with protocol violations.

Rewrite Section 4.8 line 1557 on  as follows:

4.8 Handling errors.

Unless stated otherwise, if either the Server or Client receives a Control Packet which does not meet this specification, it MUST close the Network Connection on which it received that packet  [MQTT-4.8.0-1]. 
If the Client or Server encounters a transient error while processing an inbound Control Packet it MUST close the Network Connection on which it received that packet [MQTT-4.8.0-2]. If a Server detects a transient error it SHOULD NOT disconnect or have any other affect on its interactions with any other Client.

Non Normative comment
A transient error is one which may not re occur if the action is repeated. For example an authorization failure might not re occur the next time the same publication
is received if the administrator has authorized the client to make the publication in the mean time.

  was:Add these protocol violations to 4.8. 

> 3.10.1 Fixed Header - malformed? (4)
> ------------------------------------
>                 Key: MQTT-166
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-166
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1.1
>         Environment: Normative
>            Reporter: Patrick Durusau
>  A few comments ago I mused about whether 4.8 Handling protocol violations listed all the protocol violations in the draft. 
> Turns out it doesn't.
> Looking under 3.10.1, a value can be malformed and the server MUST close the network connection. That sounds like a protocol violation to me.
> On looking further, similar "malformed" statement occur at: 3.8.3 Payload, 3.8.1 Fixed Header, 3.6.1 Fixed header.
> If those are protocol violations and as normative statements I can't see them being anything else, then they should be reported under 4.8.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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