[Forces-protocol] RE: Resend: Feedback: Section 6.2

"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Fri, 29 October 2004 21:42 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 RAA16406 for <forces-protocol-web-archive@ietf.org>; Fri, 29 Oct 2004 17:42:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNeke-0003FO-CQ for forces-protocol-web-archive@ietf.org; Fri, 29 Oct 2004 17:57:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNe43-00022d-Gr; Fri, 29 Oct 2004 17:13:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNdRw-0006E1-Ej for forces-protocol@megatron.ietf.org; Fri, 29 Oct 2004 16:34:16 -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 QAA06951 for <forces-protocol@ietf.org>; Fri, 29 Oct 2004 16:34:13 -0400 (EDT)
Received: from fmr06.intel.com ([134.134.136.7] helo=caduceus.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNdgH-0000gA-B2 for forces-protocol@ietf.org; Fri, 29 Oct 2004 16:49:05 -0400
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7]) 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 i9TKXMJ7022496; Fri, 29 Oct 2004 20:33:22 GMT
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) 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 i9TKP8Op005174; Fri, 29 Oct 2004 20:26:37 GMT
Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004102913332227726 ; Fri, 29 Oct 2004 13:33:22 -0700
Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 29 Oct 2004 13:33:22 -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: Fri, 29 Oct 2004 13:33:21 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E031688E1@orsmsx408>
Thread-Topic: Resend: Feedback: Section 6.2
Thread-Index: AcS94m+BgibkvxeXT8az4KdvfDtXjAAE9s0g
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: <hadi@znyx.com>
X-OriginalArrivalTime: 29 Oct 2004 20:33:22.0496 (UTC) FILETIME=[889F4400:01C4BDF6]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable
Cc: ram.gopal@nokia.com, Ligang Dong <donglg@mail.hzic.edu.cn>, forces-protocol@ietf.org, avri@psg.com, Weiming Wang <wmwang@mail.hzic.edu.cn>, Robert Haas <rha@zurich.ibm.com>
Subject: [Forces-protocol] RE: Resend: Feedback: Section 6.2
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: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable

Ok, I see where the confusion is, the bitwise message representation is
in the correct format but the other format which you have drawn below is
not. This is a copy/paste error, I'll send out a fix to Avri.

Thanks
Hormuzd

-----Original Message-----
From: Jamal Hadi Salim [mailto:hadi@znyx.com] 
Sent: Friday, October 29, 2004 11:09 AM
To: Khosravi, Hormuzd M
Cc: avri@psg.com; Robert Haas; forces-protocol@ietf.org; Ligang Dong;
ram.gopal@nokia.com; Weiming Wang
Subject: RE: Resend: Feedback: Section 6.2

On Fri, 2004-10-29 at 13:47, Khosravi, Hormuzd M wrote:
> Jamal,
> 
> I thought we discussed this on the call and the resolution was to
change
> the Operation name from SHOW to ADVERTISE. 

The issue has nothing to do with the name but where things fit in
in the grammar.

> I am not sure why you are
> bringing this up again, pls look at the grammar once...
> 

Because it was not resolved. 

>       PL level PDU :=   MAINHDR<LFBselect>+
>       LFBselect    :=   LFBCLASSID LFBInstance <OPER>+
>       OPER         :=   <OPERATION [<path-data>]*>+
> 
> 
> I think this fits quite well into it, and the Operation name Advertise
> is more general and can be reused as opposed to what your suggestions
> are.

Look again please:

--------
   	main hdr (eg type =  Association setup)
   	     |
   	     |
   	     +--- T = LFBselect
   	     |        |
   	     |        +-- LFBCLASSID = FE object
   	     |        |
   	     |        |
   	     |        +-- LFBInstance = 0x1
   	     |
   	     +--- T = Operation = SHOW
   		      |
   		      +-- FE NAME

---------------

The operation is Not part of the LFBSelect.

It should be:

--------
   	main hdr (eg type =  Association setup)
   	     |
   	     |
   	     +--- T = LFBselect
   	             |
   	             +-- LFBCLASSID = FE object
   	             |
   	             |
   	             +-- LFBInstance = 0x1
   	             |
   	             +--- T = Operation = ADVERTISE
   		           |
   		           +-- FE NAME
---------------

If you want to leave it there call it PENAME as i suggested.


cheers,
jamal


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