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

John Leslie <john@jlc.net> Fri, 06 March 2015 16:37 UTC

Return-Path: <john@jlc.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 9A6B01ACEDC for <ietf@ietfa.amsl.com>; Fri, 6 Mar 2015 08:37:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level:
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, 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 IzYuQaRGzMSG for <ietf@ietfa.amsl.com>; Fri, 6 Mar 2015 08:37:53 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id E77EA1A09C9 for <ietf@ietf.org>; Fri, 6 Mar 2015 08:37:52 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id CE0ADC94BF; Fri, 6 Mar 2015 11:37:24 -0500 (EST)
Date: Fri, 06 Mar 2015 11:37:24 -0500
From: John Leslie <john@jlc.net>
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Last Call: <draft-farrresnickel-harassment-05.txt> (IETF Anti-Harassment Procedures) to Best Current Practice
Message-ID: <20150306163724.GA32205@verdi>
References: <20150116152211.25947.49086.idtracker@ietfa.amsl.com> <20150117174430.9A0471ACE15@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20150117174430.9A0471ACE15@ietfa.amsl.com>
User-Agent: Mutt/1.4.1i
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/aqO3j81r9zsbBWoPqp8rvW2zDyY>
Cc: ietf@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, 06 Mar 2015 16:37:54 -0000

Michael StJohns <mstjohns@comcast.net> wrote:
> 
> Has either or both of the ISOC and IETF trust lawyers reviewed this,
> especially section 5?

   As of the start of yesterday's telechat, Jari held a DISCUSS awaiting
such a review.

> 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?

   +1

> I'm still in great opposition to this document

   -1

> as I believe Section 5 provides too broad a palate of "remedies" without
> appropriate checks and balances on the system.

   +1

   I find it worrisome that a Respondent is prohibited from requiring
public review of the process which led to a decision to exclude him/her.
(Obviously the Reporter is entitled to privacy; but a person being
excluded should have some option to request that the exclusion be
publicly shown to not be arbitrary. This seems to be lacking.)

> 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.

   This, too: I fail to understand how an exclusion would be enforced.

>... Since this is targeted for a BCP, the supporting documentation needs
> to be part of the approval package.

   +0

   I think this last statement needs a public response.

--
John Leslie <john@jlc.net>