[MIP-3] Support MQTT protocol version 5

[mattisonchao]

Motivation

Current we just support MQTT protocol version 3.1/3.11 and a part of version 5.

Goal

Complete support MQTT protocol version 5.

API Changes

none.

Implementation

CONNECT

• Authentication method @Technoboy- Support MQTT-5 CONN Auth Method and Auth Data. #692
• Maximum packet size Support mqtt5 connect maximum packet size property. #631
• Receive maximum
• Request problem information @mattisonchao Support MQTT-5: Request problem information #655
• Request response information // Optional feature
• Session expiry interval
• Topic alias maximum @mattisonchao Support MQTT-5 property topicAliasMaximum #686
• User property

Last will and testament

• Content type @Technoboy- Support MQTT-5 will message with properties. #666
• Correlation data @Technoboy- Support MQTT-5 will message with properties. #666
• Message expiry interval @Technoboy- Support MQTT-5 will message with message expiry interval and delay interval #670
• Payload format indicator @Technoboy- Support MQTT-5 will message with properties. #666
• Response topic @Technoboy- Support MQTT-5 will message with properties. #666
• User property @Technoboy- Support mqtt5 last will message with user properties. #632
• Will delay interval @Technoboy- Support MQTT-5 will message with message expiry interval and delay interval #670

CONNACK

• Assigned client identifier
• Authentication data @Technoboy- Support MQTT-5 CONN Auth Method and Auth Data. #692
• Authentication method @Technoboy- Support MQTT-5 CONN Auth Method and Auth Data. #692
• Maximum packet size @Technoboy- Support MQTT-5 Conn-ACK with subscriptionIdentifiersAvailable and maximumPacketSize #685
• Maximum qos @Technoboy- Support MQTT-5 connect ack with Max Qos. #677
• Reason string
• Receive maximum
• Response information @Technoboy- Support MQTT-5 connect ack with Max Qos. #677
• Retain available // For we support retained message, so no need to do.
• Server keep alive
• Server reference // No need to implement, supported
• Session expiry interval
• Shared subscription available
• Subscription identifiers available @Technoboy- Support MQTT-5 Conn-ACK with subscriptionIdentifiersAvailable and maximumPacketSize #685
• Topic alias maximum @mattisonchao Support MQTT-5 property topicAliasMaximum #686
• User property
• Wildcard subscription available @mattisonchao // For we support wildcard subscription, so no need to do.

PUBLISH

• Content type @Technoboy- Support MQTT-5 publish related properties. #663
• Correlation data @Technoboy- Support MQTT-5 publish related properties. #663
• Message expiry interval @Technoboy- Support MQTT5-5 publish message expiry interval. #669
• Payload format indicator @Technoboy- Support MQTT-5 will message with properties. #666
• Response topic @Technoboy- Support MQTT-5 publish related properties. #663
• Subscription identifier // Currently doesn't have a use case for it. and many clients don't support it yet.
• Topic alias @mattisonchao Support MQTT-5 topic alias. #688
• User property @Technoboy- Support MQTT-5 Publish with user properties. #658

PUBACK / PUBREC / PUBREL / PUBCOMP / SUBACK / SUBSCRIBE / SUBACK

• Reason string
• User property //No need to implement

SUBSCRIBE

• Subscription identifier //No need to implement
• User property //No need to implement

DISCONNECT

• Reason string
• Server reference // No need to implement, supported
• Session expiry interval
• User property

AUTH @Technoboy- #693

• Authentication method
• Authentication data
• Reason string
• User property

Reject Alternatives

none.

[mattisonchao]

@Technoboy-

I will continue work for this after MIP-1.