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-571) New structure of the CONNACK packet

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

Ian Craggs commented on MQTT-571:

542 means allowing the return of the server assigned clientid in the connack.

In addition we might add the server capabilities if we didn't want to add a separate capabilities packet.

The server assigned clientid would be the final, variable length string field in the connack packet.

The server capabilities could be:
 * receive maximum 1 byte, default 3? 0 = unlimited
 * maximum packet size, 2 bytes, default 128?
 * topic alias maximum, 1 byte, default 3?, 0 = unlimited
 * retain available, 1 bit
 * wildcards available, 1 bit



> New structure of the CONNACK packet
> -----------------------------------
>                 Key: MQTT-571
>                 URL: https://issues.oasis-open.org/browse/MQTT-571
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>         Environment: Based on accepting #MQTT-542 we need to specify the new structure of the CONNACK to allow for the returned client id
>            Reporter: Allan Stockdill-Mander
>            Assignee: Allan Stockdill-Mander
>            Priority: Major

This message was sent by Atlassian Jira

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