[OASIS Issue Tracker] (MQTT-251) Return server assigned client id to client

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

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

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

it could be useful for problem determination, although equally you can use IP address/username. And currently any client that connects with a zero length client id has no idea what the assigned id is and that was still considered valuable. The concern is that cleansession clients are ephermeral and not providing the client id to cleansession clients that requested a server assigned id reinforces this fact so that no one is tempted to try and create a coupling or assume some state, or if they want it to use persistent sessions.

> Return server assigned client id to client
> ------------------------------------------
>
>                 Key: MQTT-251
>                 URL: https://issues.oasis-open.org/browse/MQTT-251
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>            Reporter: Allan Stockdill-Mander 
>
> In the 3.1.1 specification section 3.1.3.1 http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718031 it is permitted for a client to connect with a zero length client id, the server internally uses a unique identifier for that client but the client does not know the idenfitier and is required to connect with clean session true.



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