Re: [Asrg] C/R Thoughts: Take 1

"Eric S. Johansson" <esj@harvee.org> Wed, 14 May 2003 15:48 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 LAA22653 for <asrg-archive@odin.ietf.org>; Wed, 14 May 2003 11:48:03 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4EFEcL24166 for asrg-archive@odin.ietf.org; Wed, 14 May 2003 11:14:38 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4EFEcB24163 for <asrg-web-archive@optimus.ietf.org>; Wed, 14 May 2003 11:14:38 -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 LAA22646; Wed, 14 May 2003 11:47:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FyVU-0006wf-00; Wed, 14 May 2003 11:49:28 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FyVU-0006wc-00; Wed, 14 May 2003 11:49:28 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4EFCQB24069; Wed, 14 May 2003 11:12:26 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4EFBHB24023 for <asrg@optimus.ietf.org>; Wed, 14 May 2003 11:11:17 -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 LAA22589 for <asrg@ietf.org>; Wed, 14 May 2003 11:44:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FySG-0006vp-00 for asrg@ietf.org; Wed, 14 May 2003 11:46:08 -0400
Received: from dsl093-191-107.nyc2.dsl.speakeasy.net ([66.93.191.107] helo=harvee.billerica.ma.us) by ietf-mx with esmtp (Exim 4.12) id 19FySF-0006vm-00 for asrg@ietf.org; Wed, 14 May 2003 11:46:07 -0400
Received: from harvee.billerica.ma.us (harvee.billerica.ma.us [127.0.0.1]) by harvee.billerica.ma.us (8.12.8/8.12.5) with ESMTP id h4EFlEYv025904; Wed, 14 May 2003 11:47:14 -0400
Received: FROM harvee.org ([192.168.0.10]) BY harvee.billerica.ma.us WITH ESMTP ; Wed, 14 May 2003 11:47:10 -0400
Message-ID: <3EC264D4.9090306@harvee.org>
From: "Eric S. Johansson" <esj@harvee.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eric Dean <eric@purespeed.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] C/R Thoughts: Take 1
References: <MBEKIIAKLDHKMLNFJODBKEMJFCAA.eric@purespeed.com>
In-Reply-To: <MBEKIIAKLDHKMLNFJODBKEMJFCAA.eric@purespeed.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Camram: stamp; 0:030514:eric@purespeed.com:a25f8240206620ca
X-Camram: stamp; 0:030514:asrg@ietf.org:d4a9d7893beaf749
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: Wed, 14 May 2003 11:46:28 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Eric Dean wrote:

>>so, I'll argue for system that will allow automated systems to
>>talk to each
>>other by e-mail without any human interaction.
> 
> 
> In fact, we'll have to support both.  Newer software can automate this
> process while we'll have to rely on plain old SMTP for legacy use.

why differentiate?  Or at least, why differentiate on the basis of target or 
protocol?  You can handle both automated and manual responses in the same 
message without working hard or increasing complexity in the network.

By placing sufficient information for automatic handling in the headers, and 
human oriented information in the body, you can satisfy the demands of both 
automatic handling in human handling in one message.

example: in camram, I include an instance of a stamp with every message.  In 
this message, I will generate two stamps one to asrg and the second one to 
eric@purespeed.com.  They look something like to stand generated for an earlier 
posting:

X-Camram: stamp; 0:030514:asrg@ietf.org:c407927fbaad1fa8

In the body of the message is the human oriented material i.e. content for the 
mailing list.  The receiving filter sees the stamp, verifies that it is 
"correct" (i.e. 20 bit string of zeros collision) and that it is addressed for 
the recipient (one type of double spending) with the date that isn't too old 
(second type of double spending).  On receipt of a valid stamp, the filter knows 
to pass the message on to my inbox.  The same model can apply to other forms of 
automated challenge/response.

part of the reason I take this approach is because I realized a while ago that 
e-mail is a two-level protocol.  You have the lower-level transport protocol 
(SMTP) which is content independent.  Then you have the higher level protocol as 
represented by the message format which is instructions given by one e-mail 
client to another.  By modifying the higher level protocol by adding stamps or 
other action triggers, you can improved e-mail system functionality without 
destroying the existing infrastructure.

and yes I will be working on a working draft describing a stamp based protocol 
as soon as I can clear the decks a little bit.

it would help if I could resist answering e-mail... ;-)

---eric





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