[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-297) Packet Indentifier Leak on lost Subscription commands
[ https://issues.oasis-open.org/browse/MQTT-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65003#comment-65003 ] Ed Briggs commented on MQTT-297: -------------------------------- It is very easy to demonstrate the packet identifier leak, and I've seen it in some implementations (which is why I reported it.). Accordingly, I find the statement that there is no case where packet identifiers are lost unpersuasive. Since this is marked post MQTT 5.0, I don't see much value in further discussion at this point. > Packet Indentifier Leak on lost Subscription commands > ----------------------------------------------------- > > Key: MQTT-297 > URL: https://issues.oasis-open.org/browse/MQTT-297 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Bug > Affects Versions: 3.1.1 > Reporter: Ed Briggs > Priority: Minor > > If a SUBSCRIBE, SUBACK, UNSUBSCRIBE or UNSUBACK message is lost during transfer, the packet identifier is leaked. The leak remains for the duration of the session, which in the case of CleanSession=0 could be indefinite, during which time additional loss of packet ids could occur. > This cannot be fixed using the existing mechanisms, and is recorded here for future consideration (not MQTT 3.1.1. or MQTT 5.0). -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]