Action: Please provide comments NLT Monday July 9 on the SLPF

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

All,

 

I realized that I left a key item out of my last email:  Can you provide comments NLT Monday (and earlier would be better). I need to get the document into a format appropriate for a ballot that will take place on July 11. 

 

VR

 

Joe Brule

 

_____________________________________________
From: Brule, Joseph M
Sent: Friday, June 29, 2018 4:31 PM
To: openc2-actuator@lists.oasis-open.org
Subject: SLPF edits

 

 

All,

 

I have been looking at the SLPF firewall profile too long and having trouble catching inconsistencies/ issues.  Request violence with your red pens and I will take another look at it Monday,  https://docs.google.com/document/d/1_kMVkkNjtwNjRPN4MeLfQF8Envp_O_TrhII45vNkb-Y/edit

 

Here is a quick data dump on some of the mods that I have made since Wednesday: 

• I suggest the naming conventions of the tables and figures to be along the lines of:  Sections-integer.  For example, if you have two tables in section 2.1.1, then number then as Table 2.1.1-1 and Table 2.1.1-2 rather than simply a sequence number.  My logic or lack thereof was that it's easier for the reader to find it if the table is referenced later in the document
• Based on the discussion in Wednesday teleconference, we will remove the 'rule-number' command option
• Based on the discussion in Wednesday teleconference, we will remove the definition of the specifiers for the openc2 target type
• IN the context of network function virtualization, Refer to table 2.1.4-1.  Need to pick one (not both) of the two last rows.

Based on the discussion at the actuator profile SC meeting, the single identifier was preferred. For purposes of OpenC2, the need is to uniquely identify the actuator to the required level of precision, hence actuator (or system integrator) should map it accordingly.

The other perspective is that cloud instances are too varied therefore must a have accommodate a list of undefined elements.

 

• Did a global replace of 'slpf-query' with 'slpf:access_rules'.  When I originally cooked up the notion of the slpf-query target type, had no idea what sort of things we would need to query for.  As it turns out, the only thing one would ask of the firewall is its block and allow list so the name change seems more precise. 
• Based on Wednesday teleconference, put 'update file' back in.
• Removed all references to the command-id argument.
• Took a stab at the conformance section.  I was trying to avoid too much duplication of material but trying to be complete.  That was a difficult balance and doubt I achieved. 

 

I have done NOTHING on the example commands yet.  ON my to do list for Monday.  Also the JADN schema is still tbs

 

Thank you

 

VR

 

Joe B