mqtt-comment message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: MQTT 5.0 WD13 - Message retaining
- From: Boris Verkhovykh <b_a_v@mail.ru>
- To: mqtt-comment <mqtt-comment@lists.oasis-open.org>
- Date: Tue, 30 May 2017 19:00:22 +0300
Hello!
I think I have found a discrepancy in the message retaining description:
1734 3.3.1.3 RETAIN
1735 Position: byte 1, bit 0.
...
1771 The setting of the RETAIN flag in an Application Message forwarded by the Server from an established
1772 connection is controlled by the Retain As Published subscription option. Refer to section 3.8.3.1 for a
1773 definition of the Subscription Options.
1774
1775 If the value of Retain As Published subscription option is set to 0, the Server MUST set the RETAIN
1776 flag to 0 when forwarding an Application Message regardless of how the RETAIN flag was set in the
1777 received PUBLISH packet [MQTT-3.3.1-12].
1778 If the value of Retain As Published subscription option is set to 1, the Server MUST set the RETAIN
1779 flag equal to the RETAIN flag in the received PUBLISH packet [MQTT-3.3.1-13].
And it appears that [MQTT-3.3.1-12] (RaP bit == 0) contradicts the last sentence from the following chapter:
2332 3.8.3.1 Subscription Options
...
2341 Bit 3 of the Subscription Options represents the Retain As Published option. If 1, Application Messages
2342 forwarded using this subscription keep the RETAIN flag they were published with. If 0, the RETAIN flag in
2343 the PUBLISH packet indicates whether it came from a retained source or is a new publication.
Or, is it different functionality for bridging? Then it should be articulated more the clearly.
Best regards,
Boris Verkhovykh
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]