Re: [Asrg] Forbes: Pay up

mathew <meta@pobox.com> Tue, 15 July 2003 03:08 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23934 for <asrg-archive@odin.ietf.org>; Mon, 14 Jul 2003 23:08:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cGB7-0000VV-3z for asrg-archive@odin.ietf.org; Mon, 14 Jul 2003 23:08:33 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6F38Xrp001879 for asrg-archive@odin.ietf.org; Mon, 14 Jul 2003 23:08:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cGB5-0000UE-45 for asrg-web-archive@optimus.ietf.org; Mon, 14 Jul 2003 23:08:31 -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 XAA23895; Mon, 14 Jul 2003 23:08:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cGAy-00074n-00; Mon, 14 Jul 2003 23:08:24 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cGAx-00074k-00; Mon, 14 Jul 2003 23:08:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cG9e-0008Ua-KY; Mon, 14 Jul 2003 23:07:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cG9U-0008TJ-EY for asrg@optimus.ietf.org; Mon, 14 Jul 2003 23:06:53 -0400
Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23748 for <asrg@ietf.org>; Mon, 14 Jul 2003 23:06:46 -0400 (EDT)
Received: from pobox.com (h005018086b3b.ne.client2.attbi.com[66.31.45.164](untrusted sender)) by comcast.net (sccrmhc11) with SMTP id <20030715030616011002j6k1e>; Tue, 15 Jul 2003 03:06:16 +0000
X-Habeas-Swe-6: email in exchange for a license for this Habeas
Subject: Re: [Asrg] Forbes: Pay up
Mime-Version: 1.0 (Apple Message framework v552)
Content-Transfer-Encoding: 7bit
From: mathew <meta@pobox.com>
In-Reply-To: <E19XskJ-00039k-00@mail.nitros9.org>
To: asrg@ietf.org
X-Habeas-Swe-1: winter into spring
X-Habeas-Swe-2: brightly anticipated
X-Habeas-Swe-3: like Habeas SWE (tm)
X-Habeas-Swe-4: Copyright 2002 Habeas (tm)
X-Habeas-Swe-5: Sender Warranted Email (SWE) (tm). The sender of this
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
X-Habeas-Swe-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-Swe-8: Message (HCM) and not spam. Please report use of this
X-Habeas-Swe-9: mark in spam to <http://www.habeas.com/report/>.
X-Image-Url: http://meta.ATH0.com/photos/MailPictures/meta@pobox.com
Message-Id: <4C831D85-B671-11D7-B331-00039380F1B6@pobox.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
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: Mon, 14 Jul 2003 23:06:16 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Wednesday, July 2, 2003, at 09:18 PM, Alan DeKok wrote:
>   That is, would the possible centralization of the administration of
> $$ (i.e. trust verification) be less problematic to the recipient than
> spam?  I could see people deciding that receiving ~100 spams/week is a
> reasonable trade-off for preventing a third party from having access
> to your email messages, or habits.

That's why it's important to design the protocols correctly.

It's perfectly possible to implement digital cash systems such that the 
"bank" doesn't get to see the e-mail, the sender and recipient can stay 
anonymous to each other, yet the recipient can be confident that his 
account was credited with the appropriate cash sum.

There's also no reason why it would be necessary to have a centralized 
system. You could have a number of administration entities, just like 
you do for DNS etc.

I've been thinking for a while that a bunch of people on this list, 
myself included, are pretty much convinced that the "use as much 
resources and as much of people's attention as you like, for free" 
model is fundamentally broken, and that sender-pays will be necessary.

It seems to me that those of us who think "sender pays" is necessary 
could usefully set up a separate list to come up with requirements, and 
a proposed implementation model, which could then be brought back here 
for the inevitable nit-picking.

It also seems clear to me that even if the majority think that "sender 
pays" won't work, that's no reason why it need be killed. Unlike many 
other solutions, it can quite happily "compete" with free e-mail and 
live or die by whether it works in the real world; it doesn't need 
universal adoption to be useful.


mathew


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