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] Updated: (MQTT-6) What should a server do if it receives a connect packet with and incorrect protocol name?


     [ http://tools.oasis-open.org/issues/browse/MQTT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Banks updated MQTT-6:
----------------------------

      Proposal: 
If the first data that the server receives is not an MQTT CONNECT packet, including the correct protocol name, then it MAY continue to process it
as some other protocol,  alternatively it MUST disconnect the TCP session without sending a CONNACK. The server MUST NOT continue to process a malformed initial packet in line with this specification.

Non normative comment.
A server can support multiple protocols by checking to see if the initial data it receives is a valid CONNECT packet or valid data for some other protocol such as an earlier version of the MQTT specification.
    Resolution: Updated in WD08.

> What should a server do if it receives a connect packet with and incorrect protocol name?
> -----------------------------------------------------------------------------------------
>
>                 Key: MQTT-6
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-6
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>            Reporter: Andrew Banks
>
> What should a server do if it receives a connect packet with and incorrect protocol name?
> If the server receives a connect packet with no MQIsdp field present ( or its replacement field) The server could.
> 1) Disconnect the Clients TCP session
> 2) Return CONNACK  RC=X01, then disconnect the clients TCP session.
> 3) Return CONNACK with some new return code and then disconnect the clients TCP session.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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