Re: IESG Statement on Spam Control on IETF Mailing Lists

John Levine <johnl@iecc.com> Tue, 15 April 2008 05:07 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DE4A3A6BF9; Mon, 14 Apr 2008 22:07:44 -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 B825C3A6BF9 for <ietf@core3.amsl.com>; Mon, 14 Apr 2008 22:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.489
X-Spam-Level:
X-Spam-Status: No, score=-8.489 tagged_above=-999 required=5 tests=[AWL=2.410, BAYES_00=-2.599, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_MED=-4]
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 QL3Pstm6dSM4 for <ietf@core3.amsl.com>; Mon, 14 Apr 2008 22:07:41 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 654D23A68D9 for <ietf@ietf.org>; Mon, 14 Apr 2008 22:07:41 -0700 (PDT)
Received: (qmail 26338 invoked from network); 15 Apr 2008 05:06:34 -0000
Received: from simone.iecc.com (208.31.42.47) by mail1.iecc.com with QMQP; 15 Apr 2008 05:06:34 -0000
Date: Tue, 15 Apr 2008 05:08:12 -0000
Message-ID: <20080415050812.1946.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: IESG Statement on Spam Control on IETF Mailing Lists
In-Reply-To: <01MTMMIYGP88001WS1@mauve.mrochek.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Cc: ned.freed@mrochek.com
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

>> > * IETF mailing lists MUST provide a mechanism for legitimate technical
>> > participants to bypass moderation, challenge-response, or other techniques
>> > that would interfere with a prompt technical debate on the mailing list
>> > without requiring such participants to receive list traffic.
>
>> Here, again, is something that is not a technical specification and
>had no clear criterion ...
>
>The goal is simple: Whitelisting.

I had the same problem with it as everyone else.  If you say it's
supposed to mean that list managers can whitelist people, that's fine,
but in that case it desperately needs to be rewritten so it says what
it means, e.g.:

* IETF lists MUST provide a mechanism that allows list managers to
whitelist mail from legitimate technical participants to bypass
moderation and spam filters, and to allow one-way participation for
people who are too important to spend time reading or dealing with
responses to their mail.

R's,
John
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf