Client Id format

XMLWordPrintable

    • Type: Task
    • Resolution: Applied
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: MQTT-SN
    • None
    • Hide

      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

      Show
      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

      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.

            Assignee:
            thesii
            Reporter:
            simon.johnson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: