Paul Vixie wrote: > On Thursday, 23 July 2020 18:34:07 UTC Evan Hunt wrote: > > > > I share the desire for perfection, but IMHO the transition from > > "master" to "primary" and "slave" to "secondary" is far enough > > under way and well enough understood at this point that I suspect > > it would be easier to add modifiers when necessary than to try to > > deploy new vocabulary entirely.
I have to agree: Primary and secondary are now used fairly consistently in software documentation. They are about as expressive and lacking in precision as the previous terms. > -1. there are zones lacking primaries, and a secondary which can also > talk to other secondaries gives a second role to those other > secondaries. we must not simply revert to the STD 13 terminology. the > role of an authority server depends on what zone we're talking about > and what other server they're talking to. that's why i've recommended > we stop talking about "primary servers" or "secondary servers", and > instead talk about "transfer initiators" and "transfer responders", > where the transfer pertains to a zone and the initiator or responder > is a server's role with respect to that zone and that transfer. The problem with this is that the initiation of a transfer and data flow are opposite which makes this all very confusing. Reading "initiator" and "responder", I have to stop and think "Wait, how did XFR work again?" Whereas primary and secondary describe the data flow in a rather natural way. If I hear these terms, I know immediately who has which role in this particular exchange. The terms may not be perfect and may not precisely describe any possible arrangement of servers one can come up with, but unless we switch to German-style descriptive terms, we’ll always fall short. And those descriptive terms tend to then turn into acronyms which is a straight road into undecipherable jargon. Side note: Whenever using "upstream" and "downstream", I’ve pretty much always first had a half-hour discussion what each means and still later ran into issues a la "What was downstream again?" Kind regards, Martin _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop