[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:all-tabpanel ]

Ian Craggs updated MQTT-563:
----------------------------
    Proposal: 
Client Identifier (ClientID)
 The Client Identifier (ClientID) identifies the Client to the Server. Each Client connecting to the Server has a unique ClientID. The ClientID MUST be used by Clients and by Servers to identify state that they hold relating to this MQTT-SN Session between the Client and the Server.
 The ClientID MUST be a String containing only characters defined as "Graphic Characters" in Section 4.3 of ANSI X3.4-1986 (US-ASCII)
 The Server MUST allow ClientIDâs which are between 1 and 23 bytes in length.
 A Client Identifier of 0 bytes indicates that the Client is requesting the Server generate and assign a Client Identifier

  was:
Client Identifier (ClientID)
The Client Identifier (ClientID) identifies the Client to the Server. Each Client connecting to the Server has a unique ClientID. The ClientID MUST be used by Clients and by Servers to identify state that they hold relating to this MQTT-SN Session between the Client and the Server.
The ClientID MUST be a String containing only characters defined as "Graphic Characters" in Section 4.3 of ANSI X3.4-1986 (US-ASCII)
The Server MUST allow ClientIDâs which are between 1 and 32 bytes in length.
A Client Identifier of 0 bytes indicates that the Client is requesting the Server generate and assign a Client Identifier


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