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] Commented: (MQTT-36) Editorial comments on Connect Payload

    [ http://tools.oasis-open.org/issues/browse/MQTT-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33872#action_33872 ] 

Rahul Gupta commented on MQTT-36:

in WD-05

1) line 810 - The payload of the CONNECT control packet contains one or more length-prefixed UTF-8 encoded strings, based on the flags in the variable header. 
3) line 819 - If the Client ID contains no Unicode characters or more than 23 Unicode characters,

To discuss with Andy and propose text for  2. and 4.

> Editorial comments on Connect Payload
> -------------------------------------
>                 Key: MQTT-36
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-36
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: edits
>            Reporter: Peter Niblett
>            Priority: Trivial
> 1. I know we provide our definition of "UTF-8 encoded strings in 2.1.3, however readers of the first para of 3.13 (line 667) might not realise this. We should either say "length-prefixed UTF-8 encoded strings" or "UTF-8 encoded strings as defined in 2.1.3". 
> 2. Line 676 says (when talking about the Client Identifier) "It is the key in handling Message Identifiers for messages with QoS levels 1 and 2". The phrase "key in handling" looks a bit odd,  and in any case the Client Id is used as a key to all state held on the server for the client, not just some kind of scoping construct for message Ids.
> 3. Line 677 2 instances of unicode should be Unicode
> 4. Line 684 says "The Client Identifier might have been presented to the client implementation as a Unicode string" and then goes on to talk about surrogate characters.  Surrogate characters are not valid Unicode, so can't appear in a Unicode string.  What you should have said is "The Client Identifier might have been presented to the client implementation as a UTF-16 encoded string [RFC2781]" 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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