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-486) RFC 2119 scan for MAYs

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

Andrew Banks edited comment on MQTT-486 at 6/28/17 3:39 PM:

for b) i also included the case where auth is shortend to a zero byte variable header, like disconnect

was (Author: andrew_banks):
for b) i also included the case where auth is shortend to a zero byte payload, like disconnect

> RFC 2119 scan for MAYs
> ----------------------
>                 Key: MQTT-486
>                 URL: https://issues.oasis-open.org/browse/MQTT-486
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: core
>    Affects Versions: wd14
>            Reporter: Peter Niblett
>             Fix For: wd15
> I have scanned WD14 for all cases of may or MAY.  This is the list of occurrences that I found that I think are problematic.  There are a number of lower case mays in Non-Normative text, and I am ignoring most of them here.
> 1. Lower case mays which should be upper case MAYs
> None
> 2. Lower case mays which aren't RFC 2119 MAYs. For the avoidance of doubt I recommend these get changed to an alternative, as shown in the proposal
> -
> -,,,,
> -,,,,,, (User Property)
> - 4.4 footnote
> - 4.10.1
> - 4.13.2
> 3. Upper case MAYs which should not be. 
> - 3.14 "The Client or Server MAY send a DISCONNECT packet before closing the Network Connection".  This is borderline, but it's not really an optional implementation thing, so I think this could be a "can"
> -----------------------
> In passing, one thing I found a bit surprising was "The Server MAY check that the contents of the CONNECT packet meet any further restrictions" in 3.1.4. This is ok regarding RFC 2119, but it means that, for example, a server that doesn't like the Will Topic can choose to ignore it and reply with a 0 return code, so the client is none the wiser

This message was sent by Atlassian JIRA

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