RE: [Asrg] C/R Thoughts: Take 1

"Eric Dean" <eric@purespeed.com> Tue, 13 May 2003 15:44 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 LAA17358 for <asrg-archive@odin.ietf.org>; Tue, 13 May 2003 11:44:22 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DFAQO02204 for asrg-archive@odin.ietf.org; Tue, 13 May 2003 11:10:26 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DFAQB02201 for <asrg-web-archive@optimus.ietf.org>; Tue, 13 May 2003 11:10:26 -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 LAA17329; Tue, 13 May 2003 11:43:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FbyN-0005C0-00; Tue, 13 May 2003 11:45:47 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FbyM-0005Bx-00; Tue, 13 May 2003 11:45:46 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DF91B02074; Tue, 13 May 2003 11:09:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DF8qB02032 for <asrg@optimus.ietf.org>; Tue, 13 May 2003 11:08:52 -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 LAA17258 for <asrg@ietf.org>; Tue, 13 May 2003 11:42:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Fbwr-0005Au-00 for asrg@ietf.org; Tue, 13 May 2003 11:44:14 -0400
Received: from ns2.tidalwave.net ([66.77.68.8] helo=mailgate.purespeed.com) by ietf-mx with esmtp (Exim 4.12) id 19Fbwr-0005Ab-00 for asrg@ietf.org; Tue, 13 May 2003 11:44:13 -0400
Received: from purespeed.com (mail.purespeed.com [66.77.69.8]) by mailgate.purespeed.com (Postfix Relay Hub) with ESMTP id E535713DE4; Tue, 13 May 2003 11:47:04 -0400 (EDT)
Received: from HOMEY [171.75.47.105] by purespeed.com (SMTPD32-7.13) id A2E9A0D5008A; Tue, 13 May 2003 11:44:41 -0400
From: Eric Dean <eric@purespeed.com>
To: Jon Kyme <jrk@merseymail.com>, ASRG <asrg@ietf.org>
Subject: RE: [Asrg] C/R Thoughts: Take 1
Message-ID: <MBEKIIAKLDHKMLNFJODBAEJGFCAA.eric@purespeed.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-reply-to: <E19Fagt-0001Ou-00@argon.connect.org.uk>
Content-Transfer-Encoding: 7bit
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, 13 May 2003 11:46:53 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Excellent, these are all good points.  I'll take the lead on compiling a
framework that includes components provided.  I'll probably start with a
simple Table of Contents.

> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of Jon
> Kyme
> Sent: Tuesday, May 13, 2003 10:24 AM
> To: ASRG
> Subject: Re: [Asrg] C/R Thoughts: Take 1
>
>
> >> Issues like this:
> >> http://www.toyz.org/SpamArrestSpams.html
> >>
> >> Summary: Alleges SpamArrest harvests sender addresses
> >
> >I see privacy issues for challenge/response systems, but that's not
> >one.
>
> Perhaps I should have said "data protection" (as we call it in the UK).
>
>
> >Ths SpamArrest abuse is a potential problem in any system where
> >you let a third party with handle your mail.  It is a consideration
> >in any system where that involves asking a third party anything about
> >mail, including DNS blacklists.
> >
>
> Of course the *sender* isn't aware (in advance) that this particular
> 3rd party is handling the mail.
>
>
>
> >
> >I think any spam filtering RFC ought to have a section on privacy
> >like the required section on security.
> >
>
> That would be nice.  No negative privacy impact is a "requirement".
> I think we had a fairly good consensus on the
> Requirements...
>
>
>

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