[Forces-protocol] Meeting Notes for today

"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Wed, 27 October 2004 21:51 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19193 for <forces-protocol-web-archive@ietf.org>; Wed, 27 Oct 2004 17:51:04 -0400 (EDT)
Received: from megatron.ietf.org ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMvv9-0000D1-Q2 for forces-protocol-web-archive@ietf.org; Wed, 27 Oct 2004 18:05:32 -0400
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMvf7-000056-CK; Wed, 27 Oct 2004 17:48:57 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMva6-0007su-FK for forces-protocol@megatron.ietf.org; Wed, 27 Oct 2004 17:43:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18501 for <forces-protocol@ietf.org>; Wed, 27 Oct 2004 17:43:43 -0400 (EDT)
Received: from fmr06.intel.com ([] helo=caduceus.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMvo2-0008VJ-No for forces-protocol@ietf.org; Wed, 27 Oct 2004 17:58:11 -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 i9RLgsnx028169; Wed, 27 Oct 2004 21:42:54 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 i9RLZ1FM027718; Wed, 27 Oct 2004 21:36:04 GMT
Received: from orsmsx332.amr.corp.intel.com ([]) by orsmsxvs040.jf.intel.com (SAVSMTP with SMTP id M2004102714420031095 ; Wed, 27 Oct 2004 14:42:11 -0700
Received: from orsmsx408.amr.corp.intel.com ([]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 27 Oct 2004 14:41:49 -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
Subject: [Forces-protocol] Meeting Notes for today
Date: Wed, 27 Oct 2004 14:41:39 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E02579243@orsmsx408>
Thread-Topic: [Forces-protocol] Meeting Notes for today
Thread-Index: AcS7f3o4ECQg9kCnTLeIyq3/bNK4MAAAZoRgAAAksGAAAYJZ0AA5YlTw
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: "Robert Haas" <rha@zurich.ibm.com>, <ram.gopal@nokia.com>, <avri@psg.com>, <donglg@mail.hzic.edu.cn>, <forces-protocol@ietf.org>, <wmwang@mail.hzic.edu.cn>, <hadi@znyx.com>
X-OriginalArrivalTime: 27 Oct 2004 21:41:49.0880 (UTC) FILETIME=[C3FCD380:01C4BC6D]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: quoted-printable
Cc: "Putzolu, David" <david.putzolu@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.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable

Here are today's meeting minutes that I took....

Meeting Notes

1. PATH - Weiming wants to split path in 2 pieces, path/attribute id and
data (one is static, other depends on the data) Attribute ID may be
Table ID.
Weiming to post email with text describing the two schemes - include
Model team in email
(Advantages, disadvantages)

2. MultiLFB Addressing - 3 schemes, Robert to present at the IETF
(TLV of multiple LFB instances, MIID, changing LFB class/instance TLV
Jamal - tradeoff between compute and bandwidth

3. Packet Subscribe - 2 schemes - configure attribute of sink/source
LFBs using Config,
or special operation Packet Subscribe
Resolution - use a Config msg to configure the attribute of some LFBS
(Source/Sink like LFBs)
Do we need to define the Source/Sink LFBs - we need to define the
functionality, these LFBs would probably be defined by the model team
Do we need anything special for the packet mirroring - this is part of
the LFB attributes

4. Jamal/Robert/Hormuzd had more discussion later on about Jamal's
comments on 6.1, 6.2. One resolution was to change the name of operation
"SHOW" to "ADVERTISE". Jamal will send out an email to summarize the
other topic regarding Events being addressed to LFBs rather than CE,

Let me know if there are any comments,

Thanks all for attending,

Forces-protocol mailing list