OpenC2 TC Members,
ITEM ONE:Â Contribute to PR01 Issue Resolution.
The TC's #1 priority right now is resolving PR01 issues to create the PR02 versions of the three specifications. Our goal is to approve new CSD/PR versions of the specifications following the 20 February meeting and hopefully initiate PR02 before or concurrent with the upcoming RSA Conference.
Please remember: the specification editors are using GitHub to manage PR01 issue resolution. All three specifications have Comment Resolution Matrices (CRMs) that link to GitHub issue and pull-requests that capture the proposed resolutions to the comments we received. The editors greatly desire TC member input on the resolutions, which can be as simple as "+1" to a specific pull request (if you're not a GitHub member, sign-up is easy; if you don't want to sign up, use the SC mail lists or Slack to provide your feedback on any issue or PR). If you'd like to do more, creating pull requests for specific issues is a real help, too: every PR created by a non-editor TC member makes the editor's job a bit easier. Here are links to the issue lists; the pull requests with line-in / line-out changes are readily accessible from these pages:
Language Specification:ÂÂhttps://github.com/oasis-tcs/openc2-oc2ls/issues
SLPF AP:ÂÂhttps://github.com/oasis-tcs/openc2-apsc-stateless-packet-filter/issues
HTTPS Transfer Specification:ÂÂhttps://github.com/oasis-tcs/openc2-impl-https/issuesÂÂÂ
SLPF AP:ÂÂhttps://github.com/oasis-tcs/openc2-apsc-stateless-packet-filter/issues
HTTPS Transfer Specification:ÂÂhttps://github.com/oasis-tcs/openc2-impl-https/issuesÂÂÂ
ITEM TWO:ÂÂNominees for Co-Chair Positions.
We will be having elections at the March TC meeting for a co-chair for the TC and each of the three SCs. It's time for nominations, please consider serving or approaching a colleague to serve as a co-chair for the TC or one of the subcommittees. Please remember that there is no obligation for a co-chair to be a document editor or vice-versa; that our co-chairs are also currently editors is a coincidence.
ITEM THREE: Proposal for Next Face-to-Face.
The TC co-chairs are proposing that the next F2F meeting be held April 30 -Â May 1 in the Washington - Baltimore area. This would schedule the meeting adjacent to the next IACD Integrated Cyber event, planned for May 2-3 at JHU APL. There is notable overlap of OpenC2 participants with interest in Integrated Cyber. Please advise Joe Brule or Sounil Yu regarding this proposed schedule.
ITEM FOUR: Meetings For This Week.
Meetings this week are aÂ90-minuteÂLanguage SC meeting and a regular duration IC-SC meeting. Focus for both continues to be PR01 issue resolution:
- Language SC: Tuesday, 5 February at 1:00pmÂuntil 2:30pmÂEST
https://meet.lucidmeetings.com/meeting/207160 - Implementation Considerations SC:Â Wednesday, 6 February at 1:00pm EST
https://meet.lucidmeetings.com/meeting/207165Â
The Language SC will be meeting weekly at the usual time but for 90-minute sessions throughout February to allow more time for issue resolution. In the interest of speeding up issue resolution, the SC co-chairs may need to extend their usual 1-hour meeting lengths or scheduleÂad hocÂmeetings. Please watch the SC mail lists and slack channels for meeting announcements.
Very Respectfully,
Sent by David Lemire, TC Secretary, on behalf of
  Joe Brule & Sounil Yu, OpenC2 TC Co-Chairs