[OASIS Issue Tracker] (MQTT-340) If this value is not 5 ...

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Ken Borgendale commented on MQTT-340:
-------------------------------------

This wording was originally put into the MQTTv3.1.1 spec as an issue saying that the Server MUST reject a CONNECT packet with an invalid version field.  It was pointed out that a strict interpretation of that would not allow a server to implement multiple versions of MQTT.  This was the wording done then and carried over (and indeed duplicated) in the MQTTv5 spec.

I argued at the time that the better solution would be to just leave out the requirement that the server treat an incorrect version as a malformed packet.

We have several other places where we talk about other versions of MQTT.  I think it is always a mistake to say what to do if another version is received or how to interact between them.

As noted, there were comments and replies about this in the editor's draft for 3 months.  It got deleted when there was no response to statements about what the intent was.

> If this value is not 5 ...
> --------------------------
>
>                 Key: MQTT-340
>                 URL: https://issues.oasis-open.org/browse/MQTT-340
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Assignee: Ed Briggs
>            Priority: Minor
>             Fix For: 5, wd10
>
>
> The rationale for this normative language is absent:
> 821 If this value is not 5, the Server MAY continue processing the CONNECT packet in accordance with some
> 822 other specification,
> What is the intent?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)