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] Updated: (MQTT-45) summary of editorial issues from read through of WD07


     [ http://tools.oasis-open.org/issues/browse/MQTT-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Coppen updated MQTT-45:
-------------------------------

    Description: 
line 35: change TCPIP network, to operating environment
line 42: remove bracketed section 
line 254: remove "allows applications to exchange messages with specific levels of reliability. It" and restructure introduction sentence for clarity
line 292: make it clear that the DUP flag must be set to 0 if  QOS 0 messages
line 351: remove MultiByte length header and reword in terms of remaining length (global change: help with readability and simplicity)
In addition remove confusion around 'digit' in the algorithm (i.e., resolve MQTT-29) 
line 471: Section 2.3 moved to start of Section 2 as part of the introduction as it is a key concept
line 431: Non-normative content promoted --> client server pairs must be able to manage overlapping packetIDs
line 486: remove surrogate pairs removed as not longer relevant (machine representation v wire format)
line 493: Storing state subsection moved to Section 4
line 1293: Section 4 "Flows" changed to "Implementation consideration"
line 500+ "MQTT Control Packets": move description of terms and discussion under correct subsections
line 501+ restructure CONNECT subsection for clarity
line 750: refactor existing CONNECT processing steps under 3.1.4 "Response"

  

  was:
line 35: change TCPIP network, to operating environment
line 42: remove bracketed section 
line 254: remove "allows applications to exchange messages with specific levels of reliability. It" and restructure introduction sentence for clarity
line 292: make it clear that the DUP flag must be set to 0 if  QOS 0 messages
line 351: remove MultiByte length header and reword in terms of remaining length (global change: help with readability and simplicity)
In addition remove confusion around 'digit' in the algorithm (i.e., resolve MQTT-29) 
line 471: Section 2.3 moved to start of Section 2 as part of the introduction as it is a key concept
line 431: Non-normative content promoted --> client server pairs must be able to manage overlapping packetIDs
line 486: remove surrogate pairs removed as not longer relevant (machine representation v wire format)
line 493: Storing state subsection moved to Section 4
line 1293: Section 4 "Flows" changed to "Implementation consideration"
line 500+ "MQTT Control Packets": move description of terms and discussion under correct subsections
line 501+ restructure CONNECT subsection for clarity
  


> summary of editorial issues from read through of WD07
> -----------------------------------------------------
>
>                 Key: MQTT-45
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-45
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: edits
>    Affects Versions: 3.1.1
>            Reporter: Richard Coppen
>            Assignee: Andrew Banks
>            Priority: Minor
>             Fix For: 3.1.1
>
>
> line 35: change TCPIP network, to operating environment
> line 42: remove bracketed section 
> line 254: remove "allows applications to exchange messages with specific levels of reliability. It" and restructure introduction sentence for clarity
> line 292: make it clear that the DUP flag must be set to 0 if  QOS 0 messages
> line 351: remove MultiByte length header and reword in terms of remaining length (global change: help with readability and simplicity)
> In addition remove confusion around 'digit' in the algorithm (i.e., resolve MQTT-29) 
> line 471: Section 2.3 moved to start of Section 2 as part of the introduction as it is a key concept
> line 431: Non-normative content promoted --> client server pairs must be able to manage overlapping packetIDs
> line 486: remove surrogate pairs removed as not longer relevant (machine representation v wire format)
> line 493: Storing state subsection moved to Section 4
> line 1293: Section 4 "Flows" changed to "Implementation consideration"
> line 500+ "MQTT Control Packets": move description of terms and discussion under correct subsections
> line 501+ restructure CONNECT subsection for clarity
> line 750: refactor existing CONNECT processing steps under 3.1.4 "Response"
>   

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