[OASIS Issue Tracker] (MQTT-539) TopicId in PUBACK is superfluous

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

     [ https://issues.oasis-open.org/browse/MQTT-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Craggs updated MQTT-539:
----------------------------
    Proposal: 
In section 5.4.13 remove the TopicId field from table 17 and from the list of fields below.

MsgId becomes bytes 2 and 3

ReturnCode becomes byte 4

Â

  was:In section 5.4.13 remove the TopicId field from table 17 and from the list of fields below.


> TopicId in PUBACK is superfluous
> --------------------------------
>
>                 Key: MQTT-539
>                 URL: https://issues.oasis-open.org/browse/MQTT-539
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Ian Craggs
>            Assignee: Ian Craggs
>            Priority: Trivial
>
> Via Tomoaki Yamaguchi. "The topicId in the PUBACK packet makes the gateway implementation complicated. The msgId in PUBACK is enough for the client to handle the response."
> This also makes the PUBACK different to the PUBREC, PUBREL and PUBCOMP. Perhaps this was for the purpose of reporting errors as these three acks also lack a return code field (which will be dealt with in another issue).



--
This message was sent by Atlassian Jira
(v8.3.3#803004)