Re: On harassment at IETF
Kyle Rose <krose@krose.org> Sat, 30 March 2019 11:45 UTC
Return-Path: <krose@krose.org>
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 8A14F12019A
for <ietf@ietfa.amsl.com>; Sat, 30 Mar 2019 04:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=krose.org
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 KQanGOBpHizC for <ietf@ietfa.amsl.com>;
Sat, 30 Mar 2019 04:45:37 -0700 (PDT)
Received: from mail-yw1-xc30.google.com (mail-yw1-xc30.google.com
[IPv6:2607:f8b0:4864:20::c30])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 6F60112013D
for <ietf@ietf.org>; Sat, 30 Mar 2019 04:45:37 -0700 (PDT)
Received: by mail-yw1-xc30.google.com with SMTP id w66so1625279ywd.4
for <ietf@ietf.org>; Sat, 30 Mar 2019 04:45:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=n0/i6zkChsyvXP3xW3/KZ2vcGrPcmMqSwROQzsSdvu4=;
b=Una++A7TCaZg0wmplB1tcE7E2BdzH2toyWkeffE4Olfr3p7l3yJTjtm25xJG0QWMex
XAS8a+XPwTk1VQHQrNUyI0x51jbofhK9uFI7+bpij/vraUa4O2wUvzCGuYp2UXsJPlPX
wTAutVF5ZedruZM7hy94eUxQqerb4f2oMslDY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=n0/i6zkChsyvXP3xW3/KZ2vcGrPcmMqSwROQzsSdvu4=;
b=ravE4C8tZlYSHUpmlOwaYGartLjwkjEqKar/KcxdZtEPLE9TntnpgJevzB71dQ4Z6P
JYbHX9+IoZEYCgiv0ldeWch+CAMcWhuDtftWTTRVVQwObFwQhDm8VwFJq+fSTkVAAIdd
io4AIdSZi3Nhs5fCKLFuQxs8xLykInb8Xyn/4sp5eg/TnWBz9aXW8wLN0iOKPAPhaeAo
07hQeIrXYB2c4tCYHsqvMLOLHZ3VvgIj7kBQGfdOCn9JZuanpOB8V43zwI8aZwwoLoE4
VrKcH5O7kYPz5n0Id6f7iosFkmnl9ET5+sfPFMcRdFYcVfszYrlY7zHCS8kFcI0zhEgD
ZiIA==
X-Gm-Message-State: APjAAAWdR1AQbJXdkdhKW8CgMcaAwVup42LQCgzfb2pTZwva++acX6CR
agzJEsU/1etdqsGNUPr7taiUIitr2uaNQ6SVR7ErCfWW/Ev4Qw==
X-Google-Smtp-Source: APXvYqysXv6IYNlpDwYRtAaCsra6hVO7zlTR7jWILuhSmb/yCzJVeLo4iYiW9J1FWXzkSG3USTIX2Qo9cMfgmzurIT8=
X-Received: by 2002:a81:9143:: with SMTP id i64mr42492122ywg.314.1553946335437;
Sat, 30 Mar 2019 04:45:35 -0700 (PDT)
MIME-Version: 1.0
References: <91e75af7-03f9-7565-5a9f-26f5f7bc9f29@openca.org>
In-Reply-To: <91e75af7-03f9-7565-5a9f-26f5f7bc9f29@openca.org>
From: Kyle Rose <krose@krose.org>
Date: Sat, 30 Mar 2019 12:45:23 +0100
Message-ID: <CAJU8_nX0qTDs2tcwFC_4R-9X48NxUdiHEfDEbCrtFxEnNN9m-w@mail.gmail.com>
Subject: Re: On harassment at IETF
To: "Dr. Pala" <director@openca.org>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/related; boundary="000000000000532f0c05854e5387"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9NuB578hUZbm1VLs5txbItFsazk>
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 11:45:40 -0000
On Sat, Mar 30, 2019 at 12:31 AM Dr. Pala <director@openca.org> wrote: > I am sorry to use strong language, but this is an issue that I have been > exposed to in the past and that I find COMPLETELY UNACCEPTABLE. I do not > know what the policy is at the IETF, but I think there should be ZERO > tolerance for such behavior. And if you are one the people that think this > community will tolerate your behavior maybe because you are a well-known > figure in the Industry, be sure of one thing: I will fight to make sure > that (a) your behavior is publicly exposed, and (b) you get shamed and > BANNED from IETF. The behavior, I think, should also be reported to the HR > department of the organization that sent that individual for further > actions. > Many of us observe a clear distinction between taking official action via established channels against those who have violated IETF policies on harrassment, and advocating mob justice. I am in favor of the former. I am against the latter. Kyle
- 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