Another out of band comment I received
From: Brule, Joseph M
Sent: Thursday, April 5, 2018 8:41 AM
My original thought was ‘applicable to’ is a superset of ‘required and optional’ and the first set of bullets were ‘purpose’ and the other bullets were ‘scope’.
However in the interest of being concise, your comments sound logical to me. I will go on the googledoc and try to capture your points. Make it a point to go to the googledoc and make sure that I captured your concerns accurately.
Misc note; I am NOT looking the proverbial gift horse in the mouth, but in a perfect world, it would be good ot have you modify the googledoc. Avoids anything
being lost in the translation….
Thank you
VR
Joe B
Sent: Tuesday, April 3, 2018 1:35 PM
To: Brule, Joseph M <jmbrule@radium.ncsc.mil>
Subject: [Non-DoD Source] Re: [openc2-actuator] Firewall Profile: Purpose and Scope
* Identify the OpenC2 ACTIONS that are applicable to the actuators with firewall functionality.
* Identify the TARGET types and associated specifiers that are applicable to each action in the firewall class of actuators.
Instead of "applicable" I think we should say "required or optional". I could see different targets being optional for some actions and required for other actions.
* Identify ACTUATOR SPECIFIERS, ACTUATOR-OPTIONS and COMMAND OPTIONS for each action-target pair that are applicable and/or unique to the firewall
class of actuators
Instead of "applicable and/or unique" I think we should say "required or optional".
* Annotate each Action/ Target pair with a justification and example and provide sample OpenC2 commands to a firewall
* Provide an abstract schema that captures the specifiers and options for a firewall
* Does not define or implement ACTIONS external to Version 1.0 of the Language Specification.
* Is conformant with version 1.0 of the OpenC2 Language Specification
I think the 7 above are all we need and the 3 below are a bit redundant. I tried to fold the "required and optional" bits into the 7 above so we don't need the 3 below.
* Defines the required and optional ACTIONS and OPTIONS.
* Defines the applicable TARGETS utilizing the target data model provided in version 1.0 of the OpenC2 Language this specification..
* Defines the required and optional actuator 'specifiers'.
On Tue, Apr 3, 2018 at 6:03 AM, Brule, Joseph M <jmbrule@radium.ncsc.mil> wrote:
Actuator Profile Subcommittee,
This probably should have been the first email I sent....
We will spend a lot of time talking past each other if we do not have a common understanding of the purpose and scope. Please review the following ten bullets. If you do not agree, please identify which one(s), why, and ideally provide alternate text.
* Identify the OpenC2 ACTIONS that are applicable to the actuators with firewall functionality.
* Identify the TARGET types and associated specifiers that are applicable to each action in the firewall class of actuators.
* Identify ACTUATOR SPECIFIERS, ACTUATOR-OPTIONS and COMMAND OPTIONS for each action-target pair that are applicable and/or unique to the firewall class of actuators
* Annotate each Action/ Target pair with a justification and example and provide sample OpenC2 commands to a firewall
* Provide an abstract schema that captures the specifiers and options for a firewall
* Does not define or implement ACTIONS external to Version 1.0 of the Language Specification.
* Is conformant with version 1.0 of the OpenC2 Language Specification
* Defines the required and optional ACTIONS and OPTIONS.
* Defines the applicable TARGETS utilizing the target data model provided in version 1.0 of the OpenC2 Language this specification..
* Defines the required and optional actuator 'specifiers'.
Thank you
Joe B
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php