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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 12 March 2015 15:01 UTC

Return-Path: <spencerdawkins.ietf@gmail.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 3A2901A8771; Thu, 12 Mar 2015 08:01:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] 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 dW1tcj_qCcTz; Thu, 12 Mar 2015 08:01:47 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACDF81A873C; Thu, 12 Mar 2015 08:01:40 -0700 (PDT)
Received: by lbvn10 with SMTP id n10so16633347lbv.1; Thu, 12 Mar 2015 08:01:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VTVY1gLH1vQ1nJ/F2AhgIFX5QaE1oAc3RmSacigs9Wc=; b=mGXraGCBXzqwBR13kJFfc7TL0d1avmW3NaVPtwmRHSbs4slO9nzFnmEG3fVfyDVfkT YaO0JL7at8CavbsFKLa1KWE6AT2n7Kfrwndsd4slXduRFSoSekmdHk8Xcdfl7SS9H5e1 2kxzHUdvbS8AKkGfNmbgq4LMPVeoTyLaNbH6GPbszxplnWpK8nNsC6qq7GHg9JpnH0sm UA3OONNkO7E6vDkChSVSUWOjp5/FKOabu/tpTJdd/94w9e/CaMe/ld/zxw7hiSVBsHHU x1v4ug/1EBn7yNXcOxQZLqtyOEJK4rQuJDn8BqmJRIJRGP71wkVLuz2SSTSCT+OqWo6x hLiA==
MIME-Version: 1.0
X-Received: by 10.152.1.194 with SMTP id 2mr15297844lao.38.1426172499205; Thu, 12 Mar 2015 08:01:39 -0700 (PDT)
Received: by 10.152.129.193 with HTTP; Thu, 12 Mar 2015 08:01:38 -0700 (PDT)
Received: by 10.152.129.193 with HTTP; Thu, 12 Mar 2015 08:01:38 -0700 (PDT)
In-Reply-To: <36671C44-DE53-4AC9-B8EA-465BF97B2FDB@piuha.net>
References: <20150116152211.25947.49086.idtracker@ietfa.amsl.com> <20150117174430.9A0471ACE15@ietfa.amsl.com> <20150306163724.GA32205@verdi> <tsl385im2yp.fsf@mit.edu> <781553AA-EA2C-4057-9888-491C80A780DA@piuha.net> <54FE045D.3080606@qti.qualcomm.com> <tslr3sxep1l.fsf@mit.edu> <54FE6297.4090008@qti.qualcomm.com> <tslzj7i2wid.fsf@mit.edu> <55019E72.4090004@qti.qualcomm.com> <tslfv9a2t6p.fsf@mit.edu> <36671C44-DE53-4AC9-B8EA-465BF97B2FDB@piuha.net>
Date: Thu, 12 Mar 2015 10:01:38 -0500
Message-ID: <CAKKJt-e27Xv1v20dc_q1U-B7C1-TjMtFkYPEqCSs2dBkdtfqBg@mail.gmail.com>
Subject: Re: Last Call: <draft-farrresnickel-harassment-05.txt> (IETF Anti-Harassment Procedures) to Best Current Practice
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary="089e013c6bcc3423eb051118a9e3"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/2RZTkLUvLJOMjvbAtCXU7KE9l7M>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Sam Hartman <hartmans-ietf@mit.edu>, iesg@ietf.org, 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: Thu, 12 Mar 2015 15:01:54 -0000

Sam,

On Mar 12, 2015 9:34 AM, "Jari Arkko" <jari.arkko@piuha.net> wrote:
>
> Sam,
>
> Cutting to the 2nd item, i.e., what effect the ombudsteam might have on
leadership.
>
> I understand your concern Sam. Do you have a suggestion on how that
should be addressed? As an aside, I think we all agree that leadership that
misbehaves needs to be removed. The debate is about the mechanics - whether
those indirect through effects of action from the ombudsteam, indirect via
their recommendation, or more direct.

I just wanted to confirm that the IESG talked about the "recommendation to
remove" seriously, and IIRC, we couldn't figure out WHO the Ombudsteam
would make a recommendation to, much less what they might say.

It seemed cleaner to me, to say "the community already has an
IETF-consensus way to remove anyone in I-star leadership using a recall,
why not use that, instead of coming up with some other mechanism after IETF
Last Call?"

I am open to the possibility that this was the wrong answer. I've been
wrong before.

I look forward to understanding what people think better than I do today.

Spencer