see below inline.
Masataka Ohta wrote on 2022-04-21 05:59:
Suzanne Woolf wrote:
...
That's simply wrong.
As I, to confirm the freedom speech in IETF, explicitly confirmed
destructive harsh criticisms are not "unprofessional" (w.r.t.
the code) in
https://mailarchive.ietf.org/arch/msg/ietf/lBs5-1u3asjocT56PoQEdnv1m2g/
without resulting in SAAs' actions. There was no one who
argued against me that the statement were "unprofessional".
There was no one who argued against me that the statement
were "inappropriate" nor "impolite", which means such
destructive statements as
IPv6 with unnecessarily lengthy 16B addresses without
valid technical reasoning only to make network
operations prohibitively painful is a garbage protocol.
and
LISP, which perform ID to locator mapping, which is
best performed by DNS, in a lot less scalable way than
DNS is a garbage protocol.
is protected by "the freedom of speech" and is not "unprofessional"
and is fully acceptable.
i think the code of conduct may be inadequately worded. the above
snippets in which ipv6 and lisp are designated "garbage protocols" have
a productivity error in that neither is actionable. to use community
resources and to take time and attention from other participants for no
reason other than to publish invective is an abuse of position. even if
i previously agreed with those statements or was persuaded to agree by
those statements, there remains nothing i can do about that agreement.
if i disagree then there is also nothing i can do.
we should make the best case we can for the positions we hope the WG
will adopt, and answer any questions or misunderstandings of those
positions during any subsequent debate. for example, here is my
statement on the quality and utility of DNSSEC, along with others':
https://dnssec.net/why-deploy-dnssec
i raise this example because it's possible to criticize actionably. an
oft-repeated criticism that paves no roads is a waste of everyone's time
and is disrespectful on that basis.
my advice is to make your case and then make peace with the result.
--
P Vixie
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
