[Forces-protocol] RE: Instance Select
Jamal Hadi Salim <hadi@znyx.com> Fri, 22 October 2004 01:00 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 VAA18134 for <forces-protocol-web-archive@ietf.org>; Thu, 21 Oct 2004 21:00:29 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKnzw-0007z7-BQ for forces-protocol-web-archive@ietf.org; Thu, 21 Oct 2004 21:13:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKl9W-0000Li-4H; Thu, 21 Oct 2004 18:11:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKjOp-0003pa-7b for forces-protocol@megatron.ietf.org; Thu, 21 Oct 2004 16:19:03 -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 QAA17162 for <forces-protocol@ietf.org>; Thu, 21 Oct 2004 16:19:00 -0400 (EDT)
Received: from znx208-2-156-007.znyx.com ([208.2.156.7] helo=lotus.znyx.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKjbV-0005xX-NM for forces-protocol@ietf.org; Thu, 21 Oct 2004 16:32:10 -0400
Received: from [10.0.0.9] ([208.2.156.2]) by lotus.znyx.com (Lotus Domino Release 5.0.11) with ESMTP id 2004102113213374:36381 ; Thu, 21 Oct 2004 13:21:33 -0700
From: Jamal Hadi Salim <hadi@znyx.com>
To: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
In-Reply-To: <468F3FDA28AA87429AD807992E22D07E02F99D71@orsmsx408>
References: <468F3FDA28AA87429AD807992E22D07E02F99D71@orsmsx408>
Organization: Znyx Networks
Message-Id: <1098389939.1029.140.camel@jzny.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2
Date: Thu, 21 Oct 2004 16:18:59 -0400
X-MIMETrack: Itemize by SMTP Server on Lotus/Znyx(Release 5.0.11 |July 24, 2002) at 10/21/2004 01:21:33 PM, Serialize by Router on Lotus/Znyx(Release 5.0.11 |July 24, 2002) at 10/21/2004 01:21:35 PM, Serialize complete at 10/21/2004 01:21:35 PM
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
Cc: ram.gopal@nokia.com, "Wang, Weiming" <wmwang@mail.hzic.edu.cn>, "Joel M. Halpern" <jhalpern@MEGISTO.com>, "Steven Blake (petri-meat)" <slblake@petri-meat.com>, forces-protocol@ietf.org, Alan DeKok <alan.dekok@idt.com>, zsolt@nc.rr.com, "Yang, Lily L" <lily.l.yang@intel.com>, Ellen M Deleganes <ellen.m.deleganes@intel.com>
Subject: [Forces-protocol] RE: Instance Select
X-BeenThere: forces-protocol@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: hadi@znyx.com
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: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
My opinion is this issue should be defered for this release of the protocol draft. If Weiming can be given a slot to present on the topic (I will also provide him with my data) then lets discuss at the meeting. If not a presentation then maybe over a meal and some good caffeine. cheers, jamal On Thu, 2004-10-21 at 15:58, Khosravi, Hormuzd M wrote: > Weiming, > > I haven't seen any compelling example (real NE) to need this kind of > functionality in the protocol. > Therefore, I don't think this complexity needs to be added...at most we > need a Broadcast Instance ID definition (Send msgs to all LFBs of a > particular Type). But I will be happy to hear what Jamal, others have to > say on this ? I am not religious either way... > > > regards > Hormuzd > > -----Original Message----- > From: Wang,Weiming [mailto:wmwang@mail.hzic.edu.cn] > Sent: Wednesday, October 20, 2004 9:48 PM > To: forces-protocol@ietf.org > Cc: Khosravi, Hormuzd M; hadi@znyx.com; Joel M. Halpern; > ram.gopal@nokia.com; Yang, Lily L; Alan DeKok; zsolt@nc.rr.com; Steven > Blake (petri-meat); Deleganes, Ellen M > Subject: Instance Select > > Hi Jamal, Hormuzd, etc, > > To summarize the discussions on multiple instances, I try to propose > following > scheme for instance selection, which follows Robert's idea and Jamal's > format, > as: > > PL level PDU : = MAINHDR<LFBselect>+ > LFBselect := LFBCLASSID InsSelect <OPER>+ > InsSelect := InstanceID <RangeMark | Instance ID >+ > RangeMark := '0xFFFFFFFF'; the value is the same as Broadcast Instance > address, > no worry of ambiguity here. > > The InsSelect is a TLV, whose structure is shown as: > > main hdr (eg type = config) > | > | > +-- T = LFBselect > | | > | +- LFBCLASSID = target LFB class > | | > | | > | +- T = InsSelect > | | | > | | V = InstanceID <RangeMark | Instance ID >+ > | | > | +- T = operation { ADD, DEL, GET, etc} > ... > > Best Regards, > Weiming > > > _______________________________________________ Forces-protocol mailing list Forces-protocol@ietf.org https://www1.ietf.org/mailman/listinfo/forces-protocol
- [Forces-protocol] RE: Instance Select Khosravi, Hormuzd M
- [Forces-protocol] RE: Instance Select Jamal Hadi Salim
- [Forces-protocol] RE: Instance Select Khosravi, Hormuzd M
- [Forces-protocol] Re: Instance Select Wang,Weiming