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

Michael StJohns <mstjohns@comcast.net> Sat, 17 January 2015 17:44 UTC

Return-Path: <mstjohns@comcast.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 7D13B1ACE48 for <ietf@ietfa.amsl.com>; Sat, 17 Jan 2015 09:44:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.512
X-Spam-Level:
X-Spam-Status: No, score=-1.512 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MISSING_MID=0.497, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
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 BouF3FbyIlTB for <ietf@ietfa.amsl.com>; Sat, 17 Jan 2015 09:44:26 -0800 (PST)
Received: from resqmta-po-09v.sys.comcast.net (resqmta-po-09v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:168]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B788E1ACD45 for <ietf@ietf.org>; Sat, 17 Jan 2015 09:44:26 -0800 (PST)
Received: from resomta-po-13v.sys.comcast.net ([96.114.154.237]) by resqmta-po-09v.sys.comcast.net with comcast id h5kJ1p00357bBgG015kSTR; Sat, 17 Jan 2015 17:44:26 +0000
Received: from Mike-T530ssd.comcast.net ([69.255.115.150]) by resomta-po-13v.sys.comcast.net with comcast id h5kJ1p00n3Em2Kp015kRzA; Sat, 17 Jan 2015 17:44:26 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sat, 17 Jan 2015 12:44:15 -0500
To: ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Last Call: <draft-farrresnickel-harassment-05.txt> (IETF Anti-Harassment Procedures) to Best Current Practice
In-Reply-To: <20150116152211.25947.49086.idtracker@ietfa.amsl.com>
References: <20150116152211.25947.49086.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_142395357==.ALT"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1421516666; bh=fVLPMCCnzdCa1vKpHKfJMiOepyIMYqkiilSUJZKPLv4=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=geEaiSPV35bvUMM7nO5gJw8loB6ddHiXEr0Eq9HnXRW7/dC3ON2OTAfHdxyqRmiQ3 Hk7f5s6shu/l1/W8std/UE8iOdWmpmsJi6wU0OZZYd25RUzasALQfvb/01r7/x1u+A duKOSrrKI3PtR8izeQUExiOtGR1GQ1EF1NDNoajfetkQir4NTDTyJKwdO7+nwcaWxW AYh5LAmGleVuu6uX/2DsyNyUTA23zDJfO6xerTvk5Ut8D5Pht3Hc2bYCsr/ASms6Vv fdJSJOaFceUWrDHAq/4hUc4YfXcuzNXoFWutt8ccnH9UpcSZ3Gd+h2nmYjtokZlFgZ DPuI5yQbf5dHg==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZfU1lfmx-pGluI77FdZ7RvcAJcM>
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: Sat, 17 Jan 2015 17:44:28 -0000
X-Message-ID:
Message-ID: <20150117174431.32628.56975.ARCHIVE@ietfa.amsl.com>

Has either or both of the ISOC and IETF trust lawyers reviewed this, especially section 5?  If so, would you please provide the written evaluation that indicates they see no issue with respect to IETF liability should the Ombudsman actually attempt to exclude someone from the face to face or online sessions?

I'm still in great opposition to this document  as I believe Section 5 provides too broad a palate of "remedies" without appropriate checks and balances on the system.   It's unclear that what actual recourse the IETF has if the target of the remedies simply chooses to ignore the directions of the OBs.

I would not publish it in its current form and would never publish it without appropriate documented professional review ideally by both legal and HR experts.  Since this is targeted for a BCP, the supporting documentation needs to be part of the approval package.

Later, Mike


At 10:22 AM 1/16/2015, The IESG wrote:

>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'IETF Anti-Harassment Procedures'
>  <draft-farrresnickel-harassment-05.txt> as Best Current Practice
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2015-02-13. Exceptionally, comments may be
>sent to iesg@ietf.org instead. In either case, please retain the
>beginning of the Subject line to allow automated sorting.
>
>Abstract
>
>
>   IETF Participants must not engage in harassment while at IETF
>   meetings, virtual meetings, social events, or on mailing lists.  This
>   document lays out procedures for managing and enforcing this policy.
>
>   This document updates RFC 2418.
>
>
>
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-farrresnickel-harassment/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-farrresnickel-harassment/ballot/
>
>
>No IPR declarations have been submitted directly on this I-D.