[OASIS Issue Tracker] Created: (MQTT-130) Qos=3 requested Qos, and Zero byte retained message

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

Qos=3 requested Qos, and Zero byte retained message
---------------------------------------------------

                 Key: MQTT-130
                 URL: http://tools.oasis-open.org/issues/browse/MQTT-130
             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
          Issue Type: Improvement
          Components: edits
            Reporter: Andrew Banks


Subject: Some Comments

From: Ian Craggs <icraggs@modelbasedtesting.co.uk>
To: mqtt-comment@lists.oasis-open.org
Date: Tue, 14 Jan 2014 15:00:41 +0000

1. If a requested QoS is 3 in subscribe, it is not clear whether this is a malformed packet which should cause the session to be terminated, or whether a suback should be returned with invalid request or lower granted QoS. (I think the first case is intended.)


2. When receiving a publish with the retained flag set and a payload of 0 length, it is clear that any existing retained message should be removed. But what if there is no existing retained message? In that case it is not clear if we set a retained message of 0 length, or not. (I expect not).


3. # wildcards used to be allowed at the beginning of topic filters as well as at the end. Is this a deliberate restriction?

Ian



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