29th 9:30-11AM EDT Works.
30th, 31st Only 9:30-10AM
Patrick Maroney
Principal - Cybersecurity
Chief Security Office
Office: 732.615.5287 | Cell: 609.678.5613 |
Email:
From:
Lemire, Dave (HII-TSD) <>
Date: Monday, March 21, 2022 at 12:35 PM
To: MARONEY, PATRICK <>, Vasileios Mavroeidis <>, duncan <>, Toby Considine <>, TC OpenC2 <>
Subject: Proposed Schedule for LS Issue Triage Work Session
Duncan, Patrick, Vasileios, Toby,
(I’m including Toby as he’s currently one of the LS editors; I’m including the TC mail list for situational awareness)
As this month has 5 Wednesdays, there’s no working meeting next week. I’d propose to schedule an LS Issue triage session for between 1.5 and 2.0 hours, starting at 9:30am EDT on one of Tu / Wed
/Th, March 29th, 30th, or 31st to make an initial pass through the open issues and identify ones we’d recommend
Closing
Addressing as part of a v1.1 revision to the LS
Deferring to future consideration
Please let me know if any of these times work for you. All other TC members are, of course, welcome to participate in any OpenC2 TC-related work session.
Dave
David Lemire
IA Systems Engineer
Technical Solutions
302 Sentinel Drive | Annapolis Junction, MD 20701
Work (301) 575-5190 |
Mobile (240) 938-9350
From: [mailto:]
On Behalf Of Lemire, Dave (HII-TSD)
Sent: Friday, March 11, 2022 9:20 AM
To: MARONEY, PATRICK <>; TC OpenC2 <>
Subject: EXT :[openc2] RE: EXT :Re: Language Specification Issue Clean-Up
CAUTION: This email originated from
outside your organization. Exercise caution when opening attachments or clicking links, especially from unknown senders.
I’d agree, Patrick, that context is an issue with a number of the issues. I started taking my own advice and reviewing older issues, which triggered
this example of a discussion that needs context [github.com]. Hopefully we have enough members with long memories, as many of these issues arose when Jason Romano was driving the LS forward. I know I mostly don’t have it, as I was IC-SC co-chair through
all of that period and so had other priorities.
Based on feedback so far, a dedicated kick-off session seems useful, probably scheduled earlier than our usual 11:00 meeting time to help accommodate our European contributors.
Dave
David Lemire
IA Systems Engineer
Technical Solutions
302 Sentinel Drive | Annapolis Junction, MD 20701
Work (301) 575-5190 |
Mobile (240) 938-9350
From: MARONEY, PATRICK [mailto:]
Sent: Friday, March 11, 2022 8:01 AM
To: Lemire, Dave (HII-TSD) <>; TC OpenC2 <>
Subject: EXT :Re: Language Specification Issue Clean-Up
CAUTION: This email originated from
outside your organization. Exercise caution when opening attachments or clicking links, especially from unknown senders.
Count me in as well Dave. Either way works, presuming availability.
I took a quick look and some of the circa 2018-2019 issues have missing background context for those of us on the periphery. I think a dedicated 1 Hour kick-off meeting to level set and fill in background
context would be valuable.
Patrick Maroney
Principal - Cybersecurity
Chief Security Office
Office: 732.615.5287 | Cell: 609.678.5613 |
Email:
From:
<> on behalf of Lemire, Dave (HII-TSD) <>
Date: Thursday, March 10, 2022 at 9:55 AM
To: TC OpenC2 <>
Subject: [openc2] Language Specification Issue Clean-Up
TC Members: as discussed during the 9 March 2022 working meeting, our on-going work on actuator profiles and transfer specifications has clearly indicated a need for an update to the current
v1.0 CS02 OpenC2 Language Specification. The
LS repository currently has
30 open issues, some of which have been open (and not updated) for a considerable period of time. I propose that we organize a focused work session to review the existing LS issues, identify ones that can be closed as no longer valid, and prioritize which
of the remaining should be resolved as part of a v1.1 update to the LS. This could be done either during one of our weekly Wednesday working meeting, or as a one-off special work session, depending on the availability of interested parties to commit to one
or the other.
If you are interested in contributing to this issue screening effort, please reply here with your interest and your preference for using working meeting time or for scheduling a separate focused work session.
If the majority preference is for a separate session I will undertake to coordinate scheduling that meeting. In the interim, there would be value in our members taking a fresh look at the issues on GH and adding their opinions there regarding any / all of
the currently open issues; having that input prior to a work session may significantly improve the efficiency of the meeting.
As an FYI, my software team has identified some concerns with the LS (and to a lesser degree the architecture spec) that I plan to being recording as new issues in the appropriate repositories.
Dave
David Lemire
IA Systems Engineer
Technical Solutions
302 Sentinel Drive | Annapolis Junction, MD 20701
Work (301) 575-5190 |
Mobile (240) 938-9350
