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] (MQTT-475) Eliminate repetitious text in PUB* Reason Code sections

    [ https://issues.oasis-open.org/browse/MQTT-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66656#comment-66656 ] 

Ken Borgendale commented on MQTT-475:

The first paragraph defines the reason codes, and the second paragraph is the mandatory statement about the use of the return codes.  They should remain separate. 

> Eliminate repetitious text in PUB* Reason Code sections
> -------------------------------------------------------
>                 Key: MQTT-475
>                 URL: https://issues.oasis-open.org/browse/MQTT-475
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd14
>            Reporter: Brian Raymor
>            Priority: Minor
>             Fix For: 5, wd14
> There seems to be much repetitious text using this "template" in all the PUB* Reason Code sections.  
> For example:
> Lines 2166-2167:
> The values for the one byte unsigned Publish Reason Code field are listed in Table 3 6 – PUBREC . If the Remaining Length is 2, then the Publish Reason Code has the value 0x00 (Success). 
> and then after the table of reason codes
> Lines 2171-2173:
> The Client or Server sending the PUBREC MUST use one of the PUBREC Reason Codes in Table 3 6 – PUBREC Reason Codes [MQTT-3.5.2-1]. The Reason Code 0x00 (Success) and no Properties may be sent by using a Remaining Length of 2.
> Why not delete 2166 and replace with 2171?

This message was sent by Atlassian JIRA

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