IETF Logo Mail Archive

Re: 6. Proposals - Sender Verification (was Re: [Asrg] Simple way to verify sender, track mail abusers)

david nicol <whatever@davidnicol.com> Sun, 28 September 2003 23:09 UTC

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 TAA04704 for <asrg-archive@odin.ietf.org>; Sun, 28 Sep 2003 19:09:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A3kf2-00089x-Rj for asrg-archive@odin.ietf.org; Sun, 28 Sep 2003 19:09:06 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8SN94o1031359 for asrg-archive@odin.ietf.org; Sun, 28 Sep 2003 19:09:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A3kf2-00089i-Ni for asrg-web-archive@optimus.ietf.org; Sun, 28 Sep 2003 19:09:04 -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 TAA04699 for <asrg-web-archive@ietf.org>; Sun, 28 Sep 2003 19:08:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A3kez-0005j0-00 for asrg-web-archive@ietf.org; Sun, 28 Sep 2003 19:09:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A3kez-0005ix-00 for asrg-web-archive@ietf.org; Sun, 28 Sep 2003 19:09:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A3kez-00086F-Jb; Sun, 28 Sep 2003 19:09:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A3keq-000862-Os for asrg@optimus.ietf.org; Sun, 28 Sep 2003 19: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 TAA04696 for <asrg@ietf.org>; Sun, 28 Sep 2003 19:08:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A3ken-0005it-00 for asrg@ietf.org; Sun, 28 Sep 2003 19:08:49 -0400
Received: from ms-smtp-02.rdc-kc.rr.com ([24.94.166.122]) by ietf-mx with esmtp (Exim 4.12) id 1A3ken-0005iq-00 for asrg@ietf.org; Sun, 28 Sep 2003 19:08:49 -0400
Received: from CPE-65-28-12-217.kc.rr.com (CPE-65-28-12-217.kc.rr.com [65.28.12.217]) by ms-smtp-02.rdc-kc.rr.com (8.12.8p1/8.12.7) with ESMTP id h8SN8HsN012135; Sun, 28 Sep 2003 18:08:30 -0500 (CDT)
Subject: Re: 6. Proposals - Sender Verification (was Re: [Asrg] Simple way to verify sender, track mail abusers)
From: david nicol <whatever@davidnicol.com>
To: Dennis Gearon <gearond@fireserve.net>
Cc: asrg@ietf.org
In-Reply-To: <3F738916.8070907@fireserve.net>
References: <3F737A5E.8080606@fireserve.net> <3F737D96.10000@solidmatrix.com> <3F738916.8070907@fireserve.net>
Content-Type: text/plain
Message-Id: <1064790496.970.21.camel@plaza.davidnicol.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Symantec AntiVirus Scan Engine
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/mail-archive/working-groups/asrg/>
Date: Sun, 28 Sep 2003 18:08:16 -0500
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Thu, 2003-09-25 at 19:32, Dennis Gearon wrote:
> Yakov Shafranovich wrote:
> 
> > Fourth, take a look at the CRI proposal:
> >
> > http://www.ietf.org/internet-drafts/draft-irtf-asrg-cri-00.txt
> 
> Actually, my idea, I believe, takes care of most of the problems with 
> the Level 2 CRI system. I will think about it for awhile.

When is CRI 01 due?  Who is maintaining it (I nominate Eric Dean)?
It has been pointed out that body hashing would make CRI level-2
work, and this was AIUI generally agreed-to.  Yet a revised CRI
document has not yet appeared.


-- 
David Nicol /  kernel 2.6.0 is pretty whippy



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

v2.23.0 | Report a Bug | By Email