[OASIS Issue Tracker] (MQTT-603) Reliabilty of the Will Setup Exchange on Connect

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

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

Davide Lenzarini commented on MQTT-603:
---------------------------------------

[~ian.craggs] [~simon622867]Âcan we close it now?

> Reliabilty of the Will Setup Exchange on Connect
> ------------------------------------------------
>
>                 Key: MQTT-603
>                 URL: https://issues.oasis-open.org/browse/MQTT-603
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>            Reporter: Ian Craggs
>            Assignee: Simon Johnson
>            Priority: Major
>         Attachments: Screenshot 2024-01-05 at 12.38.39.png, Screenshot 2024-01-11 at 09.10.21.png
>
>
> This was highlighted by Davide Lenzarini in asking the question about the timeouts involved in the connect procedure with will setup. This involves a 6 packet exchange - when should the client timeout when waiting for one of those packets from the Gateway?
> This then morphed into the question of why have separate packets to set the will at all, why not have the will message in the connect packet? The original reasons for this were twofold:
> # The length of each packet is minimized because of the reduced MTU or max packet size generally supplied by transports used by MQTT-SN
> # MQTT-SN was originally designed to have only one length field per packet - the overall length. This meant that there could be only one variable length field per packet. We now have deviated from that in the publish packet, so it could be done in the connect packet too.



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