OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt-comment message

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

Subject: Re: [mqtt-comment] Wildcard Subsriptions, QoS 1 / 2 optional


I agree with Christohp and Roger, optional functions and QoS will reduce interoperability, complexify applications and have a negative impact on the use of MQTT.


PS: Some brokers like AWS MQTT already reduce QoS and the functionalities without negotiating with the client.

Le 19/03/2017 à 22:19, Roger Light a écrit :

I agree with Christoph here as well, there should be some more
consideration given to all of the optional options and whether they
should be required or not.



On Tue, Mar 14, 2017 at 12:29 PM, c@ckrey.de <c@ckrey.de> wrote:
Dear committee members,

Wildcard Subscriptions and QoS 1 and 2 have always been key features of

You leave it to the decision of the broker implementors to make QoS 1 or QoS
2 available.

The existence of a Return Code "0xA2 Wildcard Subscription not support“
suggests that the
implementation of wildcard subscriptions is another „MAY“ for brokers.

Would you include in the v5 specification a section were all features which
became optional compared to MQTT3.1.1.
And for the broader audience, it would be very helpful to understand why you
made such proposals.

Please review your decision. Otherwise I see
- interoperability issues between applications and brokers (think bridging)
- more complex client applications
- a decrease in the use of MQTT

Christoph Krey
<c@ckrey.de> 7582 9188 8D6C E945 15BA  4CD9 900D FB34 2AB0 38D7
Breite Strasse 79, 41460 Neuss, Germany
+49 1511 874 4526

ScalAgent Distributed Technologies        http://jorammq.scalagent.com
Freyssinet Andre
Tel : 33 (0) / 33 (0)

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