Re: [Asrg] Consent Proposal

"Jon Kyme" <jrk@merseymail.com> Fri, 27 June 2003 19:22 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 PAA16202 for <asrg-archive@odin.ietf.org>; Fri, 27 Jun 2003 15:22:12 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5RJLiC08244 for asrg-archive@odin.ietf.org; Fri, 27 Jun 2003 15:21:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VyfX-0001Dd-F1 for asrg-web-archive@optimus.ietf.org; Fri, 27 Jun 2003 15:13:59 -0400
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 OAA09296; Fri, 27 Jun 2003 14:22:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VxrH-0004fR-Ip; Fri, 27 Jun 2003 14:22:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vn98-0006Ol-Dn for asrg@optimus.ietf.org; Fri, 27 Jun 2003 02:55:46 -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 CAA19430 for <asrg@ietf.org>; Fri, 27 Jun 2003 02:55:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Vn94-0001ru-00 for asrg@ietf.org; Fri, 27 Jun 2003 02:55:42 -0400
Received: from argon.connect.org.uk ([193.110.243.33]) by ietf-mx with esmtp (Exim 4.12) id 19Vn8t-0001rd-00 for asrg@ietf.org; Fri, 27 Jun 2003 02:55:32 -0400
Received: from mmail by argon.connect.org.uk with local (connectmail/exim) id 19Vn7J-00031y-00; Fri, 27 Jun 2003 07:53:53 +0100
In-Reply-To: <5.2.0.9.2.20030626205450.00b41768@std5.imagineis.com>
Subject: Re: [Asrg] Consent Proposal
To: Yakov Shafranovich <research@solidmatrix.com>
From: Jon Kyme <jrk@merseymail.com>
Cc: ASRG <asrg@ietf.org>
X-Mailer: [ConnectMail 3.5.7]
X-connectmail-Originating-IP: 158.152.118.31
Message-Id: <E19Vn7J-00031y-00@argon.connect.org.uk>
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: Fri, 27 Jun 2003 07:53:53 +0100

> >I don't believe that this adds up to what you claim.
> >
> >There was some more fundamental (but probably premature)
> >discussion of "consent" early in the life this group.
> 
> The charter goes on and on about consent, however aside from Gordon's
> HTML
> blocking thread, there has been no discussion of that. 

You might be interested in the threads starting with
<E18r0iB-0000Ci-00@mail.nitros9.org> "[Asrg] The Consent 4-Tuple"
and
<E18sKmk-00009r-00@argon.connect.org.uk> "[Asrg] What would consent look
like?"

>If discussion of 
> consent is premature at the moment, 

I meant premature at the time. People were busy contributing their pet
silver bullets. I thought this would have stopped by now.
Shows how much I know... :-)

>what should we be looking at right
> now?
> In general, what directions should the group be pursuing at the moment?

I strongly believe that you are right, that an analysis of the consent
problem is important. I believe that one can get to a general framework for
anti-spam systems from first principles.

I think it tends to something like:
message classifier function
+ expression of recipient policy (consent expression)
+ policy enforcement agent







--

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