Regarding the ClockState the question came up when to provide a timestamp in DateAndTime:
Current date/time setting. As the current date/time changes at a high frequency, a change of this value SHALL NOT cause an update of the state version unless it has been synchronized either remotely or manually.
NOTE—DateAndTime could be filled when the clock is explicitly requested.
What's the conclusion from this clause? The DateAndTime attribute should only be added to GetMdib and GetMdState? What's the expected result from adding it to reports when the clock has been synchronized? As far as I understood, that's the idea of @LastSet. Please clarify.
In addition, this contradicts R0038. Furthermore: What do we gain from this requirement in the first place? If the state version is not incremented but an episodic update is sent anyway (I do not see an explicit link between state version and episodic update), we end up with inconsistent states: same version, different DateAndTime.
See also [#217].
Related
11073-10207 Revision: #217
Corrigendum: An SERVICE PROVIDER SHALL NOT set ClockState/@DateAndTime.
Revision: see [#217]
Related
11073-10207 Revision: #217
Last edit: Björn Andersen 2023-10-09
See https://github.com/ornet-ev/biceps/pull/64
needs further discussion with Stefan.