Re: Possible RFC 3683 PR-action

John Levine <johnl@iecc.com> Tue, 25 March 2008 15:47 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD80A28C1AD; Tue, 25 Mar 2008 08:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.073
X-Spam-Level:
X-Spam-Status: No, score=-102.073 tagged_above=-999 required=5 tests=[AWL=-1.536, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RCVD_IN_BSP_OTHER=-0.1, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AOnNRaQjcPdH; Tue, 25 Mar 2008 08:47:16 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E58413A6ADD; Tue, 25 Mar 2008 08:47:15 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A95A63A6A55 for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 08:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sKpfFPRsjxdG for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 08:47:09 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id AE04E3A6ADD for <ietf@ietf.org>; Tue, 25 Mar 2008 08:47:08 -0700 (PDT)
Received: (qmail 38919 invoked from network); 25 Mar 2008 15:44:46 -0000
Received: from simone.iecc.com (208.31.42.47) by mail1.iecc.com with QMQP; 25 Mar 2008 15:44:46 -0000
Date: Tue, 25 Mar 2008 15:44:46 -0000
Message-ID: <20080325154446.17333.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Possible RFC 3683 PR-action
In-Reply-To: <02a401c88e86$32be8e10$6401a8c0@china.huawei.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>o how widespread, and how frequent, a problem this is,

In terms of the number of people, it's tiny.  I can only think of
three incorrigibly abusive people that bother the IETF, and even if I
polled everyone here to name candidates, I doubt that I'd run out of
fingers.

On the other hand, the amount of time that they waste is enormous,
because they abuse processes designed to deal with people whose
misbehavior is ambiguous and temporary, which theirs is not.  If
someone doesn't get the hint to behave after one or two taps on the
wrist, they'll never get it and it's a waste of time to keep grinding
through processes to re-re-re-eject them.  In view of the fact that
the same people come back to annoy us year after year after year, we
really need efficient ways to make them go away permanently.  I also
observe that they tend to have, ah, characteristic writing styles that
makes it rather easy to recognize when they've grown another
personality.

So rather than inventing yet more complex rules, I would be inclined
to have a much simpler rule that says that if a group's leader sees
mail from someone who is obviously You Know Who or You Know Who Else
already subject to 3683, just block it and send out a one sentence
notice reporting it.  Then return to useful work.

Regards,
Glenn Curtiss
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf