← Prev in month ← Prev in thread

[OASIS Issue Tracker] Updated: (MQTT-50) Handling of invalid CONNECT packets

From
OASIS Issues Tracker <>
Date
2013-09-05T13:34:09+00:00
ID
497867335.7891378388080117.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Updated: (MQTT-50) Handling of invalid CONNECT packets
[ http://tools.oasis-open.org/issues/browse/MQTT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Coppen updated MQTT-50:
-------------------------------

    Proposal: 
The server MAY disconnect the client if the protocol name is incorrect. If the protocol name is correct, but the version number is incorrect, then the server MUST flow a connack rc=0 and then disconnect the client. 

This is already in the spec from WD08 (MQTT-6). See section 3.1.4 response and 3.1.2.2 protocol level (WD10). 

Previously: see MQTT-6 

  was:see MQTT-6 


See updated proposal this like a dup and can be closed.

> Handling of invalid CONNECT packets
> -----------------------------------
>
>                 Key: MQTT-50
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-50
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1.1
>            Reporter: Richard Coppen
>             Fix For: 3.1.1
>
>
> What should the server do if it receives a connect packet that it does not recognize?
> For example:
> 1. The packet contains an invalid (or unsupported) protocol name
> 2. The packet contains an invalid (or unsupported) protocol version

-- 
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
← Prev in month ← Prev in thread