[Forces-protocol] RE: Feedback on section 6.3

"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Sat, 23 October 2004 21:23 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23404 for <forces-protocol-web-archive@ietf.org>; Sat, 23 Oct 2004 17:23:45 -0400 (EDT)
Received: from megatron.ietf.org ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLTZh-0004WH-DC for forces-protocol-web-archive@ietf.org; Sat, 23 Oct 2004 17:37:21 -0400
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLTLd-0000Nv-1U; Sat, 23 Oct 2004 17:22:49 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLTL1-0000G6-Ip for forces-protocol@megatron.ietf.org; Sat, 23 Oct 2004 17:22:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23281 for <forces-protocol@ietf.org>; Sat, 23 Oct 2004 17:22:08 -0400 (EDT)
Received: from fmr12.intel.com ([] helo=orsfmr001.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLTY8-0004Ul-4l for forces-protocol@ietf.org; Sat, 23 Oct 2004 17:35:44 -0400
Received: from petasus.jf.intel.com (petasus.jf.intel.com []) by orsfmr001.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 i9NLMIY5000376; Sat, 23 Oct 2004 21:22:18 GMT
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com []) by petasus.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 i9NLPGfU016995; Sat, 23 Oct 2004 21:25:18 GMT
Received: from orsmsx331.amr.corp.intel.com ([]) by orsmsxvs040.jf.intel.com (SAVSMTP with SMTP id M2004102314213731500 ; Sat, 23 Oct 2004 14:21:37 -0700
Received: from orsmsx408.amr.corp.intel.com ([]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Sat, 23 Oct 2004 14:21:37 -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: Sat, 23 Oct 2004 14:21:26 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E02579214@orsmsx408>
Thread-Topic: Feedback on section 6.3
Thread-Index: AcS5QAsAX0qkSGFIQsaswILUFnWiNwABgzcw
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: <hadi@znyx.com>, <avri@psg.com>
X-OriginalArrivalTime: 23 Oct 2004 21:21:37.0920 (UTC) FILETIME=[47F36800:01C4B946]
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


I'll respond to your comments by end of today (within next 12 hrs)
Avri, pls don't make any changes before that,


-----Original Message-----
From: Jamal Hadi Salim [mailto:hadi@znyx.com] 
Sent: Saturday, October 23, 2004 1:37 PM
To: avri@psg.com
Cc: Khosravi, Hormuzd M; ram.gopal@nokia.com; Ligang Dong;
forces-protocol@ietf.org; Weiming Wang; Robert Haas
Subject: Feedback on section 6.3

section 6.3

And in general i hope those are seen as sample layouts of the message;
i.e hopefully, nobody sees that layout as the way they must build the
message with an ADD and a DEL etc.

- 6.3.1  Config Message

+ "Config data"   should be "Config data and path"

+ Type is bad to describe operations. That should be operations

+ UPDATE/REPLACE, DEL ALL are really flag extensions which will become
clear once we have path-data noise cleared. Suggest you remove.


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

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


Forces-protocol mailing list