[OASIS Issue Tracker] (MQTT-394) 3.4 PUBACK – Publish acknowledgement - comments

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Brian Raymor edited comment on MQTT-394 at 1/19/17 1:04 AM:
------------------------------------------------------------

1953 Table 3.5 - PUBACK Return Codes

Just curious - for "No matching subscribers" - why would the Server not know this?

If the Server does not know if there are any matching subscribers, it SHOULD use the 0x00 (Success) Return Code.

For 0x80, should this be "PUBLISH" for consistency with the other descriptions in the table?

The receiver does not accept the [publish]


was (Author: brianraymor):
1953 Table 3.5 - PUBACK Return Codes

Just curious - for "No matching subscribers" - why would the Server not know this?

If the Server does not know if there are any matching subscribers, it SHOULD use the 0x00 (Success) Return Code.

> 3.4 PUBACK – Publish acknowledgement  - comments
> ------------------------------------------------
>
>                 Key: MQTT-394
>                 URL: https://issues.oasis-open.org/browse/MQTT-394
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Assignee: Rahul Gupta
>            Priority: Trivial
>             Fix For: 5, wd11
>
>
> 1. Extra "it":
> 1939 Code is specified and 2 if [it] a Return Code is not specified.
> 2. Are we correcting figure references at this time or later? It's Figure 3.11.
> 1941 The variable header format is illustrated in Figure 3.13 – PUBACK Packet variable header. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)