Re: On harassment at IETF

Alissa Cooper <alissa@cooperw.in> Sat, 30 March 2019 07:24 UTC

Return-Path: <alissa@cooperw.in>
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 26DFE12017B for <ietf@ietfa.amsl.com>; Sat, 30 Mar 2019 00:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=sgf+5cPZ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=6LAoXw9C
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 zHuFI6c-1oTN for <ietf@ietfa.amsl.com>; Sat, 30 Mar 2019 00:24:19 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09DF312015D for <ietf@ietf.org>; Sat, 30 Mar 2019 00:24:18 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id A08FE620A; Sat, 30 Mar 2019 03:24:17 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Sat, 30 Mar 2019 03:24:17 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=Z 2rFwk1qg3FPwyiYoEX/lnF9wn6nA2l+6PdL2YYH6WQ=; b=sgf+5cPZrCYfdS872 7yvdYNPaBnEVJr4vYbceA1FMcmOg5mdC2/1YwozQg2qNPivk/i7+iTOuMW8R8j/d nv1CFnEwTHqpNO+e4yPFruJsoN8LIMcWUhlhh9gc7DbvP3zdlEnT9Ahdr8LfEehQ yY/Ubw5k9xhs0f42O/b1y7uGH6qIhMhzz2NDi7joaH8ZE5TNfhIxdbYON5RwY5ME f7RDchLkFuFsJsY6CwEJc8rivgztFmW5H0kYjVcu7DR52Y1lRY/0svyG9VKeAmkp wxlLttM7Im6BcjC/fR+CVqNVm1lEkHA0gI9JMdxM1MCBaKgeVUDFZka1izow3otl i9C9w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=Z2rFwk1qg3FPwyiYoEX/lnF9wn6nA2l+6PdL2YYH6 WQ=; b=6LAoXw9CahoTW3Pwzd8GrSdbwgYSdv9W7ofuwogKTJ64GGoZ3o/GxN8jO 9aZEVcUfdm1ApiTW69ZCca41VpH8FnkVtrX3xNIx1XBktgRWPBkFuMiRvuyKac9a Nr1EBKmQE8Ig/ndriqhz61b4E7uSuR5oo+ueDvkbliLttY7GTBbmDvA1z0WokH2k yv97rQgptpO3TeH1QiizvyEqn2fNZzD+lXt21qFIRvnf6960TlPGVYLelf/JPap4 FX49BeCzWA6nEKZb4GQkRmKIM35jgVL8GD+YEJMHDwNr7Jap5P46Z+3CX4GuVibx 5ky7er+fSXzzvB2aq1kfAtfeRa8cQ==
X-ME-Sender: <xms:oBmfXLthmUtokCq-yf5fCqjv_pjoROmxZfq8KjcvwUUzSQvp11jsaQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkeekgddutdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhofgjfffgkfhfvfesthejmhdthhdtvdenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinheptghrhihsthgrlhhhuhhffhdrtghomhenucfkphepudeiiedrudejvddrheejrdei leenucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinh enucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:oBmfXH7sFo-yb1MNSWLTQvId8atkhsTyhtdOUZR61m1XlVA9z2AB0w> <xmx:oBmfXCT5TlXzJvlNi36mN98IKy3V3ZFwEfH39M1SmmiaK-k3i0UxNg> <xmx:oBmfXOpS00aeZ47trmh0BmcSe52p_aJqB0znL2KzP8pXhtnpS-o1XQ> <xmx:oRmfXGkGpgxEi18OtULH5-LuH9lo3EicnkUO1UJ-_5aIuAoo1lU4ng>
Received: from [10.89.169.252] (mobile-166-172-57-69.mycingular.net [166.172.57.69]) by mail.messagingengine.com (Postfix) with ESMTPA id 1FD7E100E5; Sat, 30 Mar 2019 03:24:16 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: On harassment at IETF
From: Alissa Cooper <alissa@cooperw.in>
X-Mailer: iPhone Mail (16D57)
In-Reply-To: <104B6F032981170C3F54394E@PSB>
Date: Sat, 30 Mar 2019 08:24:12 +0100
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <00D42A7F-C35C-46B4-8BDF-B4E7B35D1C3F@cooperw.in>
References: <91e75af7-03f9-7565-5a9f-26f5f7bc9f29@openca.org> <690B8BAA-61C9-436E-85B3-0E31739C6527@consulintel.es> <tsl4l7l13r8.fsf@suchdamage.org> <104B6F032981170C3F54394E@PSB>
To: John C Klensin <john-ietf@jck.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zgTmeOYNFyfIY-ej6mQkf4V3Uo4>
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 07:24:22 -0000


> On Mar 30, 2019, at 7:58 AM, John C Klensin <john-ietf@jck.com> wrote:
> 
> 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.

+1

Thanks to Sam, Brian, and others for your responses. 

Alissa

> 
> --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
> 
> 
> 
>