[OASIS Issue Tracker] Commented: (MQTT-42) Clean session and random client ids

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

    [ http://tools.oasis-open.org/issues/browse/MQTT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34125#action_34125 ] 

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

I'm not actually proposing we consider changes like I mentioned/Roger linked to, but now seems as good a time as any to discuss them.
Why does the client always want to know its client id? You're obviously right that in the situation of server autogenerated ids there is no way currently to communicate that back to the client but there are many situations where knowing the client id just isn't necessary.

Considering a situation where you have a client side autogenerated clientid and a server side autogenerated one, practically what difference is there between them for tracking and logging purposes? For auditing purposes I would hope/imagine you would be using other authentication mechanisms the use of which is not precluded by serverside auto generated clientids.

In any application where the client needed to know it's own id the current situation of being able to specify it is still available, and a future revision that allowed a generated client id to be flowed back in the CONNACK would allow the best of both.

> Clean session and random client ids
> -----------------------------------
>
>                 Key: MQTT-42
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-42
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1.1
>         Environment: N/A
>            Reporter: Raphael Cohen
>            Priority: Minor
>             Fix For: 3.1.1
>
>
> Opened on behalf of Roger Light:-
> Hi,
> A lot of MQTT client libraries offer the feature of generating random
> client ids rather than having to supply one. This is good.
> I recently had over 10,000 client connections made to
> test.mosquitto.org using a random client id, but also having set clean
> session to false, which meant that when they disconnected their
> information was stored on the server but there was basically no chance
> they could reconnect.
> It would be nice to have a comment in the spec suggesting that
> implementations may offer to generate random client ids but that they
> must refuse to do so if clean session is set to false.
> Cheers,
> Roger

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira