Handling permission problems

The 3.1.1 specification should provide a clarification to promote better clients client side error handling, retry and recovery behavior. Change Publish (WD13 844) If a server implementation does not authorize a PUBLISH to be performed by a client; it has no way of informing that client. It MUST either make a positive acknowledgement, according to the normal QoS rules or disconnect the TCP session. Change Subscribe (WD13 979) The Payload of a SUBSCRIBE packet MUST contain at least one topic filter / QoS pair. A SUBSCRIBE packet with no payload is a protocol violation. Remove 991 - 995 (WD13) See MQTT Issue-52 ... authorized to subscribe. Change from 997 A SUBACK Packet MUST be sent to the Client by the Server containing a return code for each topic filter/QoS pair. The Server might grant a lower maximum QoS than the subscriber requested. The QoS of Payload Messages sent in response to a subscription MUST be the minimum of the QoS of the originally published message and the maximum QoS granted by the Server. Change table under 3.9.3 SUBACK Payload to have 4 values, all bits used, remove reserved/granted QoS to read return code. 0x00 - Success - Maximum QoS0 0x01 - Success - Maximum QoS1 0x02 - Success - Maximum QoS2 0x80 - Failure All other return codes are reserved and MUST NOT be used <add to non normative example for failed> change 1048 - substitute "return codes" for "granted QoS's"