[Asrg] (no subject)

Richard Willey <richard_willey@symantec.com> Tue, 27 April 2004 15:11 UTC

Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06259 for <asrg-archive@odin.ietf.org>; Tue, 27 Apr 2004 11:11:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIUAi-0007tm-Pw for asrg-archive@odin.ietf.org; Tue, 27 Apr 2004 11:06:57 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RF6uqa030358 for asrg-archive@odin.ietf.org; Tue, 27 Apr 2004 11:06:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIU3w-0006I7-M6 for asrg-web-archive@optimus.ietf.org; Tue, 27 Apr 2004 10:59:56 -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 KAA05412 for <asrg-web-archive@ietf.org>; Tue, 27 Apr 2004 10:59:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIU3q-0003og-7I for asrg-web-archive@ietf.org; Tue, 27 Apr 2004 10:59:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIU2r-0003m1-00 for asrg-web-archive@ietf.org; Tue, 27 Apr 2004 10:58:50 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BIU1u-0003k1-00 for asrg-web-archive@ietf.org; Tue, 27 Apr 2004 10:57:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BITtP-0004ES-VM; Tue, 27 Apr 2004 10:49:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BITma-0003AR-Jd for asrg@optimus.ietf.org; Tue, 27 Apr 2004 10:42:00 -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 KAA04603 for <asrg@ietf.org>; Tue, 27 Apr 2004 10:41:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BITmU-00034E-0J for asrg@ietf.org; Tue, 27 Apr 2004 10:41:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BITlb-00032C-00 for asrg@ietf.org; Tue, 27 Apr 2004 10:40:59 -0400
Received: from navgwout.symantec.com ([198.6.49.12]) by ietf-mx with esmtp (Exim 4.12) id 1BITkf-0002xa-00 for asrg@ietf.org; Tue, 27 Apr 2004 10:40:01 -0400
Received: from navgwout.symantec.com (localhost [127.0.0.1]) by navgwout.symantec.com (8.11.7p1+Sun/8.11.7) with SMTP id i3REdX124766 for <asrg@ietf.org>; Tue, 27 Apr 2004 07:39:33 -0700 (PDT)
Received: from uscu-smtpob01-1.symantec.com ([155.64.74.130]) by navgwout.symantec.com (SAVSMTP 3.1.2.35) with SMTP id M2004042707393213577 for <asrg@ietf.org>; Tue, 27 Apr 2004 07:39:33 -0700
In-Reply-To: <20040426160004.11664.33737.Mailman@www1.ietf.org>
To: asrg@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
From: Richard Willey <richard_willey@symantec.com>
X-MIMETrack: S/MIME Sign by Notes Client on Richard Willey/Cupertino/Cal/SYMANTEC(Release 6.0.2CF1|June 9, 2003) at 04/27/2004 10:37:20 AM, Serialize by Notes Client on Richard Willey/Cupertino/Cal/SYMANTEC(Release 6.0.2CF1|June 9, 2003) at 04/27/2004 10:37:20 AM, Serialize complete at 04/27/2004 10:37:20 AM, S/MIME Sign failed at 04/27/2004 10:37:20 AM: The cryptographic key was not found, Serialize by Router on USCU-SMTPOB01-1/GLOBE-ADMIN/SYMANTEC(602CF1HF35 | July 14, 2003) at 04/27/2004 07:39:33 AM, Serialize complete at 04/27/2004 07:39:33 AM
Message-ID: <OFC0C3FCFE.42EB83EE-ON85256E83.004EF5DD-85256E83.005085DD@symantec.com>
Content-Type: text/plain; charset="US-ASCII"
Subject: [Asrg] (no subject)
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/mail-archive/working-groups/asrg/>
Date: Tue, 27 Apr 2004 07:39:31 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

>>3. The mailing list should not focus on implementing its own 
Micropayment 
>>architecture, but rather:
>>
>>(a) Determine whether a working micropayment architecture would 
represent 
>>a feasible solution to SPAM
>>(b) Determine whether an E-Postage system would create a unique set of 
>>requirements for a working micropayments architecture.
>>(c) Attempt to ballpark a set of parameters that describe the boundary 
>>conditions necessary to make an E-Postage system feasible. ...

> ... which remains entirely hypothetical since nobody has any idea how
>to build a micropayment system within a couple of orders of magnitude
>of what you'd need for any plausible e-mail system.  The unique
>requirement is be that the vast majority of attempted transactions
>would be bogus which rules out a lot of statistical approaches, but
>it's the scale that's the killer.

Not sure whether I necessarily buy into this assertion:

One size does not fit all, and an anti-SPAM solution that is appropriate 
for one set of mail exchanges will not necessarily be applied to all mail 
exchanges.

When I think about email, I differentiate between two different types of 
transactions:

One set of exchanges occurs went I communicate with a relatively small 
group of individuals with whom I have some sort of trust relationship:

This includes:

(a) The people that I work with
(b) My friends
(c) My family

These transactions encompass the vast majority of the emails that I send 
and receive.
Equally significant, they don't require any type of E-Postage or 
Micropayments.
Instead, some combination of whie listing and digital signatures 
represents a very efficient solution to this type of communications.

However, there is a second set of email exchages that I need to consider. 
On occasion, I receive emails from "random" individuals with whom I don't 
have any kind of pre-existing trust relationship.
While these exchanges are relatively infrequent, they often contain 
important information.

Here, we require some form of additional solution that can be used to 
screen the wheat from the chaff.
There are a wide variety of technical solutions that have been proposed 
including:

(a) Challenge Response
(b) Micro-Payments
(c) Intelligent Filters.

Personally, I think that the Micro-Payment systems offer the best 
approach.
This is technology that is going to be adopted / deployed anyway and I'd 
just as soon piggyback off it.

Your arguments that the system would collapse under transaction volume 
seem to assume that all emails would need to E-Postage rather than a 
selective subset.



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