IETF Logo Mail Archive

Re: RFC Series Editor Resignation

"Theodore Ts'o" <tytso@mit.edu> Fri, 28 June 2019 21:55 UTC

Return-Path: <tytso@mit.edu>
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 7168E1201A8 for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2019 14:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 kucI6MGV803b for <ietf@ietfa.amsl.com>; Fri, 28 Jun 2019 14:55:56 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 B9460120105 for <ietf@ietf.org>; Fri, 28 Jun 2019 14:55:56 -0700 (PDT)
Received: from callcc.thunk.org (guestnat-104-133-0-109.corp.google.com [104.133.0.109] (may be forged)) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x5SLtrHa003080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 28 Jun 2019 17:55:54 -0400
Received: by callcc.thunk.org (Postfix, from userid 15806) id F338E42002E; Fri, 28 Jun 2019 17:55:52 -0400 (EDT)
Date: Fri, 28 Jun 2019 17:55:52 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: Michael StJohns <mstjohns@comcast.net>, ietf@ietf.org
Subject: Re: RFC Series Editor Resignation
Message-ID: <20190628215552.GB19489@mit.edu>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20190628214503.GC30882@kduck.mit.edu>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tnhkBPuiyjSs2Zvx4Bs9nfwYehY>
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: Fri, 28 Jun 2019 21:55:58 -0000

On Fri, Jun 28, 2019 at 04:45:04PM -0500, Benjamin Kaduk wrote:
> > * 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.    Feel free to come up with your own terms.
> 
> I appreciate that you have put thought into your phrasing.  However, this
> term nonetheless fails to meet the bar for professional conduct required
> by RFC 3005.  We must treat each other with courtesy, even when we find
> events to be disconcerting.  Making observations about the situation is
> reasonable; attacking community members is out of bounds.

Ben,

I interpreted Mike's statement as saying the *decision* was stupid,
and not that an individual had a low IQ.  "This stupidity" doesn't
appear to be an attack on an individual.

Do you disagree?

					- Ted

v2.23.0 | Report a Bug | By Email