ITEM THREE:ÂPost-plug fest. AsÂ
has been reportedÂwe had a very successful plug fest / hackathonÂ
27-28 January. We are in the process of documenting and capturing lessons learned. Review the plug fest outcomes page on GitHub. If you were there,Â
pleaseÂcontribute your experience.
https://github.com/oasis-tcs/openc2-usecases/blob/master/Cybercom-Plugfest/Plugfest-Outcomes.mdRegardless of whether or not you attended the Plug Fest, letâs find ways to improve our suite of specifications, which leads us toâ Â
ITEM FOUR:ÂA call for post 1.0 Participation. Version 1.0 of the specifications have been posted, approved, announced and we are seeing implementations. Letâs take advantage of the momentum.
- Do you have a product or service that's a candidate for producing / consuming OpenC2 commands and responses? Please consider sharing your Custom Actuator Profile or Proposed Committee specification. Contact the AP-SC co-chairs (Alex Everett and Dave Kemp).
- We are seeing interest in augmenting the HTTPS transfer specification and other message fabrics. Is there a message fabric that is more suitable for your cyber-ecosystem? Share your proposed key management, transport solutions and other implementation considerations with the IC-SC co-chairs (Dave Lemire and Michelle Barry)
- Do you need OpenC2 to do more? Do you have a use case or scenario that we have not considered? Please inform Toby Considine of your use cases and architectural concerns. Â
Meetings This Week:Actuator Profile SCTuesday,Â
24ÂFebruary at 13:00 EST
Meeting link:Â
https://meet.lucidmeetings.com/meeting/243199ÂÂ
Sent on behalf of the TC Co-Chairs,