Re: [DNSOP] List conduct
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Fri, 22 April 2022 12:30 UTC
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 61D473A106F
for <dnsop@ietfa.amsl.com>; Fri, 22 Apr 2022 05:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5,
RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001,
SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01]
autolearn=ham autolearn_force=no
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 K0W3cVG_j_jx for <dnsop@ietfa.amsl.com>;
Fri, 22 Apr 2022 05:30:32 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp
[131.112.32.132])
by ietfa.amsl.com (Postfix) with SMTP id BA1C83A0FFD
for <dnsop@ietf.org>; Fri, 22 Apr 2022 05:30:29 -0700 (PDT)
Received: (qmail 16587 invoked from network); 22 Apr 2022 12:26:02 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132)
by necom830.hpcl.titech.ac.jp with SMTP; 22 Apr 2022 12:26:02 -0000
Message-ID: <c1558d94-38a1-c663-d1fe-d397b16d5c86@necom830.hpcl.titech.ac.jp>
Date: Fri, 22 Apr 2022 21:30:22 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.8.1
Content-Language: en-US
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop@ietf.org
References: <6818F50A-AF06-4EA5-AD47-2F8BC3CD2A31@pir.org>
<d4e5a968-b41e-d5b3-6576-32d52d93b345@necom830.hpcl.titech.ac.jp>
<4bef1c62-d18d-7379-d627-aa0d3ec6b30d@redbarn.org>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4bef1c62-d18d-7379-d627-aa0d3ec6b30d@redbarn.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lz3ee5UrdTdSAIpAk8Sin99j8rA>
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: Fri, 22 Apr 2022 12:30:35 -0000
Paul Vixie wrote: >> 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. Code itself? Then, you should discuss it not here but other appropriate places. > the above > snippets in which ipv6 and lisp are designated "garbage protocols" > have a productivity error in that neither is actionable. Action by IETF becomes possible only after some IETF consensus is reached, which is obviously impossible for poor IPv6 and LISP, because there are certain amount of people disparately acting for them. But, it does not mean arguments against IPv6, LISP and DNSSEC are prohibited in the main and other mailing lists as if they were "unprofessional". > 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. Which position? It should be noted that "freedom of speech" of people without any position always assumes > to use > community resources and to take time and attention from other > participants So? Or, are you saying chairs are abusing their position? > we should make the best case we can for the positions we hope the WG > will adopt, As we, including chairs, are talking about "the IETF Code of Conduct". you MUST make the best case not for this WG but for the entire Internet. > and answer any questions or misunderstandings of those > positions during any subsequent debate. I'm fine to continue such debate. > for example, here is my > statement on the quality and utility of DNSSEC, along with others': Let me respond for or against it later in a separate mail. Masataka Ohta
- [DNSOP] List conduct (was: Re: DNSSEC as a Best C… Suzanne Woolf
- Re: [DNSOP] List conduct (was: Re: DNSSEC as a Be… Masataka Ohta
- Re: [DNSOP] List conduct Paul Vixie
- Re: [DNSOP] List conduct Masataka Ohta
- Re: [DNSOP] List conduct (was: Re: DNSSEC as a Be… Warren Kumari
- Re: [DNSOP] List conduct Paul Vixie
- Re: [DNSOP] List conduct Masataka Ohta
- Re: [DNSOP] List conduct (was: Re: DNSSEC as a Be… Masataka Ohta