[OASIS Issue Tracker] Updated: (MQTT-106) Behaviour when Will Flag = 0

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

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

Richard Coppen updated MQTT-106:
--------------------------------

        Fix Version/s: 3.1.1
    Affects Version/s: 3.1.1

> Behaviour when Will Flag = 0
> ----------------------------
>
>                 Key: MQTT-106
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-106
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1.1
>            Reporter: Peter Niblett
>            Priority: Minor
>             Fix For: 3.1.1
>
>
> In 3.1.2.3.2. there's a normative statement "
> The Will Flag indicates that a Will Message MUST be published by the server when the server detects that the client is disconnected for any reason other than the client flowing a DISCONNECT Packet [MQTT-3.1.2-7]"
> 1. Editorial comment - This should say "If the Will Flag is set to 1, a Will Message MUST be published by the server when the server detects that the client is disconnected for any reason other than the client flowing a DISCONNECT Packet [MQTT-3.1.2-7]"
> 2. Core comment. For the avoidance of doubt, we should say what happens if the Will Flag is 0
> I assume that the default is that no will message gets published, but if a server wants to use a $SYS topic to log unexpected disconnects, then it is free to do that, We should consider making it clear that a server does not "remember" the last Will Mesage / Topic that the client used. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira