Does the "source clock of that timestamp" mean the current clock in the mds or the clock when the timestamp was recorded? This is the same thing, otherwise the timestamp is simply not correct and the MDIB is in an inconsistent state - given some tolerances of course, since no clock is perfect. From the point of view of the ClockService, it would be the current clock though. A SequenceId and InstanceId may be insufficient to identify which epoch a time stamp belongs to. A SequenceId, InstanceId and...
Or can we not rely on http transport features in case it turns into protobuf in the future, or for some disconnect between the consumer's service stack and processing? Yes. If you propose transport changes to enable additional behavior such as this, BICEPS is not the right place. HTTP is not even a known concept here, for all intents and purposes, this could be done via carrier pigeon. I personally also do not think it is a great idea for a consumer, which is unable to process notifications in a...
Detect consumer processing delay in provider
Detect consumer processing delay in provider
ClockService
Detect consumer processing delay in provider
Remove implied value for B.282
SafetyClassification responsibility