[OASIS Issue Tracker] Commented: (MQTT-65) Should the QoS flag for PUBREL, SUBSCRIBE and UNSUBSCRIBE be reserved ?

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

    [ http://tools.oasis-open.org/issues/browse/MQTT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34284#action_34284 ] 

Raphael Cohen commented on MQTT-65:
-----------------------------------

Ta Roger for the comments.


> Should the QoS flag for PUBREL, SUBSCRIBE and UNSUBSCRIBE be reserved ?
> -----------------------------------------------------------------------
>
>                 Key: MQTT-65
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-65
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1.1
>            Reporter: Richard Coppen
>             Fix For: 3.1.1
>
>
> The current spec is ambiguous with respect to the acceptable values of the QoS flag for PUBREL, SUBSCRIBE and UNSUBSCRIBE operations.
> It could be interpreted that QoS must be set to 1 to force an appropriate ACK. However the ACK behavior is described independently.
> do we accept only one value ?
> if so, should it be 0, 1 or 2?
> Are other values be treated as malformed?
> Forcing 0 would change the protocol flow on the wire. 
> Forcing 1 is consistent with the spirit of the input spec, but we need some clarity. The intended ACK behavior is not really related to QoS. 

-- 
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