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

John C Klensin <john-ietf@jck.com> Tue, 22 October 2013 18:50 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 0C90921F9EF2 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.55
X-Spam-Level:
X-Spam-Status: No, score=-103.55 tagged_above=-999 required=5 tests=[AWL=0.049, 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 W5OfIN+161wr for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:50:15 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4979821F9F2D for <ietf@ietf.org>; Tue, 22 Oct 2013 11:50:09 -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 1VYh1s-0003Zk-MC; Tue, 22 Oct 2013 14:50:08 -0400
Date: Tue, 22 Oct 2013 14:50:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Message-ID: <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com>
In-Reply-To: <5266C6CA.30900@gmail.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>
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
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 18:50:36 -0000

Although I usually object to doing this, +1.  Well stated and I
strongly concur.

    john


--On Tuesday, October 22, 2013 10:41 -0800 Melinda Shore
<melinda.shore@gmail.com> wrote:

> The more I've been thinking about this the less comfortable
> I am with how this was executed.  I have no disagreement
> whatsoever with removing this person's posting privileges.
> But, I have a huge problem with Jordi's statement:
> 
>   "As Sergeant-at-arms, I agree with other previous
>   postings and believe that anonymous posting is not
>   tolerable in the IETF mail exploders."
> 
> Clearly, there are non-trivial problems around making decisions
> on the basis of something sort of like identity in
> unauthenticated email.  We don't *really* know who other
> people are - we tend to assume that they are who they say they
> are and evaluate their credibility (or not) on things like
> content, reputation, past performance, etc.  The problem with
> mars.techno.cat@gmail.com isn't that he (and since we're
> pretty sure we know who this is, we'll stick with masculine
> pronouns) has an email address that doesn't look like a name
> (although his name could have been Mars Techno Cat, as
> unlikely as that is).  The problem is that he had no prior
> history of posting -as that name- and posted nothing but
> off-topic rants and personal attacks. I would hope that the
> attacks would be sufficient to have his posting privileges
> revoked and that having an unfamiliar email address would not
> be sufficient.
> 
> Additionally, let me suggest that finding anonymous posts
> "not tolerable" is inconsistent with the perpass discussions
> and concerns expressed *here* about privacy.
> We want accountability in our documents and that means knowing
> that the people who contribute to our work 1) have technical
> substance, and 2) are having their comments and text evaluated
> by other people of technical substance.  It does not
> necessarily mean knowing their names or identities.  In many
> discussions about privacy and about whether or not various
> cryptographic technologies have been deliberately weakened by
> some US government agency, there have been repeated assertion
> that open processes and aggressive review provide protection
> against that sort of problem.  That ought to apply here, as
> well.
> 
> Anonymity is not a problem.  Behaving badly is a problem.
> I really never want to see someone's ejection justified on
> the basis of their putative "anonymity" again.  I am not
> arguing that mars.techno.cat@gmail.com ought to be allowed
> anywhere near an IETF mailing list but that the reason that
> was given for throwing him off was not correct.  We should
> be working to protect anonymity and privacy, not punishing it.
> 
> Melinda