Re: What is a "management position? [Last Call: <draft-farrresnickel-harassment-05.txt> (IETF Anti-Harassment Procedures) to Best Current Practice]

Scott Kitterman <scott@kitterman.com> Fri, 20 March 2015 21:55 UTC

Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6B201A908A for <ietf@ietfa.amsl.com>; Fri, 20 Mar 2015 14:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 NNuZrLINBNXK for <ietf@ietfa.amsl.com>; Fri, 20 Mar 2015 14:55:35 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 440A21A907D for <ietf@ietf.org>; Fri, 20 Mar 2015 14:55:03 -0700 (PDT)
Received: from kitterma-e6430.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 5F894C40477 for <ietf@ietf.org>; Fri, 20 Mar 2015 16:55:02 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1426888502; bh=IjH88xR4SLGaPg2FwQGLOgZaBqO++0ewwamKqAuwkMs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XSQs185ybEsAOF7PGvCqUY9dr9tkdH6EriligdJ+2hQN+jw32wrZcjExN07zcpBAs n32y57rnjwermh6f/JWpN9QWlIhTawm76rE5ddo0x3brptzvTtcpVjqYFl2svmfjLM zMcDACPcZwaoDcN+t9rFnU9ZtizHlZ+4JRNbebp8=
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: What is a "management position? [Last Call: <draft-farrresnickel-harassment-05.txt> (IETF Anti-Harassment Procedures) to Best Current Practice]
Date: Fri, 20 Mar 2015 17:55:02 -0400
Message-ID: <5428096.h6mqNfeZ1i@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-46-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <92FC37287A9D7FA1656E2601@JcK-HP8200.jck.com>
References: <5503914A.7060209@gmail.com> <965AA861-EAB8-4DCE-BB9B-9D02BE63AE68@piuha.net> <92FC37287A9D7FA1656E2601@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/utTbawCDgAeuMkH4UB8TplVQKpk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 20 Mar 2015 21:55:37 -0000

On Friday, March 20, 2015 05:46:11 PM John C Klensin wrote:
> --On Friday, March 20, 2015 13:23 -0500 Jari Arkko
> 
> <jari.arkko@piuha.net> wrote:
> > I agree with the points from Scott, Christian, and you John
> > that it is possible that confidentiality is not maintained on
> > a case involving a continuously bad actor. (Assuming we get to
> > such a bad situation to begin with, which I hope we wont.)
> > 
> > My question to you though is what effect do you believe that
> > observation should have on our procedures? Are you suggesting
> > that they should not by default be confidential?
> 
> I think the draft outlines a process that should, in the hands
> of the right people with the right professional skills (see
> Mike's comments) work rather well for careless or insensitive
> offenders who do things in the IETF that, on reflection, they
> can be persuaded they should not be doing.  I thing a
> confidential process is completely consistent with that.
> 
> If that fails, I think, first, that the neutral "respondent" is
> no longer appropriate and we should be using terms like
> "offender".    Whether "offender" gets qualified with terms like
> "persistent", "obstinate about the correctness of his or her
> behavior", "unrepentant" or other words may or may not be
> relevant depending on the particular issues (and, by the way,
> those applicable/local laws). Because of that I think we get
> into a process, whether it involves the Ombudsteam, Recall, Post
> Rights actions, and/or something else, that involves either
> preventing another repetition whether the offender agrees or not
> or protecting the community from the effects and consequences of
> the offender's behavior, typically both.
> 
> To a considerable extent, I believe that once that line is
> crossed, the presumption must be that the harassment is
> interfering with the IETF getting work done and we are all
> victims.
> 
> At that point, I think the most important role of the Ombudsteam
> (one that, by the way, requires an even higher level of
> professionalism than the "normal" case) is to work with
> Reporter-victims, and, when appropriate, with the IESG and
> potentially Counsel on behalf of community-victims to determine
> whether the advantages of taking further steps --steps in which
> confidentiality is ultimately not going to be possible and may
> be less desirable-- to the community and individual victims
> exceed the disadvantages of, e.g., risking disclosure of victim
> identities, community gossip. etc.   I think we need to accept
> something that others have said in different ways: when we start
> doing things like blocking someone's ability to participate, it
> better be done via and open process with the guarantees that
> only openness at critical stages can bring.

This description presumes false or incorrect reports don't happen.  Just 
because the respondent doesn't fall all over themselves to recant, doesn't 
mean they've done anything wrong.

Scott K