Re: Actuator Profile Roadmap - Invitation to comment

["Kemp, David P" <dpkemp@radium.ncsc.mil>]

Jason,
Thanks for the inquiry.  OpenC2 uses the word "profile" in the same sense as Bluetooth:

Profiles are definitions of possible applications and specify general behaviors that Bluetooth(r) enabled devices use to communicate with other Bluetooth devices. Profiles build on the Bluetooth standard to more clearly define what kind of data a Bluetooth module is transmitting. The device's application determines which profiles it must support, from hands-free capabilities to heart rate sensors to alerts and more.
            -- https://www.bluetooth.com/specifications/profiles-overview

OpenC2 actuator profiles are not Common Criteria Protection Profiles, but they do specify the functions supported by each actuator type, which functions are required in order to claim conformance to the profile, and which functions are optional.

Regards,
Dave Kemp

On Fri, Oct 13, 2017 at 4:13 PM -0400, "Liu, Jason J [US] (MS)" <jason.liu@ngc.com> wrote:
David and et al,
 
I just recently joined the group discussion, and realized that you have spent significant time and contributed greatly to the definition of the actuator profiles. Not knowing what have been discussed in the past, please forgive me if I ask any naive question here. I know many organizations have made similar efforts, for examples, Common Criteria Security protection profiles, NIAP protection profiles, and etc.  Will our actuator categories and profiles be aligned with those profile specifications to save time and effort? If so, the reaming work would be for us to define the functions, and determine what to be the mandatory or optional under each profile. Like said early, you may have discussed this in the past and made your decision, forgive my ignorance if so. 
 
Thanks,
Jason Liu