MRU parameters are cheap

Eric S. Raymond esr at
Thu Dec 22 11:54:59 UTC 2016

Hal, in case you are able to come up with design improvements to the
MRU mess, here are a couple of things to keep in mind.

1. The MRUlist command already does payload parsing for parameters
like maxlstint and recent.  Therefore the incremental cost of adding
new parameters to the command is low.  You may design under the
assumption that I can implement such things easily.

2. Similarly, the complexity cost of adding new tags to the generation
of MRU spans in ntpd, and then interpreting them on the client side, is
also low.  You may also design on the assumption that those features
are cheap.

The only real constraint here is backwards compatibility.  We can add
to Mode 6 at low cost, but if we break interoperability with Classic
that is a problem.
		<a href="">Eric S. Raymond</a>

Good intentions will always be pleaded for every assumption of
authority. It is hardly too strong to say that the Constitution was
made to guard the people against the dangers of good intentions. There
are men in all ages who mean to govern well, but they mean to
govern. They promise to be good masters, but they mean to be masters.
	-- Daniel Webster

More information about the devel mailing list