[OASIS Issue Tracker] (MQTT-304) Metadata: Add User defined CONNECT data

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

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

Konstantin Dotchkoff commented on MQTT-304:
-------------------------------------------

I propose to introduce an optional field id for custom defined data. Unlike other field ids that are followed by a value (of a specific data type), for custom defined data we can use 2 strings representing a 'key name' and a 'value'. The optional field id followed by the 2 strings can be repeated. Thus, multiple custom fields (with different key names) can be specified in a single packet.

> Metadata: Add User defined CONNECT data
> ---------------------------------------
>
>                 Key: MQTT-304
>                 URL: https://issues.oasis-open.org/browse/MQTT-304
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 5
>            Reporter: Ed Briggs
>            Assignee: Ed Briggs
>
> 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=62192page=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)