OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (MQTT-288) Define metadata for all control packets

Ken Borgendale created MQTT-288:

             Summary: Define metadata for all control packets
                 Key: MQTT-288
                 URL: https://issues.oasis-open.org/browse/MQTT-288
             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
          Issue Type: New Feature
          Components: futures
    Affects Versions: 5
            Reporter: Ken Borgendale
             Fix For: 5

MQTT-256 defines the basic mechanism for metadata but was originally designed to only show the metadata used on PUBLISH for message format.  This leaves a lot of more general metadata items yet to be defined.

- What is the format of metadata on control packets other than PUBLISH?

- What are the rules for assigning IDs and the code to skip over metadata fields.

- One of the original concepts of metadata was that it should be possible for receivers of metadata to easily skip over metadata they did not want to process.  This is especially important for small clients.  Thus we should specify the minimum that a receiver must do to validate the received metadata.

- We should define the responsibility of the sender of metadata to only send valid metadata.  This does imply that when a client or server passes on metadata it received, it needs to validate it first.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]