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-513) 4. Need a variable conformance clause, for teh sake of interoperability

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

Ken Borgendale commented on MQTT-513:

MQTT only deals with the application layer and does not specify anything about the other layers except that the client and server must be able to communicate across an ordered, lossless connection.

Interoperability requires that the client and server communicate over compatible network stacks, but this is not really an MQTT conformance issue.

> 4.	Need a variable conformance clause, for teh sake of interoperability
> -----------------------------------------------------------------------
>                 Key: MQTT-513
>                 URL: https://issues.oasis-open.org/browse/MQTT-513
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, CSD01
>            Reporter: Ken Borgendale
>              Labels: TAB
> TAB-1563 - Jacques Durand
> We read: “A conformant Server MUST support the use of one or more underlying transport protocols that provide an ordered, lossless, stream of bytes from the Client to Server and Server to Client [MQTT-7.1.1-1]. However, conformance does not depend on it supporting any specific transport protocols. A Server MAY support any of the transport protocols listed in section 4.2, or any other transport protocol that meets the requirements of section 4.2.” But that will not help an end-user to know if its conforming Server will be able to communicate with a conforming Client. For this, the conformance clause should be “parameterized” –see “5.5 variable conformance clauses” in http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html . The “TransportProtocol” should be a variable of the Clause, and a claim should then look like: “Our server product XYZ conforms as a “MQTT tServer”, with TransportProtocol = {protocolX, protocolY}

This message was sent by Atlassian JIRA

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