Re: RFC Series Editor Resignation

Michael StJohns <mstjohns@comcast.net> Tue, 02 July 2019 00:41 UTC

Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50F0120279 for <ietf@ietfa.amsl.com>; Mon, 1 Jul 2019 17:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 EnqCOZgRH3hb for <ietf@ietfa.amsl.com>; Mon, 1 Jul 2019 17:41:38 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D5621201D3 for <ietf@ietf.org>; Mon, 1 Jul 2019 17:41:38 -0700 (PDT)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id hz9MhN6LmViXOi6rZhTMqW; Tue, 02 Jul 2019 00:41:37 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1562028097; bh=KxKrVKSfcJR1QSo9wkcTrnW5Ni5rw9pwRkA6YsIBVBk=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=qSluvre42iNK2M/pNqzoo0498sRVWTMXu0/+4+rEvjvLQwBA9jlVBJmEYVsZ4Tcej HES3ME1JeyiuYpdYeWGs84H82vsTInjK7VgVEc/BXW7KyFK36btZnAiYl+TO7DqhZt UFDTSArS8Mf2Rlv/mXOuuW8rIkRvABkV6Qbwj6wBE9+hzqspNvyOAuxYwuOuGIO6+T MS+cY9mevG6/eP+bxOtoDB4nggP+BLw0PdtWr0NUzBAAO6VZ2gYbw14nzZidGs1oVy JlEtlr9XQLU/xY9p44Wpxz7LJRG7nGGWTQzRTRgekRTrkIBzdzHnSVyKUfN67+Bex1 NDNRn4bbKKMEA==
Received: from [107.17.72.138] ([107.17.72.138]) by resomta-ch2-12v.sys.comcast.net with ESMTPSA id i6rQhpv9L0aW5i6rRhevQE; Tue, 02 Jul 2019 00:41:35 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgeduvddrvdejgdefgecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefoihgthhgrvghlucfuthflohhhnhhsuceomhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtqeenucfkphepuddtjedrudejrdejvddrudefkeenucfrrghrrghmpehhvghloheplgdutdejrddujedrjedvrddufeekngdpihhnvghtpedutdejrddujedrjedvrddufeekpdhmrghilhhfrhhomhepmhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtpdhrtghpthhtohepihgvthhfsehivghtfhdrohhrghdprhgtphhtthhopehkrgguuhhksehmihhtrdgvughunecuvehluhhsthgvrhfuihiivgeptd
X-Xfinity-VMeta: sc=-100;st=legit
Subject: Re: RFC Series Editor Resignation
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: ietf@ietf.org
References: <685B34F6-E0E2-4050-B9DD-615F475F62B7@encrypted.net> <6E58094ECC8D8344914996DAD28F1CCD18D3A5CF@dggemm526-mbx.china.huawei.com> <8CDEE96C-B1DA-4991-B8AA-A2455B705B77@mnt.se> <34F6E9B8-2BC2-46AC-8AF8-EFDA552D659D@tzi.org> <EA13A490-2636-459F-919B-8A72F4F45174@cable.comcast.com> <df5a6b6c-d444-7e72-dd6c-e2fa844195fa@comcast.net> <20190628214503.GC30882@kduck.mit.edu> <7e5167bf-8167-bf81-981f-662d6da6f1ab@comcast.net> <20190628232206.GC10013@kduck.mit.edu> <e7bf71c3-7842-8699-1f56-36ffa823da99@comcast.net> <20190701223914.GK13810@kduck.mit.edu>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <bad99f11-0d66-4aba-72ef-b4b648470753@comcast.net>
Date: Mon, 01 Jul 2019 20:41:28 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <20190701223914.GK13810@kduck.mit.edu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vJlVNHey4GYkhrohfdLvDEEgJTU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2019 00:41:51 -0000

Seriously??

As someone much smarter than me once said: "When you reach the bottom of 
the hole, stop digging." While I admire persistence in trying to defend 
an untenable position, I'm at a loss to understand why this is 
acceptable behavior from the SAA?  As far as I can tell, you've tried 
your best to imply the worst possible meaning of my statement even in 
the face of multiple folk explaining the difference between calling some 
one stupid and calling a result a stupidity.

You also - again - seem to be missing the context.  The actual * quote was:

> With respect to the term "stupidity", this was the least offensive
> term I was able to come up with that had the appropriate impact in the
> above statement. This is not an "unfortunate event" or a "well meaning
> action" or even a "mistake". "Stupidity" at least leaves the question of
> malign intent open.

"this stupidity" is conjugate with "unfortunate event", "well meaning 
action" and "mistake" all items relating to the event/result.   Had I 
been able to prove malign intent, or I were trying to be offensive just 
to be offensive I would have used something more like: "this crime", 
"nefarious outcome", "underhanded result", or "dishonorable treatment".

But I'm sure we would then be discussing why I called someone a criminal.

This subject and this poster are in my kill file.  If you want me to 
read any further, again, please use your inside voice and mail me 
directly as I've now ask three times.

Later, Mike


On 7/1/2019 6:39 PM, Benjamin Kaduk wrote:
> Hi Mike,
>
> On Sat, Jun 29, 2019 at 06:23:22PM -0400, Michael StJohns wrote:
>> Hi -
>>
>> I'm going to top post because replying to this line by line isn't really
>> the best way to dispose of this part of the thread.  And as someone
> Agreed.  I will just make a few key points (and reorder slightly for my
> convenience).  FWIW, my stance on the goal of "dispos[ing] of this part of
> the thread" is not to come to agreement on the definition of "stupidity",
> since that's off-topic for this list; I will try to limit myself to trying
> to explain why, with my Sergeant-at-Arms hat, I continue to believe it is
> not appropriate.
>
>> noted, if I remained silent it might be taken as implicit approval of
>> what I consider a unsupportable take on "stupidity" as described below.
> [...]
>> To finish up - I appreciate that the Sargent at Arms has to walk a fine
>> line here, but I don't think this is even close.  Again, I'd appreciate
>> it if in the future we follow the general contract and first have
>> private conversations.   You'll  have plenty of time afterward to make
>> your explicit disapproval clear if necessary.
> In this case, we felt a public statement was necessary, precisely because
> you decided to use the word after a (presumed) careful deliberation and
> thought it was still appropriate, and used it in the same sentence as "the
> question of malign intent".  Situations and objects do not have "intent";
> individuals (and perhaps groups) do.  To speak of "stupidity" as the result
> of something with intent seems really hard to separate from the perceived
> "stupidity" of the intended action leading to that result, i.e., the action
> taken by the individual or group.  I do not think that's appropriate
> professional conduct for this forum, and am compelled to publicly dispute
> the stance that such conduct is a valid result of a careful consideration
> of how to say something.
>
>> Also I'd really appreciate it if you don't attribute a particular
>> emotion to my persistence with this set of discussions - it's yet
>> another form of demeaning behavior. You attributed "frustration", and
>> another I* attributed "upset" to me.  What I actually am is "sad" at the
>> state of affairs and "disappointed" in the various folk that caused this
>> stupidity to occur somewhat including myself.  Feel free to use either
>> of those words in future correspondence.
> My apologies.  (Perhaps I was projecting my own frustration onto you, since
> our responses to the situation seemed otherwise similar.)  I'll try to keep
> that in mind.
>
> -Ben