RE: [Asrg] Consent Proposal

Vernon Schryver <vjs@calcite.rhyolite.com> Fri, 27 June 2003 04:05 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 AAA03958 for <asrg-archive@odin.ietf.org>; Fri, 27 Jun 2003 00:05:36 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5R459x05028 for asrg-archive@odin.ietf.org; Fri, 27 Jun 2003 00:05:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VkU1-0001J1-HN for asrg-web-archive@optimus.ietf.org; Fri, 27 Jun 2003 00:05:09 -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 AAA03947; Fri, 27 Jun 2003 00:05:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VkTz-0000wp-00; Fri, 27 Jun 2003 00:05:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VkTt-0000wm-00; Fri, 27 Jun 2003 00:05:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VkTt-0001BY-GN; Fri, 27 Jun 2003 00:05:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VkTU-00017p-HQ for asrg@optimus.ietf.org; Fri, 27 Jun 2003 00:04:36 -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 AAA03927 for <asrg@ietf.org>; Fri, 27 Jun 2003 00:04:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VkTD-0000we-00 for asrg@ietf.org; Fri, 27 Jun 2003 00:04:19 -0400
Received: from calcite.rhyolite.com ([192.188.61.3]) by ietf-mx with esmtp (Exim 4.12) id 19VkSw-0000wa-00 for asrg@ietf.org; Fri, 27 Jun 2003 00:04:05 -0400
Received: (from vjs@localhost) by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5R43Puj013664 for asrg@ietf.org env-from <vjs>; Thu, 26 Jun 2003 22:03:25 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306270403.h5R43Puj013664@calcite.rhyolite.com>
To: asrg@ietf.org
Subject: RE: [Asrg] Consent Proposal
References: <DD198B5D07F04347B7266A3F35C42B0B0FD07E@io.cybercom.local>
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: Thu, 26 Jun 2003 22:03:25 -0600

> From: "Peter Kay" <peter@titankey.com>

>...
> A. there exists a plug-in infrastructure that can run on MUA or MTA
> (ISP).

Things that MTAs and MUAs can do differ radically.

> B. each plug-in provides for some type of policy definition, related to
> the plugins purpose. This can range from filtering to CR to all the
> other methods mentioned below.

"Plug-in" worries me.  At best it suggests an implementation mechanism
instead of a protocol notion.  At worst it suggests an intolerable
security nightmare as is standard in commodity desktop software.


> C. each plug-in can be configured by a hierarchy. Starting w/ the ISP
> (for instance), then perhaps a domain-level admin (for corporate
> applications0 and then the end-user.  We can decide on varying levels of
> defaults or override capability so that for example if an ISP whitelists
> a source, the end-user may have the option to blacklist it. 
> ...

That needs to be made concrete in terms of protocols and mechanisms
so that it can be discussed by a technical group.


Vernon Schryver    vjs@rhyolite.com

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