RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Avoidance
"Peter Kay" <peter@titankey.com> Thu, 02 October 2003 16:32 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 MAA29705 for <asrg-archive@odin.ietf.org>; Thu, 2 Oct 2003 12:32:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A56NU-0002H1-3c for asrg-archive@odin.ietf.org; Thu, 02 Oct 2003 12:32:33 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h92GWWxr008733 for asrg-archive@odin.ietf.org; Thu, 2 Oct 2003 12:32:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A56NT-0002Gm-V0 for asrg-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 12:32:31 -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 MAA29641 for <asrg-web-archive@ietf.org>; Thu, 2 Oct 2003 12:32:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A56NS-0003FG-00 for asrg-web-archive@ietf.org; Thu, 02 Oct 2003 12:32:30 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A56NS-0003FD-00 for asrg-web-archive@ietf.org; Thu, 02 Oct 2003 12:32:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A56N0-000297-92; Thu, 02 Oct 2003 12:32:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A56Mh-00027m-UV for asrg@optimus.ietf.org; Thu, 02 Oct 2003 12:31:44 -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 MAA29604 for <asrg@ietf.org>; Thu, 2 Oct 2003 12:31:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A56Mg-0003EI-00 for asrg@ietf.org; Thu, 02 Oct 2003 12:31:42 -0400
Received: from imail.centuryc.net ([216.30.168.20]) by ietf-mx with esmtp (Exim 4.12) id 1A56Mf-0003Dt-00 for asrg@ietf.org; Thu, 02 Oct 2003 12:31:41 -0400
Received: from cybercominc.com [66.91.134.126] by imail.centuryc.net (SMTPD32-8.03) id A32B66C0100; Thu, 02 Oct 2003 06:32:43 -1000
Received: from rrcs-west-66-91-134-123.biz.rr.com (66.91.134.123) by cybercominc-zzt with SMTP; Thu, 02 Oct 2003 16:40:28 GMT
X-Titankey-e_id: <14205b2f-e6c4-4afd-b19f-c6995e63cf98>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Avoidance
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Message-ID: <DD198B5D07F04347B7266A3F35C42B0B150EB7@io.cybercom.local>
Thread-Topic: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Avoidance
Thread-Index: AcOIfNKmSlBpi/+JTai0rj7cJKuyUgAhdsng
From: Peter Kay <peter@titankey.com>
To: Eric Dean <eric@purespeed.com>, asrg@ietf.org
Content-Transfer-Encoding: quoted-printable
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: Thu, 02 Oct 2003 06:33:57 -1000
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Eric, > > If we start adding various messaging such as with DSNs...I > don't think that we should be hijacking a sender's email > address to carry various protocol information. > I'm not sure what you mean by that. If CRI is a protocol between two people, instead of two systems, I don't see what's wrong w/ using the user's email addresses. > Of course, that's just my opinion and why it's merely a > recommendation rather than a must, shall... > If its just a recommendation, then why not recommend something which simplifies the situation and reduces overhead? > > -----Original Message----- > > From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On Behalf Of > Peter > > Kay > > Sent: Wednesday, October 01, 2003 12:08 PM > > To: asrg@ietf.org > > Subject: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Avoidance > > > > 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 _______________________________________________ Asrg mailing list Asrg@ietf.org https://www1.ietf.org/mailman/listinfo/asrg
- [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Avoida… Peter Kay
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Eric Dean
- Re: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Yakov Shafranovich
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Kee Hinckley
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Peter Kay
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Peter Kay
- Re: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Yakov Shafranovich
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Eric Dean
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Eric Dean
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Eric Dean
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Eric Dean
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Peter Kay
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Eric Dean
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Peter Kay
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Kee Hinckley
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Peter Kay
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Eric Dean
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Peter Kay
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Eric Dean
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… david nicol
- RE: [Asrg] 6. Proposals - CRI Draft - 4.1 Loop Av… Eric Dean