RE: [openc2] Action/Target Pairings

[<duncan@sfractal.com>]

The LS is necessary but not sufficient to define compliance.

We will need to define compliance in context of what is being called compliant - eg an actuator interface.

You then test compliance with an actuator profile which defines the subset of the language that actuator must implement. Similarly, it you are testing the orchestrator interface to a particular actuator, it also use the actuator profile.

However there are still some obvious non-compliant tests that could be done even without the actuator profile since all the actions and all the targets are in the LS. Ie you can define non-compliance with just the LS. For example is you used 'block' (not in openc2) instead of 'deny' (the proper openc2 action) than it's clear you are non-compliant.

Once we get into defining compliance, and if there is concern on 'looking at two documents', maybe that will cause us to change the structure (eg maybe the current language spec and the profiles become 'parts' of one doc like Stix did it). But compliance and one/two docs are separate issues from action/target pairings (ie we already had actuator profiles).

Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

-------- Original Message --------
Subject: [openc2] Re: [EXT] [openc2] Action/Target Pairings
From: Bret Jordan <Bret_Jordan@symantec.com>
Date: Wed, September 06, 2017 11:20 am
To: "duncan@sfractal.com" <duncan@sfractal.com>, TC OpenC2
<openc2@lists.oasis-open.org>

I understand the rational for this, however, I still have concerns about what it means to be "compliant" with the Language Specification.  An organization or vendors that wants to claim conformance to the Language Specification, what does that mean?

Bret

---

From: openc2@lists.oasis-open.org <openc2@lists.oasis-open.org> on behalf of duncan@sfractal.com <duncan@sfractal.com>
Sent: Monday, September 4, 2017 2:50:42 PM
To: TC OpenC2
Subject: [EXT] [openc2] Action/Target Pairings

 

An issue was discussed and resolved over the last two Language
Subcommittee meetings and this note documents the resolution for the
benefit of everyone who was not able to attend. Since it impacts
actuator-profiles as well, this note is being sent to the entire TC.
Obviously if anyone has any issue with the resolution, please let us
know.

Prior to this discussion, the language specification contained many
'action/target pairings' eg action="" target=file. The wording could
be considered ambiguous with respect to whether those pairing were
normative in that only those pairings were allowed. Some (including one
of the author/editors) read it as the LS would contain the complete
list; and some (including a different editor) read the pairings as
informative examples but that other pairings would be legal.

The Language Subcommittee discussed over two meetings and agreed to the
following:
- the language specification would NOT contain the complete list of
action/target pairings
- any action with any target is possible from the language specification
document view
- each actuator profiles will list the mandatory and optional pairings
for that actuator
- the language specification will contain many examples, all of which
eventually be legal in some actuator profile
- the exhaustive list currently in the language spec (in the many
property tables) will be removed from the language spec, but will be
retained for use by the subcommittee

Those who attended, please validate I captured the points correctly.
Everyone - let us know if you disagree with any of the points.


Duncan Sparrell
sFractal Consulting LLC
iPhone, iTypo, iApologize

---------------------------------------------------------------------
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://clicktime.symantec.com/a/1/xHRvjUJ2HBVDaAD_OAo_ZbJpCMxCA--rqULbrBlURo0=?d=pPoVRlxl4Z4v_55R8dWjBKutGC1wJ6dtvuWvqV3BOdePMw8KXyrjm4jBYp0YN_sER6Ve8xVSBnz17uVpmDjs95XeuYqzBXpZGJX0Xe-zaYCE5WLMxUi04rTZlNpbt_CZ-m8MsKM58MQAF5e016jB142GYTh1PSVmJD4a8sp5bInDo8Xe2c8DOH4ZeDXgTWfQvTM1NOuCiu4ag0_9MSkixzEIPGT_6aUF7xYNoic6kxV99Vii7wOmEBXZ5oEME07ettqbzIYYRZnCn8lTG4fEwENVpe9bfUsob5Dg01xwIe7U65UfYgUXh3cDxgWjC2cuG3yxrdxuoVfsyF3I8NHQu-E3XBYcun4DCQ0xFPa58NtjUdzwZtITjuUU1RL7WirXw9xLEJ9Qk5ZwZzyP2xmRK4SCr3oTyLxFdMDb5ZN1wR3WWnBpss_3UqUNYQ_frU5GitVK1Q5aYBpWLgq1JhC7y4q5sfkfyJU%3D&u=https%3A%2F%2Fwww.oasis-open.org%2Fapps%2Forg%2Fworkgroup%2Fportal%2Fmy_workgroups.php