Re: [Fwd: [Forces-protocol] Presentation of the options for LFB-level multicast]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Fwd: [Forces-protocol] Presentation of the options for LFB-level multicast]
- To: "Wang,Weiming" <wmwang at mail.hzic.edu.cn>
- Subject: Re: [Fwd: [Forces-protocol] Presentation of the options for LFB-level multicast]
- From: Jamal Hadi Salim <hadi at znyx.com>
- Date: 10 Nov 2004 10:34:54 -0500
- Cc: "Khosravi, Hormuzd M" <hormuzd.m.khosravi at intel.com>, "\(Ram Gopal \)" <ram.gopal at nokia.com>, Avri Doria <avri at acm.org>, forces-protocol at ietf.org, joel at STEVECROCKER.COM, Patrick Droz <dro at zurich.ibm.com>, David.Putzolu at intel.com, Dong Ligang <donglg at mail.hzic.edu.cn>, Robert Haas <rha at zurich.ibm.com>
- In-reply-to: <142a01c4c6d6$13569980$845c21d2@Necom.hzic.edu.cn>
- List-archive: <http://www1.ietf.org/pipermail/forces-protocol>
- List-help: <mailto:forces-protocol-request@ietf.org?subject=help>
- List-id: forces-protocol <forces-protocol.ietf.org>
- List-post: <mailto:forces-protocol@ietf.org>
- List-subscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=unsubscribe>
- Organization: ZNYX Networks
- 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> <1099885892.2167.13.camel@jzny.localdomain> <132001c4c551$86023150$845c21d2@Necom.hzic.edu.cn> <1099911200.2169.29.camel@jzny.localdomain> <134f01c4c585$216584c0$845c21d2@Necom.hzic.edu.cn> <4191299F.4020809@zurich.ibm.com> <142a01c4c6d6$13569980$845c21d2@Necom.hzic.edu.cn>
- Reply-to: hadi at znyx.com
- Sender: forces-protocol-bounces at ietf.org
Hi Weiming,
I am not sure if this is what you are saying all along, but i think it
may be valuable to have "relative" path encoding.
i.e you say parent-path=1,2,3,4 then everything else is relative to
that.
Example if you say 5 afterwards for relative path, then the full path
is: 1,2,3,4,5.
I still dont think that "5" should be in the data portion though.
cheers,
jamal
On Tue, 2004-11-09 at 22:33, Wang,Weiming wrote:
> Hi Robert,
>
> Thank you very much to bring the slides to the meeting.
>
> ----- Original Message -----
> From: Robert Haas
> Subject: Re: [Fwd: [Forces-protocol] Presentation of the
> options for LFB-level multicast]
>
> All,
> I presented Weiming's slides just after Jamal's presentation
> yesterday. No divergence of views on the principle of how to
> describe paths was found.
>
> Whereas, according to his slides, Weiming considers that the
> distinction of Attribute, field, and index, must be reflected
> in the path notation, the consensus in the room was that this
> is not necessary: a path could be x.y.z, where it is clear
> that x must be an attribute, and y and z can be field or
> index. No need to mention it explicitely in the path notation.
> [Weiming] Actually this is not the key point. While I'm just a
> little afraid it may lead to ambiguity if , e.g., z can be a
> field ID or a subscript without tag to indicate it.
> The path can be constructed with index-search or
> content-search. The consensus in the room was that the path
> should include the whole thing, not only the first attribute,
> as opposed to Weiming's suggestion on the last slide.
> [Weiming]This is really the key point. We need to verify if it
> is possible for a single 'path' format to describe all need
> for path. I just think that, apart from the attribute ID part,
> others are tightly combined with Data. We may feel difficulty
> to try to separate path explicitly.
> Content-search remains to be defined more precisely, as well
> as block access. So it is too early to disagree ;-)
>
> Regards,
> -Robert
>
> Thank you again.
> Weiming
> Wang,Weiming wrote:
>
> > Jamal,
> >
> > ----- Original Message -----
> > From: "Jamal Hadi Salim" <hadi at znyx.com>
> >
> >
> > > On Mon, 2004-11-08 at 00:12, Wang,Weiming wrote:
> > >
> > > > Jamal,
> > > > ----- Original Message -----
> > > > From: "Jamal Hadi Salim" <hadi at znyx.com>
> > > > To: "Weiming Wang" <wmwang at mail.hzic.edu.cn>
> > > >
> > > >
> > > > > I still dont see what where we have differences. If Robert can see that
> > > > > difference i think it would be worth presenting it.
> > > > >
> > > >
> > > > Sorry, but I don't think it's very proper for you to try to stop an
> > > >
> >
> > individual
> >
> > > > presentation :)
> > > >
> > >
> > > The first step is to understand what you are trying to show.
> > > Look at how many emails it took for you to say "i see the difference".
> > >
> >
> > Sorry, I know the difference very well, just can not see why you cannot catch
> > it. That's just the 'i see the difference' mean.
> >
> > Cheers,
> > Weiming
> >
> >
> > > So i am not trying to stop your presentation rather trying to understand
> > > what you are saying. Let me go back and read your other email now.
> > >
> > > cheers,
> > > jamal
> > >
> > > PS:- Everyone i have talked to here upto before i went to bed did not
> > > see any difference. This includes Robert.
> > >
> > >
> >
> >
> >
> >
> >
>
>
> --
> Robert Haas
> IBM Zurich Research Laboratory
> Säumerstrasse 4
> CH-8803 Rüschlikon/Switzerland
> phone +41-1-724-8698 fax +41-1-724-8578 http://www.zurich.ibm.com/~rha
>
>
> ______________________________________________________________________
>
> _______________________________________________
> Forces-protocol mailing list
> Forces-protocol at ietf.org
> https://www1.ietf.org/mailman/listinfo/forces-protocol
_______________________________________________
Forces-protocol mailing list
Forces-protocol at ietf.org
https://www1.ietf.org/mailman/listinfo/forces-protocol
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.