[LEAPSECS] Windows Server 2019

[Steven Sommars]

Some direct links for the Matsakis, et al paper.
USNO:
https://tycho.usno.navy.mil/papers/ts-2018/Traceability-of-Time-Signals.pdf
NIST: https://tf.nist.gov/general/pdf/2941.pdf



On Wed, Jul 18, 2018 at 11:27 PM, Steve Allen <sla at ucolick.org> wrote:

> 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                    <sla at 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 at leapsecond.com
> https://pairlist6.pair.net/mailman/listinfo/leapsecs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist6.pair.net/pipermail/leapsecs/attachments/20180719/8fe66cfd/attachment-0001.html>