This is interesting work, but doesn’t OpenNTPD’s constraints feature provide the same benefits (protection against MITM and NTP servers going rogue) while being much simpler and without requiring dedicated servers?
Using TLS to bootstrap the clock to bootstrap TLS cert checking… A bit circular. :) It works, but it has some weak spots.
For comparison, ntpd still has the design of using a trusted server. It doesn’t really try building consensus. And if your ntp packets go out of whack, you can’t be sure if it’s a rogue server or mitm. It looks like rough time could be used for even narrower constraints.