IETF Logo Mail Archive

RE: [Asrg] C/R Interworking Framework

"Eric Dean" <eric@purespeed.com> Wed, 28 May 2003 13:53 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 JAA03339 for <asrg-archive@odin.ietf.org>; Wed, 28 May 2003 09:53:27 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4SDr1d04841 for asrg-archive@odin.ietf.org; Wed, 28 May 2003 09:53: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 h4SDr1B04838 for <asrg-web-archive@optimus.ietf.org>; Wed, 28 May 2003 09:53:01 -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 JAA03332; Wed, 28 May 2003 09:52:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19L1Kq-0003Cd-00; Wed, 28 May 2003 09:51:21 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19L1Kq-0003Ca-00; Wed, 28 May 2003 09:51:20 -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 h4SDnOB04690; Wed, 28 May 2003 09:49:24 -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 h4SDlfB04598 for <asrg@optimus.ietf.org>; Wed, 28 May 2003 09:47:41 -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 JAA03115 for <asrg@ietf.org>; Wed, 28 May 2003 09:47:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19L1Fh-000382-00 for asrg@ietf.org; Wed, 28 May 2003 09:46:01 -0400
Received: from ns2.tidalwave.net ([66.77.68.8] helo=mailgate.purespeed.com) by ietf-mx with esmtp (Exim 4.12) id 19L1Fg-00037l-00 for asrg@ietf.org; Wed, 28 May 2003 09:46:00 -0400
Received: from purespeed.com (mail.purespeed.com [66.77.69.8]) by mailgate.purespeed.com (Postfix Relay Hub) with ESMTP id 746D513BC6; Wed, 28 May 2003 09:49:35 -0400 (EDT)
Received: from HOMEY [171.75.32.173] by purespeed.com (SMTPD32-7.13) id AD861784014C; Wed, 28 May 2003 09:45:42 -0400
From: Eric Dean <eric@purespeed.com>
To: Yakov Shafranovich <research@solidmatrix.com>, asrg@ietf.org
Subject: RE: [Asrg] C/R Interworking Framework
Message-ID: <MBEKIIAKLDHKMLNFJODBGEHMFFAA.eric@purespeed.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <5.2.0.9.2.20030527221043.00ba0b18@std5.imagineis.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
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: Wed, 28 May 2003 09:48:02 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>
> I meant mail headers as defined in RFCs 822 and 2822. A MIME header I
> believe can be used anywhere inside the message body in any part of the
> message if the message if multi-formed. RFC 822 headers are only used on
> the entire message body.

Hmm..yes, that would seem more appropriate.

>
> Perhaps we should leave enough room or provide some form of an extension
> mechanism where in implementations can provide their own ways for
> validating the responses while leaving the basic CRI protocol
> intact. This
> would allow all C/R systems to interoperate and leave room for people to
> piggy-back various systems on top of the basic CRI protocol.

That's an excellent way to put it.  Whatever we do, we should not be in
conflict with other methods.

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

v2.14.0 | Report a Bug | By Email