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-502) Handling version 3.x clients

Ken Borgendale created MQTT-502:

             Summary: Handling version 3.x clients
                 Key: MQTT-502
                 URL: https://issues.oasis-open.org/browse/MQTT-502
             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
          Issue Type: Bug
          Components: core
    Affects Versions: 5, CSD01
            Reporter: Ken Borgendale
             Fix For: 5

Could you add a sort of non normative comments about handling version
3.x clients for backward compatibility?

For example:

What reason code should the broker send with CONNACK for protocol
error before determining the client version ?
(Version 3.x clients expect 0x01, while version 5 do 0x81 or 0x82.)
The broker cannot determine clients version immediately because
version 5 CONNECT magic word "MQTT" is as same as version 3.1.1.

How should the broker convert the messages between version 3.x clients
and version 5 ?
(Add or delete properties obviously. Anything else to concern ?)

Tatsuzo Osawa

This message was sent by Atlassian JIRA

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