RE: [Forces-protocol] FE Protocol LFBs
"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Fri, 22 October 2004 16:35 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 MAA18801 for <forces-protocol-web-archive@ietf.org>; Fri, 22 Oct 2004 12:35:59 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL2bO-0001nc-Pg for forces-protocol-web-archive@ietf.org; Fri, 22 Oct 2004 12:49:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL2MN-0005BF-Mg; Fri, 22 Oct 2004 12:33:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL2Jd-0003wC-WA for forces-protocol@megatron.ietf.org; Fri, 22 Oct 2004 12:30:58 -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 MAA18454 for <forces-protocol@ietf.org>; Fri, 22 Oct 2004 12:30:53 -0400 (EDT)
Received: from fmr06.intel.com ([134.134.136.7] helo=caduceus.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL2WR-0001g1-BG for forces-protocol@ietf.org; Fri, 22 Oct 2004 12:44:12 -0400
Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6]) by caduceus.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 i9MGTwSA000614; Fri, 22 Oct 2004 16:29:58 GMT
Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by petasus.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 i9MGXnmd024600; Fri, 22 Oct 2004 16:33:57 GMT
Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs041.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004102209300904655 ; Fri, 22 Oct 2004 09:30:10 -0700
Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 22 Oct 2004 09:30:07 -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] FE Protocol LFBs
Date: Fri, 22 Oct 2004 09:30:06 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E02FD8F49@orsmsx408>
Thread-Topic: [Forces-protocol] FE Protocol LFBs
Thread-Index: AcS4S/m2WaJB/ua7SxSyBzh9QQP2XQACDceA
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: "Wang,Weiming" <wmwang@mail.hzic.edu.cn>, hadi@znyx.com
X-OriginalArrivalTime: 22 Oct 2004 16:30:07.0998 (UTC) FILETIME=[64BB59E0:01C4B854]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable
Cc: avri@psg.com, ram.gopal@nokia.com, Robert Haas <rha@zurich.ibm.com>, Ligang Dong <donglg@mail.hzic.edu.cn>, forces-protocol@ietf.org
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: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
Weiming, All We should definitely define these LFBs related with FE, Protocol, etc as part of the protocol draft. There is no need to have them in a separate draft Regards Hormuzd -----Original Message----- From: Wang,Weiming [mailto:wmwang@mail.hzic.edu.cn] > > Also dont forget to look at the overview section in the latest draft > posted by Avri. Theres a little refinement of the split of the two LFBs > (each in its own section). > As to what to do about the FE Object and FE Protocol object, My opinion > is we should define everything taht we think we will need. > I would think the model team will take those needs and make sure its > part of the XML spec. Weiming, are you suggesting to do the xml from us? [Weiming] Yes, but I'm not sure if it should be defined inside this protocol text or just by another draft. I remember you also mentioned such thought before. We actually have the same question on Redirect LFBs, anyway any LFB like things that between FE model and protocol. Now it seems very popular to summarize everything as LFB, I even think of TML layer as LFBs from PL layer, but not sure. cheers, weiming _______________________________________________ Forces-protocol mailing list Forces-protocol@ietf.org https://www1.ietf.org/mailman/listinfo/forces-protocol
- RE: [Forces-protocol] FE Protocol LFBs Khosravi, Hormuzd M
- RE: [Forces-protocol] FE Protocol LFBs Jamal Hadi Salim