RE: [Asrg] CRI Header

Yakov Shafranovich <research@solidmatrix.com> Sun, 15 June 2003 19:54 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 PAA09650 for <asrg-archive@odin.ietf.org>; Sun, 15 Jun 2003 15:54:08 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5FJrej20975 for asrg-archive@odin.ietf.org; Sun, 15 Jun 2003 15:53:40 -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 h5FJrem20972 for <asrg-web-archive@optimus.ietf.org>; Sun, 15 Jun 2003 15:53:40 -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 PAA09637; Sun, 15 Jun 2003 15:53:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RdXB-0004z4-00; Sun, 15 Jun 2003 15:51:25 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19RdXB-0004z1-00; Sun, 15 Jun 2003 15:51:25 -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 h5FHx1a14119; Sun, 15 Jun 2003 13:59: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 h5FHwsm14108 for <asrg@optimus.ietf.org>; Sun, 15 Jun 2003 13:58:54 -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 NAA06465 for <asrg@ietf.org>; Sun, 15 Jun 2003 13:58:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Rbk7-0004WU-00 for asrg@ietf.org; Sun, 15 Jun 2003 13:56:39 -0400
Received: from 000-249-011.area7.spcsdns.net ([68.27.212.92] helo=68.27.212.92 ident=trilluser) by ietf-mx with smtp (Exim 4.12) id 19Rbk5-0004WR-00 for asrg@ietf.org; Sun, 15 Jun 2003 13:56:38 -0400
Message-Id: <5.2.0.9.2.20030615135503.00ba1bb0@std5.imagineis.com>
X-Sender: research@solidmatrix.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
To: "Eric D. Williams" <eric@infobro.com>, "asrg@ietf.org" <asrg@ietf.org>, Peter Kay <peter@titankey.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: RE: [Asrg] CRI Header
In-Reply-To: <01C332C9.DF290A90.eric@infobro.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-MimeHeaders-Plugin-Info: v2.03.00
X-GCMulti: 1
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: Sun, 15 Jun 2003 13:58:30 -0400

At 11:08 PM 6/14/2003 -0400, Eric D. Williams wrote:

>On Monday, June 09, 2003 2:39 PM, Yakov Shafranovich
>[SMTP:research@solidmatrix.com] wrote:
>8<...>8
> > HOWEVER, the same section states:
> >
> > "Whenever an SMTP transaction is used to send a DSN, the MAIL FROM command
> > MUST use a NULL return address, i.e., "MAIL FROM:<>"."
>
>A proper intepretation of that statement requires its full context.  The 
>intent
>is to prevent message looping.  As such the CRI or other systems SHOULD 
>ensure
>that specfied addresses do not violate that tenet.
>
>
>    The envelope sender address of the DSN SHOULD be chosen to ensure
>    that no delivery status reports will be issued in response to the DSN
>    itself, and MUST be chosen so that DSNs will not generate mail loops.
>    Whenever an SMTP transaction is used to send a DSN, the MAIL FROM
>    command MUST use a NULL return address, i.e., "MAIL FROM:<>".
>
>
> > That means that C/R systems such as yours MUST support the empty return
> > path (<>).
>
>No it does not, IMO, given the full context of the requirement.

We were considering implementing CRI within the extension framework of 
DSNs. DSNs require the return path to be <>, so any system that would use 
such protocol in this matter, would require <> as well. I didn't not mean 
that ALL C/R systems will use it - thank you for pointing this out.

Someone pointed out that DSNs might not be the best solution, since it is 
intended to be a one-way notification, as opposed to CRI where the 
challenge is intended to be responded to and there is also an issue of all 
systems that do not support CRI but support DSNs. I also contacted Keith 
Moore who wrote the DSN RFCs for his opinion, so we'll see how this one 
will fall out. DSNs have an advantage of having an ESMTP extension defined. 
In any case, we might want to take a look at the MIME type of 
"multipart/report" within which DSNs operate. This MIME part might be used 
for CRI, patterned after the DSNs structure.

Yakov






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