[OASIS Issue Tracker] (MQTT-300) Metadata: CONNACK Maximum QoS

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

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

Ed Briggs commented on MQTT-300:
--------------------------------

Thank you Peter, your text is clearer and more precise. I think I need to add a sentence regarding the Client.  Using your text as a template, how about this:
 
"A Client is NOT REQUIRED to support  reception or transmission of QoS 1 or QoS 2 PUBLISH packets. If this is the case, the Client simply restricts the maximum QoS field in any SUBSCRIBE commands it sends to a value it can support. A Client MUST NOT send a Maximum QoS Advertisement to the Server."

Also, I think it should be mandatory that

"If a Server receives a SUBSCRIBE command containing a maximum QoS value it does not support, it MUST return a QoS value it supports in the SUBACK unless it rejects the subscription for a different reason. In that case, the Server MUST return an appropriate error code in the SUBACK."




> Metadata: CONNACK Maximum QoS 
> ------------------------------
>
>                 Key: MQTT-300
>                 URL: https://issues.oasis-open.org/browse/MQTT-300
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 5
>            Reporter: Brian Raymor
>            Assignee: Ed Briggs
>              Labels: Proposed
>
> This was discussed in MQTT-276 with notes from the F2F meetings and has been tracked in MQTT-256. 
> I'm opening a separate, specific issue per Ken's comments - https://issues.oasis-open.org/browse/MQTT-256?focusedCommentId=62192&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-62192:
> "All of these would be defined in separate JIRAs, but what we should do in this JIRA is to define the mechanism used to pass these values."



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