Fix Version/s: None
During my analysis to characterize the latency of the Summit EFD, I noticed that MTM2 topics have the private_sndStamp in UTC instead of TAI.
At this moment we are running SAL version 4.0 at the Summit.
This also relates to
DM-23496, we want to use the private_sndStamp as the InfluxDB timestamp, so it would be nice to have all values in TAI.
This issue was original entered by Angelo Fausti in TSS-3463
Not an issue in M2 anymore because the M2 Python CSC based on ts_salobj is applied already.