> On Jan 27, 2015, at 9:03 PM, Steve Allen <s...@ucolick.org> wrote: > > On Tue 2015-01-27T22:47:48 -0500, Tim Shepard hath writ: >> Why does such a system need to know what time it is UTC? > > For some devices I would expect it is because of statutory or > regulatory requirements which require that it should do so. > > Not everyone feels able to take the course of GPS, Galileo, IEEE 1588, > BeiDou, and IRNSS and 'Just Say No' to UTC.
In our case, it was contractual language that was non-negotiable. There was one time, and it was UTC and that’s what was externally visible, end of discussion. They didn’t care if this made some other contractual requirements hard: time was UTC and that’s that. Warner _______________________________________________ LEAPSECS mailing list LEAPSECS@leapsecond.com https://pairlist6.pair.net/mailman/listinfo/leapsecs
