[OASIS Issue Tracker] (MQTT-253) Subscription identification

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

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

Andrew Banks commented on MQTT-253:
-----------------------------------

To address Ken's comment "I do not understand the paragraph stating that the subscription IDs are not part of the client session state."

This comes about because Section 3.1.2.12 does not list the subscription as being part of the client state. The client does not need to remember what it has subscribed for, although it is often useful to do so. 

We could define the subscriptions and their identifiers to be part client state, but there is no way to  check this in a compliance test

> Subscription identification
> ---------------------------
>
>                 Key: MQTT-253
>                 URL: https://issues.oasis-open.org/browse/MQTT-253
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: futures
>    Affects Versions: 5
>            Reporter: Andrew Schofield
>            Assignee: Andrew Banks
>            Priority: Minor
>
> Subscribe and unsubscribe operations are performed on topic filters in MQTT 3.1.1. Adding subscription identifiers would enable unambiguous identification of subscriptions.



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