[OASIS Issue Tracker] (MQTT-563) Client Id format

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

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

Ian Craggs commented on MQTT-563:
---------------------------------

Simon's comment sounds good to me. The gateway knows the max packet size that the MQTT-SN client can support, either because of the max packet size received in the connect packet or due to the constraints of the underlying transport. So it can generate a server assigned client id of a suitable length. Perhaps this topic is also suitable for discussion in the implementation guide as well as any normative comments.

> Client Id format 
> -----------------
>
>                 Key: MQTT-563
>                 URL: https://issues.oasis-open.org/browse/MQTT-563
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Task
>          Components: MQTT-SN
>            Reporter: Simon Johnson [X]
>            Assignee: Allan Stockdill-Mander 
>            Priority: Major
>
> It was discussed that aligning the clientId format (23 UTF-8 bytes) to MQTT 5.0 was potentially dangerous in SN given the complexity of validation etc. However given ASCII is a subset of UTF-8 it is upon the broker & client implementation to enforce a more restrictive set if required. A note in implementation is required for this item.



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