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

Rich Kulawiec <rsk@gsp.org> Fri, 26 June 2009 10:09 UTC

Return-Path: <rsk@gsp.org>
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 1C5933A6985 for <asrg@core3.amsl.com>; Fri, 26 Jun 2009 03:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level:
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=-0.349, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 wVzkpPpTbHoW for <asrg@core3.amsl.com>; Fri, 26 Jun 2009 03:09:26 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by core3.amsl.com (Postfix) with ESMTP id 307B53A6855 for <asrg@irtf.org>; Fri, 26 Jun 2009 03:09:26 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.17.162.dsl.charm.net [207.114.17.162]) by taos.firemountain.net (8.14.1/8.14.1) with ESMTP id n5QA7g2I015765 for <asrg@irtf.org>; Fri, 26 Jun 2009 06:07:43 -0400 (EDT)
Received: from avatar.gsp.org (avatar.gsp.org [192.168.0.11]) by squonk.gsp.org (8.14.1/8.14.1) with ESMTP id n5QA30ox016106 for <asrg@irtf.org>; Fri, 26 Jun 2009 06:03:00 -0400 (EDT)
Received: from avatar.gsp.org (localhost [127.0.0.1]) by avatar.gsp.org (8.14.3/8.14.3/Debian-4) with ESMTP id n5QA7aT8029346 for <asrg@irtf.org>; Fri, 26 Jun 2009 06:07:36 -0400
Received: (from rsk@localhost) by avatar.gsp.org (8.14.3/8.14.3/Submit) id n5QA7aMj029345 for asrg@irtf.org; Fri, 26 Jun 2009 06:07:36 -0400
Date: Fri, 26 Jun 2009 06:07:36 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <20090626100736.GA29159@gsp.org>
References: <4A43B696.2000106@cybernothing.org> <4A449A7C.6070106@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4A449A7C.6070106@tana.it>
User-Agent: Mutt/1.5.18 (2008-05-17)
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: Fri, 26 Jun 2009 10:09:27 -0000

On Fri, Jun 26, 2009 at 11:53:00AM +0200, Alessandro Vesely wrote:
>
> That paper thickens the ranks of anti-anti-spam trenches. It is good as 
> it avoids an excess of proposal that would possibly result in a waste of 
> time for evaluating proposed techniques that don't come quite close to 
> the point. However, I think an it could, and should, go beyond that. For 
> example, why is it not in the scope of that document "to attempt to 
> distinguish or justify any more detailed definition of [the term spam]"? 

The canonical definition of spam (in the context of email) was settled
on a very long time ago ("unsolicited bulk email") and is NOT in need of
tinkering or refinement.  It's served us very well -- and one reason
why is that it's *deliberately* silent on a number of points.  It would
be a very serious mistake -- one that would greatly assist spammers --
to change that situation.

---Rsk