<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On Wed, May 01, 2019 at 02:35:58PM -0700, Harlan Stenn wrote:<br class=""><blockquote type="cite" class="">- Why do folks want to have one or more NTP server masters that have at<br class="">least 1 refclock on them in a data center, instead of having their data<br class="">center NTP server masters that only get time over the internet?<br class=""></blockquote><div class=""><br class=""></div>Answers to that include:<div class=""><ul class=""><li class="">Keeping the Auditors happy</li><li class="">Knowing that “everyone does it” - the vendor told them so</li><li class="">Bragging rights (expensive hardware)</li><li class="">Being unbothered by fighting with facilities for building penetrations and antenna mounts</li><li class="">Misunderstanding the beauty and economy Dave Mills marvelous algorithms for consistent time based on multiple sources, even those connected via internet</li><li class="">Unwillingness or inability to leverage other local resources capacity to run ntpd with minimal impact in order to have a good constellation of local NTP servers</li><li class="">Willingness to farm out time service without doing a deep dive into why and how, just leaving the design to the appliance vendors </li></ul><div class="">This covers most of what I have encountered in providing enterprise time services for $dayjob+clients. I probably left out some significant points, but it has been a few years...</div><div class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div></div></body></html>