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-509) exercise reuse in Conformance Clauses

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

Ken Borgendale commented on MQTT-509:

Sections 2 and 3 define the format and semantics of the control packets.  Implementations cannot choose which control packets to support.  They must support all of them in accordance with this spec.  Servers are allowed to have very minimal support for some options by declaring non-support and closing the connection if the client sends them.  Clients can avoid fully supporting some function by not ever using that function.

In the conformance clauses for Server and Client in sections 7.1.1 and 7.1.2 we say that conformance requires that "the format of all MQTT Control Packets that the (Server or Client) sends matches the format described in Chapter 2 and Chapter 3".

Thus what exists if basically what is suggested, except that we do not break down conformance by control packet, but say that clients and servers must support them all.

> exercise reuse in Conformance Clauses
> -------------------------------------
>                 Key: MQTT-509
>                 URL: https://issues.oasis-open.org/browse/MQTT-509
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, CSD01
>            Reporter: Ken Borgendale
>            Priority: Minor
>              Labels: TAB
> TAB-1559 - Jacques Durand (TAB)
> A lot of normative content is really about the message itself, or “packet”. 
>  In Section 2, but also section 3. Some normative content is expressed in tables and packet structure, not in textual; keyworded (MUST) statements (MUST…) Which is fine. But then it may be better to create a conformance clause just for the message itself (as a separate conf target). Then other conf clauses may refer to this one (in Server clause, one of theconditions would be: “ all messages sent by Server are conforming to Message per the Message CClause”) 

This message was sent by Atlassian JIRA

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