OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [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=59325#comment-59325 ] 

Raphael Cohen commented on MQTT-251:

I think Andrew's observation swings this for me, as it allows a server to assign clients ids, thus making it easier to field-deploy new devices w/o configuration (indeed, the first message they receive could also include a client X.509 certificate). In my experience with AMQP in the past, it was often hard for clients to decide on a suitable client id. The downside to this approach is there's no way for the server to g'tee the uniqueness of the client id across all clients, but so be it. We may also want to think carefully about client impacts, as a server assigned client id could be very long and there's no way for a client to say, "hang on a sec, I've only got 48 bytes to store this in". Of course, one could take the view that this is too bad...

Alternatively, we could do server assigned client ids by committee note, simply by having the client subscribe to a known $ shared subscription topic... (perhaps automatically) - there's nothing to stop these being server-generated...

> 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 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]