Re: [Asrg] 3. Proof-of-work analysis

Richard Clayton <richard@highwayman.com> Tue, 18 May 2004 16:41 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26453 for <asrg-archive@odin.ietf.org>; Tue, 18 May 2004 12:41:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ7TZ-0004a2-Fs for asrg-archive@odin.ietf.org; Tue, 18 May 2004 12:29:57 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IGTvYj017606 for asrg-archive@odin.ietf.org; Tue, 18 May 2004 12:29:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ7H5-0001Fh-MM for asrg-web-archive@optimus.ietf.org; Tue, 18 May 2004 12:17:03 -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 MAA25273 for <asrg-web-archive@ietf.org>; Tue, 18 May 2004 12:17:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQ7H4-0004cx-EY for asrg-web-archive@ietf.org; Tue, 18 May 2004 12:17:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQ7GE-0004bA-00 for asrg-web-archive@ietf.org; Tue, 18 May 2004 12:16:11 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQ7Fs-0004Ya-00 for asrg-web-archive@ietf.org; Tue, 18 May 2004 12:15:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ70i-00040H-T8; Tue, 18 May 2004 12:00:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQ6yc-0003Ji-Is for asrg@optimus.ietf.org; Tue, 18 May 2004 11:57:58 -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 LAA24352 for <asrg@ietf.org>; Tue, 18 May 2004 11:57:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQ6yb-0003XR-At for asrg@ietf.org; Tue, 18 May 2004 11:57:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQ6xj-0003St-00 for asrg@ietf.org; Tue, 18 May 2004 11:57:04 -0400
Received: from anchor-post-32.mail.demon.net ([194.217.242.90]) by ietf-mx with esmtp (Exim 4.12) id 1BQ6wl-0003Pt-00 for asrg@ietf.org; Tue, 18 May 2004 11:56:03 -0400
Received: from gti.noc.demon.net ([195.11.55.101] helo=rnc1.al.cl.cam.ac.uk) by anchor-post-32.mail.demon.net with esmtp (Exim 3.35 #1) id 1BQ6wh-000D6d-0W for asrg@ietf.org; Tue, 18 May 2004 16:56:02 +0100
Message-ID: <mevaB4e60fqAFAu2@highwayman.com>
To: asrg@ietf.org
From: Richard Clayton <richard@highwayman.com>
Subject: Re: [Asrg] 3. Proof-of-work analysis
References: <LV1hjGBSmTqAFAry@highwayman.com> <CB27C1AA-A8AB-11D8-B336-000393863768@chromatix.demon.co.uk>
In-Reply-To: <CB27C1AA-A8AB-11D8-B336-000393863768@chromatix.demon.co.uk>
MIME-Version: 1.0
X-Mailer: Turnpike Integrated Version 5.01 M <7fPN0OjtGdv6AX1irDkRphaT6+>
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, 18 May 2004 13:10:34 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,DATE_IN_PAST_03_06 autolearn=no version=2.60

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <CB27C1AA-A8AB-11D8-B336-000393863768@chromatix.demon.co.uk>,
Jonathan Morton <chromi@chromatix.demon.co.uk> writes

>> We then
>> carefully worked through all the calculations, using the best data
>> that we could obtain -- and we did indeed come to the conclusion that
>> proof-of-work is not a viable proposal :(
>
>That's a very interesting paper, thank you.  I wonder, however, what 
>the distribution curves are like when "regular correspondents" are 
>exempted from proof-of-work, not just mailing lists.  Would it be 
>possible to re-examine the MTA logs for this type of pattern?

in principle yes ... however I doubt that the systems at the top of the
curve (sending lots of email per day) would have regular correspondents.
Besides the people running mailing lists, they will be e-commerce
systems sending acknowledgements, hospitals confirming appointments, fax
delivery systems relaying incoming messages etc.

However, I could not be sure of that statement without a fair amount of
processing. Since I'd like to know how much of the top of the curve
involves mailing lists, that's not processing that I'm averse to doing.

>By "regular correspondents" I mean people who know each other well 
>enough to send mail regularly, not necessarily frequently - even once a 
>week over a period of months.  I ask this because I expect that users 
>with slow machines - who would otherwise be the group most 
>inconvenienced by proof-of-work schemes - send mail that mostly falls 
>into this category.  I don't know, however, how much of the overall 
>picture is accounted for by these.

I don't see why one should expect any correlation between machine speed
and regularity of sending email. Many businesses will not splash out for
admin staff machines, so it is they as well as aged parents who might be
expected to have old kit :)

>For future work, it might be instructive to identify various non-spam 
>use-cases which appear to have a high proof-of-work load - ie. on the 
>"long tail" of the distribution curves presented - and consider 
>practical ways of relieving or accommodating it.

indeed so ... though you should note that there is not much difference
between spam viability thresholds and the average case, let alone power-
users.

For proof-of-work to look plausible (and not a high-risk strategy) I'd
like to see factors of a thousand or more between plausible workloads
for legitimate senders and any economically viable spamming activity :-(

- -- 
richard                                              Richard Clayton

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.         Benjamin Franklin

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBQKn9OhfnRQV/feRLEQJruQCZAeu3ZpTgrPIspvVIhs1sFk8yFbAAn2JQ
HTxFfnBPFrZm/jskT4NwehQE
=3MEJ
-----END PGP SIGNATURE-----

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