← Prev in month ← Prev in thread

[OASIS Issue Tracker] (MQTT-262) Clarify will messages if server disconnects

From
OASIS Issues Tracker <>
Date
2016-07-05T12:42:51+00:00
ID
Thread
[OASIS Issue Tracker] (MQTT-262) Clarify will messages if server disconnects
[ https://issues.oasis-open.org/browse/MQTT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62836#comment-62836 ] 

Ed Briggs commented on MQTT-262:
--------------------------------

To summarize, if session take-over occurs, the WILL message is issued. In MQTT vNext, the server will also send a DISCONNECT message to the client (victim) with an error code indicating "connection closing due to session take-over". and then close the transport connection with the 'victim'.  This error message will be defined in the consolidated list of error messages for MQTT-236 (Ack/Naks) and the Server initiated DISCONNECT. 

(I agree with Peter that the security section should include a non-normative warning to authenticate a user first, and then check they are entitled to use the client ID.) 

> Clarify will messages if server disconnects
> -------------------------------------------
>
>                 Key: MQTT-262
>                 URL: https://issues.oasis-open.org/browse/MQTT-262
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 3.1.1
>            Reporter: Raphael Cohn
>            Assignee: Raphael Cohn
>            Priority: Critical
>
> If a server disconnects a connection because a second client has connected with the same client id, should the first connections' will message be sent? I would argue it should, because this scenario is intended to reflect 'stuck' and 'hung' clients.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
← Prev in month ← Prev in thread