[OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's

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

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

Allan Stockdill-Mander commented on MQTT-550:
---------------------------------------------

TopicId mappings

The pool of TopicIds for predefined topics is separate from the pool of TopicIds for registered topic aliases.

The pool of TopicIds for registered topic aliases is separate and unique between clients. For performance and efficiency reasons the broker may choose to align TopicIds for registered topic alises between multiple clients.

> Mandate the use of separate id spaces for device normal topic alias's
> ---------------------------------------------------------------------
>
>                 Key: MQTT-550
>                 URL: https://issues.oasis-open.org/browse/MQTT-550
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Simon Johnson
>            Assignee: Allan Stockdill-Mander
>            Priority: Trivial
>              Labels: Implementation-notes
>
> The implementation notes strongly suggestâ using a separate id space per device for topicId mapping. 
> Suggest the implementation notes are explicit and mandate that device alias' exist in their own 0-65535 space and do not overlap with alias's used by other devices.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)