After the usual status update I’d like to talk about device identifiers:
·
In MQTT there’s a clientID in the CONNECT packet that is really just a way for the broker to uniquely identify the device to track connection state.
·
In our proposed MQTT topic structure there’s a place for device-specific channels (oc2/cmd/device/<deviceID> or something like that).
·
In the OpenC2 message format we’ve got TO: and ACTUATOR: fields whose content is undefined.
It seems like there’s potential for a useful discussion of how we should determine device identifiers for the topic name and message content. Hopefully we get enough participants to have some meaningful exchange.
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