Mandate the use of separate id spaces for device normal topic alias's

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Trivial
    • None
    • Affects Version/s: MQTT-SN-1.2
    • Component/s: MQTT-SN
    • Hide

      Section changed and should read;

      7.3 Topic Name Aliasing and Mapping
      On the gateway the mapping table between registered topic ids and topic names is implemented per client (and not by a single shared pool between all clients), to reduce the risk of an incorrect topic id from a client matching another client’s valid topic. For performance and efficiency reasons the broker may choose to align TopicIds for registered topic aliases between multiple clients. The mapping table of predefined topic aliases is separate from registered aliases. It is global and shared between all clients and gateways and may overlap with registered aliases, since it is considered to be in a different pool.

      Show
      Section changed and should read; 7.3 Topic Name Aliasing and Mapping On the gateway the mapping table between registered topic ids and topic names is implemented per client (and not by a single shared pool between all clients), to reduce the risk of an incorrect topic id from a client matching another client’s valid topic. For performance and efficiency reasons the broker may choose to align TopicIds for registered topic aliases between multiple clients. The mapping table of predefined topic aliases is separate from registered aliases. It is global and shared between all clients and gateways and may overlap with registered aliases, since it is considered to be in a different pool.

      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.

            Assignee:
            simon.johnson
            Reporter:
            simon.johnson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: