[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed.
[ http://tools.oasis-open.org/issues/browse/MQTT-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Coppen updated MQTT-8:
------------------------------
Proposal:
If a correctly formed CONNECT packet is received but the sever, but the server is unable to process it (for some reason), then the server SHOULD attempt to flow one of the following connack return codes before disconnecting the TCP Connection.
1 0x01 Connection Refused: unacceptable protocol version - The server does not support the level of the MQTT protocol requested by the client.
2 0x02 Connection Refused: identifier rejected - the client identifier is correct UTF-8 but not allowed in the server.
3 0x03 Connection Refused: server unavailable - the TCP connection has been made but the MQTT service is unavailable.
4 0x04 Connection Refused: bad user name or password - the data in the user name or password is malformed.
5 0x05 Connection Refused: not authorized - the client is not authorized to connect.
If none of these return codes are deemed applicable, then the server MUST disconnect the TCP Connection
was:
If an MQTT Packet cannot be processed by the server or client then the server or client MUST immediately disconnect the TCP session.
The client or server might want to log some diagnostics locally as to why the TCP connection was disconnected.
In the case where a correctly formed CONNECT packet is received, the server SHOULD attempt to flow one of the following connack return code before disconnecting the TCP session..
1 0x01 Connection Refused: unacceptable protocol version - The server does not support the level of the MQTT protocol requested by the client.
2 0x02 Connection Refused: identifier rejected - the client identifier is correct UTF-8 but not allowed in the server.
3 0x03 Connection Refused: server unavailable - the TCP connection has been made but the MQTT service is unavailable.
4 0x04 Connection Refused: bad user name or password - the data in the user name or password is malformed.
5 0x05 Connection Refused: not authorized - the client is not authorized to connect.
Related / dependent issues are therefore resolved as follows.:
MQTT-15 Should the CONNECT packet Protocol Name and Protocol Version fields be changed?
Flow CONNACK withe return code 0X01 if the protocol version is not supported.
If the server supports the older MQTT specification then it continues but uses the older version of the protocol.
MQTT-6 What should a server do if it receives a connect packet with and incorrect protocol name?
Disconnect the TCP session.
MQTT-22 Specification is ambiguous with regards to dynamic topics.
Disconnect the TCP session if use of the topic name is not authorized.
MQTT-38 Malformed QoS for topics in SUBSCRIBE packet.
Disconnect the tcp session.
> Create a new CONNACK return code to indicate that the CONNECT packet was malformed.
> -----------------------------------------------------------------------------------
>
> Key: MQTT-8
> URL: http://tools.oasis-open.org/issues/browse/MQTT-8
> Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
> Issue Type: Improvement
> Components: core
> Environment: MQTT Server
> Reporter: Andrew Banks
>
> The server should flow a new CONNACK with a new return code before disconnecting the TCP session if it receives a CONNECT message which is malformed.
> Malformed means that the protocol name and version are correct but something else is incorrect, for example a User Name flag is set to indicate there is a User Name in the payload but the payload is empty.
--
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]