[Forces-protocol] Feedback on section 6.3

Jamal Hadi Salim <hadi@znyx.com> Sat, 23 October 2004 20:44 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 QAA21198 for <forces-protocol-web-archive@ietf.org>; Sat, 23 Oct 2004 16:44:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLSxw-0003nQ-4q for forces-protocol-web-archive@ietf.org; Sat, 23 Oct 2004 16:58:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLSgj-0001k3-BQ; Sat, 23 Oct 2004 16:40:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLSdC-00019V-30 for forces-protocol@megatron.ietf.org; Sat, 23 Oct 2004 16:36:54 -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 QAA20991 for <forces-protocol@ietf.org>; Sat, 23 Oct 2004 16:36:51 -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 1CLSqI-0003h4-I7 for forces-protocol@ietf.org; Sat, 23 Oct 2004 16:50:26 -0400
Received: from [127.0.0.1] ([208.2.156.2]) by lotus.znyx.com (Lotus Domino Release 5.0.11) with ESMTP id 2004102313392355:39243 ; Sat, 23 Oct 2004 13:39:23 -0700
From: Jamal Hadi Salim <hadi@znyx.com>
To: avri@psg.com
In-Reply-To: <CE5A3946-252D-11D9-9DB1-000393CC2112@psg.com>
References: <468F3FDA28AA87429AD807992E22D07E02579210@orsmsx408> <1E526654-24BF-11D9-9DB1-000393CC2112@psg.com> <417A23E6.7010504@zurich.ibm.com> <005b01c4b907$242b1790$020aa8c0@wwm1> <417AA8B6.1040601@zurich.ibm.com> <1098558745.1097.42.camel@jzny.localdomain> <CE5A3946-252D-11D9-9DB1-000393CC2112@psg.com>
Organization: ZNYX Networks
Message-Id: <1098563810.1096.93.camel@jzny.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2
Date: 23 Oct 2004 16:36:50 -0400
X-MIMETrack: Itemize by SMTP Server on Lotus/Znyx(Release 5.0.11 |July 24, 2002) at 10/23/2004 01:39:23 PM, Serialize by Router on Lotus/Znyx(Release 5.0.11 |July 24, 2002) at 10/23/2004 01:39:24 PM, Serialize complete at 10/23/2004 01:39:24 PM
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>, ram.gopal@nokia.com, Ligang Dong <donglg@mail.hzic.edu.cn>, forces-protocol@ietf.org, Weiming Wang <wmwang@mail.hzic.edu.cn>, Robert Haas <rha@zurich.ibm.com>
Subject: [Forces-protocol] Feedback on section 6.3
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: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit

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.

+ What is PACKET SUBSCRIBE/UNSUBSCRIBE?

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



cheers,
jamal


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