Discussion: More than one timeSyncBeacon for Loss_of_Synchronization and same beaconRequester
Should the CSE reject or allow multiple timeSyncBeacon resources with beaconCriteria set to Loss_of_Synchronization and the same requester ID in beaconRequester?
The timeSyncBeacon can be configured in two different ways via the beaconCriteria attribute:
- Loss_of_Synchronization (together with the beaconRequester and beaconThreshold attributes)
- Periodic (together with the beaconInterval attribute)
While it might make sense to have have more than one "Periodic" timesyncBeacon configured (does it really?), for "Loss_of_Synchronization" it doesn't make sense to have more than one such configurations for a beaconRequester. Only the shortest threshold will be the relevant one.