IETF Logo Mail Archive

RE: [Forces-protocol] RE: GET/SET in one msg ?

"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Mon, 18 October 2004 04:21 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25639 for <forces-protocol-web-archive@ietf.org>; Mon, 18 Oct 2004 00:21:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJPDA-00072F-Ee for forces-protocol-web-archive@ietf.org; Mon, 18 Oct 2004 00:33:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJOye-0002cO-PT; Mon, 18 Oct 2004 00:18:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJOwk-00020c-5v for forces-protocol@megatron.ietf.org; Mon, 18 Oct 2004 00:16:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24446 for <forces-protocol@ietf.org>; Mon, 18 Oct 2004 00:16:31 -0400 (EDT)
Received: from fmr05.intel.com ([134.134.136.6] helo=hermes.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJP8f-0006pT-1I for forces-protocol@ietf.org; Mon, 18 Oct 2004 00:28:53 -0400
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7]) by hermes.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-outer.mc,v 1.15 2004/01/30 18:16:28 root Exp $) with ESMTP id i9I4JemE018876; Mon, 18 Oct 2004 04:19:40 GMT
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by talaria.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-inner.mc,v 1.11 2004/07/29 22:51:53 root Exp $) with SMTP id i9I49i74004787; Mon, 18 Oct 2004 04:09:44 GMT
Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004101721154413882 ; Sun, 17 Oct 2004 21:15:44 -0700
Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Sun, 17 Oct 2004 21:15:44 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Forces-protocol] RE: GET/SET in one msg ?
Date: Sun, 17 Oct 2004 21:15:29 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E025791E5@orsmsx408>
Thread-Topic: [Forces-protocol] RE: GET/SET in one msg ?
Thread-Index: AcS0A9SuIKE3+OnSSBaiP+GAz3jk1QAxDaQg
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: "Joel M. Halpern" <jhalpern@MEGISTO.com>, zsolt@nc.rr.com, Jamal Hadi Salim <hadi@znyx.com>
X-OriginalArrivalTime: 18 Oct 2004 04:15:44.0295 (UTC) FILETIME=[2310DB70:01C4B4C9]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: quoted-printable
Cc: ram.gopal@nokia.com, forces-protocol@ietf.org, "Steven Blake (petri-meat)" <slblake@petri-meat.com>, Alan DeKok <alan.dekok@idt.com>, "Deleganes, Ellen M" <ellen.m.deleganes@intel.com>, "Yang, Lily L" <lily.l.yang@intel.com>
X-BeenThere: forces-protocol@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: forces-protocol <forces-protocol.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/forces-protocol>
List-Post: <mailto:forces-protocol@ietf.org>
List-Help: <mailto:forces-protocol-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=subscribe>
Sender: forces-protocol-bounces@ietf.org
Errors-To: forces-protocol-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: quoted-printable

-----Original Message-----
From: Joel M. Halpern [mailto:jhalpern@MEGISTO.com] 

PS: On the structuring of messages and operations, I can live with
creating 
two kinds of operations, one type for query operations, used in query 
messages, and one type for manipulation  operations, used in config 
messages.  Clearly, we want the structures to be the same, even if we do

use two message types.

[HK] Agreed, seems like we have a concensus on this issue now
(CONFIG-REQUEST, CONFIG-RESPONSE, QUERY-REQUEST, QUERY-RESPONSE msgs).

Jamal, can we close on this one now for the protocol? Think you said
yes, but just want to confirm.

Thanks
Hormuzd


_______________________________________________
Forces-protocol mailing list
Forces-protocol@ietf.org
https://www1.ietf.org/mailman/listinfo/forces-protocol

v2.23.0 | Report a Bug | By Email