[Forces-protocol] RE: Feedback on section 6.3

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

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24203 for <forces-protocol-web-archive@ietf.org>; Mon, 25 Oct 2004 02:46:39 -0400 (EDT)
Received: from megatron.ietf.org ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLyqG-00074G-8b for forces-protocol-web-archive@ietf.org; Mon, 25 Oct 2004 03:00:32 -0400
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLybs-0004hz-SD; Mon, 25 Oct 2004 02:45:40 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLyb3-0004ec-7P for forces-protocol@megatron.ietf.org; Mon, 25 Oct 2004 02:44:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24143 for <forces-protocol@ietf.org>; Mon, 25 Oct 2004 02:44:47 -0400 (EDT)
Received: from fmr05.intel.com ([] helo=hermes.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLyoR-00071m-R2 for forces-protocol@ietf.org; Mon, 25 Oct 2004 02:58:40 -0400
Received: from talaria.jf.intel.com (talaria.jf.intel.com []) by hermes.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 i9P6mErk002087; Mon, 25 Oct 2004 06:48:14 GMT
Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.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 i9P6beJY004711; Mon, 25 Oct 2004 06:37:45 GMT
Received: from orsmsx332.amr.corp.intel.com ([]) by orsmsxvs041.jf.intel.com (SAVSMTP with SMTP id M2004102423441703452 ; Sun, 24 Oct 2004 23:44:17 -0700
Received: from orsmsx408.amr.corp.intel.com ([]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Sun, 24 Oct 2004 23:44:17 -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: Sun, 24 Oct 2004 23:44:02 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E02579224@orsmsx408>
Thread-Topic: Feedback on section 6.3
Thread-Index: AcS5QAsAX0qkSGFIQsaswILUFnWiNwBF4SaQ
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: <hadi@znyx.com>, <avri@psg.com>
X-OriginalArrivalTime: 25 Oct 2004 06:44:17.0227 (UTC) FILETIME=[0C7A99B0:01C4BA5E]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable
Cc: ram.gopal@nokia.com, Robert Haas <rha@zurich.ibm.com>, Weiming Wang <wmwang@mail.hzic.edu.cn>, Ligang Dong <donglg@mail.hzic.edu.cn>, forces-protocol@ietf.org
Subject: [Forces-protocol] RE: Feedback on section 6.3
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: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: quoted-printable


Thanks for your comments and very sorry for the delay in responding to
I hope you will understand (having a 6 month old yourself)...
Pls see my replies below...

-----Original Message-----
From: Jamal Hadi Salim [mailto:hadi@znyx.com] 

section 6.3

- 6.3.1  Config Message

+ "Config data"   should be "Config data and path"
[Sure, this is minor, I'll make this change in the next version]

+ Type is bad to describe operations. That should be operations
[not sure what you mean?, this is according to your diagram]

+ UPDATE/REPLACE, DEL ALL are really flag extensions which will become
clear once we have path-data noise cleared. Suggest you remove.
[These are basic operations everyone (including model team) agrees with,
I don't think these are related with path-data in any way...]

[This is to support the Requirements RFC section 6 #9 "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"...I
you have an alternative way to support this in the protocol messages,
let me know]

- 6.3.2  Config Response Message

Why do we have " Operation Result "
As far as i can see it is sufficient to look at the Main header type,
a operation, path and its associated data.
Unless this is meant to be a less verbose result? [exactly, that's the

+ BTW, what is the point of mentioning "single or Array LFB
       specific result entries" or result might be TLV. Just say the 
presentation of the data is stuill under discussion.
[sure, I will make this change as well in the next release...hopefully
we have more details by then ]

Thanks & Regards

Forces-protocol mailing list