RE: [mqtt-comment] Re: Comments on wd09

[Brian Raymor <Brian.Raymor@microsoft.com>]

Thanks for the feedback, Roger.

I've opened https://issues.oasis-open.org/browse/MQTT-328 for review and tracking.



-----Original Message-----
From: mqtt-comment@lists.oasis-open.org [mailto:mqtt-comment@lists.oasis-open.org] On Behalf Of Roger Light
Sent: Saturday, December 10, 2016 7:25 AM
To: mqtt-comment@lists.oasis-open.org
Subject: [mqtt-comment] Re: Comments on wd09

I've spotted some more overlaps in return codes.

Return code 154 is used by both pubrec and puback as "qos level not
supported", and disconnect as "alias not supported".

Return code 159 is used by subscribe as "subscription identifiers not
supported" and connack as "connection rate exceeded".

Some return codes aren't used - 141, 147, 148.

Regards,

Roger


On Sat, Dec 10, 2016 at 8:14 AM, Roger Light <roger@atchoo.org> wrote:
> Hello,
>
> In table 3.13 for disconnect codes, the code 139 is "server shutting
> down". In table 3.6 for pubrec return codes, the code 139 is "topic
> invalid". This looks to be a typo in table 3.6 because code 144
> already exists for "topic invalid".
>
> The description of the return codes is a bit inconsistent. Sticking
> with the invalid topic case, it is variously described as
>
> Topic invalid : The topic is invalid
> Topic Filter not valid : The topic filter is correctly formed, but is
> not allowed for this client
> Topic name or filter not valid : The topic name or filter is valid,
> but it is not accepted by this client or server.
>
> I see that these apply to different scenarios, but the different
> descriptions are confusing. Should I take "the topic is invalid" to
> mean that it is not correctly formed? What is the difference between
> "is correctly formed" and "is valid"?
>
> I don't think descriptions of a term should just repeat the same words
> as the term itself, it doesn't clarify anything.
>
> Regards,
>
> Roger

-- 

This publicly archived list offers a means to provide input to the

OASIS Message Queuing Telemetry Transport (MQTT) TC.



In order to verify user consent to the Feedback License terms and

to minimize spam in the list archive, subscription is required

before posting.



Subscribe: mqtt-comment-subscribe@lists.oasis-open.org

Unsubscribe: mqtt-comment-unsubscribe@lists.oasis-open.org

List help: mqtt-comment-help@lists.oasis-open.org

List archive: http://lists.oasis-open.org/archives/mqtt-comment/

Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf

List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Committee: http://www.oasis-open.org/committees/mqtt

Join OASIS: http://www.oasis-open.org/join/