Re:Roughtime: a protocol for secure, auditable time synchron...
by pcl on Tuesday September 20, 2016 @04:45PM
(#12543234)
At scale, a time server's DNS address will likely either be a reverse proxy or a multi-valued A record. The coordination amongst those separate physical servers that are serving requests for the same DNS name would become a scale challenge if they needed to share state.
[ Parent
| on HN ]
Re:Roughtime: a protocol for secure, auditable time synchron...
by amluto on Wednesday September 21, 2016 @07:36PM
(#12553217)
But they wouldn't need to share state. They could run independently, and any client that wanted to tie their clocks together could request the signed time from one and then send it to the other, causing it to get logged in the other server's chain.