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

Donald Eastlake <d3e3e3@gmail.com> Mon, 21 October 2013 19:07 UTC

Return-Path: <d3e3e3@gmail.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 7DB8111E865C for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 yTuqaEqI-RDm for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:07:01 -0700 (PDT)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id CACF511E86E6 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:03:17 -0700 (PDT)
Received: by mail-oa0-f47.google.com with SMTP id i18so2396642oag.20 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:03:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ngTTxdTgNBKNTX3cu5tsE4fkydDW6qEKkAu00MiET9g=; b=guFEiIp1qv9IzHZkgq6DPeFGKaUfY11IX6Xg/twx6gCgHhjHczp9an5jIjlQYEMesp E7/UK9o/sHV+UgrUj1gyXn2IvRTnIBt1FZeg53bXvwUi7/l5MLyQjU7Vlst0VTDo++9D cAeGwaEwnEwwW9hOA7UaB86YSeklrWSloBcLQU0VABWgI+72pEdp1WuHU4/dO+P8MPjm e3me+ZUwMNYLfArhWqtzOsm+Hz+V0K4hr3TTFsTViD5YUVifWm4L2lg3EMv+OUmD3bFa yvCGYdaIw6qhfJ2YSWP7nQ00tfy+BPqbxkXBFTgQGlaFaLpU2zjI9HRMdEtFVivr0rQT tqJA==
X-Received: by 10.182.44.167 with SMTP id f7mr21950574obm.3.1382382188397; Mon, 21 Oct 2013 12:03:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.33.102 with HTTP; Mon, 21 Oct 2013 12:02:48 -0700 (PDT)
In-Reply-To: <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 21 Oct 2013 15:02:48 -0400
Message-ID: <CAF4+nEHQ_pXS7t=Smf-9QGSj2whXNfYuK8f8FAEmRyhm9HpRCg@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
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: Mon, 21 Oct 2013 19:07:02 -0000

And we see below a perfect illustration of the difficulties that can
be caused by codification.

Three orthogonal points:

- We should be very careful to have only "guidelines" such that it is
clear any action based on those guidelines is only taken as a
judgement call by an authorized person or group and their is no
guarantee any action at all will be taken. Having "rules" or anything
that appears to guarantee enforcement and you may find people suing
you for failure to take immediate action when the infraction was the
most minor or arguable thing.

- I am very suspicious of the word "professional". Who knows what the
hell it means? Is the previous sentence "unprofessionally" worded? If
you think so, good. I typically see "unprofesional" used as a cudgel
against the strong expression of opinions the critic does not like
when they have no real counter argument to those opinions. Is the
April 1st RFC series something a professional group would do? I think
not. I don't know that a choice is necessary but I would prefer for
the IETF to call itself an "amateur" organization rather than a
"professional" organization.

- Generally, people should be allowed to comment causticly on others
actions but not on their motivations. If I say an action is
"obstructive" or whatever, well, that could be a matter of opinion but
at least in the open IETF process, people can see the action and might
or might not agree with me. If I say an action is "intended to be
obstructive", then, unless I am commenting on my own actions or the
actor has so stated, I am claiming the ability to mind-read...

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Mon, Oct 21, 2013 at 2:04 PM, Techno CAT <mars.techno.cat@gmail.com> wrote:
> "Calling someone a troll is an ad hominem. We aren't supposed to do that in
> the IETF. At least, not publicly."[1]
>
> "It is rude.
> It is bullying." [2]
>
> HARASSMENT by Brian E Carpenter has been noted for the Legal Record
>
> http://www.cs.auckland.ac.nz/~brian/
> "Network Geeks - How They Built the Internet"
>
> ===========================
>
> HARASSMENT by Stephane Bortzmeyer <bortzmeyer at nic.fr> has been noted for
> the Legal Record
> http://www.ietf.org/mail-archive/web/ietf/current/msg83330.html
>
> ===========================
>
> http://www.ietf.org/mail-archive/web/ietf/current/msg83360.html
> "judgment needs to be applied by the ombudsperson & the rest of the IETF
> management
>
> [1] http://www.ietf.org/mail-archive/web/ietf/current/msg83364.html
> [2] http://www.ietf.org/mail-archive/web/ietf/current/msg83362.html
>
> "you are encouraged to raise your concern in confidence with one of the
> Ombudspersons"
>
> http://www.intgovforum.org
> http://990s.foundationcenter.org/990_pdf_archive/541/541650477/541650477_201112_990.pdf
>
>
>
> On Sat, Oct 19, 2013 at 4:37 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>>
>> Hi Jordi,
>>
>> We seem to have a new troll using the address mars.techno.cat@gmail.com
>>
>> Can you deal with it appropriately, please?
>>
>> Thanks
>>
>>     Brian
>>
>
>
>
> --
>
> @Techno_CAT_r
> http://Twitter.com/Techno_CAT_r