[Ntp] Antw: [EXT] NTPv5 modular architecture

[Ulrich Windl <[e-mail]>]

Hi!

A few random notes on the block diagram:

* the "config" arrows to management should be bidirectional IMHO, unless the management keeps the complete config (so that it is readable)

* shouldn't there be an arrow between protocol engine and timing engine?

* I feel unsure about hw timestamps being derived from the system clock; wouldn't that be software time stamps then?

* Doesn't the timing engine have to read the system clock as well?

* I'm missing to "external" arrows: That to the network for both, management and network stack. So to say: Will there be another network stack for management, or will it be the same?


On protocol engine:

* I'd delete "for transmission", as it's more the task of the network stack, I guess

* "building packets (to send)" and "determines when to send packets" is basically the same for me, assuming a packet is sent as soon as possible after being handed to the network stack

* Does the timing engine really care about messages not received? IMHO it's part of the protocol engine. Likewise security and message status. In my view the timing engine is fed with timing information only, and maybe it has to handle the fact when it does not receive any.

On timing engine:

* Does the timing engine really select the servers? Isn't that the protocol engine (with information from the timing engine)?

* I'd replace "report statistics to management interface" with "provides performance numbers for protocol engine and management interface"

Regards,
Ulrich

>>> Doug Arnold <[e-mail]> schrieb am 22.07.2020 um 16:48 in
Nachricht
<[e-mail]>

> Here is a slightly expanded version of the modular architecture concept for 
> NTPv5.  Feedback welcome.
> 
> Doug