Re: [Forces-protocol] RE: GET/SET in one msg ?

"Weiming Wang" <wmwang@mail.hzic.edu.cn> Wed, 20 October 2004 15:12 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 LAA13336 for <forces-protocol-web-archive@ietf.org>; Wed, 20 Oct 2004 11:12:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKIKw-0002jU-H6 for forces-protocol-web-archive@ietf.org; Wed, 20 Oct 2004 11:25:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKHNa-0004ds-HN; Wed, 20 Oct 2004 10:23:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKGYT-0003kc-Cb for forces-protocol@megatron.ietf.org; Wed, 20 Oct 2004 09:31:05 -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 JAA02204 for <forces-protocol@ietf.org>; Wed, 20 Oct 2004 09:30:58 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKGkl-0000Zf-FW for forces-protocol@ietf.org; Wed, 20 Oct 2004 09:43:50 -0400
Received: from [202.96.99.56] (helo=202.96.99.56) by mx2.foretec.com with smtp (Exim 4.24) id 1CKGYK-0000h6-Lf for forces-protocol@ietf.org; Wed, 20 Oct 2004 09:30:57 -0400
Received: from [202.96.99.59] by 202.96.99.56 with StormMail ESMTP id 99432.341813895; Wed, 20 Oct 2004 21:49:36 +0800 (CST)
Received: from wwm1 (unverified [219.82.183.212]) by mail.gsu.cn (Rockliffe SMTPRA 6.0.11) with ESMTP id <B0000082780@mail.gsu.cn>; Wed, 20 Oct 2004 21:26:19 +0800
Message-ID: <00e901c4b6a9$892e55e0$020aa8c0@wwm1>
From: Weiming Wang <wmwang@mail.hzic.edu.cn>
To: hadi@znyx.com, "Joel M. Halpern" <jhalpern@megisto.com>
References: <468F3FDA28AA87429AD807992E22D07E025791E5@orsmsx408> <002d01c4b50b$1ecc9c10$020aa8c0@wwm1> <1098102734.1042.134.camel@jzny.localdomain> <013101c4b51d$a50761e0$020aa8c0@wwm1> <1098134060.1077.446.camel@jzny.localdomain> <5.1.0.14.0.20041019093826.0232d418@mail.megisto.com> <5.1.0.14.0.20041020070534.0240c390@mail.megisto.com>
Subject: Re: [Forces-protocol] RE: GET/SET in one msg ?
Date: Wed, 20 Oct 2004 21:34:12 +0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>, ram.gopal@nokia.com, "Steven Blake (petri-meat)" <slblake@petri-meat.com>, forces-protocol@ietf.org, zsolt@nc.rr.com, Alan DeKok <alan.dekok@idt.com>, Ellen M Deleganes <ellen.m.deleganes@intel.com>, "Yang, Lily L" <lily.l.yang@intel.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.3 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d

Joel,

> Even when there are large numbers of LFB instances of a given class in an
> FE that need to be set, I have trouble envisioning that they will need to
> be set to the identical values.  Some of the values will be the same.  But
> some will be different.
> If at least one value differs, then you need an operation directed at each
> individual LFB Instance.  If this is infeasible, then we have a basic
> problem that multicast at this level will not help.  If this is feasible,
> then multicast at this level seems a refinement that can wait until we know
> if we need it.
I agree your mean of 'Even when' here, therefore the 'unpractical'  I mean may
not exist. I actually don't think the extremity is a good prove for the benifits
of multiple addressing.  I just can see the great benifits even when there are
100 instances. I think it may be much helpful if you could present some drawback
for such approach. What I can see it is only a very little bit of complexity
added to the instance select field. May be I'm too pedantic :)   Anyway, I don't
think we need to wait more if we find it valuble.

Thank you.
Weiming




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