• Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: core
    • None
    • Hide

      There should be no restriction on the clientId other than it MUST comprise only Unicode characters, and the
      length of the UTF-8 encoding MUST be at least one byte and no more than 65535 bytes long.

      The server MAY restrict the clientIds it allows in terms of their lengths and the characters they contain, however the server MUST
      allow clientIds which are 23 or fewer UTF-8 encoded bytes in length, and contain only the characters "0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ".

      Show
      There should be no restriction on the clientId other than it MUST comprise only Unicode characters, and the length of the UTF-8 encoding MUST be at least one byte and no more than 65535 bytes long. The server MAY restrict the clientIds it allows in terms of their lengths and the characters they contain, however the server MUST allow clientIds which are 23 or fewer UTF-8 encoded bytes in length, and contain only the characters "0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ".
    • Hide

      Updated in draft07 lines 624 on.

      Show
      Updated in draft07 lines 624 on.

      The current specification says that the client Identifier must be 1 - 23 characters in length.
      Should this mean

      1-23 bytes when transformed to UTF-8
      1-23 Unicode characters, counting surrogate pairs as single characters
      1-23 Unicode characters, counting surrogate pairs as two characters

            Assignee:
            Andrew Banks (Inactive)
            Reporter:
            Andrew Banks (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: