Open sparrell opened 4 years ago
The implication of your second example is that the producer knows the consumer has both APs. We should consider whether the pub/sub topic structure is the right mechanism to guide the deny action to the "right" AP. For example, if we fix it for pub/sub in the topic structure that solution doesn't transfer over to HTTP(S). The optional actuator
field in the OpenC2 command would be a more general solution.
Example E.4 in WD08 addresses the first requested example: https://github.com/oasis-tcs/openc2-transf-mqtt/blob/working/transf-mqtt-v1.0.md#e4-openc2-deny-example
I will beef this up with what I mean and then create PR against csd.
Two examples:
one to a device that just has SLPF (and that can be handled with topic structure per CSD04) which will send to entire device and in this case SLPF is only AP so it's OK
one to a device that has both SLPF and SFPF (which I believe will require additions to CSD04 topic structure eg oc2/cmd/device/[device_id]/ap/slpf )