Re: RFC Series Editor Resignation

Randy Bush <randy@psg.com> Wed, 03 July 2019 02:45 UTC

Return-Path: <randy@psg.com>
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 11B601200CE for <ietf@ietfa.amsl.com>; Tue, 2 Jul 2019 19:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 ooAbl1JF8re5 for <ietf@ietfa.amsl.com>; Tue, 2 Jul 2019 19:45:17 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 4EF9E120044 for <ietf@ietf.org>; Tue, 2 Jul 2019 19:45:17 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1hiVGh-0002Gd-Bq; Wed, 03 Jul 2019 02:45:11 +0000
Date: Tue, 02 Jul 2019 19:45:10 -0700
Message-ID: <m236jnx2dl.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: Michael StJohns <mstjohns@comcast.net>, ietf@ietf.org
Subject: Re: RFC Series Editor Resignation
In-Reply-To: <34A581FE-BCFA-4FDD-A626-372E036BD79A@cooperw.in>
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> <bad99f11-0d66-4aba-72ef-b4b648470753@comcast.net> <34A581FE-BCFA-4FDD-A626-372E036BD79A@cooperw.in>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.2 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="ISO-8859-7"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9YKPvhNlwhohm_xD2t-caxGd0UI>
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: Wed, 03 Jul 2019 02:45:21 -0000

> Hi Mike,
> 
> As I mentioned to you off-list, your request below for Ben to use his inside voice is demeaning, unprofessional language that is not suitable for the IETF discussion list, per RFC 3005. Repeated use of unprofessional language may be deterring others from voicing their opinion for fear of being disrespected. It is important that everyone in the community feels comfortable enough to express their own views on the IETF discussion list if they choose to do so.
> 
> I understand that you do not intend to read further mails on the IETF discussion list regarding the RSE. I’m sending this mail so that the community understands that the IETF discussion list charter is being enforced.
> 
> Regards,
> Alissa 
> 
>> On Jul 1, 2019, at 8:41 PM, Michael StJohns <mstjohns@comcast.net> wrote:
>> 
>> 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

this is sad and embarrassing for all three concerned.  please stop and
try to get some technical work done if you are capable.

randy