Re: [Fwd: [Forces-protocol] Presentation of the options forLFB-level multicast]

Robert Haas <rha@zurich.ibm.com> Thu, 11 November 2004 13:21 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 IAA08094 for <forces-protocol-web-archive@ietf.org>; Thu, 11 Nov 2004 08:21:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSEty-0001kt-Eu for forces-protocol-web-archive@ietf.org; Thu, 11 Nov 2004 08:22:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSErm-0001Hf-42; Thu, 11 Nov 2004 08:19:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSEom-0000wc-A2 for forces-protocol@megatron.ietf.org; Thu, 11 Nov 2004 08:16:54 -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 IAA07603 for <forces-protocol@ietf.org>; Thu, 11 Nov 2004 08:16:51 -0500 (EST)
Received: from mtagate4.uk.ibm.com ([195.212.29.137]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSEpv-0001dz-Vm for forces-protocol@ietf.org; Thu, 11 Nov 2004 08:18:05 -0500
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate4.uk.ibm.com (8.12.10/8.12.10) with ESMTP id iABDGIrQ159556; Thu, 11 Nov 2004 13:16:18 GMT
Received: from sihl.zurich.ibm.com (d06av02.portsmouth.uk.ibm.com [9.149.37.228]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iABDGGXe085538; Thu, 11 Nov 2004 13:16:16 GMT
Received: from [9.145.251.19] (sig-9-145-251-19.de.ibm.com [9.145.251.19]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id OAA82598; Thu, 11 Nov 2004 14:16:09 +0100
Message-ID: <4193660E.2070601@zurich.ibm.com>
Date: Thu, 11 Nov 2004 14:15:58 +0100
From: Robert Haas <rha@zurich.ibm.com>
Organization: IBM Research Lab
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Wang,Weiming" <wmwang@mail.hzic.edu.cn>
Subject: Re: [Fwd: [Forces-protocol] Presentation of the options forLFB-level multicast]
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> <1100100893.2210.24.camel@jzny.localdomain> <14fc01c4c79f$75231f20$845c21d2@Necom.hzic.edu.cn>
In-Reply-To: <14fc01c4c79f$75231f20$845c21d2@Necom.hzic.edu.cn>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7a3b79fd9d7bf2ef1762376a62c51ec4
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>, hadi@znyx.com, David.Putzolu@intel.com, Dong Ligang <donglg@mail.hzic.edu.cn>
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>
Content-Type: multipart/mixed; boundary="===============1220918004=="
Sender: forces-protocol-bounces@ietf.org
Errors-To: forces-protocol-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 0e831a3b581a967a651997b2cbc2bae7


Wang,Weiming wrote:

>In some way, you may call it a thought of relative path. My view is actually
>from following thought:
>1. A single path is not enough for an operation. In some cases, we may need to
>assign several paths for an single operation, e.g.,   we may at the same time
>need to set value to 1.2.3 and 1.2.4 where 3 and 4 are field IDs for the same
>table. We may also possibly need to set 1.1 in the same operation.
>  
>
So why don't we support multiple times "path+data" under the same 
LFBSelect ?

>2. It's quite unnecessary we may set different Attributes in one single
>operation, therefore the AttrID part is always the same.
>  
>
I am not sure about this.

>Based on above, I think that:
>1. It may be very complex to have one specific 'path'  in one 'path' format to
>express the actual paths like 1.2.3 and 1.2.4 and 1.1 simulteneously , but it
>would be much simpler to have Data field to express it, like the data format as:
>    subpath(1.2.3) value, subpath(1.2.4) value, subpath(1.1) value
>  
>
Instead, take these subpaths out of the data part, and make normal paths 
out of them. That's doable if we decide to support multiple "path+data" 
under the same LFBSelect.

>2. for all subpaths, the head AttrID part is the same, and this is also the only
>part that are the same.
>
>Therefore, my thought is the AttrID part is defined in the protocol, leaving the
>subpath go along with the data.
>
>  
>
I would prefer to have the whole path in the "path", not mixing the 
subpath and the data. That sounds to me like a cleaner design. Note that 
this was the consensus in the room after the presentation. But if you 
have other arguments that would favor the "subpath going into the data", 
please share them with us.

Regards,
-Robert

>>i.e you say parent-path=1,2,3,4 then everything else is relative to
>>that.
>>    
>>
>The only possible common parent path is the Attribute ID.
>
>  
>
>>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.
>>    
>>
>When we have more than one subpath that should be expressed, you may see the
>necessity for this.
>
>
>Cheers,
>Weiming
>
>  
>
>>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@znyx.com>
>>>        >
>>>        >
>>>        > > On Mon, 2004-11-08 at 00:12, Wang,Weiming wrote:
>>>        > >
>>>        > > > Jamal,
>>>        > > > ----- Original Message -----
>>>        > > > From: "Jamal Hadi Salim" <hadi@znyx.com>
>>>        > > > To: "Weiming Wang" <wmwang@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@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/forces-protocol
>>>      
>>>
>>    
>>
>
>
>
>
>  
>

-- 
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@ietf.org
https://www1.ietf.org/mailman/listinfo/forces-protocol