[Forces-protocol] Re: draft-ietf-forces-protocol-01.txt

Robert Haas <rha@zurich.ibm.com> Mon, 25 October 2004 11:59 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 HAA18574 for <forces-protocol-web-archive@ietf.org>; Mon, 25 Oct 2004 07:59:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM3in-00050t-QC for forces-protocol-web-archive@ietf.org; Mon, 25 Oct 2004 08:13:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM3Se-0006b5-Fh; Mon, 25 Oct 2004 07:56:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM3RI-0006SZ-8I for forces-protocol@megatron.ietf.org; Mon, 25 Oct 2004 07:55:05 -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 HAA17965 for <forces-protocol@ietf.org>; Mon, 25 Oct 2004 07:55:02 -0400 (EDT)
Received: from e3.ny.us.ibm.com ([32.97.182.103]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM3ei-0004t8-Jw for forces-protocol@ietf.org; Mon, 25 Oct 2004 08:08:58 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e3.ny.us.ibm.com (8.12.10/8.12.9) with ESMTP id i9PBq1PJ143432; Mon, 25 Oct 2004 07:52:01 -0400
Received: from sihl.zurich.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i9PBpodh041296; Mon, 25 Oct 2004 07:51:55 -0400
Received: from [9.4.69.18] (dhcp69-18.zurich.ibm.com [9.4.69.18]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id NAA27338; Mon, 25 Oct 2004 13:51:45 +0200
Message-ID: <417CE8C7.2050701@zurich.ibm.com>
Date: Mon, 25 Oct 2004 13:51:35 +0200
From: Robert Haas <rha@zurich.ibm.com>
Organization: IBM Research Lab
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avri@psg.com
References: <468F3FDA28AA87429AD807992E22D07E02579228@orsmsx408> <572328E8-265E-11D9-9DB1-000393CC2112@psg.com>
In-Reply-To: <572328E8-265E-11D9-9DB1-000393CC2112@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by e3.ny.us.ibm.com id i9PBq1PJ143432
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: quoted-printable
Cc: Hormuzd M Khosravi <hormuzd.m.khosravi@intel.com>, "\(\(Ram Gopal \)\)" <ram.gopal@nokia.com>, Ligang Dong <donglg@mail.hzic.edu.cn>, forces-protocol@ietf.org, Jamal Hadi Salim <hadi@znyx.com>, Weiming Wang <wmwang@mail.hzic.edu.cn>
Subject: [Forces-protocol] Re: draft-ietf-forces-protocol-01.txt
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: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: quoted-printable

Avri,
Looks good. I have a few corrections, although not essential for now, 
unless you can't sleep after all the excitment on the list ...

- In the Config Response Msg section, the draft says

   Type (16 bits):
       The operations are same as those defined for Config messages.

whereas the other messages (Query, Event Notif) have now explicitely 
defined a "*-Response" operation type.  The table should therefore now 
look like:

   +-------------------+-------+------------+--------+-------------+
   |     Operation     | Query | Query-Resp | Config | Config-Resp |
   +-------------------+-------+------------+--------+-------------+
   |        Set        |       |            |    X   |             |
         Set-Response                                       X
   |                   |       |            |        |             |
   |       Delete      |       |            |    X   |             |
       Delete-Response                                      X
   |                   |       |            |        |             |
   |       Update      |       |            |    X   |            |
       Update-Response                                      X 
   |                   |       |            |        |             |
   |        Get        |   X   |            |        |             |
        Get-Response                  X 
   |                   |       |            |        |             |
   |  Event subscribe  |       |            |    X   |             |
   |  Ev.Sub.-Response |       |            |        |      X      |
   |                   |       |            |        |             |
   | Event unsubscribe |       |            |    X   |             |
   | Ev.Unsub.-Response|       |            |        |      X      |
   +-------------------+-------+------------+--------+-------------+


     +-----------+--------------+-------------+------------------+
     | Operation | Packet-Redir | Event-Notif | Event-Notif-Resp |
     +-----------+--------------+-------------+------------------+
     |  Payload  |       X      |             |                  |
     |           |              |             |                  |
     |   Report  |              |      X      |                  |
     |Report-Resp|              |             |         X        |
     +-----------+--------------+-------------+------------------+
Note that Operation "Event" was changed to "Report"


And the text I quoted above in the Config-Resp section 6.3.2 should be 
changed accordingly to :

   Type (16 bits):
       The operations include, ADD-Resp, DEL-Resp, UPDATE/REPLACE-Resp, DEL ALL-Resp, EVENT
       SUBSCRIBE-Resp, EVENT UNSUBSCRIBE-Resp, PACKET SUBSCRIBE, CANCEL-Resp.

I would drop in 6.3.1 and 6.3.2 the operation types PACKET *SUBSCRIBE. 
Note that all the messages above don't appear in the summary table, but 
maybe we should not overload the table with all of them.

-  add an Editorial's note after the text below (search for MIID):

      *  MIID table: a list of virtual LFB Instance IDs that map to a
         list of Instance IDs of LFBs in that FE

Editoral's note: it remains to be decided whether such an MIID table 
should be  used.

- search and correct typo "GET_RESPOSE"

- add a newline between Inter-FE topology and Intra-FE topology (sec 6.1.2):

         Note:  The attributes below were previously under Query
                message.
      *  Inter-FE topology Intra-FE topology


- you should appear as "Editor", not "co-editor". At least that's my 
understanding. Also, the ETRI name appears on the first page. I thought 
you said you didn't want that ? I personally don't care.

- I like the name "Core ForCES LFBs"

Thanks,
-Robert

avri@psg.com wrote:

> I have submitted the following draft:
>
> http://psg.com/~avri/forces/draft/draft-ietf-forces-protocol-01-11.txt
>
> hope it is ok.
>
> a.
>
>
>

-- 
Robert Haas
IBM Zurich Research Laboratory
Säumerstrasse 4
CH-8803 Rüschlikon/Switzerland
phone +41-1-724-8698  fax +41-1-724-8578  http://www.zurich.ibm.com/~rha


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