[Asrg] Consent Proposal

Yakov Shafranovich <research@solidmatrix.com> Thu, 26 June 2003 21:25 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 RAA22540 for <asrg-archive@odin.ietf.org>; Thu, 26 Jun 2003 17:25:34 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QLP7210263 for asrg-archive@odin.ietf.org; Thu, 26 Jun 2003 17:25:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VeEt-0002fS-Jk for asrg-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 17:25:07 -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 RAA22501; Thu, 26 Jun 2003 17:25:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VeEr-0006Au-00; Thu, 26 Jun 2003 17:25:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VeEl-0006Ar-00; Thu, 26 Jun 2003 17:24:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VeEn-0002Lu-5I; Thu, 26 Jun 2003 17:25:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VeDr-0002CM-Ku for asrg@optimus.ietf.org; Thu, 26 Jun 2003 17:24:03 -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 RAA22458 for <asrg@ietf.org>; Thu, 26 Jun 2003 17:23:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VeDp-0006A1-00 for asrg@ietf.org; Thu, 26 Jun 2003 17:24:01 -0400
Received: from 000-232-438.area5.spcsdns.net ([68.27.147.29] helo=68.27.147.29) by ietf-mx with smtp (Exim 4.12) id 19VeDd-00069w-00 for asrg@ietf.org; Thu, 26 Jun 2003 17:23:50 -0400
Message-Id: <5.2.0.9.2.20030626171332.00bd13e0@pop.pocketmail.com>
X-Sender: research@solidmatrix.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
To: asrg@ietf.org
From: Yakov Shafranovich <research@solidmatrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-MimeHeaders-Plugin-Info: v2.03.00
X-GCMulti: 1
Subject: [Asrg] Consent Proposal
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 17:23:25 -0400

I would like to provide a generic proposal for consent-based system as per 
charter:

1. Users and/or ISP define rules and filters to filter incoming email. 
Rules/filters are decided by end users and ISPs, and are not mandated. 
Every user/ISP can define its own policies ranging from banning all email 
not digitally signed to blocking HTML.
2. For each email user, the MUA or the ISP maintains a whitelist of trusted 
senders, blacklist of blocked senders and a graylist of unknown senders. 
Whitelisted senders go the inbox, graylisted senders go to the bulk folder, 
and blacklisted senders are either in the spam folder or erased.
3. Whitelists are not only a list of email addresses of trusted senders, 
but to avoid sender spoofing also have additional features such as digital 
signatures, certificates, passwords, tokens, etc.
4. Additional automatic whitelist rules are defined as such email from 
trusted senders (e.g. Habeas) is automatically goes to the inbox unless 
blacklisted, etc. C/R systems are also integrated and upon receiving a 
positive response automatically whitelist the sender.
5. Additional automatic blacklist rules are defined such as email coming 
from known open relays is blocked.
6. Whitelists, graylists and blacklists are stored hashed or encrypted to 
protect privacy.

Any thoughts?

Yakov


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