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

Stewart Bryant <stbryant@cisco.com> Fri, 13 March 2015 11:40 UTC

Return-Path: <stbryant@cisco.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 200C21A0370 for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2015 04:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, USER_IN_DEF_DKIM_WL=-7.5] 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 nsHrToK_ws8v for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2015 04:40:15 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87AAC1A0371 for <ietf@ietf.org>; Fri, 13 Mar 2015 04:40:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2666; q=dns/txt; s=iport; t=1426246814; x=1427456414; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=R1/0nDBXn44HPtPt3Gb6UlApt3WmFvnx1CHxBFFhQEc=; b=V3gwoMdPXKM8FImzNY+Uw6O/unjKvTvWyiYUUbAn4dDIXlE7bqMf3PJy btygWTyzkfkS5EAH/qKbIn8YH0TIpKIq9oEDdhNP53VuN5ZYwW8dNLO1h D/kT1G6rfA8lYBKKL0/u8Tsu3R3tDNBKy9Gx0JLLr4D2ttEHmvwpZogTX I=;
X-IronPort-AV: E=Sophos;i="5.11,394,1422921600"; d="scan'208";a="396690272"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 13 Mar 2015 11:40:13 +0000
Received: from [64.103.108.142] (dhcp-bdlk10-data-vlan301-64-103-108-142.cisco.com [64.103.108.142]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t2DBeCgI001524; Fri, 13 Mar 2015 11:40:13 GMT
Message-ID: <5502CC9C.5080400@cisco.com>
Date: Fri, 13 Mar 2015 11:40:12 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, 'Jari Arkko' <jari.arkko@piuha.net>
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> <275BDAE9-2855-44E8-852D-009A15CE8892@piuha.net> <54FEAF51.4060807@cisco.com> <CADhXe53QecMRgxwe9x7RbMZUk9ec90WU_3G1Xc1qX_fB4UFUkA@mail.gmail.com> <021201d05b78$70c13de0$5243b9a0$@olddog.co.uk> <3740BE65-0C21-4120-B9A4-EAE93E57F8E9@piuha.net> <55000EB7.40905@cisco.com> <01a801d05c21$163ce4b0$42b6ae10$@olddog.co.uk>
In-Reply-To: <01a801d05c21$163ce4b0$42b6ae10$@olddog.co.uk>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7BeU_6WukVeHeIGlAHsMYCUpKYA>
Cc: 'IETF Discussion List' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
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 11:40:18 -0000

On 11/03/2015 17:30, Adrian Farrel wrote:
> Stewart, I do wish you would reference the document before launching into your
> critique.
>
> There is nothing in this document that constitutes the IETF making up "its own
> list".
>
> The text of the document, makes an observation about the IESG statement at
> http://www.ietf.org/iesg/statement/ietf-anti-harassment-policy.html.
> This statement was made on 2nd November 2013 while you were serving on the IESG.
Not withstanding that, my position is and always was that the IETF is not
a competent body when it comes to compiling this list and that we should
use a list, or perhaps the union of a number of lists, compiled by those
with the expertise.

The alternative risks creating very messy loopholes.
>
> The text then says that the document "adopts the general definition, but does
> not attempt to further precisely define behavior that falls under the set of
> procedures..."
>
> In other word, this document does not provide a list of categories that maybe
> considered grounds for harassment. So your assertion is not founded.
>
> I understand that you have good reason to believe that the list at
> http://www.legislation.gov.uk/ukpga/2010/15/contents is well considered and
> reasonable. People coming from other cultures might consider it missing many
> categories while others might consider some of the categories it includes to be
> outrageous!
Indeed that is a concern, and there is no way around asserting the set. Any
other approach risks a dispute of the form "but that is permitted (or maybe
even required) in my culture".
> Unless we are going to build a full and water-tight definition of harassment and
> obtain IEFT consensus on it *before* adopting any anti-harassment processes and
> appointing a team to handle any complaints, I suggest we need to move ahead with
> the document as it is. Personally, I would be pleasantly surprised if a body as
> culturally diverse (and opinionated) as the IETF could come to consensus on such
> a definition in any short period of time given (as you note) the IETF "has no
> significant expertise in this area."
>
> Perhaps a way forward here would be for us to all support this document and for
> a further document to attempt to give a more precise definition as advice and
> guidance to the Ombudsteam. If you would like to start a draft on that and run
> it through the consensus process, we might all benefit from it.
Another way is to look at how other multi-national multi-cultural 
organizations
address this. For example what is the UN (i.e. ITU, UNHCR ... ) policy 
in this
regard?

- Stewart