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

From
OASIS Issues Tracker <>
Date
2016-04-13T20:34:05+00:00
ID
Thread
[OASIS Issue Tracker] (MQTT-251) Return server assigned client id to client
[ https://issues.oasis-open.org/browse/MQTT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62252#comment-62252 ] 

Richard Coppen commented on MQTT-251:
-------------------------------------

Reviewed at April face-to-face, need to consider the resulting scenarios and impact with v.next session / state management. 

> 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
>            Priority: Critical
>
> 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)