Yo Hal! On Fri, 01 Feb 2019 15:07:41 -0800 Hal Murray via devel <[email protected]> wrote:
> Those are all interesting, but I was more interested in the
> nts foo
> vs
> server foo nts
> part of the discussion.
>
> Which one is preferable and why?
TL:DR: They are very different, the syntax should make it obviously different.
To restate what was discussed earlier this week:
*foo* in this:
server foo
Has a totally different meaning than foo here:
nts foo
Most people are not gonna spot the absolute most import thing (nts) because
it is buried later in the parameter list.
Different transport: TCP vs. UDP
Different protocol: NTS-KE vs, NTPD,
Different lifetimes: Startup vs. every poll.
Many of the common options have different meaning for NTS-KE and NTPD.
Even the text representation of addresses is different: NTS-KE wants RFC
3986. NTS-KE puts the port in the address, NTPD does not.
Most of the options for NTS-KE do not apply to NTPD.
This makes "server foo nts" harder to read, harder to code, harder
to write error messages for than "nts foo".
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
[email protected] Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpoATf1NW6un.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
