Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com

John C Klensin <john-ietf@jck.com> Tue, 22 October 2013 21:49 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A5F911E8269 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:49:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.552
X-Spam-Level:
X-Spam-Status: No, score=-103.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9d4XOogIiX6q for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:49:11 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5F67111E8276 for <ietf@ietf.org>; Tue, 22 Oct 2013 14:48:24 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VYjo7-0003n5-EH; Tue, 22 Oct 2013 17:48:07 -0400
Date: Tue, 22 Oct 2013 17:48:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Randy Bush <randy@psg.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Message-ID: <1812343AEDF0C2F4312AC768@JcK-HP8200.jck.com>
In-Reply-To: <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Oct 2013 21:49:20 -0000

--On Tuesday, October 22, 2013 21:21 +0000 Ted Lemon
<Ted.Lemon@nominum.com> wrote:

> On Oct 22, 2013, at 4:55 PM, Randy Bush <randy@psg.com> wrote:
>> i am a bit taken aback by the vigilantism.  
>> 
>> it was just an email message, and a factual one at that.  the
>> usual example is _falsely_ shouting "fire" specifically
>> because it can cause *actual* *physical* *harm*.  get a
>> delete key.  get procmail.  get a grip.
> 
> Right, that's not the policy.   If that were the policy, a
> number of notorious abusers of the mailing list would still
> have posting privileges.
> 
> If the first message had been the beginning of a conversation,
> I would have taken it a lot differently, but the way it was
> dropped on the list with no discussion, it just looked like an
> attempt to start a massive flame war.   That's exactly the
> sort of thing that the sergeant-at-arms is supposed to deal
> with.

Ted, that is, IMO, an entirely reasonable comment about
inappropriate content, but, even then, our normal practice is
for the sergeant-at-arms or some other appropriate parties to
discuss and warn (usually and preferably in private first), not
take preemptive action.  "Discuss and warn first" may be a
first-order approximation to Randy's observation about due
process, or at least part of it.

The other thing that may make this situation special is that
several people are convinced that, despite the new address, the
person who made the posting is a serial (or, in your terms,
"notorious") abuser who has been banned from IETF lists before.
If that is actually the case, then preemptive action to prevent
further postings is appropriate, possibly including initiating
the RFC 3683 procedure and being done with this.

But none of that has anything to do with anonymity.  

I think it is reasonable to expect that, if the sergeant-at-arms
concludes that public action is necessary, that action and the
reasoning for it be carefully and precisely explained and even
adjusted for the record after the fact if the explanation wasn't
quite right.  If nothing else, getting the right documentation
in place is very important should anyone ever decide to
initiation a 3683-style global posting rights action.

I do not intend to criticize Jordi in any of this.  We
(fortunately) rarely have the provocation and need to do this.
We need to rely on good judgment rather than collections of
specific-seeming rules that would, themselves, be likely sources
of controversy and his judgment has generally been good.  We
should, however, all try to learn from experience, including
this one.

And, fwiw, I think we should try to see what can be learned that
might apply to harassment complaints.  By their nature, IMO,
those complaints are much more likely to be subjective and
difficult than whether someone has abused or improperly used a
mailing list.

   best,
   john