[Forces-protocol] RE: Instance Select
"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Fri, 22 October 2004 01:16 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 VAA20652 for <forces-protocol-web-archive@ietf.org>; Thu, 21 Oct 2004 21:16:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKoF4-00005F-Ob for forces-protocol-web-archive@ietf.org; Thu, 21 Oct 2004 21:29:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKlS1-0000jm-Is; Thu, 21 Oct 2004 18:30:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKk1j-0008DO-7b for forces-protocol@megatron.ietf.org; Thu, 21 Oct 2004 16:59:15 -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 QAA25397 for <forces-protocol@ietf.org>; Thu, 21 Oct 2004 16:59:12 -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 1CKkEP-00009t-Oy for forces-protocol@ietf.org; Thu, 21 Oct 2004 17:12:22 -0400
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7]) 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 i9LKw1w9027201; Thu, 21 Oct 2004 20:58:01 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 i9LKoiQG030698; Thu, 21 Oct 2004 20:51:56 GMT
Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004102113581514637 ; Thu, 21 Oct 2004 13:58:15 -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); Thu, 21 Oct 2004 13:58:14 -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
Date: Thu, 21 Oct 2004 13:58:13 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E02F99EC4@orsmsx408>
Thread-Topic: Instance Select
Thread-Index: AcS3qzh4z9sL5ur3Q+G9g6ocPFQXdQABTOyQ
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: hadi@znyx.com
X-OriginalArrivalTime: 21 Oct 2004 20:58:14.0839 (UTC) FILETIME=[AED2BC70:01C4B7B0]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: quoted-printable
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>, "Deleganes, Ellen M" <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
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: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: quoted-printable
Sounds good to me...we can leave a Editorial note in saying that this issue needs further discussion. In the mean time, can should continue discussion even on this mailing list and I will be happy to arrange a conference call before the IETF, if that is needed/requested. regards Hormuzd -----Original Message----- From: Jamal Hadi Salim [mailto:hadi@znyx.com] Sent: Thursday, October 21, 2004 1:19 PM To: Khosravi, Hormuzd M Cc: Wang,Weiming; forces-protocol@ietf.org; Joel M. Halpern; ram.gopal@nokia.com; Yang, Lily L; Alan DeKok; zsolt@nc.rr.com; Steven "Blake (petri-meat); Deleganes, Ellen M Subject: RE: Instance Select 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