[Forces-protocol] RE: draft-ietf-forces-protocol-01.txt
"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Mon, 25 October 2004 23:49 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 TAA19539 for <forces-protocol-web-archive@ietf.org>; Mon, 25 Oct 2004 19:49:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMEoQ-0004fK-GD for forces-protocol-web-archive@ietf.org; Mon, 25 Oct 2004 20:03:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMELd-0005NQ-Mg; Mon, 25 Oct 2004 19:33:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMBZB-0003c5-DX for forces-protocol@megatron.ietf.org; Mon, 25 Oct 2004 16:35:45 -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 QAA06011 for <forces-protocol@ietf.org>; Mon, 25 Oct 2004 16:35:42 -0400 (EDT)
Received: from fmr12.intel.com ([134.134.136.15] helo=orsfmr001.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMBmh-0008NM-7F for forces-protocol@ietf.org; Mon, 25 Oct 2004 16:49:43 -0400
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7]) 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 i9PKZsQm025678; Mon, 25 Oct 2004 20:35:55 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 i9PKQwKM019775; Mon, 25 Oct 2004 20:28:37 GMT
Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id M2004102513351022982 ; Mon, 25 Oct 2004 13:35:10 -0700
Received: from orsmsx408.amr.corp.intel.com ([192.168.65.52]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 25 Oct 2004 13:35:10 -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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Oct 2004 13:35:08 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E0302DC49@orsmsx408>
Thread-Topic: draft-ietf-forces-protocol-01.txt
Thread-Index: AcS6iTMyo20TNpE/SVOipDhic+KjEQASL1kw
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: Robert Haas <rha@zurich.ibm.com>, avri@psg.com
X-OriginalArrivalTime: 25 Oct 2004 20:35:10.0515 (UTC) FILETIME=[1F5AA830:01C4BAD2]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Content-Transfer-Encoding: quoted-printable
Cc: "((Ram Gopal ))" <ram.gopal@nokia.com>, Jamal Hadi Salim <hadi@znyx.com>, Weiming Wang <wmwang@mail.hzic.edu.cn>, Ligang Dong <donglg@mail.hzic.edu.cn>, forces-protocol@ietf.org
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: b2809b6f39decc6de467dcf252f42af1
Content-Transfer-Encoding: quoted-printable
Robert, It seems to me like some of the changes below need to be discussed before they are made in the draft. Most are editorial though, Regards Hormuzd -----Original Message----- From: Robert Haas [mailto:rha@zurich.ibm.com] Sent: Monday, October 25, 2004 4:52 AM To: avri@psg.com Cc: forces-protocol@ietf.org; Khosravi, Hormuzd M; Jamal Hadi Salim; ((Ram Gopal )); Ligang Dong; Weiming Wang Subject: Re: draft-ietf-forces-protocol-01.txt 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
- [Forces-protocol] RE: draft-ietf-forces-protocol-… Khosravi, Hormuzd M
- [Forces-protocol] RE: draft-ietf-forces-protocol-… Khosravi, Hormuzd M