Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None
    • Proposal:
      Hide

      Extend the specification to allow for a client to connect with a zero length client id and clean session false indicating that the client wishes to be assigned a client id and to use that client id for persistent sessions. Extend the specification to provide a mechanism for a server to return an internally assigned identifier to the client.

      Show
      Extend the specification to allow for a client to connect with a zero length client id and clean session false indicating that the client wishes to be assigned a client id and to use that client id for persistent sessions. Extend the specification to provide a mechanism for a server to return an internally assigned identifier to the client.
    • Resolution:
      Hide

      Included in WD07

      Show
      Included in WD07

      Description

      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.

        Attachments

          Activity

          Hide
          andrew_schofield Andrew Schofield (Inactive) added a comment -

          The point about client ID "stealing" is valid, but my view is that's really about establishing the right to use a particular client ID. I think that's also an aspect of access control. You could for example use a client cert and require that the client ID must match the common name, or something like that.

          Show
          andrew_schofield Andrew Schofield (Inactive) added a comment - The point about client ID "stealing" is valid, but my view is that's really about establishing the right to use a particular client ID. I think that's also an aspect of access control. You could for example use a client cert and require that the client ID must match the common name, or something like that.
          Hide
          coppen Richard Coppen (Inactive) added a comment -

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

          Show
          coppen Richard Coppen (Inactive) added a comment - Reviewed at April face-to-face, need to consider the resulting scenarios and impact with v.next session / state management.
          Hide
          andrew_banks Andrew Banks (Inactive) added a comment -

          TC-Agreed

          Show
          andrew_banks Andrew Banks (Inactive) added a comment - TC-Agreed
          Hide
          andrew_banks Andrew Banks (Inactive) added a comment -

          Add to specification

          Show
          andrew_banks Andrew Banks (Inactive) added a comment - Add to specification
          Hide
          ken.borgendale Ken Borgendale (Inactive) added a comment -

          Issue included in MQTTv5.0 CS01 December 25, 2017

          Show
          ken.borgendale Ken Borgendale (Inactive) added a comment - Issue included in MQTTv5.0 CS01 December 25, 2017

            People

            • Assignee:
              andrew_banks Andrew Banks (Inactive)
              Reporter:
              al.s-m Allan Stockdill-Mander (Inactive)
            • Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: