Re: Last Call: <draft-farrresnickel-harassment-05.txt> (IETF Anti-Harassment Procedures) to Best Current Practice

Sam Hartman <hartmans-ietf@mit.edu> Mon, 09 March 2015 23:20 UTC

Return-Path: <hartmans@mit.edu>
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 4A0081A9168 for <ietf@ietfa.amsl.com>; Mon, 9 Mar 2015 16:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=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 ZrzXLO0azUfF for <ietf@ietfa.amsl.com>; Mon, 9 Mar 2015 16:20:54 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE8151A8931 for <ietf@ietf.org>; Mon, 9 Mar 2015 16:20:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 09F2E20659; Mon, 9 Mar 2015 19:19:20 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QwDZzMR9ZaLi; Mon, 9 Mar 2015 19:19:19 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-50-177-26-195.hsd1.ma.comcast.net [50.177.26.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 9 Mar 2015 19:19:19 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 6D14A82837; Mon, 9 Mar 2015 19:20:22 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Last Call: <draft-farrresnickel-harassment-05.txt> (IETF Anti-Harassment Procedures) to Best Current Practice
References: <20150116152211.25947.49086.idtracker@ietfa.amsl.com> <20150117174430.9A0471ACE15@ietfa.amsl.com> <20150306163724.GA32205@verdi> <tsl385im2yp.fsf@mit.edu> <781553AA-EA2C-4057-9888-491C80A780DA@piuha.net> <54FE045D.3080606@qti.qualcomm.com>
Date: Mon, 09 Mar 2015 19:20:22 -0400
In-Reply-To: <54FE045D.3080606@qti.qualcomm.com> (Pete Resnick's message of "Mon, 9 Mar 2015 15:36:45 -0500")
Message-ID: <tslr3sxep1l.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mZwsusT2A9x-uSwf7pkojnXNpWg>
X-Mailman-Approved-At: Tue, 10 Mar 2015 08:28:24 -0700
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF Discussion List <ietf@ietf.org>
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: Mon, 09 Mar 2015 23:20:56 -0000

>>>>> "Pete" == Pete Resnick <presnick@qti.qualcomm.com> writes:

    Pete> On 3/9/15 3:14 PM, Jari Arkko wrote:
    >> we did discuss the leadership-as-respondent issues during IESG
    >> Evaluation, and we concluded keeping these procedures and recall
    >> separate was best. Pete or Adrian can give details if you're
    >> interested.

    Pete> The short answer is that the IESG generally thought that
    Pete> "crossing the streams" was a bad idea. Imagine that we do get
    Pete> to the particular point of horror, that someone in leadership
    Pete> has harassed someone in such a way that the Ombudsteam
    Pete> concludes the only appropriate remedy is that they are unable
    Pete> to attend future meetings or participate in list discussions,
    Pete> *and* that person refused to resign their post. Even if they
    Pete> keep the fact of the harassment confidential and simply said,
    Pete> "I will be unable to attend meetings in the future for
    Pete> personal reasons, nor will I be able to participate in WG list
    Pete> discussions, but I still wish to remain as AD", that's really
    Pete> plenty enough impetus for a recall committee to be formed and
    Pete> remove the person from their post.

OK, well, that seems kind of inconsistent with the current text that
talks about recommending someone not be in a leadership position.

I really do find the current text deeply broken and don't think I
understand it well enough that I could reasonably participate in any of
the roles outlined by the process.  Which to me seems to be a fairly
major fairness issue.

Also, there's another concern.  Imagine sexual harassment on the part of
ADs in in-person interactions.
First, if you think that doesn't happen, I'll be happy to share specific
instances where I was the target of such harassment (without names of
course) so we can get a public discussion of the sorts of things that do
happen.
I don't think situations involving me were sufficient that someone
needed to be excluded, but others may have experienced more serious
situations.
In some ways this approach forces the ombudsteam to exclude someone from
a meeting rather than what might be a lesser penalty  of removing them
from a leadership position.
Do you want to force that?

I think that most of my concerns would be addressed by adding a
statement indicating that the ombudsteam SHOULD maintain a procedure
explaining  how they resolve conflicts between the desire for
confidentiality and the disclosures necessary to do their jobs.

To me that statement accomplishes two things not present in the current
text:

1) It acknowledges that there are such conflicts; I read the current
text and I see a bunch of stuff about absolute confidentiality, with no
acknowledgement that it can't quite be absolute.

2) Indicates where people can look to see current thinking on resolving
the conflict.

Without something along these lines or a lot more work, I think this is
really very broken.