-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5
-
Fix Version/s: 5
-
Component/s: core
-
Labels:None
-
Environment:
This was discussed in
MQTT-276with notes from the F2F meetings and has been tracked inMQTT-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 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."
-
Proposal:
The working drafts do not yet include the ability to return a user defined property (key value pair) on acknowledgements (CONNACK, PUBACK, PUBREC, SUBACK, UNSUBACK, and DISCONNECT). This was part of the original requests. The purpose of these properties is to allow the return of implementation specific information and hints (e.g. 'You exceeded your message quota, try again in 15 minutes'.)
This field is not parsed by the MQTT implementation.