RE: [Non-DoD Source] [openc2] OpenC2: Face to Face Tiger Team

["Brule, Joseph M" <jmbrule@radium.ncsc.mil>]

Well this is timely!

I just got an email from Dee Schurr regarding a Borderless conference in 
Prague.  She graciously offered a venue for an OpenC2 F2F and she encouraged 
us to submit a paper.

My question is:  who can lead the Face to Face tiger team?

VR

Joe B

===== tear line =====

Thanks Joe!
We are offering space for an OpenC2 F2f on 4-5 December, the regular 
conference will follow on 6-7 December. The venue is the Prague Marriott. The 
link is http://eu17.first-oasis-conference.org/en/, the event is co-sponsored 
by FIRST and OASIS. Please encourage TC to submit presentation for the CfP, 
http://eu17.first-oasis-conference.org/en/.
Do you want me to hop on the TC call?
Thanks,
dee

Borderless Cyber USA
http://us17.borderlesscyber.org/en/

Dee Schur
Senior Manager, Development & Advocacy
OASIS | Advancing open standards for the information society
+1.781.425.5073 x211 (Office) | +1.941.321.6733 (Cell)
http://www.oasis-open.org

-----Original Message-----
From: openc2@lists.oasis-open.org [mailto:openc2@lists.oasis-open.org] On 
Behalf Of Mr. Joe Brule
Sent: Friday, July 14, 2017 9:06 AM
To: openc2@lists.oasis-open.org
Subject: [Non-DoD Source] [openc2] OpenC2: Face to Face Tiger Team

All,

Recall that we approved a motion to stand up a tiger team (text of the motion 
at the end of this email)

In less formal terms, the TC wants to look into whether or not we should have 
face to face meetings, and if so the how, where, when ...

Request a volunteer(s) to run point in this effort and assemble a team to do 
these preliminary queries

Thank you

VR

Joe B

===== tear line =====

OASIS OPENC2 TECHNICAL COMMITTEE FACE TO FACE MEETINGS:
Resolved; The OpenC2 Technical committee will stand up a tiger team to 
investigate OpenC2 face to face meetings to include:
	i. if such meetings are warranted
	ii. and if so, recommendations on how to proceed.
The tiger team will present its initial findings to the Technical Committee on 
August 8, 2017.

Attachment: smime.p7s
Description: S/MIME cryptographic signature