Re: Sam's text and way forward on the last call of draft-farrresnickel-harassment-05.txt

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 19 March 2015 11:30 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 725DF1A8990 for <ietf@ietfa.amsl.com>; Thu, 19 Mar 2015 04:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.46
X-Spam-Level:
X-Spam-Status: No, score=-1.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FB_GET_MEDS=2.75, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 JO6zMO9cEzBB for <ietf@ietfa.amsl.com>; Thu, 19 Mar 2015 04:30:45 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9102E1A897D for <ietf@ietf.org>; Thu, 19 Mar 2015 04:30:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D1BADBEAF; Thu, 19 Mar 2015 11:30:40 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNswyXKWPzmZ; Thu, 19 Mar 2015 11:30:39 +0000 (GMT)
Received: from [10.87.48.73] (unknown [86.46.20.71]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 83914BE3E; Thu, 19 Mar 2015 11:30:39 +0000 (GMT)
Message-ID: <550AB35F.6090707@cs.tcd.ie>
Date: Thu, 19 Mar 2015 11:30:39 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, IETF Discussion List <ietf@ietf.org>
Subject: Re: Sam's text and way forward on the last call of draft-farrresnickel-harassment-05.txt
References: <5503914A.7060209@gmail.com> <5503BF22.5020902@gmail.com> <2AE2D092-C32A-46EB-88CA-71366965F4D7@cisco.com> <5505D873.1040203@gmail.com> <CAL0qLwbQf_2WUn8PrUXCMy_3w6tt+iJw0tyF=gUojA5fwRXJNg@mail.gmail.com> <550736E0.6080101@dcrocker.net> <20150316203250.GJ2179@mx1.yitter.info> <55073F22.6000606@dcrocker.net> <20150316204616.GK2179@mx1.yitter.info> <55074AC1.9080500@dcrocker.net> <20150316214620.GO2179@mx1.yitter.info> <550751AC.7090108@dcrocker.net> <55075EBA.4000905@gmail.com> <5509BB58.4060307@qti.qualcomm.com> <B714CBFE-5D3D-4293-91C2-534A3437EB24@piuha.net>
In-Reply-To: <B714CBFE-5D3D-4293-91C2-534A3437EB24@piuha.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/sUsfKiUt1VeMf5bA34bhqhB361M>
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: Thu, 19 Mar 2015 11:30:47 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 19/03/15 10:03, Jari Arkko wrote:
>> 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.

I'm quite uneasy with us saying that the Ombudsteam may remove
editors or similar, and especially with us saying that but not
saying how it might be done in practice. I also think we ought
not be so focused on remedies that involve role-changes, since
I think less dramatic remedies will be far more common (or I
hope so).

I'd therefore suggest we focus more on what the Ombudsteam are
allowed to communicate, so I'd suggest:

NEW new:

"
The Ombudsteam MAY ask a respondent to consider resigning from an IETF
management position or from a working group  or document editor
position.

To the extent required in order to ensure a remedy in encforced, the
Ombudsteam are allowed to (where absolutely necessary) reveal some
details of their investigation. In doing so, the Ombudstream must
only reveal details that the Subject or Reporter agree may be
revealed. The intent here is to allow the Ombudsteam flexibility
in how they get remedies enforced - in practice, in order to
enforce some remedies whilst preserving as much confidentiality
as possible, (in particular for a Subject) the Ombudsteam may need
to convince someone not involved in the situation that e.g. a change
in role or organisation is needed.

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.

"

I'd be fine with any wordsmithed version of the above that avoids
getting into too much mechanical detail.

Cheers,
S.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVCrNfAAoJEC88hzaAX42ijbUH/A6+0k8YFC5mwz5CGHxr7xPO
UcfbKwTLl3fyjHMJDekiNBmgdV288JLnipHkevk/H2moti5YtHerc8gy5aXM/vV6
PvBdkcA6o/jYlc8WscE+B+RU8o3QBfyvo8NGzAyfmeOdnTr4eT4u1QQ/TJXjo7Ol
dEyaAkv3kSovB9Ov3CRh6Jj4fyoOiNBztbMm2Xt0yi/BJhoT+y/xdyU9t4z4dPEQ
e39CgZ7X5MQc2OY2H39NhMo2drIUHYqJkZItiI2qW/UoSDUxvtHWq07jWLPWNAt8
L8Sp9X/9w6QC09B+H0IHFAYlIZHlw0KKAYv3LMABvoT/Nnjy/m3Dnc15HguekCM=
=xQ9h
-----END PGP SIGNATURE-----