From exim@www1.ietf.org Tue Jul 1 03:48:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01898 for ; Tue, 1 Jul 2003 03:48:42 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h617mGe20620 for gsmp-archive@odin.ietf.org; Tue, 1 Jul 2003 03:48:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XFs8-0005MV-0e for gsmp-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 03:48:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01892 for ; Tue, 1 Jul 2003 03:48:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XFry-0000fV-00 for gsmp-web-archive@ietf.org; Tue, 01 Jul 2003 03:48:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XFrr-0000fS-00 for gsmp-web-archive@ietf.org; Tue, 01 Jul 2003 03:47:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XFrs-0005KH-Jr; Tue, 01 Jul 2003 03:48:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XFrk-0005Jy-HE for gsmp@optimus.ietf.org; Tue, 01 Jul 2003 03:47:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01889 for ; Tue, 1 Jul 2003 03:47:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XFrg-0000fO-00 for gsmp@ietf.org; Tue, 01 Jul 2003 03:47:48 -0400 Received: from apocalypse.org ([192.48.232.17] ident=[RQu9VJWNFJ/p//jolqe7GDcbQwM1sX5V]) by ietf-mx with esmtp (Exim 4.12) id 19XFrV-0000fI-00 for gsmp@ietf.org; Tue, 01 Jul 2003 03:47:37 -0400 Received: from apocalypse.org (IDENT:ysRP3IQKTYJ9DXttTVFFEzXxMs1yfwlT@apocalypse.org [192.48.232.17]) by apocalypse.org (8.11.6/8.11.6) with ESMTP id h617lCG02735 for ; Tue, 1 Jul 2003 03:47:13 -0400 Date: Tue, 1 Jul 2003 16:47:11 +0900 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: avri To: gsmp@ietf.org Content-Transfer-Encoding: 7bit Message-Id: <396A2BF4-AB98-11D7-8EF1-000393CC2112@apocalypse.org> X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [GSMP] Status on Base Spec Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit (since i asked every team - or individual - working on a WG draft to send in a report of their status, I might as well go first) draft-ietf-gsmp-v3-base-spec-02.txt submitted 30 June Changes since draft-ietf-gsmpv3-base-01 1. Added MSG 24 - Triggered Add 2. Added MSG 25 - Block Add 3. Generalized Capability Set definition for technology specific use. 4. Remove VPI specific text in Report Connection State MSG. 5. Removed reference to static partitions and added mention of Partition Manager notifying switch and controller of partition resource changes Things that Remain to be done: - add notation that 8 event flags (8-15) are reserved for technology specific definition - addition of a technology specific block to msg 64 (switch configuration message) - msg 65 - the porttype specific data needs generalization. - add block to port configuration message to support port specific adaptations. - update label management - update statistics messages - update layer switching information - extend port configuration command - deal with protection ( i spent a lot of time thinking about this one and am still working on it - i have a partial draft with some changes - but still have a lot of questions - i will send a message on this topic soon) - make some of the clarifications and corrections the requirements spec includes in section 3. On most of these, i want to consult with the authors of the other specs to make sure i get it right. Most of it is trivial to change especially in the base spec since i am largely creating blocks the technology specific folks need to fill in. this is not the case, of course, with the protection issue. draft-ietf-gsmpv3-optical-spec-02 has some suggestions that i am have been using as template suggestions for some of these issues, but i think we need to make sure the solutions work for all of the specifications. The editors are planning to work together while we are in Vienna. Concerns should be posted to the list. I plan to work on finishing the changes after this meeting - as opposed to waiting until just before the next meeting as i did this time. Note: draft-ietf-gsmp-v3-base-spec-02.txt has awful page breaks in a lot of the message pictures. i need to fix this, and am hoping the xml2rfc folks come up with a clever solution - otherwise it will take putting in page breaks by hand for all of the pictures that break. i only plan to do that near the end of this editing cycle. BTW, i am not complaining about xml2rfc. I think it is wonderful and recommend it highly. a. _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Tue Jul 1 03:52:01 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01976 for ; Tue, 1 Jul 2003 03:52:01 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h617pYQ21165 for gsmp-archive@odin.ietf.org; Tue, 1 Jul 2003 03:51:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XFvK-0005VI-3s for gsmp-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 03:51:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01966 for ; Tue, 1 Jul 2003 03:51:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XFvF-0000h1-00 for gsmp-web-archive@ietf.org; Tue, 01 Jul 2003 03:51:29 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XFus-0000gi-00 for gsmp-web-archive@ietf.org; Tue, 01 Jul 2003 03:51:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XFum-0005Sl-CA; Tue, 01 Jul 2003 03:51:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XFuI-0005Qj-2Z for gsmp@optimus.ietf.org; Tue, 01 Jul 2003 03:50:30 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01941 for ; Tue, 1 Jul 2003 03:50:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XFuD-0000gS-00 for gsmp@ietf.org; Tue, 01 Jul 2003 03:50:25 -0400 Received: from cms1.etri.re.kr ([129.254.16.11] helo=cms1.cms.etri.re.kr) by ietf-mx with esmtp (Exim 4.12) id 19XFu3-0000gL-00 for gsmp@ietf.org; Tue, 01 Jul 2003 03:50:15 -0400 Received: from acm.org (129.254.191.55 [129.254.191.55]) by cms1.cms.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 3B321KZX; Tue, 1 Jul 2003 16:53:30 +0900 Date: Tue, 1 Jul 2003 16:49:49 +0900 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Avri Doria To: gsmp@ietf.org Content-Transfer-Encoding: 7bit Message-Id: <979DC18E-AB98-11D7-8EF1-000393CC2112@acm.org> X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [GSMP] Speaking of Partitioning Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Now that the partitioning requirements are published, are any of the authors of the pib and mib willing to revive their work. Not that i am insisting it must come in the form of a mib or a pib, i understand there are other options in the wind, such as xml or sming (whatever that is). The main point is someone needs to get back to working on this. Any takers? a. _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Tue Jul 1 03:56:08 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02130 for ; Tue, 1 Jul 2003 03:56:08 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h617tg621688 for gsmp-archive@odin.ietf.org; Tue, 1 Jul 2003 03:55:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XFzJ-0005dj-V1 for gsmp-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 03:55:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02099 for ; Tue, 1 Jul 2003 03:55:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XFzA-0000jA-00 for gsmp-web-archive@ietf.org; Tue, 01 Jul 2003 03:55:32 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XFyl-0000ir-00 for gsmp-web-archive@ietf.org; Tue, 01 Jul 2003 03:55:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XFyf-0005aA-AM; Tue, 01 Jul 2003 03:55:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XFyM-0005Z4-9N for gsmp@optimus.ietf.org; Tue, 01 Jul 2003 03:54:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02048 for ; Tue, 1 Jul 2003 03:54:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XFyI-0000iX-00 for gsmp@ietf.org; Tue, 01 Jul 2003 03:54:38 -0400 Received: from cms1.etri.re.kr ([129.254.16.11] helo=cms1.cms.etri.re.kr) by ietf-mx with esmtp (Exim 4.12) id 19XFxs-0000iL-00 for gsmp@ietf.org; Tue, 01 Jul 2003 03:54:12 -0400 Received: from acm.org (129.254.191.55 [129.254.191.55]) by cms1.cms.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 3B321LAP; Tue, 1 Jul 2003 16:57:34 +0900 Date: Tue, 1 Jul 2003 16:53:53 +0900 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Avri Doria To: gsmp@ietf.org Content-Transfer-Encoding: 7bit Message-Id: <28E400A8-AB99-11D7-8EF1-000393CC2112@acm.org> X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [GSMP] Speaking of MIBS Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit The current GSMP MIB RFC3295 needs to be updated to match the changes we are making. I need volunteers to edit that document. a. _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Tue Jul 1 05:02:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03460 for ; Tue, 1 Jul 2003 05:02:33 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h61928400866 for gsmp-archive@odin.ietf.org; Tue, 1 Jul 2003 05:02:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XH1c-0000Dt-3Q for gsmp-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 05:02:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03453 for ; Tue, 1 Jul 2003 05:02:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XH1X-0001FT-00 for gsmp-web-archive@ietf.org; Tue, 01 Jul 2003 05:02:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XH1R-0001FQ-00 for gsmp-web-archive@ietf.org; Tue, 01 Jul 2003 05:01:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XH1V-0000CS-DB; Tue, 01 Jul 2003 05:02:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XH10-0000C2-4H for gsmp@optimus.ietf.org; Tue, 01 Jul 2003 05:01:30 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03442 for ; Tue, 1 Jul 2003 05:01:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XH0v-0001FD-00 for gsmp@ietf.org; Tue, 01 Jul 2003 05:01:25 -0400 Received: from apocalypse.org ([192.48.232.17] ident=[2fYKrDF1EDzqsE1NzYnt2SAbiogubTLH]) by ietf-mx with esmtp (Exim 4.12) id 19XH0k-0001F5-00 for gsmp@ietf.org; Tue, 01 Jul 2003 05:01:14 -0400 Received: from apocalypse.org (IDENT:TAkiNHjKW6RKFkIf7DUeY6lJD4NGZAU1@apocalypse.org [192.48.232.17]) by apocalypse.org (8.11.6/8.11.6) with ESMTP id h6190rG20127 for ; Tue, 1 Jul 2003 05:00:53 -0400 Date: Tue, 1 Jul 2003 18:00:51 +0900 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: avri To: gsmp@ietf.org Content-Transfer-Encoding: 7bit Message-Id: <841771A9-ABA2-11D7-BC41-000393CC2112@apocalypse.org> X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [GSMP] Protection Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit i have seen and worked through a few possible solutions for the protection requirements, but i am looking for the one that is the simplest and requires the fewest changes to the protocol. i have started making some simplifying assumptions, and i am not sure to what extent the hold. So before making any changes to the spec i am hoping the specialists of protection will let me know if i am wrong. (and apologies in advance if i display glaring ignorance.) 1. 1+1 protection is not really that much different in terms of messages then any other add. First one creates a branch. Then, as is done for multicast, one adds other branches. The main difference is that one would have to designate the appropriate branches as the protection ones and thus distinguish them from multicast. Implicit in this assumption is that dedicated protection branches terminate on the same port as either the input or output port of the primary branch since they have a common label (either input or output) This would still leave issues of deletion, as I assume the protection link(s) should be deleted at the same time as the primary link. The simplest solution is for it to be a requirement that in deleting a protected link, the controller must also include delete the protection branch. 2. In the non dedicated protection modes one is reserving resources and notifying the switch that these resources are possibly available for use as protection/recovery links for designated branches. In the case of non dedicated protection, the protection link(s) can be associated with multiple connections. Assuming this is the case, then i could modify the reservation message to indicate which reservations are for protection branches and modify the connection messages to include several reservation ids. I am making the assumption that it is not necessary in the case of non-dedicated protection that the branches be on the same ports as either the input or output label. This will need to be accounted for. In the case of deletion of a primary branch, I also assume that the protection will not necessary be deleted, though it will be disassociated from the branch being deleted. I am not sure that this needs to be dealt within the GSMP messaging, though the switch would need to do the housekeeping. comments please! a. _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Tue Jul 1 13:48:17 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08432 for ; Tue, 1 Jul 2003 13:48:17 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5RIMtx21295 for gsmp-archive@odin.ietf.org; Fri, 27 Jun 2003 14:22:55 -0400 Received: from [132.151.1.176] (helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vxs6-0005P9-Hu for gsmp-web-archive@optimus.ietf.org; Fri, 27 Jun 2003 14:22:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09193 for ; Fri, 27 Jun 2003 14:22:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VxrX-000544-00 for gsmp-web-archive@ietf.org; Fri, 27 Jun 2003 14:22:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VxrM-000538-00 for gsmp-web-archive@ietf.org; Fri, 27 Jun 2003 14:22:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VxrH-0004fc-V0; Fri, 27 Jun 2003 14:22:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VnBS-0006Wr-R5 for gsmp@optimus.ietf.org; Fri, 27 Jun 2003 02:58:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19446 for ; Fri, 27 Jun 2003 02:58:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VnBO-0001sQ-00 for gsmp@ietf.org; Fri, 27 Jun 2003 02:58:06 -0400 Received: from cms1.etri.re.kr ([129.254.16.11]) by ietf-mx with esmtp (Exim 4.12) id 19VnBE-0001sN-00 for gsmp@ietf.org; Fri, 27 Jun 2003 02:57:56 -0400 Received: from apocalypse.org (129.254.191.55 [129.254.191.55]) by cms1.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NAHCTM6T; Fri, 27 Jun 2003 15:57:42 +0900 Date: Fri, 27 Jun 2003 15:47:21 +0900 Content-Type: text/plain; charset=US-ASCII; format=flowed Resent-Date: Fri, 27 Jun 2003 15:57:46 +0900 Content-Transfer-Encoding: 7bit Resent-Message-Id: <33BB01EC-A86B-11D7-9F47-000393CC2112@apocalypse.org> Resent-To: gsmp@ietf.org Mime-Version: 1.0 (Apple Message framework v552) From: avri To: gsmp@ietf.org Message-Id: Resent-From: avri X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [GSMP] question on size of reservation id - addition Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit {i left out the picture for the single port based bulk transaction msg} do we really need 32 bits of reservation id? would 16 bits suffice? since reservation ids are a global resource as opposed to a port resource, i am concerned that it might be too small a value. but the concern for parsimony dictate that i should at least ask. the questions comes in the context adding a (result,code) byte to every transaction in a bulk msg. assuming that bulk msgs would only be supported when there was a prexisitng complete reservation, that would give a trigger msd of [header] x 3 [port session id] [reservation id, result, code] and a bulk msg [header] x 3 [port session id] [reservation id, result, code] . . . [port session id] [reservation id, result, code] that is, of course assuming that a bulk msg can support transactions on multiple ports. we could also define it to support msgs on on single port per bulk message. in that case the message would look like: [header] x 3 [port session id] [reservation id, result, code] [reservation id, result, code] . . . [reservation id, result, code] would anyone who has implemented already object to such a change to the reservation id? and what do people think - should bulk message be restricted to a single port? a. _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Tue Jul 1 13:48:15 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08393 for ; Tue, 1 Jul 2003 13:48:14 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5RINSV21862 for gsmp-archive@odin.ietf.org; Fri, 27 Jun 2003 14:23:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vxsa-0005fa-0t for gsmp-web-archive@optimus.ietf.org; Fri, 27 Jun 2003 14:23:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09389 for ; Fri, 27 Jun 2003 14:22:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Vxs8-00055m-00 for gsmp-web-archive@ietf.org; Fri, 27 Jun 2003 14:22:56 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Vxrf-00053S-00 for gsmp-web-archive@ietf.org; Fri, 27 Jun 2003 14:22:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VxrK-0004iF-7Y; Fri, 27 Jun 2003 14:22:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VnLd-00006O-OX for gsmp@optimus.ietf.org; Fri, 27 Jun 2003 03:09:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19685 for ; Fri, 27 Jun 2003 03:08:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VnLZ-0001vO-00 for gsmp@ietf.org; Fri, 27 Jun 2003 03:08:37 -0400 Received: from cms1.etri.re.kr ([129.254.16.11]) by ietf-mx with esmtp (Exim 4.12) id 19VnLP-0001vI-00 for gsmp@ietf.org; Fri, 27 Jun 2003 03:08:27 -0400 Received: from apocalypse.org (129.254.191.55 [129.254.191.55]) by cms1.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NAHCTNFJ; Fri, 27 Jun 2003 16:08:13 +0900 Date: Fri, 27 Jun 2003 16:07:51 +0900 Resent-Date: Fri, 27 Jun 2003 16:08:16 +0900 Subject: Re: [GSMP] Bulk Transactions Content-Type: multipart/alternative; boundary=Apple-Mail-4--1066398038 Mime-Version: 1.0 (Apple Message framework v552) From: avri To: "Anderson, Todd A" Resent-To: gsmp@ietf.org Resent-Message-Id: <10DEB34E-A86E-11D7-9F47-000393CC2112@apocalypse.org> Resent-From: avri Message-Id: <20178DEE-A86E-11D7-9F47-000393CC2112@apocalypse.org> X-Mailer: Apple Mail (2.552) Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , --Apple-Mail-4--1066398038 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable On fredag, jun 27, 2003, at 01:41 Asia/Seoul, Anderson, Todd A wrote: > If atomicity is not > required, then you need to know which sub-messages succeeded and which=20= > failed. > =A0 or you would be required to unroll, as i think is required in snmp. a. --Apple-Mail-4--1066398038 Content-Type: text/enriched; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On fredag, jun 27, 2003, at 01:41 Asia/Seoul, Anderson, Todd A wrote: = Arial0000,0000,FFFEIf atomicity is not = Arial0000,0000,FFFErequired, then you need to know which sub-messages succeeded and which = failed. =A0 or you would be required to unroll, as i think is required in snmp. a. --Apple-Mail-4--1066398038-- _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Wed Jul 2 06:51:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01632 for ; Wed, 2 Jul 2003 06:51:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfCa-0001yb-Hg for gsmp-archive@odin.ietf.org; Wed, 02 Jul 2003 06:51:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62Ap4w2007591 for gsmp-archive@odin.ietf.org; Wed, 2 Jul 2003 06:51:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfCa-0001yM-Ek for gsmp-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 06:51:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01517 for ; Wed, 2 Jul 2003 06:50:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XfCW-00011h-00 for gsmp-web-archive@ietf.org; Wed, 02 Jul 2003 06:51:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XfCV-00011Z-00 for gsmp-web-archive@ietf.org; Wed, 02 Jul 2003 06:50:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfCY-0001x2-IS; Wed, 02 Jul 2003 06:51:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfCD-0001wP-RW for gsmp@optimus.ietf.org; Wed, 02 Jul 2003 06:50:41 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01429; Wed, 2 Jul 2003 06:50:36 -0400 (EDT) Message-Id: <200307021050.GAA01429@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: gsmp@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 02 Jul 2003 06:50:36 -0400 Subject: [GSMP] I-D ACTION:draft-ietf-gsmp-optical-spec-02.txt Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the General Switch Management Protocol Working Group of the IETF. Title : General Switch Management Protocol (GSMP) v3 for Optical Support Author(s) : J. Choi et al. Filename : draft-ietf-gsmp-optical-spec-02.txt Pages : 25 Date : 2003-7-1 This document describes the General Switch Management Protocol version 3 (GSMPv3) for the support of optical switching. GSMPv3 controller SHOULD control optical label switches and manage optical resources on them. This document describes the extended functions of GSMPv3 for optical switching and explains operational mechanisms to implement them. It SHOULD be referred with [1] for the complete implementation. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-gsmp-optical-spec-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-gsmp-optical-spec-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-gsmp-optical-spec-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-7-1133550.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-gsmp-optical-spec-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-gsmp-optical-spec-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-1133550.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Wed Jul 2 16:17:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11533 for ; Wed, 2 Jul 2003 16:17:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xo2N-0001Fg-0b for gsmp-archive@odin.ietf.org; Wed, 02 Jul 2003 16:17:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62KH6pA004806 for gsmp-archive@odin.ietf.org; Wed, 2 Jul 2003 16:17:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xo2M-0001FR-Ts for gsmp-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 16:17:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11495 for ; Wed, 2 Jul 2003 16:17:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xo2J-0006wk-00 for gsmp-web-archive@ietf.org; Wed, 02 Jul 2003 16:17:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Xo2I-0006wh-00 for gsmp-web-archive@ietf.org; Wed, 02 Jul 2003 16:17:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xo2G-0001DX-Ne; Wed, 02 Jul 2003 16:17:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xo1I-0000wh-MS for gsmp@optimus.ietf.org; Wed, 02 Jul 2003 16:16:00 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11149; Wed, 2 Jul 2003 16:15:55 -0400 (EDT) Message-Id: <200307022015.QAA11149@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: gsmp@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 02 Jul 2003 16:15:54 -0400 Subject: [GSMP] I-D ACTION:draft-ietf-gsmp-v3-base-spec-02.txt Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the General Switch Management Protocol Working Group of the IETF. Title : GSMPv3 Base Specification Author(s) : A. Doria Filename : draft-ietf-gsmp-v3-base-spec-02.txt Pages : 101 Date : 2003-7-2 This document describes the base General Switch Management Protocol Version 3 (GSMPv3). The GSMPv3 is an asymmetric protocol that allows one or more external switch controllers to establish and maintain the state of a label switch. The GSMPv3 allows control of both unicast and multicast switch connection state as well as control of switch system resources and QoS features. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-gsmp-v3-base-spec-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-gsmp-v3-base-spec-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-gsmp-v3-base-spec-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-7-2160942.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-gsmp-v3-base-spec-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-gsmp-v3-base-spec-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-2160942.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Mon Jul 7 08:44:40 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23085 for ; Mon, 7 Jul 2003 08:44:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZVLo-00077H-5O for gsmp-archive@odin.ietf.org; Mon, 07 Jul 2003 08:44:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67CiC3M027356 for gsmp-archive@odin.ietf.org; Mon, 7 Jul 2003 08:44:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZVLo-000779-1u for gsmp-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 08:44:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23070 for ; Mon, 7 Jul 2003 08:44:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZVLm-0003p1-00 for gsmp-web-archive@ietf.org; Mon, 07 Jul 2003 08:44:10 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZVLm-0003ox-00 for gsmp-web-archive@ietf.org; Mon, 07 Jul 2003 08:44:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZVLc-00075Z-RB; Mon, 07 Jul 2003 08:44:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZVLI-00075A-P8 for gsmp@optimus.ietf.org; Mon, 07 Jul 2003 08:43:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23057 for ; Mon, 7 Jul 2003 08:43:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZVLH-0003of-00 for gsmp@ietf.org; Mon, 07 Jul 2003 08:43:39 -0400 Received: from zctfs063.nortelnetworks.com ([47.164.128.120]) by ietf-mx with esmtp (Exim 4.12) id 19ZVLC-0003oI-00 for gsmp@ietf.org; Mon, 07 Jul 2003 08:43:34 -0400 Received: from zctfc040.europe.nortel.com (zctfc040.europe.nortel.com [47.164.129.95]) by zctfs063.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h67CgtA20227 for ; Mon, 7 Jul 2003 14:42:55 +0200 (MEST) Received: from zctfc002.europe.nortel.com ([47.164.129.43]) by zctfc040.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NB6NB2S0; Mon, 7 Jul 2003 14:42:55 +0200 Received: from nortelnetworks.com (ksundell-1.europe.nortel.com [47.167.132.215]) by zctfc002.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id MNLRRFA6; Mon, 7 Jul 2003 14:42:55 +0200 Message-ID: <3F096C04.9080206@nortelnetworks.com> Date: Mon, 07 Jul 2003 14:48:04 +0200 X-Sybari-Space: 00000000 00000000 00000000 From: Kenneth Sundell User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: gsmp Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [GSMP] Status on GSMPv3 Packet/L2 spec Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, here follows a list of changes between and . The changes are primarly adjustments to recent changes to the base spec (draft-ietf-gsmp-v3-base-spec-02.txt). I would appreciate any pointer to places in the document where further clean-up could improve the quality of the draft. - Changed Label Type values (ch. 3) according to the new ranges defined in the Base spec. - Removed section about Label Stacking (these are general for GSMPv3 and belong to the Base spec). - Added Definition of Capability Set Records (ch. 7.6) since they are technology specific. - Resized the Result and Code fields in the general headers reflecting the recent change in the Base spec. - Adjusted the Service ID ranges according to the ones that are being defined in the Base spec. - Added text to the Failure Response codes (Ch.11). - In addition to these, there has been a number of minor editorial changes. The next step is to coordinate with the members of the other design teams in order to finalize the work. Cheers, Ken _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Mon Jul 7 17:27:36 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17013 for ; Mon, 7 Jul 2003 17:27:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZdVt-0007ZA-C5 for gsmp-archive@odin.ietf.org; Mon, 07 Jul 2003 17:27:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67LR98r029078 for gsmp-archive@odin.ietf.org; Mon, 7 Jul 2003 17:27:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZdVt-0007Yv-7r for gsmp-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 17:27:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16999 for ; Mon, 7 Jul 2003 17:27:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZdVq-0003EI-00 for gsmp-web-archive@ietf.org; Mon, 07 Jul 2003 17:27:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZdVq-0003EF-00 for gsmp-web-archive@ietf.org; Mon, 07 Jul 2003 17:27:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZdVk-0007XU-CT; Mon, 07 Jul 2003 17:27:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZdV1-0007Wi-Fe for gsmp@optimus.ietf.org; Mon, 07 Jul 2003 17:26:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16984 for ; Mon, 7 Jul 2003 17:26:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZdUz-0003Dg-00 for gsmp@ietf.org; Mon, 07 Jul 2003 17:26:13 -0400 Received: from smtp.hsia.fairmont.com ([142.131.15.59] helo=torntsims03.hsia.fairmont.com) by ietf-mx with esmtp (Exim 4.12) id 19ZdUy-0003C1-00 for gsmp@ietf.org; Mon, 07 Jul 2003 17:26:12 -0400 Received: from apocalypse.org (unverified [142.131.77.128]) by torntsims03.hsia.fairmont.com (Vircom SMTPRS 2.0.244) with ESMTP id for ; Mon, 7 Jul 2003 17:21:25 -0400 Date: Thu, 26 Jun 2003 20:46:34 +0900 Resent-Date: Mon, 7 Jul 2003 17:18:35 -0400 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: avri To: gsmp@ietf.org Content-Transfer-Encoding: 7bit Resent-Message-Id: <2C9BAFC6-B0B7-11D7-A876-000393CC2112@apocalypse.org> Resent-From: avri Message-Id: <91B73004-B0C0-11D7-A876-000393CC2112@apocalypse.org> X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [GSMP] GSMP IETF57 Agenda Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit - Agenda Review - Triggered Add msg and Burst Switch requirements - Bulk Transactions - Capability Set Issues - Message changes to handle protection - How multi-layer capability maps into GSMP port/adaptation. _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Fri Jul 11 05:38:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22938 for ; Fri, 11 Jul 2003 05:38:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19auLr-0000Ot-Ok for gsmp-archive@odin.ietf.org; Fri, 11 Jul 2003 05:38:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B9c35p001536 for gsmp-archive@odin.ietf.org; Fri, 11 Jul 2003 05:38:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19auLr-0000Oh-J7 for gsmp-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 05:38:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22930 for ; Fri, 11 Jul 2003 05:37:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19auLo-00049y-00 for gsmp-web-archive@ietf.org; Fri, 11 Jul 2003 05:38:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19auLn-00049u-00 for gsmp-web-archive@ietf.org; Fri, 11 Jul 2003 05:37:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19auLo-0000OK-U9; Fri, 11 Jul 2003 05:38:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19auLN-0000Kp-IJ for gsmp@optimus.ietf.org; Fri, 11 Jul 2003 05:37:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22911 for ; Fri, 11 Jul 2003 05:37:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19auLK-00049g-00 for gsmp@ietf.org; Fri, 11 Jul 2003 05:37:30 -0400 Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19auLJ-00049V-00 for gsmp@ietf.org; Fri, 11 Jul 2003 05:37:29 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h6B9auh13353 for ; Fri, 11 Jul 2003 04:36:57 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Fri, 11 Jul 2003 11:36:55 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155020171E6@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Gsmp (E-mail)" Cc: "Allison Mankin (E-mail)" Date: Fri, 11 Jul 2003 11:36:45 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [GSMP] IESG review of: draft-ietf-gsmp-reqs-06.txt Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , The IESG yesterday discussed this documment. With the following RFC-Editor note the document can be approved. Before we send out that approval, we'd like to give GSMP WG a chance to review and let us know if this is OK. Pls check if I did correctly expand DCN RFC-Editor notes: 1) Third paragraph of section 2.5 - expand DCN. OLD: used in legacy DCN environments that use OSI CLNP. NEW: used in legacy Data Communication Network (DCN) environments that use OSI CLNP. 2) For section 2.5 - Add a final paragraph: The security risks of additional non-IP encapsulations MUST be described, since the mandatory to implement mechanism of IPsec is not available for these control channels, as in the RFC 3293 Ethernet and ATM cases. It is in scope to perform risk analysis and describe if mechanisms for link-level security mitigate the risk. 3) reword text in section 3.3 OLD: A retransmission policy should be used if no reply is received for a message with "AckAll" set. NEW: A retransmission policy with a well-designed exponential backoff should be used if no reply is received for a message with "AckAll" set. Bert and Allison _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Fri Jul 18 04:58:05 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23694 for ; Fri, 18 Jul 2003 04:58:05 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dR3a-0003Dp-9c for gsmp-archive@odin.ietf.org; Fri, 18 Jul 2003 04:57:38 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I8vcfK012379 for gsmp-archive@odin.ietf.org; Fri, 18 Jul 2003 04:57:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dR3a-0003Da-4T for gsmp-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 04:57:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23684 for ; Fri, 18 Jul 2003 04:57:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dR3X-0006g7-00 for gsmp-web-archive@ietf.org; Fri, 18 Jul 2003 04:57:35 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dR3R-0006g2-00 for gsmp-web-archive@ietf.org; Fri, 18 Jul 2003 04:57:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dR2z-00035B-Py; Fri, 18 Jul 2003 04:57:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dR2P-00033q-Oz for gsmp@optimus.ietf.org; Fri, 18 Jul 2003 04:56:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23644 for ; Fri, 18 Jul 2003 04:56:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dR2A-0006fM-00 for gsmp@ietf.org; Fri, 18 Jul 2003 04:56:10 -0400 Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19dR1z-0006f8-00 for gsmp@ietf.org; Fri, 18 Jul 2003 04:55:59 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h6I8t3518870 for ; Fri, 18 Jul 2003 03:55:03 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Fri, 18 Jul 2003 10:55:02 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502017BB9@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Gsmp (E-mail)" Cc: "Randy Bush (E-mail)" Date: Fri, 18 Jul 2003 10:55:00 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [GSMP] Action Requested: WG participation Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , GSMP WG participants/listeners, I am seriously worried about the very low level of participation, both in the face-to-face meeting(s) and on the WG mailing list. Since I took over this WG at the IETF in March this year, I have not seen enough participation of WG members/participants. For me (and I assume for everyone who looks at the status of this WG) that seems to indicate: - There is no wide interest in the current WG charter work-items. - So it seems as if a few people are working in private. - Work has not been progressing at all according to schedule. I hear from WG chair(s) that people are approaching them in private emails about this work. Well, that is all great, but that is NOT how we work in IETF. We participate on the mailing list, so that everyone can see each others input/comments/concerns etc. We also offer help to write documents and to review documents and to feedback to the list our findings during such review. Pls act and make this a real WG. Thanks, Bert _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Fri Jul 18 05:03:38 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23859 for ; Fri, 18 Jul 2003 05:03:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dR8x-0003gS-95 for gsmp-archive@odin.ietf.org; Fri, 18 Jul 2003 05:03:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I93Baf014154 for gsmp-archive@odin.ietf.org; Fri, 18 Jul 2003 05:03:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dR8x-0003gD-57 for gsmp-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 05:03:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23847 for ; Fri, 18 Jul 2003 05:03:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dR8t-0006jJ-00 for gsmp-web-archive@ietf.org; Fri, 18 Jul 2003 05:03:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dR8o-0006jG-00 for gsmp-web-archive@ietf.org; Fri, 18 Jul 2003 05:03:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dR8m-0003eU-S7; Fri, 18 Jul 2003 05:03:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dR8V-0003W6-9t for gsmp@optimus.ietf.org; Fri, 18 Jul 2003 05:02:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23841 for ; Fri, 18 Jul 2003 05:02:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dR8S-0006ig-00 for gsmp@ietf.org; Fri, 18 Jul 2003 05:02:40 -0400 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19dR8H-0006hv-00 for gsmp@ietf.org; Fri, 18 Jul 2003 05:02:29 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h6I91Xw04106 for ; Fri, 18 Jul 2003 04:01:34 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Fri, 18 Jul 2003 11:01:32 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502017BBD@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Gsmp (E-mail)" Cc: "Alex Zinin (E-mail)" , "Randy Bush (E-mail)" Date: Fri, 18 Jul 2003 11:00:58 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [GSMP] FW: Action Requested: WG participation Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , [ resend reason: I copied Randy (he is my OPS co-AD) while I meant to copy Alex (he is my SUB-IP co_AD) ] And.. I am speaking as AD in the posting below Thanks, Bert -----Original Message----- From: Wijnen, Bert (Bert) Sent: vrijdag 18 juli 2003 10:55 To: Gsmp (E-mail) Cc: Randy Bush (E-mail) Subject: Action Requested: WG participation GSMP WG participants/listeners, I am seriously worried about the very low level of participation, both in the face-to-face meeting(s) and on the WG mailing list. Since I took over this WG at the IETF in March this year, I have not seen enough participation of WG members/participants. For me (and I assume for everyone who looks at the status of this WG) that seems to indicate: - There is no wide interest in the current WG charter work-items. - So it seems as if a few people are working in private. - Work has not been progressing at all according to schedule. I hear from WG chair(s) that people are approaching them in private emails about this work. Well, that is all great, but that is NOT how we work in IETF. We participate on the mailing list, so that everyone can see each others input/comments/concerns etc. We also offer help to write documents and to review documents and to feedback to the list our findings during such review. Pls act and make this a real WG. Thanks, Bert _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Tue Jul 22 12:20:52 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18738 for ; Tue, 22 Jul 2003 12:20:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ezsH-0005lM-MU for gsmp-archive@odin.ietf.org; Tue, 22 Jul 2003 12:20:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MGKPxN022146 for gsmp-archive@odin.ietf.org; Tue, 22 Jul 2003 12:20:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ezsH-0005l7-JP for gsmp-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 12:20:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18728 for ; Tue, 22 Jul 2003 12:20:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ezsG-0005oS-00 for gsmp-web-archive@ietf.org; Tue, 22 Jul 2003 12:20:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ezsA-0005oK-00 for gsmp-web-archive@ietf.org; Tue, 22 Jul 2003 12:20:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ezrv-0005i2-7j; Tue, 22 Jul 2003 12:20:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ezqw-0005Xu-TI for gsmp@optimus.ietf.org; Tue, 22 Jul 2003 12:19:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18649 for ; Tue, 22 Jul 2003 12:18:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ezqv-0005n0-00 for gsmp@ietf.org; Tue, 22 Jul 2003 12:19:01 -0400 Received: from h33s128a211n47.user.nortelnetworks.com ([47.211.128.33] helo=znsgs01r.nortelnetworks.com) by ietf-mx with esmtp (Exim 4.12) id 19ezqk-0005mI-00 for gsmp@ietf.org; Tue, 22 Jul 2003 12:18:50 -0400 Received: from zctfc040.europe.nortel.com (zctfc040.europe.nortel.com [47.164.129.95]) by znsgs01r.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6MGHvn08068; Tue, 22 Jul 2003 17:17:57 +0100 (BST) Received: from zctfc002.europe.nortel.com ([47.164.129.43]) by zctfc040.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NB6N10P4; Tue, 22 Jul 2003 18:17:56 +0200 Received: from nortelnetworks.com (ksundell-1.europe.nortel.com [47.167.132.215]) by zctfc002.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id PDYAXNCQ; Tue, 22 Jul 2003 18:17:57 +0200 Message-ID: <3F1D63C7.906@nortelnetworks.com> Date: Tue, 22 Jul 2003 18:18:15 +0200 X-Sybari-Space: 00000000 00000000 00000000 From: Kenneth Sundell User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: "Gsmp (E-mail)" CC: "Wijnen, Bert (Bert)" , "Allison Mankin (E-mail)" Subject: Re: [GSMP] IESG review of: draft-ietf-gsmp-reqs-06.txt References: <7D5D48D2CAA3D84C813F5B154F43B155020171E6@nl0006exch001u.nl.lucent.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, At the GSMP WG in Vienna last week, I tried to get feedback on the proposed text that Bert sent out. While no one opposed, and at least one of the authors agreed to the text, I would like to hear the opinion from others, at least from the members of the design team. And please answer to the list... Cheers, Ken Wijnen, Bert (Bert) wrote: >The IESG yesterday discussed this documment. >With the following RFC-Editor note the document can be >approved. Before we send out that approval, we'd like >to give GSMP WG a chance to review and let us know if >this is OK. > >Pls check if I did correctly expand DCN > >RFC-Editor notes: > >1) Third paragraph of section 2.5 - expand DCN. > OLD: > used in legacy DCN environments that use OSI CLNP. > NEW: > used in legacy Data Communication Network (DCN) environments > that use OSI CLNP. > >2) For section 2.5 - Add a final paragraph: > > The security risks of additional non-IP encapsulations MUST be > described, since the mandatory to implement mechanism of IPsec > is not available for these control channels, as in the RFC 3293 > Ethernet and ATM cases. It is in scope to perform risk analysis > and describe if mechanisms for link-level security mitigate the > risk. > > >3) reword text in section 3.3 > > OLD: > A retransmission policy should be used if no reply is > received for a message with "AckAll" set. > NEW: > A retransmission policy with a well-designed exponential > backoff should be used if no reply is received for a > message with "AckAll" set. > >Bert and Allison > >_______________________________________________ >GSMP mailing list >GSMP@ietf.org >https://www1.ietf.org/mailman/listinfo/gsmp > -- Kenneth Sundell Sr. Protocols Architect CTO/ATI Strategic Protocols Nortel Networks (Sweden) ESN 521-3538, Ext IAC+46 8 5088-3538 _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Mon Jul 28 05:46:39 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25502 for ; Mon, 28 Jul 2003 05:46:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h4a5-0007i7-Ip for gsmp-archive@odin.ietf.org; Mon, 28 Jul 2003 05:46:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6S9kDvA029635 for gsmp-archive@odin.ietf.org; Mon, 28 Jul 2003 05:46:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h4a5-0007hu-EM for gsmp-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 05:46:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25462 for ; Mon, 28 Jul 2003 05:46:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19h4a1-0000Co-00 for gsmp-web-archive@ietf.org; Mon, 28 Jul 2003 05:46:09 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19h4a1-0000Ck-00 for gsmp-web-archive@ietf.org; Mon, 28 Jul 2003 05:46:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h4Zt-0007fq-Gk; Mon, 28 Jul 2003 05:46:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h4Zf-0007fV-EC for gsmp@optimus.ietf.org; Mon, 28 Jul 2003 05:45:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25457 for ; Mon, 28 Jul 2003 05:45:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19h4ZD-0000CQ-00 for gsmp@ietf.org; Mon, 28 Jul 2003 05:45:20 -0400 Received: from h35s128a211n47.user.nortelnetworks.com ([47.211.128.35] helo=znsgs01r.nortelnetworks.com) by ietf-mx with esmtp (Exim 4.12) id 19h4ZD-0000Bk-00 for gsmp@ietf.org; Mon, 28 Jul 2003 05:45:19 -0400 Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124]) by znsgs01r.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6S9iWT01748; Mon, 28 Jul 2003 10:44:32 +0100 (BST) Received: from nortelnetworks.com (47.163.50.99 [47.163.50.99]) by zwcwc012.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NP6TYDSJ; Mon, 28 Jul 2003 10:44:33 +0100 Message-ID: <3F24F07A.3040204@nortelnetworks.com> Date: Mon, 28 Jul 2003 11:44:26 +0200 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Georg Kullgren User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wijnen, Bert (Bert)" CC: "Gsmp (E-mail)" , "Allison Mankin (E-mail)" Subject: Re: [GSMP] IESG review of: draft-ietf-gsmp-reqs-06.txt References: <7D5D48D2CAA3D84C813F5B154F43B155020171E6@nl0006exch001u.nl.lucent.com> In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155020171E6@nl0006exch001u.nl.lucent.com> X-Enigmail-Version: 0.74.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Bert, Sorry for the late reply but I've been away from email for a while... I have no issues with the proposed changes. See comments below: Wijnen, Bert (Bert) wrote: > The IESG yesterday discussed this documment. > With the following RFC-Editor note the document can be > approved. Before we send out that approval, we'd like > to give GSMP WG a chance to review and let us know if > this is OK. > > Pls check if I did correctly expand DCN > > RFC-Editor notes: > > 1) Third paragraph of section 2.5 - expand DCN. > OLD: > used in legacy DCN environments that use OSI CLNP. > NEW: > used in legacy Data Communication Network (DCN) environments > that use OSI CLNP. I'm not the one to ask about this... Jonathan? > > 2) For section 2.5 - Add a final paragraph: > > The security risks of additional non-IP encapsulations MUST be > described, since the mandatory to implement mechanism of IPsec > is not available for these control channels, as in the RFC 3293 > Ethernet and ATM cases. It is in scope to perform risk analysis > and describe if mechanisms for link-level security mitigate the > risk. I agree with this one. Security should definately be considered. > > > 3) reword text in section 3.3 > > OLD: > A retransmission policy should be used if no reply is > received for a message with "AckAll" set. > NEW: > A retransmission policy with a well-designed exponential > backoff should be used if no reply is received for a > message with "AckAll" set. Sounds good to me! An exponential backoff would be the preferred way and it doesn't hurt to put that in the requirements. > > Bert and Allison > > _______________________________________________ > GSMP mailing list > GSMP@ietf.org > https://www1.ietf.org/mailman/listinfo/gsmp > /Georg -- ------------------------------------------------------------------------ Georg Kullgren Nortel Networks AB geku@nortelnetworks.com Systems Architect S:t Eriksgatan 115 A Tel: +46-8-50 88 36 18 Routing Architecture Lab SE-113 85 Stockholm Mobile: +46-703-14 36 18 ATI Strategic Protocols Sweden Fax: +46-8-50 88 35 01 _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Mon Jul 28 11:15:07 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05586 for ; Mon, 28 Jul 2003 11:15:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h9hv-0001qt-BF for gsmp-archive@odin.ietf.org; Mon, 28 Jul 2003 11:14:40 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6SFEdSP007115 for gsmp-archive@odin.ietf.org; Mon, 28 Jul 2003 11:14:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h9hv-0001qg-8F for gsmp-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 11:14:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05536 for ; Mon, 28 Jul 2003 11:14:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19h9hu-0003V0-00 for gsmp-web-archive@ietf.org; Mon, 28 Jul 2003 11:14:38 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19h9ht-0003Ux-00 for gsmp-web-archive@ietf.org; Mon, 28 Jul 2003 11:14:37 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h9hJ-0001nv-9g; Mon, 28 Jul 2003 11:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h9gi-0001nH-Bh for gsmp@optimus.ietf.org; Mon, 28 Jul 2003 11:13:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05343 for ; Mon, 28 Jul 2003 11:13:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19h9gh-0003QG-00 for gsmp@ietf.org; Mon, 28 Jul 2003 11:13:23 -0400 Received: from mx4.tellabs.com ([204.154.129.57]) by ietf-mx with esmtp (Exim 4.12) id 19h9gg-0003Ok-00 for gsmp@ietf.org; Mon, 28 Jul 2003 11:13:22 -0400 Received: from mailw02.hq.tellabs.com (mailw02.hq.tellabs.com [172.23.207.12]) by mx4.tellabs.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AES04710; Mon, 28 Jul 2003 10:12:19 -0500 (CDT) Received: from tellabs.com (dhcp-172-23-111-53.hq.tellabs.com [172.23.111.53]) by mailw02.hq.tellabs.com with ESMTP (8.11.1/8.7.1) id h6SFCKS16372; Mon, 28 Jul 2003 10:12:20 -0500 (CDT) Message-ID: <3F253D4D.32AE55A7@tellabs.com> Date: Mon, 28 Jul 2003 10:12:13 -0500 From: Jonathan Sadler X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Georg Kullgren CC: "Wijnen, Bert (Bert)" , "Gsmp (E-mail)" , "Allison Mankin (E-mail)" Subject: Re: [GSMP] IESG review of: draft-ietf-gsmp-reqs-06.txt References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mirapoint-Sig: mx4.tellabs.com Content-Transfer-Encoding: 7bit Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Georg, et al - Sorry, it was recorded in the minutes at the GSMP meeting in Vienna, but not echoed to the list: - DCN has been correctly expanded - I agree with all of the suggested changes. Jonathan Sadler Georg Kullgren wrote: > Hi Bert, > > Sorry for the late reply but I've been away from email for a while... > I have no issues with the proposed changes. > See comments below: > > Wijnen, Bert (Bert) wrote: > > The IESG yesterday discussed this documment. > > With the following RFC-Editor note the document can be > > approved. Before we send out that approval, we'd like > > to give GSMP WG a chance to review and let us know if > > this is OK. > > > > Pls check if I did correctly expand DCN > > > > RFC-Editor notes: > > > > 1) Third paragraph of section 2.5 - expand DCN. > > OLD: > > used in legacy DCN environments that use OSI CLNP. > > NEW: > > used in legacy Data Communication Network (DCN) environments > > that use OSI CLNP. > > I'm not the one to ask about this... > Jonathan? > > > > > 2) For section 2.5 - Add a final paragraph: > > > > The security risks of additional non-IP encapsulations MUST be > > described, since the mandatory to implement mechanism of IPsec > > is not available for these control channels, as in the RFC 3293 > > Ethernet and ATM cases. It is in scope to perform risk analysis > > and describe if mechanisms for link-level security mitigate the > > risk. > > I agree with this one. > Security should definately be considered. > > > > > > > 3) reword text in section 3.3 > > > > OLD: > > A retransmission policy should be used if no reply is > > received for a message with "AckAll" set. > > NEW: > > A retransmission policy with a well-designed exponential > > backoff should be used if no reply is received for a > > message with "AckAll" set. > > Sounds good to me! > An exponential backoff would be the preferred way and it doesn't hurt > to put that in the requirements. > > > > > Bert and Allison > > > > _______________________________________________ > > GSMP mailing list > > GSMP@ietf.org > > https://www1.ietf.org/mailman/listinfo/gsmp > > > > /Georg > -- > ------------------------------------------------------------------------ > Georg Kullgren Nortel Networks AB geku@nortelnetworks.com > Systems Architect S:t Eriksgatan 115 A Tel: +46-8-50 88 36 18 > Routing Architecture Lab SE-113 85 Stockholm Mobile: +46-703-14 36 18 > ATI Strategic Protocols Sweden Fax: +46-8-50 88 35 01 > > _______________________________________________ > GSMP mailing list > GSMP@ietf.org > https://www1.ietf.org/mailman/listinfo/gsmp ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================ _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp From exim@www1.ietf.org Mon Jul 28 15:22:42 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17820 for ; Mon, 28 Jul 2003 15:22:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hDZX-0003w8-7w for gsmp-archive@odin.ietf.org; Mon, 28 Jul 2003 15:22:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6SJMFuV015132 for gsmp-archive@odin.ietf.org; Mon, 28 Jul 2003 15:22:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hDZW-0003vz-LZ for gsmp-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 15:22:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17808 for ; Mon, 28 Jul 2003 15:22:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hDZV-0006vA-00 for gsmp-web-archive@ietf.org; Mon, 28 Jul 2003 15:22:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hDZU-0006v7-00 for gsmp-web-archive@ietf.org; Mon, 28 Jul 2003 15:22:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hDZJ-0003tm-A3; Mon, 28 Jul 2003 15:22:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hDYP-0003tR-1d for gsmp@optimus.ietf.org; Mon, 28 Jul 2003 15:21:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17782 for ; Mon, 28 Jul 2003 15:20:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hDYI-0006ue-00 for gsmp@ietf.org; Mon, 28 Jul 2003 15:20:58 -0400 Received: from fmr06.intel.com ([134.134.136.7] helo=caduceus.jf.intel.com) by ietf-mx with esmtp (Exim 4.12) id 19hDYH-0006uR-00 for gsmp@ietf.org; Mon, 28 Jul 2003 15:20:57 -0400 Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7]) by caduceus.jf.intel.com (8.11.6p2/8.11.6/d: outer.mc,v 1.66 2003/05/22 21:17:36 rfjohns1 Exp $) with ESMTP id h6SJEWO29038 for ; Mon, 28 Jul 2003 19:14:32 GMT Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by talaria.jf.intel.com (8.11.6p2/8.11.6/d: inner.mc,v 1.35 2003/05/22 21:18:01 rfjohns1 Exp $) with SMTP id h6SIiTq04255 for ; Mon, 28 Jul 2003 18:44:29 GMT Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2003072812321917438 ; Mon, 28 Jul 2003 12:32:19 -0700 Received: from orsmsx407.amr.corp.intel.com ([192.168.65.50]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 28 Jul 2003 12:20:24 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Subject: RE: [GSMP] IESG review of: draft-ietf-gsmp-reqs-06.txt Date: Mon, 28 Jul 2003 12:20:23 -0700 Message-ID: <42050DF556283A4D977B111EB7063208DAEB7E@orsmsx407.jf.intel.com> Thread-Topic: [GSMP] IESG review of: draft-ietf-gsmp-reqs-06.txt Thread-Index: AcNHkENmEMSfDLSHQymN3DHChOLLzgNrLlcg From: "Khosravi, Hormuzd M" To: "Wijnen, Bert (Bert)" , "Gsmp (E-mail)" Cc: "Allison Mankin (E-mail)" X-OriginalArrivalTime: 28 Jul 2003 19:20:24.0003 (UTC) FILETIME=[4B3B0130:01C3553D] Content-Transfer-Encoding: quoted-printable Sender: gsmp-admin@ietf.org Errors-To: gsmp-admin@ietf.org X-BeenThere: gsmp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: General Switch Management Protocol List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sorry for the late reply.=20 I agree with the changes below, Regards Hormuzd -----Original Message----- From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20 Sent: Friday, July 11, 2003 2:37 AM To: Gsmp (E-mail) Cc: Allison Mankin (E-mail) Subject: [GSMP] IESG review of: draft-ietf-gsmp-reqs-06.txt The IESG yesterday discussed this documment. With the following RFC-Editor note the document can be approved. Before we send out that approval, we'd like to give GSMP WG a chance to review and let us know if this is OK.=20 Pls check if I did correctly expand DCN RFC-Editor notes: 1) Third paragraph of section 2.5 - expand DCN. OLD: used in legacy DCN environments that use OSI CLNP. NEW: used in legacy Data Communication Network (DCN) environments that use OSI CLNP. 2) For section 2.5 - Add a final paragraph: The security risks of additional non-IP encapsulations MUST be described, since the mandatory to implement mechanism of IPsec is not available for these control channels, as in the RFC 3293 Ethernet and ATM cases. It is in scope to perform risk analysis and describe if mechanisms for link-level security mitigate the risk. 3) reword text in section 3.3 OLD: A retransmission policy should be used if no reply is=20 received for a message with "AckAll" set. NEW: A retransmission policy with a well-designed exponential backoff should be used if no reply is received for a message with "AckAll" set. Bert and Allison _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp