[OASIS Issue Tracker] (MQTT-321) Add User Defined Property to ACKs

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

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

Ed Briggs commented on MQTT-321:
--------------------------------

1. The proposal does not require clients to take action based on the value of the properties, and specifically says the values can be ignored.  In large cloud environments, it is quite possible (and often necessary) for the 'server' to generate diagnostic information which does not originate with another client. For example, the server may know that a particular error was logged with a particular log entry identifier. Returning this information might make it possible for support personnel to quickly locate the log entry (as an example).

2. There is a need to provide extended diagnostic information beyond the what the MQTT specification can sensibly provide, as Konstantin wrote earlier.

3. All properties, topics, properties, payloads etc., complicate handling the maximum packet size.  A similar approach could be used with this property.

> Add User Defined Property to ACKs
> ---------------------------------
>
>                 Key: MQTT-321
>                 URL: https://issues.oasis-open.org/browse/MQTT-321
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 5
>         Environment: 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." 
>            Reporter: Ed Briggs
>            Assignee: Ed Briggs
>              Labels: Proposed
>
> 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. 



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