Re: [Asrg] Point of information...

Yakov Shafranovich <research@solidmatrix.com> Fri, 20 June 2003 22:11 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12155 for <asrg-archive@odin.ietf.org>; Fri, 20 Jun 2003 18:11:33 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5KMB6o25894 for asrg-archive@odin.ietf.org; Fri, 20 Jun 2003 18:11:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TU66-0006jZ-OR for asrg-web-archive@optimus.ietf.org; Fri, 20 Jun 2003 18:11:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12091; Fri, 20 Jun 2003 18:11:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TU64-0003tw-00; Fri, 20 Jun 2003 18:11:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19TU63-0003tt-00; Fri, 20 Jun 2003 18:11:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TU61-0006hc-Vh; Fri, 20 Jun 2003 18:11:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TU5b-0006hH-NQ for asrg@optimus.ietf.org; Fri, 20 Jun 2003 18:10:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12040 for <asrg@ietf.org>; Fri, 20 Jun 2003 18:10:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TU5Z-0003tk-00 for asrg@ietf.org; Fri, 20 Jun 2003 18:10:33 -0400
Received: from 000-228-098.area5.spcsdns.net ([68.27.130.7] helo=68.27.130.7 ident=trilluser) by ietf-mx with smtp (Exim 4.12) id 19TU5X-0003th-00 for asrg@ietf.org; Fri, 20 Jun 2003 18:10:31 -0400
Message-Id: <5.2.0.9.2.20030620175628.00b92600@std5.imagineis.com>
X-Sender: research@solidmatrix.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
To: Barry Shein <bzs@world.std.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: Re: [Asrg] Point of information...
Cc: asrg@ietf.org
In-Reply-To: <16115.32269.783632.400725@world.std.com>
References: <5.2.0.9.2.20030619221149.00b67008@std5.imagineis.com> <200306192120.RAA16724@world.std.com> <5.2.0.9.2.20030619221149.00b67008@std5.imagineis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-MimeHeaders-Plugin-Info: v2.03.00
X-GCMulti: 1
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Fri, 20 Jun 2003 18:10:14 -0400

At 05:35 PM 6/20/2003 -0400, Barry Shein wrote:


>On June 19, 2003 at 22:14 research@solidmatrix.com (Yakov Shafranovich) wrote:
>  > The legal aspect is not within the scope of our group and even if it was,
>  > there isn't much we can do anyway. So what technical solutions in this 
> area
>  > are possible?
>  >
>  > Yakov
>
>Virtually all proposals here imply a legal aspect. For example, RMX
>implies prevention of identity fraud, a crime. RMX (and related) is
>always proposed as a way to thwart those who are trying to
>fraudulently identify themselves as having some affiliation with
>another, usually readily recognizable, institution. That's illegal, so
>your comments would apply to their problem definition.
>
>What we haven't seemed to converge on is what is the root of the
>problem, where are efforts best expended, etc. Even if some are
>anxious to just get on with proposed solutions lacking any foundation
>in reality.
>
>I am asserting that the source of the actual problem with spam is the
>amplification of the distribution channel through illegal exploitation
>of others' resources (computation and bandwidth, via viruses.)
>
>If that's the case and I'm correct then expending effort on (e.g.)
>weak authentication schemes such as RMX is mostly a waste of time IN
>THIS SPHERE (it might still be useful for other problems, in fact I
>think it is.)
>
>There's a lot more to spam than knowing you don't want another penis
>enlargement message in your mailbox or that some of the header might
>be unreliable or the body trickily encoded with base64,
>quoted-printable and/or images.
>
>Yet those aspects get virtually all the attention here, primarily
>because they're easily understood by dabblers who haven't really come
>to understand the problem and believe they can work entirely from two
>pieces of information: what spam messages usually look like, and some
>mental model of how SMTP works.
>
>I am asserting that this is fool's gold and of little or no value to
>the perceived purpose of this group.
>
>The problem is how spammers amplify their distribution channels while
>keeping costs nearly at zero. Without this, they would virtually cease
>to exist.
>
>Given some agreement and more importantly realization that this is
>indeed the problem then we can proceed to have a meaningful dialogue
>on what possible counter-measures exist.
>
>But don't be so impatient demanding both a problem description and
>solution in one bite. You had trouble even digesting just the problem
>description alone.

So your bottom line is that the spam problem is based on "how spammers 
amplify their distribution channels while keeping costs nearly at zero." 
Legally pursuing spammers is not something we can affect or do in this 
group. But what we CAN do, is look at these aspects closer and see if any 
technical solutions are possible.

There are several approaches that have been mentioned that might have 
relevance to this. First of all, making sure email is not untraceble allows 
for LEA to catch the spammers. This would involve either changing SMTP, 
implementing C/R, or some other system that would allow for traceability. 
Domain names being owned by spammers is a problem too. Solutions must be 
made to deal with that as well. Foreign ISPs, allowing for spam are also a 
problem. And as you have mentioned many times before computers infected 
with viruses and other similar junk are a problem as well, although I do 
not see any possible solutions for that as well, not even any avenues of 
research.

Yakov





_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg