Re: Proposed IETF Anti-Harassment Policy

Ted Lemon <Ted.Lemon@nominum.com> Tue, 22 October 2013 14:15 UTC

Return-Path: <Ted.Lemon@nominum.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 488A611E83DF for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 07:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.293
X-Spam-Level:
X-Spam-Status: No, score=-106.293 tagged_above=-999 required=5 tests=[AWL=-0.294, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RNs3EuupF-Ua for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 07:15:25 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id EC3A411E83DA for <ietf@ietf.org>; Tue, 22 Oct 2013 07:15:23 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUmaIc5eWVDZa4OA3ULf8HeX7P3aeW2IY@postini.com; Tue, 22 Oct 2013 07:15:23 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 813761B82E4 for <ietf@ietf.org>; Tue, 22 Oct 2013 07:15:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 709E5190052; Tue, 22 Oct 2013 07:15:13 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.03.0158.001; Tue, 22 Oct 2013 07:15:13 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Theodore Ts'o <tytso@mit.edu>
Subject: Re: Proposed IETF Anti-Harassment Policy
Thread-Topic: Proposed IETF Anti-Harassment Policy
Thread-Index: AQHOzbxVzZsUK86MhUyC7IRlHFizLZoAeVGAgABzWwCAAE9xAA==
Date: Tue, 22 Oct 2013 14:15:13 +0000
Message-ID: <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org>
In-Reply-To: <20131022093052.GF9517@thunk.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F6A6D352B6232840B87A0BDB9FCAC446@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 22 Oct 2013 14:15:31 -0000

On Oct 22, 2013, at 5:30 AM, Theodore Ts'o <tytso@mit.edu> wrote:
> These are indeed the critical questions.  It's easy to have a
> statement about what might be considered "harassment".  If however
> someone tries to use this as a debating tactic during a particularly
> robust technical discussion, what happens next?  Does it get raised to
> the wg chair?  If the wg chair says, that's just a robust technical
> discussion, does it get escalated to ombudsman?  If the ombudsman
> says, "nope, sorry", does it get escalated to the AD and IESG, and do
> they then have to write up carefully crafted appeal documents which
> will no doubt suck up huge amounts of their time?

The path is harassment->ombudsbeing, not harassment->wg chair.  I would expect the ombudsperson to push back at this point unless something inappropriate was said.   If someone says "that's a stupid idea, because FOO" and "because FOO" is valid, then it would be appropriate for the ombudsperson to say to the offending party, "you know, you didn't need to say that was a stupid idea—all you needed to say was 'because FOO.'".   OTOH, if the offending party said "I'm going to cut off a deer's head and leave it in your refrigerator if you don't stop denying that FOO," then that would elicit a different response.

> Should there be any cost to someone who tries to escalate disputes via
> the anti-harassment process, when it is determined afterwards that it
> is not harassment?  If we do, then it might deter valid plaintiffs
> from coming forward.  If we don't, how do we deter people who might
> try to abuse this process from using it to that end?  Historically, we
> certainly had people who have been rather enthusiastic about using
> whatever appeal processes we've made available.

I think if someone develops a history of engaging in this kind of tactic, it might become grounds for banning from mailing list discussion, and there might be appeals, and that would suck.   But that's really the status quo now, so it's not like this changes anything.   It's unlikely that it would be appropriate to respond to a single accusation of harassment that the ombudsperson does not agree is harassment with any kind of censure.

> One hint --- we should definitely try to pursuade folks not to try to
> get a decision based on the specific facts of a particulate dispute
> via the court of public opinion:
> 
>       "Adria Richards, PyCon, and How We All Lost"
>       http://amandablumwords.wordpress.com/2013/03/21/

What happened at PyCon is a really strong argument for having an escalation path other than twitter.   We can't stop participants from doing stuff like this, but hopefully the lesson has been learned that this is a bad tactic for dealing with behavior in meetings that one finds inappropriate.   So there should be an incentive to try the ombudsperson tactic first, and then escalate to twitter only if that fails.