Re: [Asrg] draft-irtf-asrg-criteria (was Re: request for review for a non FUSSP proposal)

Alessandro Vesely <vesely@tana.it> Wed, 01 July 2009 12:47 UTC

Return-Path: <vesely@tana.it>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F3FA28C516 for <asrg@core3.amsl.com>; Wed, 1 Jul 2009 05:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[AWL=-0.181, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, SARE_SUB_RAND_LETTRS4=0.799]
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 J4PD9T+d3DUR for <asrg@core3.amsl.com>; Wed, 1 Jul 2009 05:47:33 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 0F29D28C54F for <asrg@irtf.org>; Wed, 1 Jul 2009 05:40:57 -0700 (PDT)
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 ale@tana.it, TLS: TLS1.0, 256bits, RSA_AES_256_CBC_SHA1) by wmail.tana.it with esmtp; Wed, 01 Jul 2009 14:34:16 +0200 id 00000000005DC030.000000004A4B57C8.00004968
Message-ID: <4A4B57C8.2000207@tana.it>
Date: Wed, 01 Jul 2009 14:34:16 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4A43B696.2000106@cybernothing.org> <4A449A7C.6070106@tana.it> <4A452A12.2070302@cybernothing.org> <5ec229170906300004m687af225vf5a3f621646f5fcb@mail.gmail.com> <CFF41897-E082-47C1-938D-4D747CC1FB59@blighty.com>
In-Reply-To: <CFF41897-E082-47C1-938D-4D747CC1FB59@blighty.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] draft-irtf-asrg-criteria (was Re: request for review for a non FUSSP proposal)
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jul 2009 12:47:34 -0000

Steve Atkins wrote:
> On Jun 30, 2009, at 12:04 AM, Danny Angus wrote:
>> Actually I would have liked to have included *some* definition, but 
>> because members of this group hold pretty entrenched opinions covering 
>> most possible definitions I felt that on the one hand it would be 
>> impossible and on the other hand it would be unnecessary.
>>
>> I believe that it is unnecessary for two reasons, the first being that 
>> this group cannot agree a definition, yet operates reasonably 
>> successfully, and secondly there can be an empirical test for a 
>> solution, even if there is no agreed definition of spam itself.

In that case, the criteria draft should not give a definition at all. 
Instead, it should mention that proposed techniques may give the 
definition of the phenomenon they are intended to operate against, if 
necessary. A warning against incautious use of the term "spam" would 
be in order, since it is an undefinable term. It may or may not be 
useful to enumerate some of the existing definitions.

> The problem arises when someone, anyone, claims that there is 
> One True Definition of spam. The fact that that's blatantly false 
> isn't the problem. That it causes hordes of people to come out of 
> the woodwork to argue for their One True Definition of spam, causing 
> yet another rerun of the Thread That Would Not Die is the problem.

Agreed. However, the anti-spam endeavor should not have the tones of a 
religious debate. It's not. One reason why I would have liked to 
classify objections against a tentative definition is to understand 
where does that holy war spirit originate from. Is it still strong as 
in the MARID epoch, or has that lesson been learned? I'm not sure 
whether those hordes, or the thoughts that trouble them, thwart more 
than just definitions.

(The other reason is that definitions are generally useful. They are 
not true or false, they define something. They may be good or bad, 
though. Good definitions provide constructive hints; for example, the 
U in UBE suggests that a technique might attempt to maintain a 
register of presupposed solicitations.)

> (A problem that's usually best solved by killfiling anyone participating
> in that sort of thread).

I believe you meant fundamentalists rather than mere participants. I 
hope I'm not stamping on anyone's feet if I rise these questions. I do 
so because I can't stand the perpetual failure to effectively counter 
mail abuse. IMHO, it must be related to some wicked cripples that 
undermine anti-spam work. New solutions arouse no interest, 
independently of their technical content. Some bafflingly conclude 
that spam is a natural fact of life, that cannot be even diminished, 
and any solution would only alter its delivery mechanisms. Preemptive 
rebuttal, I don't think it's sane. Marketing may be considered a 
natural fact of life, if regarded as the commercial facet of Darwinian 
evolution. However, if direct marketing is considered spam, the 
"spammers-are-stupid*" entries of Rhyolite's list, hinging on the 
assumption that spammers won't respect RFCs, may not apply.

It will be helpful for newcomers if Danny's paper will have an 
Introduction that explains the questions I've been tried to address 
above --lengthily and vaguely, as I don't know the answers myself. 
Bill mentioned a "dynamic equilibrium" in [1], depicting a chronic 
syndrome that can only be alleviated by a "really big push". Even if 
that's not a satisfactory answer, his words help understanding the 
problem.

--
[1 http://www.ietf.org/mail-archive/web/asrg/current/msg15369.html]