[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=63709#comment-63709 ] 

Ed Briggs commented on MQTT-304:
--------------------------------

I propose the following new identified data type for this purpose. 

type name:  user defined name-value pair = 0xNN (TBD)

ident  : byte = 0xNN {TBD}
length : Variable Byte Integer
name  : UTF-8 encoded string
value  : UTF-8 encoded string

The user defined name-value pair is an optional value that used in CONNECT and PUBLISH command packets to carry 'application layer' information which is NOT interpreted by MQTT in any way.  The format, meaning, and uniqueness of the name is not enforced by MQTT.

The user defined name-value pair may appear zero or more times in a CONNECT or PUBLISH command packet.

The identifier is a byte value 0xNN {TBD}.

The length field is a variable length integer which is the number of bytes contained in the two counted UTF-8 strings that follow it (including the string length fields). The value of the length field must be at least 4 (signifying 2 empty UTF-8 strings) and can be no more than 2 * 65535 + 4 = 131074, which means it can be no more than 3 bytes when encoded. The sender MUST not send a user defined name-value pair with a length of less than 4, or a length of greater than 131074.

  

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