All,
Here is the 'state of affairs' as I understand it.
The current SLPF has two conformance profiles with two conformance targets each summarized as:
BASIC profile
- Basic Producer supports the deny (or allow) ip_connection AND ip_addr
- Basic consumer supports the deny (or allow) ip_connection OR ip_addr
COMPLETE profile
- Complete Producer supports the optional 'delete rule number', 'update file' and the five optional arguments (temporal, running, direction, insert_rule and drop_process) in addition to the basic
- Complete Consumer supports the optional 'delete rule number', 'update file' and the five optional arguments (temporal, running, direction, insert_rule and drop_process) in addition to deny (or allow) ip_connection AND ip_addr
Here is the guidance I got wrt to how the conformance section is to be written:
- Write a 'IP Connection SLPF' conformance profile (with corresponding consumer and producer conformance targets)
- Write a 'IP Address SLPF' conformance profile (with corresponding consumer and producer conformance targets)
- Write a 'File SLPF' conformance profile (with corresponding consumer and producer conformance targets)
Here is the guidance that I have not received, but shall I assume we need to write the following profiles?
- Write a 'delete rule number' conformance profile (with corresponding consumer and producer conformance targets) for SLPFs that support delete rule number command
- Write a 'running' conformance profile (with corresponding consumer and producer conformance targets) for SLPFs that support the running vs persistent argument
- Write a 'direction' conformance profile (with corresponding consumer and producer conformance targets) for SLPFs that support the direction argument
- Write a 'drop_process-2' profile (with corresponding consumer and producer conformance targets) for SLPFs that support two of the three possible values the drop_process argument can take
- Write a 'drop_process-3' profile (with corresponding consumer and producer conformance targets) for SLPFs that support all three of the possible values the drop_process argument can take
- Write a 'time' profile. Most SLPFs will execute the command upon receipt, but a separate profile for the SLPFs that can support start time, stop time and/or duration arguments
Also, can I assume that you only want nine profiles and I don’t have to consider combinations?
Is this what we really want to do in the conformance section?
I will write the pull request to accommodate this change but I do not consider it to be an improvement. To me, it made more sense to push the complexity to the orchestrator and have some confidence that the system will still interoperate.
VR
Joe Brule
Engineering (Y2D122)
FNX-3, B4A335
410.854.4045
'Adnius ad retinedam puritem noster peciosus corporalis fluidorum…'