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

Pete Resnick <presnick@qti.qualcomm.com> Fri, 13 March 2015 21:04 UTC

Return-Path: <presnick@qti.qualcomm.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 762511A0171; Fri, 13 Mar 2015 14:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.011
X-Spam-Level:
X-Spam-Status: No, score=-7.011 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 kkcUcUP_pQAc; Fri, 13 Mar 2015 14:04:09 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DA5F1A6F87; Fri, 13 Mar 2015 14:04:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1426280648; x=1457816648; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=UqgDe4KPMTq8jGWT4rvGE/lW/fKLZjEH+XVCKR6+F70=; b=L4zI2KdZSMrNsTdt4iW1G3sNGpwFLXky/xiTpJ7ivAdELb+VpVgKfKpt rPO7k0X8hYeIk17iKcxvyxmqDAz/1Ql+GqC56ARX8x8SkiDHpqWg6V2+G 0wlyuZLgFT0VpSy8nMzJvM+99WsgdaeHSKoEXziGAt4qWyzBZgFRbpUk0 M=;
X-IronPort-AV: E=McAfee;i="5600,1067,7739"; a="108195791"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Mar 2015 14:04:07 -0700
X-IronPort-AV: E=Sophos;i="5.11,396,1422950400"; d="scan'208";a="924545991"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 13 Mar 2015 14:04:05 -0700
Received: from presnick-mac.local (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.995.29; Fri, 13 Mar 2015 14:04:05 -0700
Message-ID: <550350C4.9040201@qti.qualcomm.com>
Date: Fri, 13 Mar 2015 14:04:04 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
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> <tslr3sxep1l.fsf@mit.edu> <54FE6297.4090008@qti.qualcomm.com> <tslzj7i2wid.fsf@mit.edu> <55019E72.4090004@qti.qualcomm.com> <tslfv9a2t6p.fsf@mit.edu> <36671C44-DE53-4AC9-B8EA-465BF97B2FDB@piuha.net> <tsly4n0zo6g.fsf@mit.edu>
In-Reply-To: <tsly4n0zo6g.fsf@mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: nasanexm01a.na.qualcomm.com (10.85.0.81) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uy74X2nDktYf9q34l3vSGSCKqGo>
Cc: IETF Discussion List <ietf@ietf.org>, iesg@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: Fri, 13 Mar 2015 21:04:11 -0000

Speaking only for myself:

On 3/13/15 12:34 PM, Sam Hartman wrote:
> old:
> (The Ombudsteam can not impose that a Respondent
>        who is in a IETF management position be removed from that
>        position.  There are existing mechanisms within IETF process for
>        the removal of people from IETF management positions that may be
>        used as necessary.)
>
> new:
> The Ombudsteam MAY ask a respondent to consider resigning from an IETF
> management position.  The Ombudsteam May remove a respondent from a
> working group  or document editor position.  While this document does
> not create additional procedures permitting a nomcom appointee be
> removed, the Ombudsteam can exclude a respondent from meetings and
> mailing lists and other activities, making it impossible for them to
> carry out their appointed tasks.
>    

- With regard to NomCom appointed positions, this is just fine, and in 
fact what the current text intended, while making it perfectly clear 
what was intended.

- I am ambivalent about the Ombudsteam being able to remove someone from 
a WG (editor/secretary/chair) position. While it certainly doesn't get 
into the morass that we do with NomCom-appointed positions, it seems to 
me that it's still a bit of "crossing-the-streams", and as far as I can 
tell the same kinds of things that can be done for NomCom-appointed 
positions (ask them to consider resigning their position, exclusion from 
meetings / mailing lists, etc.) would have equal effectiveness. So, I'm 
not sure it's necessary. But as I said, I'm ambivalent.

As for the thought experiment on how a recall might go after such an 
incident: I am certainly more sanguine than Sam. Presuming an incident 
where the Ombudsteam decides that an AD can no longer participate in 
meetings and mailing lists (already I would hope a *highly* unusual 
circumstance) *and* the AD goes haywire and refuses to relinquish their 
title (even more unlikely) *and* the "two sides" try to get their 
friends on the recall committee, *and* these supposed friends agree to 
participate in such a thing (I have a hard time imagining any of the 
people I know in the IETF being willing to do so), we still have the 
case that the (hopefully sane) ISOC-President-appointed recall committee 
chair is going to tell the committee, "Look, we are not deciding whether 
this person can start participating in meetings or on mailing lists 
again. They can't and that's not going to change. The only question is 
whether they get to keep their office in light of that fact." If at that 
(almost unimaginable) point a sufficient number of people on the recall 
committee are willing to be so destructive to the IETF that they are 
willing to participate in leaving the person in the position, I think 
I'm willing to live with the IETF going *boom*.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478