Re: [Fwd: [Forces-protocol] Presentation of theoptionsforLFB-levelmulticast]

Jamal Hadi Salim <hadi@znyx.com> Mon, 08 November 2004 04:01 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 XAA02423 for <forces-protocol-web-archive@ietf.org>; Sun, 7 Nov 2004 23:01:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CR0j6-0004vD-Am for forces-protocol-web-archive@ietf.org; Sun, 07 Nov 2004 23:01:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CR0bg-0007ap-QM; Sun, 07 Nov 2004 22:54:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CR0Z7-00079y-Nw for forces-protocol@megatron.ietf.org; Sun, 07 Nov 2004 22:51:37 -0500
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 WAA01781 for <forces-protocol@ietf.org>; Sun, 7 Nov 2004 22:51:34 -0500 (EST)
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 1CR0ZZ-0004jn-Gu for forces-protocol@ietf.org; Sun, 07 Nov 2004 22:52:06 -0500
Received: from localhost ([208.2.156.2]) by lotus.znyx.com (Lotus Domino Release 5.0.11) with ESMTP id 2004110719552454:13942 ; Sun, 7 Nov 2004 19:55:24 -0800
Subject: Re: [Fwd: [Forces-protocol] Presentation of theoptionsforLFB-levelmulticast]
From: Jamal Hadi Salim <hadi@znyx.com>
To: Weiming Wang <wmwang@mail.hzic.edu.cn>
In-Reply-To: <00bd01c4c536$fb418ee0$020aa8c0@wwm1>
References: <4189F776.4080306@zurich.ibm.com> <1099700691.1038.2.camel@jzny.localdomain> <005101c4c408$dc341600$020aa8c0@wwm1> <1099752095.1037.11.camel@jzny.localdomain> <003201c4c46d$1bbce4a0$020aa8c0@wwm1><004201c4c4ec$61d34c20$020aa8c0@wwm1> <1099829057.2165.18.camel@jzny.localdomain> <00bd01c4c536$fb418ee0$020aa8c0@wwm1>
Organization: ZNYX Networks
Message-Id: <1099885892.2167.13.camel@jzny.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2
Date: 07 Nov 2004 22:51:32 -0500
X-MIMETrack: Itemize by SMTP Server on Lotus/Znyx(Release 5.0.11 |July 24, 2002) at 11/07/2004 07:55:24 PM, Serialize by Router on Lotus/Znyx(Release 5.0.11 |July 24, 2002) at 11/07/2004 07:55:27 PM, Serialize complete at 11/07/2004 07:55:27 PM
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>, "\(Ram Gopal \)" <ram.gopal@nokia.com>, Avri Doria <avri@acm.org>, forces-protocol@ietf.org, joel@STEVECROCKER.COM, Patrick Droz <dro@zurich.ibm.com>, David.Putzolu@intel.com, Dong Ligang <donglg@mail.hzic.edu.cn>, Robert Haas <rha@zurich.ibm.com>
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: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit

Weiming,

On Sun, 2004-11-07 at 21:02, Weiming Wang wrote:
> Jamal,
> 
> ----- Original Message -----
> From: "Jamal Hadi Salim" <hadi@znyx.com>
> >
> > Weiming,
> >
> > As i am reading your slides I cant to seem to see what the difference is
> > with your scheme (vs what i would call "other"). Maybe we are just
> > saying the same thing.
> Firstly, I should say the index based path is fairly the same as you mentioned.
> Only thing I just want to specifically mention is even in the index based path
> scheme, the field ID also plays important role, and the field ID is different
> from index (subscript).

Is this the same as content based description in slide 23?
Note that content based is under discussion

> >
> > Lets use your example to refer to set g1 to value of vg1:
> >
> > You say:
> > AttrID2[i=1].f2[j=1].g1=vg1
> >
> > Other scheme:
> > Assuming table refered by AttrID2 has ID=2 and f2 has ID=2 and g1 has
> > ID=1, then configuring g1 as you described is:
> > [2,1,2,1,1]=vg1
> >
> > Is your difference in how this is presented? i.e you seem to say:
> > [2,[1]],[2,[1]],1 ? Did i get this right?
> [Weiming]This expression is actually not important. The important is it should
> contain f2 ID as well as indexes.


Weiming, Isnt this f2 the same as #2 that i assumed above when i said
"Assuming table refered by AttrID2 has ID=2 and f2 has ID=2 "?
Maybe you are refering to a mixture of content and Ids? 

> > It seems to me that we are both saying that a vector, such as a table
> > entry will have two or more "coordinates" (table,index) but a scalar
> > such as what you refer to as AttrID1 will have a single entry.
> [Weiming]Yes, this is another point I just want to say. By this, I just want to
> say that index-based searching is not enough. We have to use field ID (content)
> based searching.
> 

Content based access is tabled under discussion in slide 23.

> >
> > Please respond as soon as you can because i am not sure what to say
> > and i have asked around here and havent anyone who could point the
> > difference.
> Because it seems quite discussion topic and not very proper to be put in our
> protocol presentation, therefore I just want to ask Robert to help to show it.
> 

I still dont see what where we have differences. If Robert can see that
difference i think it would be worth presenting it. 

cheers,
jamal


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