[OASIS Issue Tracker] (MQTT-345) re connection and re transmission

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

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

Ken Borgendale commented on MQTT-345:
-------------------------------------

All of this is in non-normative text.  I would prefer to drop all references to other versions of the spec but again as it is non-normative text it might be considered to be a hint as to what should be done and not a requirement to implement it that way.  For instance another possible implementation would be to not allow a session to be reconnected with any version of MQTT other than the one with which it was created.  That would solve a lot of other problems such as having a shared subscription which cannot be unsubscribed.

> re connection and re transmission
> ---------------------------------
>
>                 Key: MQTT-345
>                 URL: https://issues.oasis-open.org/browse/MQTT-345
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Assignee: Rahul Gupta
>            Priority: Trivial
>             Fix For: 5, wd10
>
>
> 975 After re connection the Session lasts as long as the Network Connection plus the new Session Expiry
> 976 interval.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)