[OASIS Issue Tracker] (MQTT-385) Simple clients skipping properties

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

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

Ed Briggs commented on MQTT-385:
--------------------------------

This text appears in the section which contains the table of all properties.  One could (incorrectly) interpret this to mean that a client could 'skip over' properties like  max packet size, max qos, max topic aliases, etc., breaking mechanisms they are required to provide.  I think this does require clarification to avoid an interop problem.  A related aspect is the use of 'full function client':  can this be interpreted (devils advocate) to mean that a client may circumvent mandatory behavior by simply calling itself a non-full-function client?

> Simple clients skipping properties
> ----------------------------------
>
>                 Key: MQTT-385
>                 URL: https://issues.oasis-open.org/browse/MQTT-385
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Priority: Minor
>             Fix For: 5, wd10
>
>
> What is the rationale for this exemption -and- how is it interoperable?
> 757 A Client MAY process the Packet without checking the Properties by skipping over the number of bytes
> 758 specified by Property Length. A Client which does not check the Properties MUST NOT make use of any
> 759 Property it has not checked. A Server MUST check all Properties in a Control Packet.
> 760
> 761 Non normative comment
> 762 This exemption for Clients is designed to allow for simple Clients that do not require the
> 763 information sent in Properties. A full function Client should check and use the information in the
> 764 Properties.



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