Yo Achim! On Thu, 17 Jan 2019 20:50:46 +0100 Achim Gratz via devel <devel@ntpsec.org> wrote:
> > Does this diagram look correct?
>
> No. What the heck is an NTS client supposed to be?
A client that connects on the NTS-KE port to a NTS-KE server.
> The description
> in the file suggests it is the NTS-KE described in the RFC, so it
> clearly belongs to the server infrastructure (in fact it's the root
> of trust).
No, it is the end user client.
> There is no separation of NTS and NTP server either, an NTS server is
> supposed to answer plain NTP clients with the old style NTP packets.
Uh, no. Different port numbers.
> Yes, if you shard the service among different physical boxes that are
> supposed to have the same root of trust.
Where did sharding come from? How would you see that? Is that more
specific that just random pooling/load balancing?
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpMUrdhHuSoL.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
