Cancelling 8/24 MQTT TC call

[Brian Raymor <Brian.Raymor@microsoft.com>]

 

After consultation with the editors, I propose to cancel the upcoming “placeholder” MQTT TC call scheduled for 8/24 and review all CSD core (material) issues in subsequent calls. Thanks to Ken and Ian for responding on mqtt-comment and opening tracking issues.

 

If you want to start reviewing and/or commenting on  New/Open/Deferred issues:
 

Key	Summary	Components
MQTT-464	Add reason code 150 to PUBACK packet	core
MQTT-466	Add reason code 150 to PUBREC packet	core
MQTT-489	The term Non-Shared should be spelled Non-shared	edits
MQTT-491	Wording of 3.3.1.3 RETAIN	edits
MQTT-492	Validating the payload format	core
MQTT-493	Minor errors found in wd15	edits
MQTT-494	Unsubscribe actions does not define shared sub actions	core
MQTT-495	Reason String property on AUTH missing in 3.15.2.2	edits
MQTT-498	No way to set properties on will message. Property behaviour on retained messages unspecified	core
MQTT-499	Changes made by TC Admin in CSD01	edits
MQTT-500	Incorrect maximum value for Maximum Packet Size	edits
MQTT-501	Change type of Maximum Packet Size to Variable Byte Integer	core
MQTT-502	Handling version 3.x clients	core
MQTT-503	Properties are required for SUBACK and UNSUBACK	edits

Process refresher: If any changes that are Material are made to the draft after the public review then the TC must conduct another public review. The draft may not be considered for approval by the TC as a Committee Specification until it has undergone a review cycle during which it has received no comments that result in any changes that are Material.

 

* "Material Change" is any change to the content of a Work Production that that would require a compliant application or implementation to be modified or rewritten in order to remain compliant or which adds new features or otherwise expands the scope of the work product.

 

The TC may conduct any number of public reviews. The initial public review of a draft must take place for a minimum of 30 days, and any subsequent reviews must be held for a minimum of 15 days. Changes made to a committee draft after a review must be clearly identified in any subsequent review, and the subsequent review shall be limited in scope to changes made in the previous review. Before starting another review cycle the revisions must be re-approved as a Committee Specification Draft and then approved to go to public review by the TC.