On Tue, Apr 11, 2023 at 6:57 PM, Paul Hoffman <paul.hoff...@icann.org>
wrote:

> On Apr 11, 2023, at 3:06 PM, Paul Wouters <p...@nohats.ca> wrote:
>
> No one proposed to retire the term?
>
> Not yet, I believe.
>
> If unclear and additionally inappropriate from an inclusive language point
> of view, why not document the term as is, with a note explaining it is
> incomplete (without trying to fix it) and calling the term historic?
>
> The term is not "historic" in the sense that it is still in active use,
> albeit with somewhat different definitions depending on the speaker or
> reader.
>


Yup, lame delegation and lame server are still in very common use — and
(IMO) it's usually clear from context what is being communicated. If I'm
trying to troubleshoot an issue and say:
"Huh! ns2.example.net is lame for example.com", the person I'm talking to
is likely to grok what I'm saying (and if they don't, they'll ask for
clarification!).

Paul: I think that your addition is a fine one. Also, thank you for dealing
with all this terminology faff; it's a somewhat thankless, but important
document (and if I tried to write RFC8499 most of it would end up like:
"Label: You know, the bits between the dots. Like, um, thingie.example.com -
these are all labels. Oh, and probably LDH.. you know, labels…").

“When I use a word,” Humpty Dumpty said, in rather a scornful tone, “it
means just what I choose it to mean—neither more nor less.” “The question
is,” said Alice, “whether you can make words mean so many different
things.” “The question is,” said Humpty Dumpty, “which is to be
master—that’s all.”
 — Lewis Carrol (AKA, Charles L. Dodgson, which is nicely ironic in this
case :-))

W


Ecouraging people to not use it is fine, but maybe out of place for a
> terminology document. If you disagree, please propose the wording you would
> like to see in the document.
>
> --Paul Hoffman
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to