Re: Anticipatory whitelisting (was Re: [Asrg] Consent Proposal)

Yakov Shafranovich <research@solidmatrix.com> Tue, 01 July 2003 02:36 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 WAA27116 for <asrg-archive@odin.ietf.org>; Mon, 30 Jun 2003 22:36:05 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h612ZcF13050 for asrg-archive@odin.ietf.org; Mon, 30 Jun 2003 22:35:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XAza-0003OP-Gq for asrg-web-archive@optimus.ietf.org; Mon, 30 Jun 2003 22:35: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 WAA27090; Mon, 30 Jun 2003 22:35:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XAzX-0006Iy-00; Mon, 30 Jun 2003 22:35:35 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XAzC-0006If-00; Mon, 30 Jun 2003 22:35:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XAz0-0003Hv-51; Mon, 30 Jun 2003 22:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XAyn-0003GE-5j for asrg@optimus.ietf.org; Mon, 30 Jun 2003 22:34:49 -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 WAA27055 for <asrg@ietf.org>; Mon, 30 Jun 2003 22:34:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XAyj-0006IW-00 for asrg@ietf.org; Mon, 30 Jun 2003 22:34:45 -0400
Received: from 000-235-455.area5.spcsdns.net ([68.27.158.252] helo=68.27.158.252 ident=trilluser) by ietf-mx with smtp (Exim 4.12) id 19XAyV-0006IJ-00 for asrg@ietf.org; Mon, 30 Jun 2003 22:34:32 -0400
Message-Id: <5.2.0.9.2.20030630223206.00b5b2a8@std5.imagineis.com>
X-Sender: research@solidmatrix.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
To: Bruce Stephens <Bruce.Stephens@isode.com>, asrg@ietf.org
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: Re: Anticipatory whitelisting (was Re: [Asrg] Consent Proposal)
In-Reply-To: <84fzlvojo4.fsf_-_@cenderis.demon.co.uk>
References: <16123.34423.451831.720851@world.std.com> <5.2.0.9.2.20030626171332.00bd13e0@pop.pocketmail.com> <16123.34423.451831.720851@world.std.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-MimeHeaders-Plugin-Info: v2.03.00
X-GCMulti: 1
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, 30 Jun 2003 22:33:55 -0400

At 12:15 PM 6/27/2003 +0100, Bruce Stephens wrote:

>Barry Shein <bzs@world.std.com> writes:
>[..]
> > D. "For each email user the MUA or the ISP maintains a whitelist..."
> >
> > MUAs don't maintain whitelists, people do. And that's the crux of
> > the problem as has been shown repeatedly, people generally don't
> > know the exact details of where the confirmation of their FTC/AT&T
> > no-call list is going to come from to put them on their
> > whitelist. Etc.
>
>That's an important problem, and it's one that the IETF (or some other
>body, such as W3C) could help to solve.
>
>Something that would be helpful would be (say) and XML specification
>for small documents that web sites could offer for email lists that
>they run.  Such documents would include information about the
>originator address of email from the list (or some other kind of
>authenticator), and information for subscribing and unsubscribing from
>the list, together with information about the list (description,
>perhaps an icon that user agents can use).
>
>I've phrased that poorly in the sense that the same idea would work
>for short-term communication agreements (such as information about a
>particular order from amazon.com, say).  Some documents could specify
>an expiry time for this use.
>
>Obviously, email clients would parse such documents, and (after
>presenting the information and receiving confirmation) would be able
>to set up the whitelist (also perhaps arranging a filter to put email
>into a special folder), and then tell the originating site about the
>desire to accept communications.  (I say "email client" on the grounds
>that most people use IE/OE, so their email client is also their web
>browser.  Obviously it would be slightly more complex if the two are
>separate, but still readily doable.)
>
>I'm not sure how the information would be passed to ISPs that offer to
>do filtering.  As you say, there are privacy issues.  However, if
>these privacy issues can (to a sufficient extent) be addressed, then a
>standardised way for the permission information to be passed to ISPs
>would be valuable.
>
>Even in the absence of spam, that would be handy, since it would make
>it easy to manage mailing lists (my MUA could show me a list, and
>could automatically filter them into folders).
>[..]

This is going hand in hand with what Bob Wyman mentioned - we need to 
define what consent is, how to express it and how to make sure that various 
mail system can communicate consent between themselves.

Yakov 


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