← Prev in month ← Prev in thread
Next in thread → Next in month →

MQTT Public Review completed, way ahead

From
Lemire, Dave (HII-TSD) <>
Date
2021-10-04T13:46:05+00:00
ID
Thread
MQTT Public Review completed, way ahead
TC Members:  the public review of the MQTT Transfer spec closed last Wednesday evening, 9/29. A single comment message was submitted (copy attached) with four minor comments, none of which require material changes to the spec.  My plan
 from here:

 

1.      
Draft a pull request responding to the comment, which essentially will incorporate the comment and, where relevant, point back to the corresponding content in the MQTT v5 specification.

2.      
Create a CRM and send to the OpenC2 and OpenC2-Comment mail lists recording the resolutions.

3.      
Present the PR for discussion at this week’s working meeting and for approval at next week’s working meeting.

4.      
Posted the updated working draft to OASIS

5.      
Make motion at the 10/20 TC meeting to conduct a special majority vote to approve the new WD as a Committee Specification.

 

IMO gaining formal approval of a publish/subscribe messaging solution for OpenC2 will represent a significant step forward in the usability of our TC’s work.

 

Dave

 

David Lemire

IA Systems Engineer

Technical Solutions

302 Sentinel Drive | Annapolis Junction, MD 20701

Work (301) 575-5190 |
Mobile (240) 938-9350

 

--- Begin Message ---

From: Andrew Banks <>

To: ""	<>

Date: Tue, 7 Sep 2021 13:08:30 +0000

CAUTION: This email originated from outside your organization. Exercise caution when opening attachments or clicking links, especially from unknown senders.

2.2 Default Topic Structure

Might be worth clarifying the difference between a subscription to "oc2/rsp" and "oc2/rsp/#".

2.6 MQTT Client Identifier

Some brokers allow a connection with a zero byte ClientId. This will cause the MQTT broker to generate a ClientID that is guaranteed to be unique.

2.8 Will Message

Might be better so say "must not use a will message", that way you can opt to use a will message in the future.

3.3 SUBSCRIBE Control Packet

If Qos=1 is used, the receiver will have to be capable of dealing with a repeated (duplicate) message.

--- End Message ---
← Prev in month ← Prev in thread
Next in thread → Next in month →