[OASIS Issue Tracker] (MQTT-183) Packet format vs Implementation behavior

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Andrew Banks updated MQTT-183:
------------------------------

    Proposal: Move the description of DUP, Qos, RETAIN from chapter 2 to PUBLISH in section 3. This makes the content of chapter 2 a generic description of control packets. I left the title of Chapters 2,3 unchanged as some statements in 3 have already been moved into 4 where we consolidated the description of the QoS flows.. 

> Packet format vs Implementation behavior
> ----------------------------------------
>
>                 Key: MQTT-183
>                 URL: https://tools.oasis-open.org/issues/browse/MQTT-183
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 3.1.1
>         Environment: structure
>            Reporter: Patrick Durusau
>
> In Section 2 (supposed to be about MQTT Control Packet Format ) there are many requirements like MQTT-2.1.2-6  (in 2.1.2.3) that are more about Client/Server behavior and seem to belong more to "Operational" section 4. Unless they are moved under 4, I'd suggest to broaden the title of Section 2 to: "MQTT Control Packet Format and Semantics" or the like. Same for Section 3: add "... and Semantics" to title, or explain more clearly the difference between behavioral requirements found in Section 4 compared with section 2 & 3.



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)