On Thu 2018-07-19T04:14:12+0100 Stephen Colebourne hath writ: > "In addition, there is no standard method for applying this frequency > adjustment, so that different implementations may disagree among > themselves in addition to the time error with respect to UTC."
That quote is not from Microsoft, but rather from the ION paper by Matsakis, Levine, and Lombardi That can be got by ION members, or from USNO if their webserver recovers, or from researchgate if you can tolerate the javascript that will try to execute https://www.researchgate.net/publication/323600621_Metrological_and_legal_traceability_of_time_signals Microsoft seems to be documenting a new mode of OS configuration which actually does count the second named "60", and specifically in order that Microsoft systems can say they conform to MiFID II and other regulatory agencies that demand conformance with UTC as defined. Otherwise the old default configuration will have a second that lasts 2000 millis. -- Steve Allen <s...@ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m _______________________________________________ LEAPSECS mailing list LEAPSECS@leapsecond.com https://pairlist6.pair.net/mailman/listinfo/leapsecs