Re: What is a "management position? [Last Call: <draft-farrresnickel-harassment-05.txt> (IETF Anti-Harassment Procedures) to Best Current Practice]

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 17 March 2015 19:13 UTC

Return-Path: <brian.e.carpenter@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 0B42A1A1BC0; Tue, 17 Mar 2015 12:13:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 R6tiifEiFtCU; Tue, 17 Mar 2015 12:13:09 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (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 6B1EB1A1B66; Tue, 17 Mar 2015 12:13:09 -0700 (PDT)
Received: by pdbop1 with SMTP id op1so17898175pdb.2; Tue, 17 Mar 2015 12:13:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=I8mcpxq04QE3lOdfcJrr4HhWtehokXcHdpOu1tqwDf0=; b=BQ6+e6PAHQnrrbFrYsHUkqYQ0CRRKIPlaUIWKeHL/hMgDjnNvaolvphkGuYpqDciLu qKgVq3kdPx17x8EXOQPZwTyNBQACo4ua8iv4aH52fgc/SMtm5eJUhpyOBs02COVdhD5d KWAppcaUhQvWStdhtuCarmgcTDlXU4Ofrv+PSvthXRY6CgnNZnXye7BCK16LvMv9BGOy pnik83VxLvRORMTKmi6Hgsl8/T7LrVWrio9VBtkrZ3diYaYdNEy2+iC3jIYQ+linqukC rbAf6ghVEobuLaUZYecmfAjApFFRk63RaxaIvU3UZvU7SaSJ7vr8kHVdlS+JTPB9K4F7 hcmA==
X-Received: by 10.66.221.135 with SMTP id qe7mr151088875pac.97.1426619587963; Tue, 17 Mar 2015 12:13:07 -0700 (PDT)
Received: from ?IPv6:2406:e007:690c:1:28cc:dc4c:9703:6781? ([2406:e007:690c:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id x1sm23690359pdp.1.2015.03.17.12.13.03 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Mar 2015 12:13:06 -0700 (PDT)
Message-ID: <55087CC2.8070300@gmail.com>
Date: Wed, 18 Mar 2015 08:13:06 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>, "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: What is a "management position? [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> <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> <tsly4n0zo6g.fsf@mit.edu> <550350C4.9040201@qti.qualcomm.com> <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> <678E9B71-0D17-4FD2-BBCF-5F425A1707EC@cisco.com> <tsl4mpjr0mm.fsf@mit.edu>
In-Reply-To: <tsl4mpjr0mm.fsf@mit.edu>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/S291lTFcInZJtTlKf1otUXp5ocg>
Cc: "iesg@ietf.org" <iesg@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, IETF Discussion List <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: Tue, 17 Mar 2015 19:13:11 -0000

On 18/03/2015 06:32, Sam Hartman wrote:
>>>>>> "Fred" == Fred Baker (fred) <fred@cisco.com> writes:
> 
>     Fred> Someone else suggested “subject to the recall procedures”; I
>     Fred> second that. Consider, if you will, what the process for
>     Fred> removing a document author would actually be? I think it
>     Fred> would, perhaps, be an appeal, not a recall.
> 
> An appeal is clearly also the wrong approach for dealing with
> harassment-related complaints.
> 
> I continue to believe that it's desirable to allow the Ombudsteam to
> remove anyone who is not subject to a recall procedure.

It's hard to fault that logic. But we are kidding ourselves if we
think that confidentiality will always be preserved in that case.

There is running code. Where I live (New Zealand), there is very
strong legal support for "name suppression" by a court. It's quite
common for "a prominent New Zealander" to be charged with, and
convicted of, a serious offence against another person but to retain
name suppression, and it's a crime to reveal that name in any way.
But this is a small country, and if you are interested, it generally
takes about 5 minutes with Google to find the name. If I cited examples,
I'd be breaking the law. The IETF is an even smaller country.

A side effect is that victim's names sometimes leak too. I'm afraid
that is an unavoidable risk, but it means that the solution becomes
part of the problem.

  Brian