RE: [Asrg] Two ways to look at spam

"Bob Wyman" <bob@wyman.us> Tue, 01 July 2003 19:41 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 PAA14106 for <asrg-archive@odin.ietf.org>; Tue, 1 Jul 2003 15:41:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQzx-0004W6-7g for asrg-archive@odin.ietf.org; Tue, 01 Jul 2003 15:41:08 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h61Jf5tC017358 for asrg-archive@odin.ietf.org; Tue, 1 Jul 2003 15:41:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQzx-0004Vt-4V for asrg-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 15:41:05 -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 PAA14088; Tue, 1 Jul 2003 15:41:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XQzv-0007gj-00; Tue, 01 Jul 2003 15:41:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XQzv-0007gg-00; Tue, 01 Jul 2003 15:41:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQzu-0004Si-Aa; Tue, 01 Jul 2003 15:41:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQz8-0004S5-W7 for asrg@optimus.ietf.org; Tue, 01 Jul 2003 15:40:15 -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 PAA14068 for <asrg@ietf.org>; Tue, 1 Jul 2003 15:40:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XQz7-0007gF-00 for asrg@ietf.org; Tue, 01 Jul 2003 15:40:13 -0400
Received: from vmmrnat.verisignmail.com ([216.168.230.187] helo=mr10.verisignmail.com) by ietf-mx with esmtp (Exim 4.12) id 19XQz6-0007gB-00 for asrg@ietf.org; Tue, 01 Jul 2003 15:40:13 -0400
Received: from ms3.verisignmail.com (ms3.verisignmail.com [216.168.230.176] (may be forged)) by mr10.verisignmail.com (Mirapoint Messaging Server MOS 3.2.2-GA) with ESMTP id ACE87187; Tue, 1 Jul 2003 15:40:08 -0400 (EDT)
Received: from BOBDEV (pool-162-83-223-223.ny5030.east.verizon.net [162.83.223.223]) by ms3.verisignmail.com (Mirapoint Messaging Server MOS 3.2.2-GA) with ESMTP id AJW11628; Tue, 1 Jul 2003 15:40:06 -0400 (EDT)
Reply-To: bob@wyman.us
From: Bob Wyman <bob@wyman.us>
To: 'Yakov Shafranovich' <research@solidmatrix.com>, 'Paul Judge' <paul.judge@ciphertrust.com>, asrg@ietf.org
Subject: RE: [Asrg] Two ways to look at spam
Message-ID: <003a01c34008$944f8020$640aa8c0@BOBDEV>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <5.2.0.9.2.20030630221600.00b34f90@std5.imagineis.com>
Content-Transfer-Encoding: quoted-printable
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: Tue, 01 Jul 2003 15:40:08 -0400
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Yakov Shafranovich wrote:
>However, on the global level how does is the consent framework
relevant? 
	I don't think it is too hard to see how various consent based
systems could work on a global level. Not all of the possiblities are
going to be sensible, however...

	1. If consent can be "expressed" in some sort of a document or
data structure, that "expression of consent" can be communicated or
moved from the local periphery of the system into the more global core.
Thus, I, my ISP, or my organization, might prepare an "expression of
consent" that states that mail will not be accepted if it exceeds
certain sizes, contains certain elements (such as attachments) or is of
a "commercial" nature. If this expression can be accessed by arbitrary
nodes, then either sending nodes or intermediate nodes would be able to
determine what had been consented to and decide whether to originate or
relay any particular message.
	A very simple version of such a system would be created if we
were to adopt something like the "donotcall.gov" system which is used to
block telemarketing calls in the US.

	2. If systems that rely on "licenses to send" or
recipient-issued tokens are deployed, then depending on the way these
things are implemented, upstream nodes would be able to inspect the
licenses and determine whether or not a particular message was, in fact,
authorized. Depending on implementation choices, non-authorized messages
could be either discarded, subjected to more or greater "spam-detection"
inspections, or routed at lower quality of service.

	Consent based systems can have value on a "global" non-local
basic even though they express the consent of "local" systems or users.

		bob wyman


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