[OASIS Issue Tracker] (MQTT-604) Specify requirements on the underlying network transport

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

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

Andrew Banks commented on MQTT-604:
-----------------------------------

Davide, there is no connection identifier in the protocol so the assumption is that any packet received is in the context of the current virtual connection. 

If a DISCONNECT packet is repeated after a new CONNECT packet has been processed in the receiver thenÂ
the receiver will end the new connection, this might happen repeatedly.

If a QOS=2 PUBLISH packet is repeated after the PUBREL has been processed by the receiver, then the receiver will assume that this is a new publication and it might result in a duplicate.Â

Â

> Specify requirements on the underlying network transport
> --------------------------------------------------------
>
>                 Key: MQTT-604
>                 URL: https://issues.oasis-open.org/browse/MQTT-604
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Task
>          Components: MQTT-SN
>    Affects Versions: v2.0
>            Reporter: Ian Craggs
>            Assignee: Andrew Banks
>            Priority: Major
>
> The section on "Networks and Transport Layers" needs to specify the requirements on the underlying transport, as MQTT 5.0 does in the normative statement:
> A Client or Server MUST support the use of one or more underlying transport protocols that provide an ordered, lossless, stream of bytes from the Client to Server and Server to Client [MQTT-4.2-1].



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