Re: [Asrg] C/R Framework

"Jon Kyme" <jrk@merseymail.com> Thu, 15 May 2003 16:08 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 MAA13773 for <asrg-archive@odin.ietf.org>; Thu, 15 May 2003 12:08:28 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4FFZXc11076 for asrg-archive@odin.ietf.org; Thu, 15 May 2003 11:35:33 -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 h4FFZXB11073 for <asrg-web-archive@optimus.ietf.org>; Thu, 15 May 2003 11:35:33 -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 MAA13739; Thu, 15 May 2003 12:07:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GLIm-0000Rd-00; Thu, 15 May 2003 12:09:52 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19GLIm-0000Ra-00; Thu, 15 May 2003 12:09:52 -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 h4FFV6B10792; Thu, 15 May 2003 11:31:06 -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 h4FFUTB10741 for <asrg@optimus.ietf.org>; Thu, 15 May 2003 11:30:29 -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 MAA13578 for <asrg@ietf.org>; Thu, 15 May 2003 12:02:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GLDt-0000PE-00 for asrg@ietf.org; Thu, 15 May 2003 12:04:49 -0400
Received: from argon.connect.org.uk ([193.110.243.33]) by ietf-mx with esmtp (Exim 4.12) id 19GLDs-0000PB-00 for asrg@ietf.org; Thu, 15 May 2003 12:04:48 -0400
Received: from mmail by argon.connect.org.uk with local (connectmail/exim) id 19GLEz-0007zB-00; Thu, 15 May 2003 17:05:57 +0100
In-Reply-To: <5.2.0.9.2.20030515115340.00bafae8@std5.imagineis.com>
Subject: Re: [Asrg] C/R Framework
To: Yakov Shafranovich <research@solidmatrix.com>
From: Jon Kyme <jrk@merseymail.com>
Cc: ASRG <asrg@ietf.org>
X-Mailer: [ConnectMail 3.5.4]
X-connectmail-Originating-IP: 172.25.243.3
Message-Id: <E19GLEz-0007zB-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: Thu, 15 May 2003 17:05:57 +0100

> problem too. As I mentioned before, perhaps we should not store plain
> email
> addresses - but some form of checksum or something. Even though that is 
> susceptible to dictionary attacks, the attacker must know what he is 
> looking for. This will at least protect against people snooping at
> messages.
> 


I don't think it's necc. to specify what steps an implementer needs to take
to protect/hide the data - just an recommendation that they should take
steps is probably enough. Maybe?






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