Re: IESG Statement on Spam Control on IETF Mailing Lists

"Tom.Petch" <sisyphus@dial.pipex.com> Tue, 15 April 2008 14:13 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 C638228C139; Tue, 15 Apr 2008 07:13:54 -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 3B0D73A6EC9; Tue, 15 Apr 2008 07:13:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 NXYZWnI4UnqX; Tue, 15 Apr 2008 07:13:52 -0700 (PDT)
Received: from mk-outboundfilter-5.mail.uk.tiscali.com (mk-outboundfilter-5.mail.uk.tiscali.com [212.74.114.1]) by core3.amsl.com (Postfix) with ESMTP id CDAB63A6B1F; Tue, 15 Apr 2008 07:13:51 -0700 (PDT)
X-Trace: 7223770/mk-outboundfilter-5.mail.uk.tiscali.com/PIPEX/$ACCEPTED/pipex-customers/62.188.120.129
X-SBRS: None
X-RemoteIP: 62.188.120.129
X-IP-MAIL-FROM: sisyphus@dial.pipex.com
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap8EAEhVBEg+vHiB/2dsb2JhbACLR6FoBA
X-IP-Direction: IN
Received: from 1cust129.tnt29.lnd3.gbr.da.uu.net (HELO allison) ([62.188.120.129]) by smtp.pipex.tiscali.co.uk with SMTP; 15 Apr 2008 15:14:22 +0100
Message-ID: <04b601c89efa$191861a0$0601a8c0@allison>
From: "Tom.Petch" <sisyphus@dial.pipex.com>
To: iesg <iesg@ietf.org>
References: <20080414153938.0A5153A6D4D@core3.amsl.com>
Subject: Re: IESG Statement on Spam Control on IETF Mailing Lists
Date: Tue, 15 Apr 2008 15:08:31 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "Tom.Petch" <sisyphus@dial.pipex.com>
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

----- Original Message -----
From: "IESG Secretary" <iesg-secretary@ietf.org>
To: "IETF Announcement list" <ietf-announce@ietf.org>
Cc: <iesg@ietf.org>; <ietf@ietf.org>
Sent: Monday, April 14, 2008 5:39 PM
Subject: IESG Statement on Spam Control on IETF Mailing Lists


> The following principles apply to spam control on IETF mailing lists:
>
> * IETF mailing lists MUST provide spam control.

And what is spam?  I have seen this discussed on several occasions on lists
whose prime concern is spam and there has been no rough consensus.  For example,
Phillip Hallam-Baker, on asrg, summed up one discussion well with
"OK so defining the term spam is off limits to the group because it ends up in
definitional flame wars."

For me, it is dead obvious that the 397kbyte PowerPoint file I received on an
IETF list last week is spam, and I know some IETF moderators who would not have
allowed it on to the list; but equally, I am sure that the sender would protest
his innocence.

If we do not agree what spam is, then the whole of this statement seems to me
pointless.

Tom Petch


> * Such spam control SHOULD track accepted practices used on the Internet.
> * 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.
> * IETF mailing lists MUST provide a mechanism for legitimate technical
> participants to determine if an attempt to post was dropped as apparent
> spam.
> * The Internet draft editor, RFC editor, IESG secretary, IETF chair and
> IANA MUST be able to post to IETF mailing lists. The relevant identity
> information for these roles will be added to any white-list mechanism used
> by an IETF mailing list.
> * There MUST be a mechanism to complain that a message was inappropriately
> blocked.
>
> The realization of these principles is expected to change over time.
> List moderators, working group chairs and area directors are expected to
> interpret these principles reasonably and within the context of IETF
> policy and philosophy.
>
> This supercedes a previous IESG statement on this topic:
> http://www.ietf.org/IESG/STATEMENTS/mail-submit-policy.txt
> That statement contains justification and implementation advice that may
> be helpful to anyone applying these principles.
>
> A separate IESG statement applies to moderation of IETF mailing lists:
> http://www.ietf.org/IESG/STATEMENTS/moderated-lists.txt
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf