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] Commented: (MQTT-148) 7 conformance

    [ http://tools.oasis-open.org/issues/browse/MQTT-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36536#action_36536 ] 

Richard Coppen commented on MQTT-148:

Candidate TC action: trawl doc and validate RFC2119 language. Possible options:

1. Update to MUST statements where appropriate
2. Add specific existing clauses to the summary appendix A

> 7 conformance
> -------------
>                 Key: MQTT-148
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-148
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1.1
>         Environment: Conformance
>            Reporter: Patrick Durusau
>            Priority: Critical
> The reference to MUST level requirements is insufficient as conformance clauses. 
> To illustrate: for both client and server, summarizing:
> 1. Follow syntax in chaps 2 and 3
> 2. MUST level for Chapter 3 
> OK, so where does: 
> 3.1 "A Client can only flow the CONNECT Packet once over a Network Connection."
> "If set to 0, the Server resumes communications with the Client based on state from the current Session (as identified by the Client identifier). If there is no Session associated with the Client identifier the Server creates a new Session. "
>, "The Keep Alive is a time interval measured in seconds. Expressed as a 16-bit word, it is the maximum time interval that is permitted to elapse between two successive Control Packets sent by the Client."
>, "If a Client does not receive a PINGRESP Packet within a reasonable amount of time after it has sent a PINGREQ, it SHOULD close the Network Connection to the Server...."
> "The Server MAY restrict the ClientId it allows in terms of their lengths and the characters they contain" (Note the ",." typo at the end of this sentence.)
> I won't go all the way through three but you get the idea. 
> The conformance clauses as written, are leaving a lot of normative behavior unspecified for "conforming" applications. I could depart from any of these statements and still be a conforming server/client under MQTT. I don't think that is what you intended. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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