[OASIS Issue Tracker] (MQTT-449) 3.13 CONNECT Payload - "MUST" versus "is" for flags

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

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

Ken Borgendale commented on MQTT-449:
-------------------------------------

These should be changed to remove the MUST.  The fields in the CONNECT payload are in a defined order.  Elsewhere when things are in a defined order we do not also say they MUST be in this order.  The receiver interprets the fields in this order and the data is either correct or not.


> 3.13 CONNECT Payload - "MUST" versus "is" for flags
> ---------------------------------------------------
>
>                 Key: MQTT-449
>                 URL: https://issues.oasis-open.org/browse/MQTT-449
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd14
>            Reporter: Brian Raymor
>            Priority: Minor
>             Fix For: 5, wd14
>
>
> For ClientID, "MUST" is used:
> Line 1289: "The ClientID ... MUST be the first field ..."
> but then for all other fields, the language changes to:
> Line 1315: "... the Will Topic is the next field ..."
> Line 1319: "... the Will Message is the next field ..."
> etc.
> Why not, "... the Will Topic MUST be the next field ..."?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)