[OASIS Issue Tracker] (MQTT-555) Clarification of broker behaviour when client REGISTERs a PREDEFINED topic

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

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

Ian Craggs commented on MQTT-555:
---------------------------------

I was wondering whether topic aliases should be separate spaces for client and server, as they are in MQTT 5.0. It's probably not needed to do that, but either way we should explicitly state this in the specification, for clarity.

Â

> Clarification of broker behaviour when client REGISTERs a PREDEFINED topic
> --------------------------------------------------------------------------
>
>                 Key: MQTT-555
>                 URL: https://issues.oasis-open.org/browse/MQTT-555
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Simon Johnson [X]
>            Assignee: Ian Craggs
>            Priority: Minor
>              Labels: Implementation-notes
>
> If a client issues a âREGISTER âagainst the topic that happens to also be predefined, should  this be allowed? If so, does this yield a normalId in the REGACK, in which case the broker must use an order of precedence when selecting the topic id scheme to use in deliveries to this client.



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