Re: [DNSOP] List conduct

Paul Vixie <paul@redbarn.org> Thu, 21 April 2022 14:16 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 995ED3A12AD for <dnsop@ietfa.amsl.com>; Thu, 21 Apr 2022 07:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redbarn.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d7yX4Jeag0kd for <dnsop@ietfa.amsl.com>; Thu, 21 Apr 2022 07:16:46 -0700 (PDT)
Received: from util.redbarn.org (util.redbarn.org [IPv6:2001:559:8000:cd::222]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1532B3A12EE for <dnsop@ietf.org>; Thu, 21 Apr 2022 07:16:43 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by util.redbarn.org (Postfix) with ESMTPS id 33A281A2423; Thu, 21 Apr 2022 14:16:42 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=redbarn.org; s=util; t=1650550602; bh=3rUpl0UndEXMlOCPvfWfL7xBPxYpAQlKwidW/4jPPY8=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=PwsF8mASIKm4sVJNslcFAhQySSC1btu9urqpgbrt2oKz7xQiiYgpR9RFbuaf8fGTy M96H3baJrXc4p42OhcIE6/UkvB3xaXD8thF3tQ+uelO+9G1J/nJ3RnmoGUH75Px/jp N87XXszN6I4CvE5yGuF3rGc+dyIAL2MucJL9PeE8=
Received: from [24.104.150.149] (dhcp-149.access.rits.tisf.net [24.104.150.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 159287597E; Thu, 21 Apr 2022 14:16:42 +0000 (UTC)
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: dnsop@ietf.org
References: <6818F50A-AF06-4EA5-AD47-2F8BC3CD2A31@pir.org> <d4e5a968-b41e-d5b3-6576-32d52d93b345@necom830.hpcl.titech.ac.jp>
From: Paul Vixie <paul@redbarn.org>
Message-ID: <4bef1c62-d18d-7379-d627-aa0d3ec6b30d@redbarn.org>
Date: Thu, 21 Apr 2022 07:16:42 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/7.0.56
MIME-Version: 1.0
In-Reply-To: <d4e5a968-b41e-d5b3-6576-32d52d93b345@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wDc4FCPHgtbWjdEsNKbHr7LxOzM>
Subject: Re: [DNSOP] List conduct
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2022 14:16:51 -0000

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