[Asrg] 6. Proposals - CRI Draft - 4.1 Loop Avoidance

"Peter Kay" <peter@titankey.com> Wed, 01 October 2003 16:06 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 MAA21167 for <asrg-archive@odin.ietf.org>; Wed, 1 Oct 2003 12:06:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jUi-0002Sk-4C for asrg-archive@odin.ietf.org; Wed, 01 Oct 2003 12:06:29 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h91G6SDx009460 for asrg-archive@odin.ietf.org; Wed, 1 Oct 2003 12:06:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jUi-0002SV-09 for asrg-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 12:06:28 -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 MAA21143 for <asrg-web-archive@ietf.org>; Wed, 1 Oct 2003 12:06:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4jUg-0001TX-00 for asrg-web-archive@ietf.org; Wed, 01 Oct 2003 12:06:26 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A4jUg-0001TU-00 for asrg-web-archive@ietf.org; Wed, 01 Oct 2003 12:06:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jUI-0002OY-4K; Wed, 01 Oct 2003 12:06:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jTo-0002NT-Cg for asrg@optimus.ietf.org; Wed, 01 Oct 2003 12:05:32 -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 MAA21087 for <asrg@ietf.org>; Wed, 1 Oct 2003 12:05:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4jTn-0001SZ-00 for asrg@ietf.org; Wed, 01 Oct 2003 12:05:31 -0400
Received: from imail.centuryc.net ([216.30.168.20]) by ietf-mx with esmtp (Exim 4.12) id 1A4jTm-0001S6-00 for asrg@ietf.org; Wed, 01 Oct 2003 12:05:30 -0400
Received: from cybercominc.com [66.91.134.126] by imail.centuryc.net (SMTPD32-8.03) id AB824A900F4; Wed, 01 Oct 2003 06:06:26 -1000
Received: from rrcs-west-66-91-134-123.biz.rr.com (66.91.134.123) by cybercominc-zzt with SMTP; Wed, 01 Oct 2003 16:14:10 GMT
X-Titankey-e_id: <82001fb0-bb2c-4826-91ea-c6ed0f1015eb>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Message-ID: <DD198B5D07F04347B7266A3F35C42B0B0FD19A@io.cybercom.local>
Thread-Topic: 6. Proposals - CRI Draft - 4.1 Loop Avoidance
Thread-Index: AcOINiRI0PVzy83cRCa4TrFIE44ufg==
From: Peter Kay <peter@titankey.com>
To: asrg@ietf.org
Content-Transfer-Encoding: quoted-printable
Subject: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Avoidance
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: Wed, 01 Oct 2003 06:07:41 -1000
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I finally had a chance to come up for air to respond to Eric/Yakov's
draft 
at http://www.ietf.org/internet-drafts/draft-irtf-asrg-cri-00.txt  .
ASRG owes you much for your hard work in creating this document and I
personally thank you for furthering an important area of
interoperability.

On loop avoidance section, specifically:

"For CRI systems that issue challenge messages, it is also recommended
that each CRI system use a local systemwide user, such as cri@foo.com,
for issuing challenges rather than preserving the original sender's
email address as the sender of the challenge message."

We disgree.

Most CR systems automatically/dynamically add the recipient to the
sender's whitelist.  So if I send an email to eric@cri.com, he's
automatically added to my whitelist.  If the mail-from on his challenge
is eric@cri.com, his email comes straight to my inbox without delays or
filters and certainly won't get challenged.  If the mail-from on his
challenge is "challenger@cri.com", the CRI protocol needs to be invoked,
possibly creating unecessary overhead.

Keeping the mail-from consistent allows CRI systems to naturally
interoperate and assuming that the CR system adds recipients to the
whitelist, elegantly solves the problem of CR systems challenging other
challenges.  

Peter





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