[Forces-protocol] RE: Meaning of PACKET *SUBSCRIBE operation type unclear

Jamal Hadi Salim <hadi@znyx.com> Tue, 26 October 2004 01:26 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 VAA28265 for <forces-protocol-web-archive@ietf.org>; Mon, 25 Oct 2004 21:26:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMGKS-0006cS-OK for forces-protocol-web-archive@ietf.org; Mon, 25 Oct 2004 21:40:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMG5s-0006jc-Dt; Mon, 25 Oct 2004 21:25:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMFy9-0004P8-4n for forces-protocol@megatron.ietf.org; Mon, 25 Oct 2004 21:17:49 -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 VAA27744 for <forces-protocol@ietf.org>; Mon, 25 Oct 2004 21:17:46 -0400 (EDT)
Received: from znx208-2-156-007.znyx.com ([208.2.156.7] helo=lotus.znyx.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMGBh-0006T4-Mc for forces-protocol@ietf.org; Mon, 25 Oct 2004 21:31:50 -0400
Received: from [127.0.0.1] ([208.2.156.2]) by lotus.znyx.com (Lotus Domino Release 5.0.11) with ESMTP id 2004102518201246:41644 ; Mon, 25 Oct 2004 18:20:12 -0700
From: Jamal Hadi Salim <hadi@znyx.com>
To: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
In-Reply-To: <468F3FDA28AA87429AD807992E22D07E0302DD86@orsmsx408>
References: <468F3FDA28AA87429AD807992E22D07E0302DD86@orsmsx408>
Organization: ZNYX Networks
Message-Id: <1098753460.1041.29.camel@jzny.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2
Date: 25 Oct 2004 21:17:40 -0400
X-MIMETrack: Itemize by SMTP Server on Lotus/Znyx(Release 5.0.11 |July 24, 2002) at 10/25/2004 06:20:12 PM, Serialize by Router on Lotus/Znyx(Release 5.0.11 |July 24, 2002) at 10/25/2004 06:20:18 PM, Serialize complete at 10/25/2004 06:20:18 PM
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: ram.gopal@nokia.com, "Wang, Weiming" <wmwang@mail.hzic.edu.cn>, forces-protocol@ietf.org, avri@psg.com, Ligang Dong <donglg@mail.hzic.edu.cn>, Robert Haas <rha@zurich.ibm.com>
Subject: [Forces-protocol] RE: Meaning of PACKET *SUBSCRIBE operation type unclear
X-BeenThere: forces-protocol@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: hadi@znyx.com
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.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit

Seems to me this would probably be difficult to do per LFB.
Yes, the LFB will request for certain packets to be sent to it.
However _who_ does it send this request to is the question.
Lets put it on the agenda for wednesday meeting (Which i plan to attend)

cheers,
jamal

On Mon, 2004-10-25 at 17:17, Khosravi, Hormuzd M wrote:
> Robert,
> 
> I am not so sure about this, what kind of attributes would the LFB have
> to expose for this ?
> What do others think about this ? Jamal, you had a similar
> question...let us know what your experience has been in this regard.
> 
> In our experience, we had such messages which would specify filters,
> e.g. Packet Subscribe for filters A, B, C, etc. But I am fine with doing
> this a different way as well...what is important is that this
> functionality needs to be supported by the protocol.
> 
> Thanks
> Hormuzd 
> 
> -----Original Message-----
> From: Robert Haas [mailto:rha@zurich.ibm.com] 
> 
> My current thinking is that any LFB that generates PKT_REDIR messages 
> will provide attributes that can be configured to decide which packets 
> must be redirected or mirrored. A CONFIG msg to the appropriate 
> attribute(s) should suffice, no ?
> 
> Regards,
> -Robert


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