RE: [Asrg] C/R Framework

"Eric D. Williams" <eric@infobro.com> Thu, 15 May 2003 13:35 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 JAA08539 for <asrg-archive@odin.ietf.org>; Thu, 15 May 2003 09:35:21 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4FD2MP31171 for asrg-archive@odin.ietf.org; Thu, 15 May 2003 09:02:22 -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 h4FD2MB31168 for <asrg-web-archive@optimus.ietf.org>; Thu, 15 May 2003 09:02:22 -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 JAA08521; Thu, 15 May 2003 09:34:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GIua-0007Ix-00; Thu, 15 May 2003 09:36:44 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19GIua-0007Iu-00; Thu, 15 May 2003 09:36:44 -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 h4FCw2B30850; Thu, 15 May 2003 08:58:02 -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 h4FCvUB30818 for <asrg@optimus.ietf.org>; Thu, 15 May 2003 08:57:30 -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 JAA08426 for <asrg@ietf.org>; Thu, 15 May 2003 09:29:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GIpt-0007HQ-00 for asrg@ietf.org; Thu, 15 May 2003 09:31:53 -0400
Received: from black.infobro.com ([63.71.25.39] helo=infobro.com) by ietf-mx with smtp (Exim 4.12) id 19GIps-0007HM-00 for asrg@ietf.org; Thu, 15 May 2003 09:31:52 -0400
Received: from red (unverified [207.199.136.153]) by infobro.com (EMWAC SMTPRS 0.83) with SMTP id <B0002496426@infobro.com>; Thu, 15 May 2003 09:30:58 -0400
Received: by localhost with Microsoft MAPI; Thu, 15 May 2003 09:31:04 -0400
Message-ID: <01C31AC4.B47B5680.eric@infobro.com>
From: "Eric D. Williams" <eric@infobro.com>
To: 'Eric Dean' <eric@purespeed.com>, "asrg@ietf.org" <asrg@ietf.org>
Subject: RE: [Asrg] C/R Framework
Organization: Information Brokers, Inc.
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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/pipermail/asrg/>
Date: Thu, 15 May 2003 09:30:13 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Wednesday, May 14, 2003 10:24 PM, Eric Dean [SMTP:eric@purespeed.com] wrote:
8<...>8
>  << File: CR_System.txt >>

Introduction
"Challenge Response systems intend to authenticate a sender's identity and 
determine if a sender originated a message to a particular recipient."

Suggested change:

Challenge Response systems intend to validate message origination for a 
designated recipient.

Rationale:

C/R systems may not be required to authenticate identity (perhaps they should 
not, that does not matter) however the basis intent is to validate using some 
mechanism (automated or manual) a messages originator, where origination may be 
a human or machine actor.  Additionally, the use of 'particular' connotes for 
me that any 'addressed' recipient may be the subject of 'determination'.  IMHO, 
the more appropriate term would be designated recipient as that for me connotes 
an association between the originator and the recipient.

On a slightly different point, in my terms a sender and originator are 
functionally equivalent but since your paper also addresses possible machine 
actors I use the term originator as a semantic abstraction.

<insert>
Message Originator

 An actor, human or machine, that causes the insertion of an
 original or revised message into the message transfer system.

Sender

 The nomenclature used to designate a message originator or a
 process acting as a origination point for a message in the MTS.
 Sender is also a message header.
</insert>

-e

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