[OASIS Issue Tracker] (MQTT-537) AUTH packet cannot used implied properties as there is a require property

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

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

Ken Borgendale commented on MQTT-537:
-------------------------------------

A strict reading of the v5 spec in this area would say that it is not a malformed packet to use the short form of an AUTH packet without the properties, but that it would be a protocol error since the Authentication Method property is required.

While this is silly it is not necessarily wrong.

If we get up a place to put some deveoper's notes, this is one we could put there and to change in future versions of the spec.

> AUTH packet cannot used implied properties as there is a require property
> -------------------------------------------------------------------------
>
>                 Key: MQTT-537
>                 URL: https://issues.oasis-open.org/browse/MQTT-537
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>    Affects Versions: 5
>         Environment: Â
>            Reporter: Ken Borgendale
>            Priority: Minor
>
> From Will Lisac
> {quote}Itâs unclear to me if the "Authentication Methodâ property must always be included. I see two potentially conflicting statements. 
> 3.15.2.1 Authenticate Reason Code 
> â 
> The Reason Code and Property Length can be omitted if the Reason Code is 0x00 (Success) and there are no Properties. In this case the AUTH has a Remaining Length of 0. 
> 3.15.2.2.2 Authentication Method 
> â 
> It is a Protocol Error to omit the Authentication Method or to include it more than once{quote}



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)