Re: Last Call: <draft-farrresnickel-harassment-08.txt> (IETF Anti-Harassment Procedures) to Best Current Practice
Jari Arkko <jari.arkko@piuha.net> Tue, 01 September 2015 13:23 UTC
Return-Path: <jari.arkko@piuha.net>
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 2C1931A9177 for <ietf@ietfa.amsl.com>; Tue, 1 Sep 2015 06:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 89EAI5yU8lK3 for <ietf@ietfa.amsl.com>; Tue, 1 Sep 2015 06:23:19 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5B4CD1B351F for <ietf@ietf.org>; Tue, 1 Sep 2015 06:23:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E459C2CC6B for <ietf@ietf.org>; Tue, 1 Sep 2015 16:23:17 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KdoIX6IyAIsv for <ietf@ietf.org>; Tue, 1 Sep 2015 16:23:17 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 575B42CC5C for <ietf@ietf.org>; Tue, 1 Sep 2015 16:23:17 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_429437E7-11C0-41A0-8945-EA0937972D94"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Last Call: <draft-farrresnickel-harassment-08.txt> (IETF Anti-Harassment Procedures) to Best Current Practice
X-Pgp-Agent: GPGMail 2.5.1
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20150831144507.2223.61158.idtracker@ietfa.amsl.com>
Date: Tue, 01 Sep 2015 16:23:16 +0300
Message-Id: <EAD77D5D-64D5-4CBA-A1BA-0E6D0707828B@piuha.net>
References: <20150831144507.2223.61158.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/69YuEHD_0nPufcgvQFrpYcHhFKk>
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: <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: Tue, 01 Sep 2015 13:23:22 -0000
I wanted to thank the design team and the editors for good work. I’m very happy with this version. I did, however, have a couple of editorial nits that I wanted to bring up. Section 5: o At the other end of the spectrum the Ombudsteam could decide that the Respondent is no longer permitted to participate in a particular IETF activity, for example, ejecting them from a meeting or requiring that the Respondent can no longer attend future meetings. If the Respondent holds a management position ... I’d suggest adding a sentence here about the purpose of the remedy, even if there’s a whole section about it later. For instance: “… no longer attend future meetings as a way to ensure that a serious harassment can not continue. If the Respondent … " Section 5.1: o In the event that an AD declines to act on the recommendation of the Ombudsteam and fails to convince the Ombudsteam, the Ombudsteam should raise the issue with the whole IESG while continuing to attempt to retain confidentiality. The IESG may choose to reorganize the responsibilities for working groups within its own structure so that the conflicted AD is no longer in the direct management path. Where does “declines to act” refer to? The previous bullet item, where an AD is expected to follow the advice of the ombudsteam? I that case “conflicted” is probably the wrong term. Or maybe I don’t understand what you are trying to say here. If the AD disagrees with the recommendation from the ombudsteam, there could be various reasons for it, from being conflicted somehow to mere disagreement etc. Please clarify. Section 5.1: All such forced removals from management positions should be considered by the Ombudsteam as acts of last resort. That is, before a Respondent is recommended for removal, the Ombudsteam should discuss the situation with the Respondent giving them ample opportunity to understand what might happen and to step down of their own volition. This text could perhaps be modified to also account for the fact that not only are these removals last resort in the above sense, but also in the sense that not all situations require removal/stepping down. Jari
- Re: Last Call: <draft-farrresnickel-harassment-08… Jari Arkko
- Re: Last Call: <draft-farrresnickel-harassment-08… Mark Nottingham
- RE: Last Call: <draft-farrresnickel-harassment-08… Adrian Farrel
- RE: Last Call: <draft-farrresnickel-harassment-08… John C Klensin
- Re: Last Call: <draft-farrresnickel-harassment-08… Dave Crocker
- Re: Last Call: <draft-farrresnickel-harassment-08… John C Klensin
- Re: Last Call: <draft-farrresnickel-harassment-08… Jari Arkko
- Re: Last Call: <draft-farrresnickel-harassment-08… Donald Eastlake
- RFC content history ( Re: Last Call: <draft-farrr… Dave Crocker