After working through the MQTT Transfer Spec so far, based on v3.1.1 of the protocol, and working w/my software team on some of the details, it's becoming clearer to me that some of the v5.0 features really would be beneficial for OpenC2
messaging:
·
Payload Format Description -- provides clear indication of text vs. binary payload
·
Session & Message Expiry -- allows management of how long messages stay in the system awaiting delivery
·
User Properties -- provide equivalent to HTTP headers for metadata regarding the payload, etc.
·
Enhanced Authentication -- should allow for stronger / more flexible I&A of OpenC2 communicants
There are other advantages to v5.0; improved error / status information, cleaner logic for the renamed Clean Start flag, etc.
I think it's worth considering whether the best course of action is to refocus the specification on v5.0 once the 28 October plug-fest event is complete and skip a v3.1.1-based transfer spec.
Dave
David Lemire
Systems Engineer
HII Mission Driven Innovated Solutions (HII-MDIS)
Technical Solutions Division
302 Sentinel Drive | Annapolis Junction, MD 20701
Work (301) 575-5190 |
Mobile (443) 535-1182