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

"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Mon, 25 October 2004 23:49 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19627 for <forces-protocol-web-archive@ietf.org>; Mon, 25 Oct 2004 19:49:59 -0400 (EDT)
Received: from megatron.ietf.org ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMEok-0004gK-8c for forces-protocol-web-archive@ietf.org; Mon, 25 Oct 2004 20:04:03 -0400
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMENl-0006iE-5h; Mon, 25 Oct 2004 19:36:09 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMBdh-0004ea-3R for forces-protocol@megatron.ietf.org; Mon, 25 Oct 2004 16:40:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06677 for <forces-protocol@ietf.org>; Mon, 25 Oct 2004 16:40:21 -0400 (EDT)
Received: from fmr06.intel.com ([] helo=caduceus.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMBr8-0000AI-Ql for forces-protocol@ietf.org; Mon, 25 Oct 2004 16:54:22 -0400
Received: from talaria.jf.intel.com (talaria.jf.intel.com []) by caduceus.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-outer.mc,v 1.15 2004/01/30 18:16:28 root Exp $) with ESMTP id i9PKdRr8013536; Mon, 25 Oct 2004 20:39:27 GMT
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com []) by talaria.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-inner.mc,v 1.11 2004/07/29 22:51:53 root Exp $) with SMTP id i9PKXCJU024730; Mon, 25 Oct 2004 20:33:14 GMT
Received: from orsmsx332.amr.corp.intel.com ([]) by orsmsxvs040.jf.intel.com (SAVSMTP with SMTP id M2004102513394523987 ; Mon, 25 Oct 2004 13:39:45 -0700
Received: from orsmsx408.amr.corp.intel.com ([]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 25 Oct 2004 13:39:45 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Oct 2004 13:39:44 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E0302DC76@orsmsx408>
Thread-Topic: Meaning of PACKET *SUBSCRIBE operation type unclear
Thread-Index: AcS6iW8omijdpPo4TRKDWk8zmxIcHwASLpbQ
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: "Robert Haas" <rha@zurich.ibm.com>
X-OriginalArrivalTime: 25 Oct 2004 20:39:45.0804 (UTC) FILETIME=[C3706CC0:01C4BAD2]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable
Cc: ram.gopal@nokia.com, "Wang, Weiming" <wmwang@mail.hzic.edu.cn>, forces-protocol@ietf.org, avri@psg.com, Jamal Hadi Salim <hadi@znyx.com>, Ligang Dong <donglg@mail.hzic.edu.cn>
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
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: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable


I tried to explain this in my response to Jamal, not sure if you saw
that ? 

This has been added to support the Requirements RFC section6 #9...

 9) Packet Redirection/Mirroring
      a) The ForCES protocol MUST define a way to redirect packets from
         the FE to the CE and vice-versa.  Packet redirection terminates
         any further processing of the redirected packet at the FE.
      b) The ForCES protocol MUST define a way to mirror packets from
         the FE to the CE.  Mirroring allows the packet duplicated by
         the FE at the mirroring point to be sent to the CE while the
         original packet continues to be processed by the FE.

   Examples of packets that may be redirected or mirrored include
   control packets (such as RIP, OSPF messages) addressed to the
   interfaces or any other relevant packets (such as those with Router
   Alert Option set).  The ForCES protocol MUST also define a way for
   the CE to configure the behavior of a) and b) (above), to specify
   which packets are affected by each.

If there is a cleaner/faster way to do this, pls propose and I am happy
to discuss.
But lets not make changes to the draft before discussing these issues.


P.s. I first had this as part of Event Type, but based on your comments
I made this change, I thought this was cleaner...

-----Original Message-----
From: Robert Haas [mailto:rha@zurich.ibm.com] 

Could you please explain again the use of PACKET *SUBSCRIBE in the 
Config msg ?
Can we use another existing operation type and/or LFB for this ?


Forces-protocol mailing list