Re: On harassment at IETF
John C Klensin <john-ietf@jck.com> Sat, 30 March 2019 06:58 UTC
Return-Path: <john-ietf@jck.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 3487212017C for <ietf@ietfa.amsl.com>; Fri, 29 Mar 2019 23:58:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 t-mlF-0L1rZF for <ietf@ietfa.amsl.com>; Fri, 29 Mar 2019 23:58:51 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72C1E12017B for <ietf@ietf.org>; Fri, 29 Mar 2019 23:58:51 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hA7x2-000JlF-N3; Sat, 30 Mar 2019 02:58:48 -0400
Date: Sat, 30 Mar 2019 02:58:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
cc: ietf@ietf.org
Subject: Re: On harassment at IETF
Message-ID: <104B6F032981170C3F54394E@PSB>
In-Reply-To: <tsl4l7l13r8.fsf@suchdamage.org>
References: <91e75af7-03f9-7565-5a9f-26f5f7bc9f29@openca.org> <690B8BAA-61C9-436E-85B3-0E31739C6527@consulintel.es> <tsl4l7l13r8.fsf@suchdamage.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ua_SRpKZgH81a-PcyIw1s02R6lI>
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: Sat, 30 Mar 2019 06:58:54 -0000
Sam, Many thanks. I had been trying to figure out how best to respond to Jordi's note but you have covered everything I would have wanted to say and far better than I could have done so. --On Friday, March 29, 2019 22:43 -0400 Sam Hartman <hartmans-ietf@mit.edu> wrote: >>>>>> "JORDI" == JORDI PALET MARTINEZ >>>>>> <jordi.palet=40consulintel.es@dmarc.ietf.org> writes: > > JORDI> I don't think this is something to be handled > in private > JORDI> messages. Those cases should be > publicly exposed and point > JORDI> to specific names, so > the rest of us take our own personal > JORDI> decisions on > those folks in addition to IETF actions. > Please follow your own antiharassment procedure. As Dave > Crocker pointed out during the development of the BCP in > question, there are some (non-addressed) problems with it. > Still, it's far better than what you propose above. > > Victims of harassment often don't want their experience > dragged through the consensus judgment process of the IETF. > Theey don't want the details of a difficult and painful > experience exposed and debated on a public list. Theyalmost > certainly don't want to face the inevitable victim blaiming > and debating of whether they or the harasser are more > reasonable. They don't want to watch the debate about whether > the harasser is so valuable to the organization that their > behavior *has to be* accepted. > > And speaking from personal experience as a victim, some of the > time you don't even want to see people dragged through the > mud. Some of the time people do improve and understand why > what they are doing is problematic. Or some of the time they > are your friends and you just don't want to be the one who > causes that mess to land on them. And yes, you have to > evaluate your silence against the potential that someone else > will get hurt, and yes that tradeoff sucks. But people make it > every day. > And denying them that option is both inconsistent with your > policies and with approaching the realities of > harassment/bullying with compassion. > > I'd say that the last time I was tracking the IETF closely, it > was behind the curve in approaching some of these issues. > Doubtless things are better now, but it seems inevitable that > to some degree or another the sorts of problems I raise will > absolutely come up if details become public. > Absolutely if victims want to come forward and tell their > story, they should be able to do so. > Demanding or expecting that lacks compassion. > > I may sound a bit worked up here. Debian has been facing > similar issues where some names did come forward (at least in > private) earlier this year. Everything you can imagine > happened. > > Or for another data point take a look at > https://crystalhuff.com/2018/10/25/why-im-not-at-arisia-anymor > e-my-rapist-is-president-again/ a frank and well written > discussion of what happened to one victim who came forward and > discussed her rape at the hands of one of the officers of a > local science fiction convention. > > Thanks for your consideration,- > > --Sam
- On harassment at IETF Dr. Pala
- Re: On harassment at IETF Brian E Carpenter
- Re: On harassment at IETF Ross Finlayson
- Re: On harassment at IETF JORDI PALET MARTINEZ
- Re: On harassment at IETF Sam Hartman
- Re: On harassment at IETF John C Klensin
- Re: On harassment at IETF Alissa Cooper
- Re: On harassment at IETF JORDI PALET MARTINEZ
- Re: On harassment at IETF Dr. Pala
- Re: On harassment at IETF Dr. Pala
- Re: On harassment at IETF Kyle Rose
- Re: On harassment at IETF Theodore Ts'o
- Re: On harassment at IETF Carsten Bormann
- RE: On harassment at IETF Adrian Farrel
- Re: On harassment at IETF S Moonesamy
- Re: On harassment at IETF Phillip Hallam-Baker