This is a case where I engaged mouth before putting my brain in gear. DISREGARD, everything is fine on your end, it was a googlesheet….
From: Robin Cover <email@example.com>
Sent: Thursday, April 5, 2018 12:27 PM
To: Brule, Joseph M <firstname.lastname@example.org>
Cc: email@example.com; dave.lemire <firstname.lastname@example.org>; Kemp, David P <email@example.com>; Joshua_Brulé <firstname.lastname@example.org>; Adam Bradbury <email@example.com>; Danny Martinez <firstname.lastname@example.org>; STAIR, MICHAEL A <email@example.com>;
ESSING, BLAKE <firstname.lastname@example.org>; email@example.com
Subject: Re: [openc2-imple] RE: [Non-DoD Source] RE: Seeking a few word about your repos
On Thu, Apr 5, 2018 at 11:08 AM, Brule, Joseph M <firstname.lastname@example.org> wrote:
ALCON = ‘All Concerned’.
I will shoot off an email to Robin, I am stunned that the maintainers of the repos do not have full
OK, standing by... when I read "edit rights on repo sheet", I thought Duncan means edit rights to a Google Spreadsheet document, which (?) I don't
manage, in this case
Additionally (for Dave, I guess, initially, as he is tracking and supporting the GitHub repositories): would there be opportunity to get some of the updated repo
information you are collecting into the GitHub repository README files? I recently send Danny a message about his posting to the SC 
I could make the addition if you want to authorize it as purely clerical.
https://github.com/oasis-open/openc2-pub-sub-on-bsd#additions-to-statement-of-purpose: "Repository Maintainers may include here any clarifications,,"
Was written in C and developed on HardenedBSD
It utilizes a sub//pub (zeroMQ) model for its communication fabric
The project has 3 subparts, broadcast, edge, and orchestrator
The broadcast is used to create OpenC2 messages
The orchestrator is used to send the OpenC2 messages to the appropriate places
The edge is used to receive and act upon OpenC2 messages
The edge utilizes plugins to add functionality, current two exist allow, and deny
The allow and deny plugins are structured to work with packet filter firewall
The intent is to create edge plugins for any functionality required by the actuator
Dumb question: What is ALCON?
Yes I would like edit rights on repo sheet.
On Ocas sheet (I couldn't make change myself since no permission), please add another top level bullet
+ build to forum rc4 and had minor updates but is currently out of date
+ intent is to update to CSD03 now that CSD03 has complete thread
iPhone, iTypo, iApologize
-------- Original Message --------
Subject: Re: Seeking a few word about your repos
From: Dave Lemire <email@example.com>
Date: Tue, April 03, 2018 10:32 am
To: Duncan <firstname.lastname@example.org>, "Kemp, David P"
<email@example.com>, Joshua_Brulé <firstname.lastname@example.org>, Adam
Bradbury <email@example.com>, Danny Martinez
<firstname.lastname@example.org>, "STAIR, MICHAEL A" <email@example.com>,
"ESSING, BLAKE" <firstname.lastname@example.org>
Cc: "Brule, Joseph M" <email@example.com>,
ALCON: I've drafted an informational briefing about our open repos for tomorrow's working call. You
can find the GSlides file in the GDrive implementation folder:
Please take a few minutes to review / correct, especially if I've mis-characterized your repo. :-)
Also, if you're a repo maintainer / SME, I'll be happy to give you editing rights on the repo status
GSheet referenced in the briefing:
Note: I've left off the openc2-iacd repo, as JoeB advises it will never be populated. I need to send
out a CFO to the TC for deleting it.
David P. Lemire,
OpenC2 Technical Committee Executive Secretary
OpenC2 Implementation Considerations SC Co-chair
Contractor support to NSA
Office: 301-575-5190 / Mobile: 240-938-9350
On Tue, Mar 20, 2018 at 9:09 AM, Dave Lemire <firstname.lastname@example.org>
Each of you have your names associated with one or more of our open repos for OpenC2. I would like to
"share the wealth" by giving the TC a presentation about our open source repos, and what they contain. I'd very much appreciate it if each of you could give me a few bullets about the repos you're associated with and what's interesting / special / unique
about them, and why other implementer of OpenC2 should seek them out.