Closed mmccool closed 6 years ago
Elena: problem here with a generic tag. OCF is more specific than ACE, so we should use a more specific tag than ACE. McCool: also note that OCF scheme can be used with HTTP or CoAP.
RESOLVED: will use "ocf" specific metadata tag for OCF devices to identify the use of the OCF security scheme.
RESOLVED: use "ocf" for OCF security scheme.
OCF is built on top of CoAP and follows ACE/COSE recommendations so it's unclear whether or not the OCF security model should have its own scheme tag. The other option here would be have a set of options available for CoAP security that are rich enough to describe the OCF security model. We probably want that anyway for non-OCF CoAP systems, so then this tag becomes a convenience for OCF. However, in that case, we should also add "convenience" tags for other CoAP-based standards (LWM2M, OMA, etc).