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

Robert Haas <rha@zurich.ibm.com> Fri, 22 October 2004 01:13 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 VAA20127 for <forces-protocol-web-archive@ietf.org>; Thu, 21 Oct 2004 21:13:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKoCg-0008QG-C5 for forces-protocol-web-archive@ietf.org; Thu, 21 Oct 2004 21:26:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKlJB-0001Ay-Gg; Thu, 21 Oct 2004 18:21:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKjms-0002E6-8a for forces-protocol@megatron.ietf.org; Thu, 21 Oct 2004 16:43:54 -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 QAA22798 for <forces-protocol@ietf.org>; Thu, 21 Oct 2004 16:43:51 -0400 (EDT)
Received: from e4.ny.us.ibm.com ([32.97.182.104]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKjzY-0007lW-PP for forces-protocol@ietf.org; Thu, 21 Oct 2004 16:57:01 -0400
Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206]) by e4.ny.us.ibm.com (8.12.10/8.12.9) with ESMTP id i9LKhDCE632992; Thu, 21 Oct 2004 16:43:13 -0400
Received: from sihl.zurich.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by northrelay04.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i9LKiBS8124016; Thu, 21 Oct 2004 16:44:12 -0400
Received: from [9.145.255.13] (sig-9-145-255-13.de.ibm.com [9.145.255.13]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id WAA55106; Thu, 21 Oct 2004 22:42:50 +0200
Message-ID: <41781F3D.304@zurich.ibm.com>
Date: Thu, 21 Oct 2004 22:42:37 +0200
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: Steven Blake <slblake@petri-meat.com>
Subject: Re: [Forces-protocol] RE: GET/SET in one msg ?
References: <468F3FDA28AA87429AD807992E22D07E025791E9@orsmsx408> <04ab01c4b5c7$1332c430$845c21d2@Necom.hzic.edu.cn> <417573E8.7070502@zurich.ibm.com> <1098385216.2340.239.camel@localhost.localdomain> <41781915.1030401@zurich.ibm.com> <1098390473.2340.263.camel@localhost.localdomain>
In-Reply-To: <1098390473.2340.263.camel@localhost.localdomain>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>, ram.gopal@nokia.com, "Yang, Lily L" <lily.l.yang@intel.com>, Zsolt Haraszti <zsolt@nc.rr.com>, "Joel M. Halpern" <jhalpern@MEGISTO.com>, forces-protocol@ietf.org, hadi@znyx.com, Alan DeKok <alan.dekok@idt.com>, "Deleganes, Ellen M" <ellen.m.deleganes@intel.com>, "Wang, Weiming" <wmwang@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="===============1993978357=="
Sender: forces-protocol-bounces@ietf.org
Errors-To: forces-protocol-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8


Steven Blake wrote:

>>Do you think we should explicitely forbid the "layer-breaking" option,
>>or could we use both ?
>>    
>>
>
>Yes.  I consider it analogous to mixing IP addresses and ports.  It
>requires a special case in the message parser, and it just doesn't look
>clean.
>
>  
>

As we don't mix layers, you could have the following scenario: MIID M 
"contains" LFBx1, LFBy1, LFBz1 (on FEs x, y, z).
But mcast ID m only spans FE x and FE y.

So a PL message addressed to mcast ID m, and MIID M, would only act on 
LFBx1 and LFBy1.

Or do you want to require that messages to MIID m MUST go to a mcastID 
(m or sth else) that spans at least FEs x and y ? This would be a layer 
violation too, no ?


>Note that I don't see much use in needing to map a single LFB instance
>ID (MIID) to multiple instance IDs on a single ID; i.e., I don't see the
>need for multicast within the FE.  What is really needed is a
>CE-assigned LFB instance ID alias that can be used on many FEs to allow
>coordination of multicast table updates.
>
>  
>
I agree, but Zsolt example, if I recall well, included some level of 
intra-LFB multicasting.

Regards,

-- 
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