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

"Joel M. Halpern" <joel@stevecrocker.com> Sat, 13 November 2004 22:31 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 RAA06305 for <forces-protocol-web-archive@ietf.org>; Sat, 13 Nov 2004 17:31:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CT6Sm-0006NT-Uc for forces-protocol-web-archive@ietf.org; Sat, 13 Nov 2004 17:33:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CT6G5-0000vU-Pr; Sat, 13 Nov 2004 17:20:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CT64p-0007i1-Cz for forces-protocol@megatron.ietf.org; Sat, 13 Nov 2004 17:08:59 -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 RAA03794 for <forces-protocol@ietf.org>; Sat, 13 Nov 2004 17:08:57 -0500 (EST)
Received: from ns.execdsl.net ([208.184.15.238] helo=EXECDSL.COM) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CT66Q-0005A6-Cf for forces-protocol@ietf.org; Sat, 13 Nov 2004 17:10:42 -0500
Received: from [69.170.14.230] (HELO JLaptop.stevecrocker.com) by EXECDSL.COM (CommuniGate Pro SMTP 3.3) with ESMTP id 7941855; Sat, 13 Nov 2004 17:08:38 -0500
Message-Id: <6.1.2.0.0.20041113170557.03b05e00@localhost>
X-Sender: joel@stevecrocker.com@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Sat, 13 Nov 2004 17:08:18 -0500
To: hadi@znyx.com
From: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: Re: [Fwd: [Forces-protocol] Presentation of the options forLFB-level multicast]
In-Reply-To: <1100381538.2212.914.camel@jzny.localdomain>
References: <4189F776.4080306@zurich.ibm.com> <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> <6.1.2.0.0.20041111091015.03bafec0@localhost> <155001c4c8c0$5eb73ec0$845c21d2@Necom.hzic.edu.cn> <1100269665.1106.30.camel@jzny.localdomain> <156501c4c8c5$1fb19220$845c21d2@Necom.hzic.edu.cn> <1100271071.1109.38.camel@jzny.localdomain> <1100307886.1110.20.camel@jzny.localdomain> <6.1.2.0.0.20041112220931.03c89ec0@localhost> <009a01c4c934$99cf7990$020aa8c0@wwm1> <6.1.2.0.0.20041112230835.03f0b0f0@localhost> <1100381538.2212.914.camel@jzny.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>, Avri Doria <avri@acm.org>, Dong Ligang <donglg@mail.hzic.edu.cn>, forces-protocol@ietf.org, Patrick Droz <dro@zurich.ibm.com>, "\(Ram Gopal \)" <ram.gopal@nokia.com>, David.Putzolu@intel.com, Weiming Wang <wmwang@mail.hzic.edu.cn>, Robert Haas <rha@zurich.ibm.com>
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.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

Given that the instance ID of the LFB is actually a class-instance pair, I 
believe that the combination of an LFB ID and an LFB element PATH is enoguh 
to fully decode the data that goes with that path.  There is a need for 
some length information in the encoding, but no need for type 
information.  The CE already knows the schema and the class.  The 
mechanisms for extension are deliberately defined so taht information can 
be interpretted properly even when it is actually from an unknown subclass.

Yours,
Joel

At 04:33 PM 11/13/2004, Jamal Hadi Salim wrote:
>Would you say that an ID is a coherent description of a data type at
>a given hierachy level? I.e as someone who knows the schema/template for
>a LFB I should be able to tell with 100% certainty how to decode data if
>you gave me the hierachy level and the ID (assuming the ID exists in the
>template), No?


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