(7.2.4.6.7 Status)

In JSON, the Status message contains a mandatory Timestamp when isCyclic=true. In UADP, there is no Timestamp field in this message (and the Timestamp is disabled at the NetworkMessage level).

It seems to me that it would be better to have the Timestamp for isCyclic=true in UADP as well. This is what I am doing: On the subscriber side, I am not looking at just the NextReportTime - because the publisher and subscriber clocks might be out of sync. I prefer to look at the difference of NextReportTime minus Timestamp, which basically tells me how often the publisher intends to report the status, and then add this difference (plus some extra) to my current time, for deciding when to expect the next update from the publisher. I though that that was the reason for having the Timestamp with isCyclic=true in the first place anyway.