From owner-gsmp@psyton.com Mon Jan 3 18:30:46 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09018 for ; Mon, 3 Jan 2000 18:30:45 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id SAA17671 for gsmp-list; Mon, 3 Jan 2000 18:07:39 -0500 Received: from PMESMTP01.wcom.com (pmesmtp01.wcom.com [199.249.20.1]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id SAA17668 for ; Mon, 3 Jan 2000 18:07:38 -0500 Received: from CONVERSION-DAEMON by firewall.mcit.com (PMDF V5.2-32 #41714) id <0FNS00F0187OLF@firewall.mcit.com> for gsmp@psyton.com; Mon, 3 Jan 2000 23:07:00 +0000 (GMT) Received: from ndcrelay2.mcit.com ([166.37.172.6]) by firewall.mcit.com (PMDF V5.2-32 #41714) with ESMTP id <0FNS00CC587O8S@firewall.mcit.com> for gsmp@psyton.com; Mon, 03 Jan 2000 23:07:00 +0000 (GMT) Received: from omzmta03.mcit.com (omzmta03.mcit.com [166.37.194.121]) by ndcrelay2.mcit.com (8.8.7/) with ESMTP id XAA20559 for ; Mon, 03 Jan 2000 23:01:47 +0000 (GMT) Received: from pc25811 ([165.122.129.138]) by omzmta03.mcit.com (InterMail v03.02.05 118 121 101) with SMTP id <20000103230648.WCMU15369@pc25811> for ; Mon, 03 Jan 2000 23:06:48 +0000 Date: Mon, 03 Jan 2000 17:06:36 -0600 From: Clint Bishard Subject: RE: IP related forwarding info? In-reply-to: To: gsmp@psyton.com Message-id: <001201bf563f$3007a900$8a817aa5@pc25811.wcom.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: 7bit Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit Avri, MSF99-217 is not needed. That is why I included the drawing. The point is that GSMP could be used to communicate to a switch port to map a list of IP addresses to a label internal to the switch on that same switch port. C-plane, Did you want to add anything as to the possibility of an Internet Draft for this idea? Thanks, Clint -----Original Message----- From: owner-gsmp@psyton.com [mailto:owner-gsmp@psyton.com]On Behalf Of avri.doria@nokia.com Sent: Thursday, December 30, 1999 2:31 PM To: gsmp@psyton.com Subject: RE: IP related forwarding info? Hi Clint, I think this an interesting idea. I look forward to the I-D which actually specifies the GSMP changes that would be required to support this. Unfortunately the MSF99-217 draft is only available to MSF members, which makes it difficult to discuss in detail on this list. Perhaps the MSF can make this document available to the GSMP WG. One thing though, I have strong doubts that we can get this into the GSMPv3 spec at this point in time. Regards, a. ----------------------------------- avri doria +1 781 308 7680 (this is a new number, please make a note.) > -----Original Message----- > From: EXT Clint Bishard [mailto:clint.bishard@wcom.com] > Sent: 30 December, 1999 2:37 PM > To: gsmp@psyton.com > Cc: Bishard, Clint > Subject: RE: IP related forwarding info? > > > Avri, > > At the last MSF meeting in San Diego, the SCI working group > discussed having > the GSMP protocol perform the function of mapping a list of > IP addresses to > a label on the switch. Therefore, the next hop forwarding > function could be > performed by an external processor, however, the > communication of mapping IP > address from the logical port function to a label on a switch could be > performed over GSMP. Therefore, GSMP could realize the sp as > well as the > vsc interfaces of the MSF architecture. This was shown in > MSF contribution > 217. I try to show this below: > > > Virtual Switch Control Function > | | > |sp | > | |vsc > Logical Port Function | > ____________|___ | > | | Virtual Switch Function > | IP1-label 1 | | > | IP2-label 1 |-------Switching Function-------Other Logical > Port Function > | IP3-label 2 | > | IP4-label 5 | > |______________| > > > The next hop routing would be performed in the control plane, > and the GSMP > protocol would be utilized to realize the sp and vsc interfaces and > communicate this to the switch/adaptation planes. > I believe C-place mentioned that they may compile a > contribution to add this > functionality to GSMP to be able to perform this IP to label mapping. > > Clint > > > > > -----Original Message----- > From: owner-gsmp@psyton.com [mailto:owner-gsmp@psyton.com]On Behalf Of > avri.doria@nokia.com > Sent: Thursday, December 30, 1999 9:22 AM > To: gsmp@psyton.com > Subject: RE: IP relatid forwarding info? > > > Hi, > > The whole reason behind doing GSMP in the IETF is to support MPLS. > So, no, I think that if MPLS becomes a dominant method, then we > will see a need for GSMP, in that GSMP makes it possible for an > intelligent controller to do the MPLS signaling and handle routing > protocols etc., while a relatively specialized switch concentrates > on forwarding data. GSMP is the protocol which enables the MPLS > controller to control the data switch. It is not another signaling > protocol. > > a. > ----------------------------------- > avri doria > +1 781 308 7680 > (this is a new number, please make a note.) > > > > > -----Original Message----- > > From: wangs@future.futsoft.com > [mailto:wangs@future.futsoft.com] > > Sent: 30 December, 1999 7:39 AM > > To: 'gsmp@psyton.com' > > Subject: RE: IP relatid forwarding info? > > > > Dear all: > > I think Mr. Patrick has asked a very > good question! > Very > > nice. I think at persent gsmp is not perfect enough to > > include IP related forwarding information > such as next hop > > > information for IP address prefixes or filter rules. I > think > > the main reason why gsmp protocol adopts > extension label > is > > that gsmp wants to incorporate multiple label stack > supported > > by MPLS in near future. Otherwise, if MPLS becomes the > most > > popular signaling protocol, gsmp will have a bleak > prospect. > > Am I right? Give your opinion? > > > Thanks > > & Regards! > > > > > Simon > > > > > > -----Original Message----- > > From: Patrick Droz [SMTP:dro@zurich.ibm.com] > > Sent: Thursday, December 30, 1999 3:36 PM > > To: gsmp@psyton.com > > Subject: IP relatid forwarding info? > > > > The GSMP specification includes ATM, FR, and > MPLS related > > forwarding information. Was it ever > considered to include > > also IP related forwarding information such > as next hop > > information for IP address prefixes or filter rules? > > > > Thanks, > > Patrick > > > > -- > > Patrick Droz | dro@zurich.ibm.com > > IBM Zurich Research Laboratory | > http://www.zurich.ibm.com/~dro > > Saumerstrasse 4 | Tel. > +41-1-724-85-25 > > > CH-8803 Rueschlikon/Switzerland | Fax. > +41-1-724-89-55 > From owner-gsmp@psyton.com Wed Jan 5 17:29:24 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17107 for ; Wed, 5 Jan 2000 17:29:22 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id QAA02868 for gsmp-list; Wed, 5 Jan 2000 16:53:38 -0500 Received: from cplane.com (IDENT:qmailr@[63.193.105.226]) by nighthawk.psyton.com (8.9.0/8.9.0) with SMTP id QAA02865 for ; Wed, 5 Jan 2000 16:53:36 -0500 Received: (qmail 9419 invoked from network); 5 Jan 2000 21:41:15 -0000 Received: from unknown (HELO texas.cplane.com) (unknown) by unknown with SMTP; 5 Jan 2000 21:41:15 -0000 Received: (qmail 1843 invoked from network); 5 Jan 2000 21:48:02 -0000 Received: from unknown (HELO cplane.com) (unknown) by unknown with SMTP; 5 Jan 2000 21:48:02 -0000 Message-ID: <3873BB30.244E85BB@cplane.com> Date: Wed, 05 Jan 2000 13:44:17 -0800 From: Jaroslaw Sydir Organization: CPlane Inc. X-Mailer: Mozilla 4.06 [en] (X11; I; Linux 2.0.34 i586) MIME-Version: 1.0 To: gsmp@psyton.com Subject: Re: IP related forwarding info? References: <001201bf563f$3007a900$8a817aa5@pc25811.wcom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit Clint, We are planning on writing such a draft, however, due to other commitments this will probably not happen until after the end of January. Jerry Sydir Clint Bishard wrote: > Avri, > > MSF99-217 is not needed. That is why I included the drawing. The point is > that GSMP could be used to communicate to a switch port to map a list of IP > addresses to a label internal to the switch on that same switch port. > > C-plane, > > Did you want to add anything as to the possibility of an Internet Draft for > this idea? > > Thanks, > Clint > > -----Original Message----- > From: owner-gsmp@psyton.com [mailto:owner-gsmp@psyton.com]On Behalf Of > avri.doria@nokia.com > Sent: Thursday, December 30, 1999 2:31 PM > To: gsmp@psyton.com > Subject: RE: IP related forwarding info? > > Hi Clint, > > I think this an interesting idea. > I look forward to the I-D which actually specifies the > GSMP changes that would be required to support this. > Unfortunately the MSF99-217 draft is only available > to MSF members, which makes it difficult to discuss > in detail on this list. Perhaps the MSF can make this > document available to the GSMP WG. > > One thing though, I have strong doubts that we can get > this into the GSMPv3 spec at this point in time. > > Regards, > > a. > ----------------------------------- > avri doria > +1 781 308 7680 > (this is a new number, please make a note.) > > > -----Original Message----- > > From: EXT Clint Bishard [mailto:clint.bishard@wcom.com] > > Sent: 30 December, 1999 2:37 PM > > To: gsmp@psyton.com > > Cc: Bishard, Clint > > Subject: RE: IP related forwarding info? > > > > > > Avri, > > > > At the last MSF meeting in San Diego, the SCI working group > > discussed having > > the GSMP protocol perform the function of mapping a list of > > IP addresses to > > a label on the switch. Therefore, the next hop forwarding > > function could be > > performed by an external processor, however, the > > communication of mapping IP > > address from the logical port function to a label on a switch could be > > performed over GSMP. Therefore, GSMP could realize the sp as > > well as the > > vsc interfaces of the MSF architecture. This was shown in > > MSF contribution > > 217. I try to show this below: > > > > > > Virtual Switch Control Function > > | | > > |sp | > > | |vsc > > Logical Port Function | > > ____________|___ | > > | | Virtual Switch Function > > | IP1-label 1 | | > > | IP2-label 1 |-------Switching Function-------Other Logical > > Port Function > > | IP3-label 2 | > > | IP4-label 5 | > > |______________| > > > > > > The next hop routing would be performed in the control plane, > > and the GSMP > > protocol would be utilized to realize the sp and vsc interfaces and > > communicate this to the switch/adaptation planes. > > I believe C-place mentioned that they may compile a > > contribution to add this > > functionality to GSMP to be able to perform this IP to label mapping. > > > > Clint > > > > > > > > > > -----Original Message----- > > From: owner-gsmp@psyton.com [mailto:owner-gsmp@psyton.com]On Behalf Of > > avri.doria@nokia.com > > Sent: Thursday, December 30, 1999 9:22 AM > > To: gsmp@psyton.com > > Subject: RE: IP relatid forwarding info? > > > > > > Hi, > > > > The whole reason behind doing GSMP in the IETF is to support MPLS. > > So, no, I think that if MPLS becomes a dominant method, then we > > will see a need for GSMP, in that GSMP makes it possible for an > > intelligent controller to do the MPLS signaling and handle routing > > protocols etc., while a relatively specialized switch concentrates > > on forwarding data. GSMP is the protocol which enables the MPLS > > controller to control the data switch. It is not another signaling > > protocol. > > > > a. > > ----------------------------------- > > avri doria > > +1 781 308 7680 > > (this is a new number, please make a note.) > > > > > > > > > -----Original Message----- > > > From: wangs@future.futsoft.com > > [mailto:wangs@future.futsoft.com] > > > Sent: 30 December, 1999 7:39 AM > > > To: 'gsmp@psyton.com' > > > Subject: RE: IP relatid forwarding info? > > > > > > Dear all: > > > I think Mr. Patrick has asked a very > > good question! > > Very > > > nice. I think at persent gsmp is not perfect enough to > > > include IP related forwarding information > > such as next hop > > > > > information for IP address prefixes or filter rules. I > > think > > > the main reason why gsmp protocol adopts > > extension label > > is > > > that gsmp wants to incorporate multiple label stack > > supported > > > by MPLS in near future. Otherwise, if MPLS becomes the > > most > > > popular signaling protocol, gsmp will have a bleak > > prospect. > > > Am I right? Give your opinion? > > > > > Thanks > > > & Regards! > > > > > > > > Simon > > > > > > > > > -----Original Message----- > > > From: Patrick Droz [SMTP:dro@zurich.ibm.com] > > > Sent: Thursday, December 30, 1999 3:36 PM > > > To: gsmp@psyton.com > > > Subject: IP relatid forwarding info? > > > > > > The GSMP specification includes ATM, FR, and > > MPLS related > > > forwarding information. Was it ever > > considered to include > > > also IP related forwarding information such > > as next hop > > > information for IP address prefixes or filter rules? > > > > > > Thanks, > > > Patrick > > > > > > -- > > > Patrick Droz | dro@zurich.ibm.com > > > IBM Zurich Research Laboratory | > > http://www.zurich.ibm.com/~dro > > > Saumerstrasse 4 | Tel. > > +41-1-724-85-25 > > > > > CH-8803 Rueschlikon/Switzerland | Fax. > > +41-1-724-89-55 > > -- Jerry Sydir phone: +1(650) 938-8066 x102 CPlane Inc. fax : +1(650) 938-8068 5150 El Camino Real Suite B-31 Los Altos, CA 94022 From owner-gsmp@psyton.com Thu Jan 6 12:37:02 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17667 for ; Thu, 6 Jan 2000 12:36:59 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id MAA07868 for gsmp-list; Thu, 6 Jan 2000 12:20:34 -0500 Received: from beta.mcit.com (omzrelay02.mcit.com [199.249.19.244]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id MAA07865 for ; Thu, 6 Jan 2000 12:20:33 -0500 Received: from CONVERSION-DAEMON by firewall.mcit.com (PMDF V5.2-32 #38417) id <0FNX00401C4KDW@firewall.mcit.com> for gsmp@revnetworks.com; Thu, 6 Jan 2000 17:19:32 +0000 (GMT) Received: from ndcrelay.mcit.com ([166.37.172.49]) by firewall.mcit.com (PMDF V5.2-32 #38417) with ESMTP id <0FNX0099OC4KY3@firewall.mcit.com> for gsmp@revnetworks.com; Thu, 06 Jan 2000 17:19:32 +0000 (GMT) Received: from omzmta03.mcit.com (omzmta03.mcit.com [166.37.194.121]) by ndcrelay.mcit.com (8.8.7/) with ESMTP id RAA10871 for ; Thu, 06 Jan 2000 17:17:42 +0000 (GMT) Received: from pc25811 ([165.122.129.138]) by omzmta03.mcit.com (InterMail v03.02.05 118 121 101) with SMTP id <20000106171923.RFJZ15369@pc25811>; Thu, 06 Jan 2000 17:19:23 +0000 Date: Thu, 06 Jan 2000 11:19:14 -0600 From: Clint Bishard Subject: Question on Connection Management Messages To: gsmp@psyton.com Cc: clint.bishard@wcom.com Message-id: <000301bf586a$289515e0$8a817aa5@pc25811.wcom.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: 7bit Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit GSMP connection management messages only seem to allow a single set of QoS parameters for a given connection. Since each connection within a switch actually involves two different ports, shouldn't the connection management messages have a QMS and service selector field for both the input port and the output port instead of just one for the connection? This seems necessary given that the services on the ports may be different, such as building a connection from a FR port to an ATM port, or a connection from an ATM port to an MPLS port. Comments anyone, or am I not understanding something here? Clint From owner-gsmp@psyton.com Fri Jan 7 10:19:29 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19884 for ; Fri, 7 Jan 2000 10:19:18 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id JAA11143 for gsmp-list; Fri, 7 Jan 2000 09:48:28 -0500 Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id JAA11140 for ; Fri, 7 Jan 2000 09:48:26 -0500 From: tom.worster@nokia.com Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61]) by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id QAA06616 for ; Fri, 7 Jan 2000 16:48:23 +0200 (EET) Received: from daebh02nok.americas.nokia.com (daebh02nok.americas.nokia.com [172.18.242.183]) by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id QAA11534 for ; Fri, 7 Jan 2000 16:48:08 +0200 (EET) Received: by daebh02nok with Internet Mail Service (5.5.2448.0) id ; Fri, 7 Jan 2000 08:48:07 -0600 Message-ID: To: gsmp@psyton.com Subject: RE: Question on Connection Management Messages Date: Fri, 7 Jan 2000 08:47:55 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com From: EXT Clint Bishard [mailto:clint.bishard@wcom.com] > > GSMP connection management messages only seem to allow a > single set of QoS > parameters for a given connection. Since each connection > within a switch > actually involves two different ports, shouldn't the > connection management > messages have a QMS and service selector field for both the > input port and > the output port instead of just one for the connection? This seems > necessary given that the services on the ports may be > different, such as > building a connection from a FR port to an ATM port, or a > connection from an > ATM port to an MPLS port. the traffic/qos parameters assigned to a connection apply at the output. qos management for the input is performed by the upstream switch. c u tom From owner-gsmp@psyton.com Fri Jan 7 12:40:00 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23758 for ; Fri, 7 Jan 2000 12:39:58 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id MAA11586 for gsmp-list; Fri, 7 Jan 2000 12:26:51 -0500 Received: from beta.mcit.com (omzrelay02.mcit.com [199.249.19.244]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id MAA11583 for ; Fri, 7 Jan 2000 12:26:49 -0500 Received: from CONVERSION-DAEMON by firewall.mcit.com (PMDF V5.2-32 #38417) id <0FNZ00A017348Q@firewall.mcit.com> for gsmp@psyton.com; Fri, 7 Jan 2000 17:25:52 +0000 (GMT) Received: from ndcrelay.mcit.com ([166.37.172.49]) by firewall.mcit.com (PMDF V5.2-32 #38417) with ESMTP id <0FNZ004EC733O2@firewall.mcit.com> for gsmp@psyton.com; Fri, 07 Jan 2000 17:25:52 +0000 (GMT) Received: from omzmta04.mcit.com (omzmta04.mcit.com [166.37.194.122]) by ndcrelay.mcit.com (8.8.7/) with ESMTP id RAA29405 for ; Fri, 07 Jan 2000 17:24:08 +0000 (GMT) Received: from pc25811 ([165.122.129.138]) by omzmta04.mcit.com (InterMail v03.02.05 118 121 101) with SMTP id <20000107172550.NQQY31729@pc25811> for ; Fri, 07 Jan 2000 17:25:50 +0000 Date: Fri, 07 Jan 2000 11:25:46 -0600 From: Clint Bishard Subject: RE: Question on Connection Management Messages In-reply-to: To: gsmp@psyton.com Message-id: <000501bf5934$3ca549e0$8a817aa5@pc25811.wcom.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: 7bit Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit Tom, Thanks for the response. It still seems like the flexibility to define per port QoS parameters would me necessary. I would consider policing a function of QoS, and this would occur at the ingress port, or ingress traffic shaping may be another function that would need to be controlled at the ingress port. Therefore, I can see were we would need to specify the service parameters for each port individually given the specific service. For example, say a switch has two UNI ports to a customer. One of the UNI ports is a FR port and the other UNI port is an ATM port. We want to build a connection between these ports and offer a FR to ATM interworking service. We want policing on both ingress ports. A CIR and EIR is specified for the FR port and a PCR, SCR, MBS is specified for the ATM port. Instead of being constrained to just providing ATM parameters or FR parameters and the switch doing a conversion to the others, we want to explicitly state these parameters to the switch for each port. How could we do this with the current GSMP framework? Could this be done by building the connection with two GSMP connections and specifying FR in one and ATM in another? Thanks, Clint -----Original Message----- From: owner-gsmp@psyton.com [mailto:owner-gsmp@psyton.com]On Behalf Of tom.worster@nokia.com Sent: Friday, January 07, 2000 8:48 AM To: gsmp@psyton.com Subject: RE: Question on Connection Management Messages From: EXT Clint Bishard [mailto:clint.bishard@wcom.com] > > GSMP connection management messages only seem to allow a > single set of QoS > parameters for a given connection. Since each connection > within a switch > actually involves two different ports, shouldn't the > connection management > messages have a QMS and service selector field for both the > input port and > the output port instead of just one for the connection? This seems > necessary given that the services on the ports may be > different, such as > building a connection from a FR port to an ATM port, or a > connection from an > ATM port to an MPLS port. the traffic/qos parameters assigned to a connection apply at the output. qos management for the input is performed by the upstream switch. c u tom From owner-gsmp@psyton.com Fri Jan 7 15:28:43 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26645 for ; Fri, 7 Jan 2000 15:28:42 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id PAA12162 for gsmp-list; Fri, 7 Jan 2000 15:13:04 -0500 Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id PAA12159 for ; Fri, 7 Jan 2000 15:13:01 -0500 From: avri.doria@nokia.com Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61]) by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id WAA05508; Fri, 7 Jan 2000 22:12:50 +0200 (EET) Received: from daebh02nok.americas.nokia.com (daebh02nok.americas.nokia.com [172.18.242.183]) by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id WAA07101; Fri, 7 Jan 2000 22:12:48 +0200 (EET) Received: by daebh02nok with Internet Mail Service (5.5.2448.0) id ; Fri, 7 Jan 2000 14:12:45 -0600 Message-ID: To: gsmp@psyton.com Cc: simon@cplane.com, Dave.McDysan@wcom.com Subject: Interim Editing session Date: Fri, 7 Jan 2000 14:12:34 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Hi, This is to announce that there will be an interim GSMPv3 specification editing session held Wednesday 2 Feb 00. This session will be held jointly with the MSF switch control working group. The meeting will be held during the MSF Technical Committee meeting being held in New Orleans. While the MSF meetings are closed to non MSF members, the MSF has decided to invite GSMP WG members who want to participate in this session and who don't happen to be MSF members to attend the relevant Switch Control WG meeting on Wed 2 Feb 00 free of charge. Anyone interested in attending should notify me as soon as possible of their interest. Please note: In keeping with IETF practice any changes made to the GSMPv3 specifications at the interim/joint meeting will be subject to the subsequent approval of the IETF GSMP WG. Regards a. ----------------------------------- avri doria Office: +1 781 993 4656 Mobile: +1 781 308 7680 From owner-gsmp@psyton.com Fri Jan 7 18:05:31 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28868 for ; Fri, 7 Jan 2000 18:05:31 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id RAA12606 for gsmp-list; Fri, 7 Jan 2000 17:45:17 -0500 Received: from alpha.mcit.com (omzrelay01.mcit.com [199.249.19.243]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id RAA12603 for ; Fri, 7 Jan 2000 17:45:16 -0500 Received: from CONVERSION-DAEMON by firewall.mcit.com (PMDF V5.2-32 #38416) id <0FNZ00J01LUAO0@firewall.mcit.com> for gsmp@psyton.com; Fri, 7 Jan 2000 22:44:34 +0000 (GMT) Received: from ndcrelay.mcit.com ([166.37.172.49]) by firewall.mcit.com (PMDF V5.2-32 #38416) with ESMTP id <0FNZ00JCCLUAFZ@firewall.mcit.com>; Fri, 07 Jan 2000 22:44:34 +0000 (GMT) Received: from omta3.mcit.com (omta3.mcit.com [166.37.204.5]) by ndcrelay.mcit.com (8.8.7/) with ESMTP id WAA28956; Fri, 07 Jan 2000 22:42:43 +0000 (GMT) Received: from rip01223B.mcit.com ([166.35.249.247]) by omta3.mcit.com (InterMail v03.02.05 118 121 101) with SMTP id <20000107224435.GQUA16210@rip01223B.mcit.com>; Fri, 07 Jan 2000 22:44:35 +0000 Date: Fri, 07 Jan 2000 16:43:03 -0600 From: Dave McDysan Subject: RE: Interim Editing session In-reply-to: To: avri.doria@nokia.com, gsmp@psyton.com Cc: simon@cplane.com Message-id: <000101bf5960$8e8b75a0$f7f923a6@rip01223B.mcit.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: 7bit Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit Note that representatives who are MSF member companies must register through the normal channels on www.msforum.org. Per the MSF operating procedures, as the technical committee chair, I am inviting GSMP subject matter experts to this meeting to advance this important work within the industry. Thank you in advance for your support, Dave McDysan MSF Technical Committee Chair -----Original Message----- From: avri.doria@nokia.com [mailto:avri.doria@nokia.com] Sent: Friday, January 07, 2000 2:13 PM To: gsmp@psyton.com Cc: simon@cplane.com; Dave.McDysan@wcom.com Subject: Interim Editing session Hi, This is to announce that there will be an interim GSMPv3 specification editing session held Wednesday 2 Feb 00. This session will be held jointly with the MSF switch control working group. The meeting will be held during the MSF Technical Committee meeting being held in New Orleans. While the MSF meetings are closed to non MSF members, the MSF has decided to invite GSMP WG members who want to participate in this session and who don't happen to be MSF members to attend the relevant Switch Control WG meeting on Wed 2 Feb 00 free of charge. Anyone interested in attending should notify me as soon as possible of their interest. Please note: In keeping with IETF practice any changes made to the GSMPv3 specifications at the interim/joint meeting will be subject to the subsequent approval of the IETF GSMP WG. Regards a. ----------------------------------- avri doria Office: +1 781 993 4656 Mobile: +1 781 308 7680 From owner-gsmp@psyton.com Sun Jan 9 17:53:18 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10745 for ; Sun, 9 Jan 2000 17:53:12 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id RAA18448 for gsmp-list; Sun, 9 Jan 2000 17:26:30 -0500 Received: from sourcenet.org (host-209-214-98-110.sav.bellsouth.net [209.214.98.110]) by nighthawk.psyton.com (8.9.0/8.9.0) with SMTP id RAA18441; Sun, 9 Jan 2000 17:26:27 -0500 From: Subject: Good Luck in the New Millenium Date: Sun, 9 Jan 2000 17:32:11 Message-Id: <573.706997.486296@sourcenet.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com To be removed from this mailing list immediately press reply and enter REMOVE on the subject line. Would you like to be able to buy Computers and Software at wholesale? At below what the stores Pay? Reply with "MORE INFO" in the subject field If you are a reseller and would like information on paying what the distributors pay then Reply with Reseller in the subject field. If you have computer products you need to sell then email your details From owner-gsmp@psyton.com Sun Jan 9 18:29:06 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10957 for ; Sun, 9 Jan 2000 18:29:06 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id SAA18621 for gsmp-list; Sun, 9 Jan 2000 18:10:43 -0500 Received: from telecom.samsung.co.kr (metro.telecom.samsung.co.kr [165.213.221.4]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id SAA18618 for ; Sun, 9 Jan 2000 18:10:37 -0500 Received: from metro ([165.213.224.205]) by telecom.samsung.co.kr (8.9.3/8.9.3) with SMTP id IAA00843 for ; Mon, 10 Jan 2000 08:10:00 +0900 (KST) Message-ID: <000501bf5af8$0ead7060$cde0d5a5@telecom.samsung.co.kr> From: =?iso-8859-1?B?udrA58f2?= To: References: <573.706997.486296@sourcenet.org> Subject: REMOVE Date: Mon, 10 Jan 2000 08:19:59 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nighthawk.psyton.com id SAA18619 Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 8bit ----- Original Message ----- From: Sent: Sunday, January 09, 2000 5:32 PM Subject: Good Luck in the New Millenium > > To be removed from this mailing list immediately press reply and enter REMOVE on the subject line. > > Would you like to be able to buy Computers and Software at wholesale? > > At below what the stores Pay? > > Reply with "MORE INFO" in the subject field > > If you are a reseller and would like information on paying what the distributors pay then Reply with Reseller in the subject field. > > If you have computer products you need to sell then email your details > From owner-gsmp@psyton.com Sun Jan 9 20:14:42 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11493 for ; Sun, 9 Jan 2000 20:14:34 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id UAA19029 for gsmp-list; Sun, 9 Jan 2000 20:00:01 -0500 Received: from krdl.org.sg (rodin.krdl.org.sg [192.122.139.27]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id TAA19018 for ; Sun, 9 Jan 2000 19:59:59 -0500 Received: from mailhost.krdl.org.sg (mailbox.krdl.org.sg [192.122.134.30]) by krdl.org.sg (8.9.3/8.9.3) with ESMTP id JAA15646 for ; Mon, 10 Jan 2000 09:00:00 +0800 (SGT) Received: from krdl.org.sg (lonestar.krdl.org.sg [192.168.133.124]) by mailhost.krdl.org.sg (8.9.3/8.9.3) with ESMTP id IAA11438 for ; Mon, 10 Jan 2000 08:59:49 +0800 (SGT) Message-ID: <38792FD6.99F850E4@krdl.org.sg> Date: Mon, 10 Jan 2000 01:03:18 +0000 From: "M. Raguparan" Organization: Kent Ridge Digital Labs, Singapore X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.7 i686) X-Accept-Language: en MIME-Version: 1.0 To: gsmp@psyton.com Subject: REMOVE References: <573.706997.486296@sourcenet.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit jeffallen@sourcenet.org wrote: > To be removed from this mailing list immediately press reply and enter REMOVE on the subject line. > > Would you like to be able to buy Computers and Software at wholesale? > > At below what the stores Pay? > > Reply with "MORE INFO" in the subject field > > If you are a reseller and would like information on paying what the distributors pay then Reply with Reseller in the subject field. > > If you have computer products you need to sell then email your details -- M. Raguparan Infocom Lab, Kent Ridge Digital Labs Singapore Tel. (65) 874 8541 Fax. (65) 774 4990 From owner-gsmp@psyton.com Sun Jan 9 23:50:06 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14918 for ; Sun, 9 Jan 2000 23:50:05 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id XAA19640 for gsmp-list; Sun, 9 Jan 2000 23:39:21 -0500 Received: from fsnt.future.futusoft.com ([203.197.140.35]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id XAA19637 for ; Sun, 9 Jan 2000 23:39:07 -0500 Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Mon, 10 Jan 2000 10:16:36 +0530 Received: from simon.future.futsoft.com ([172.16.1.4]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id JAA09458 for ; Mon, 10 Jan 2000 09:59:16 +0530 Received: by simon.future.futsoft.com with Microsoft Mail id <01BF5B51.B6589340@simon.future.futsoft.com>; Mon, 10 Jan 2000 10:01:49 +0530 Message-Id: <01BF5B51.B6589340@simon.future.futsoft.com> From: Wang Shiming To: "'gsmp@psyton.com'" Subject: REMOVE Date: Mon, 10 Jan 2000 10:01:48 +0530 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="---- =_NextPart_000_01BF5B51.B6695C20" Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com ------ =_NextPart_000_01BF5B51.B6695C20 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit REMOVE -----Original Message----- From: ?UAcCo [SMTP:hyunie@telecom.samsung.co.kr] Sent: Monday, January 10, 2000 4:50 AM To: gsmp@psyton.com Subject: REMOVE ----- Original Message ----- From: Sent: Sunday, January 09, 2000 5:32 PM Subject: Good Luck in the New Millenium > > To be removed from this mailing list immediately press reply and enter REMOVE on the subject line. > > Would you like to be able to buy Computers and Software at wholesale? > > At below what the stores Pay? > > Reply with "MORE INFO" in the subject field > > If you are a reseller and would like information on paying what the distributors pay then Reply with Reseller in the subject field. > > If you have computer products you need to sell then email your details > ------ =_NextPart_000_01BF5B51.B6695C20 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+IjIEAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEkAYAgAEAAAEAAAAQAAAAAwAAMAIAAAAL AA8OAAAAAAIB/w8BAAAAPQAAAAAAAACBKx+kvqMQGZ1uAN0BD1QCAAAAAGdzbXBAcHN5dG9uLmNv bQBTTVRQAGdzbXBAcHN5dG9uLmNvbQAAAAAeAAIwAQAAAAUAAABTTVRQAAAAAB4AAzABAAAAEAAA AGdzbXBAcHN5dG9uLmNvbQADABUMAQAAAAMA/g8GAAAAHgABMAEAAAASAAAAJ2dzbXBAcHN5dG9u LmNvbScAAAACAQswAQAAABUAAABTTVRQOkdTTVBAUFNZVE9OLkNPTQAAAAADAAA5AAAAAAsAQDoB AAAAHgD2XwEAAAAQAAAAZ3NtcEBwc3l0b24uY29tAAIB918BAAAAPQAAAAAAAACBKx+kvqMQGZ1u AN0BD1QCAAAAAGdzbXBAcHN5dG9uLmNvbQBTTVRQAGdzbXBAcHN5dG9uLmNvbQAAAAADAP1fAQAA AAMA/18AAAAAAgH2DwEAAAAEAAAAAAAAAiFLAQSAAQAJAAAAIFJFTU9WRSAADgIBBYADAA4AAADQ BwEACgAKAAEAMAABAB4BASCAAwAOAAAA0AcBAAoACgAAADsAAQAoAQEJgAEAIQAAAEREOTEyMkEw NDRDN0QzMTFBODlCMDA2MDk0NUMwREM4ABAHAQOQBgAECgAAIQAAAAsAAgABAAAACwAjAAAAAAAD ACYAAAAAAAsAKQAAAAAAAwAuAAAAAAADADYAAAAAAEAAOQAgkqSbI1u/AR4AcAABAAAACQAAACBS RU1PVkUgAAAAAAIBcQABAAAAFgAAAAG/WyObcqAikd7HRBHTqJsAYJRcDcgAAB4AHgwBAAAABQAA AFNNVFAAAAAAHgAfDAEAAAAZAAAAd2FuZ3NAZnV0dXJlLmZ1dHNvZnQuY29tAAAAAAMABhD9xhuK AwAHEGkCAAAeAAgQAQAAAGUAAABSRU1PVkUtLS0tLU9SSUdJTkFMTUVTU0FHRS0tLS0tRlJPTTo/ VUFDQ09TTVRQOkhZVU5JRUBURUxFQ09NU0FNU1VOR0NPS1JTRU5UOk1PTkRBWSxKQU5VQVJZMTAs MjAwMDQ6AAAAAAIBCRABAAAA8QYAAO0GAADMEAAATFpGdSNFnoEDAAoAcmNwZzEyNXIyDGBjMQMw AQcLYG6RDhAwMzMPFmZlD5JPAfcCpANjAgBjaArAc4RldALRcHJxMgAAkioKoW5vElAgMAHQhQHQ Ng+gMDUwNBQh8wHQFBA0fQdtAoMAUAPU+xH/EwtiE+EUUBOyGPQU0K8HEwKAApEI5jsJbzAa3/pl DjA1HAodIRzfHekb9P8eEhx/IE8gDR+PHb8cDxBg/DI4Jdom8SavJ7kb9CfivyZPKh8p3SlfJ48r VDkOUB8upDABKCMwAAKCc3R56mwHkGgJ4HQAABNQA/BQZGN0bAqxXDJYYZhkanUxcAUQZ2gFQjsW MgwBYwnAMmADMHNufGV4FzAHsAWwAMACc3OxAFBzYjIUUDFgYRPw9FxrCeBwC5AyPzKjCGDrMpAL gGUxoHY5YAFAM5u/DDA0ZCgAN0AEoAuAZyfx6TTmYmEXEGQCIDWgNUbnMdAzkDuRIDExMw5QNp// N684vwBROfwAoDRuPH89hv8xJA/APo8/n0CvDlA570MP20QfPbMzAoITEGM2YEuhkzOQPbB0aTmQ IEQBEKhhdWwFQFAKwGEJwOBhcGggRgIhNiQlQOhmaS0PkDgBQDkwUDPrRw8yo2ILIHIJUFJSFqDZ UlJ3NCVBFwBwAdBNcn8zv0qfS6ZP0E6QBRACMC1DTzADYTogVG9XsFModWJqBZB0V7BEYeh0ZTo2 JDZP/1EPUh//Uy9UOTHAPaMOIUuhOrYOUJtVb1Z+UjmBFwEgSD2R+wSQNiQ3WW9af1uPXJ05Dy9d vw+QaXAI0GIKsHQ4/0n6D1RGEF+/YMZqAGHQC1C8eS9PQFywCxFiRXM2JP8oAGM/ZE9lX1yvVE9r X2xv7211V9JXdFipOW+/Mz8DMB1pszlzn3SveqBEb2P+dQeAAjAF0E8AGgF40ngw93hwcVEBgG5Y MABgCfBNoO99AAIBNeBeUmUA8H0AMYCScB6AXHYIkHdrC4D+ZGtAgKIE8AdAEGEBQA4A73EiPYKC BQIQbwVCFyES8g1YwG0LUVjAIEM6XOpcVwBvTuFtTzADEAeQTYSwTQ3gA2BzbwGAIK5PASAN4H/w XIZmRQDA9QMQLktwdH3QFxB4cDUh7WdyeAFAfwFuMdAa8IgEPU40YwMgEvMAgAWQbHb/QaFG0A5w NeCKkgGQACCLIv+A8X1BAcGKkRbgD3AAAEbQ8wzQAZAgLhoSiogOUItC/05weMCLv4zPjd8PwEbQ BYG3j3+Qj5GfbGtARtBsjz/7k/+VBSmODCVAkt+Xv5T0+GIgKAKRmN+K01lQlo//m0+cX51viwBj EJ6yi4+gH/+hL44MKACev6Q/pU+mX4sA/3gAoz+oz6nfquQK+QMweC8DeT96zXtSRU1PVv5FCoUK ha+kiGKtorCPsZ8PCME08jWgEvJia21rOayzIF99gAMQWKFhffotufJPskELgAdABdAHkPlGUGdl ufO0e7AGYv1vIP+1r3C/cc9nP2hPaV9qb7NEB7f2V3MMgiC52sDnAMf2IFtTTVRQkDpoeXUDAGVA WMBzMaAFoG0uRlB/oMfQZ8IuBaAua3Jdu5+8pP9uu73fvu+//3K/sswMIbgFXwZgAjDGhBoiuBRN AiBkoGF5LCBKAHB1CsA6eT3wMNMgAdDDYCA08jpe4UFNtHbQ2VfR0d0EZ3OEIEBwc3l0+wIgyRFt 1M/RYVgl0d2zpP+0bLAGtW+2f8+Ps1O0f9yP/92ft6MKhbnzhlC6XePFCoU9V3Q8WEABIAdAMaBu QE+GEAhwhqA1YHQuBbBnnj4KhdGDWAHS7DA50+VwNTozMk6Q1LZYF0dLgzA1IEwOcGsgsEF07zHQ B7OFwObSaX0gtAwKheY+7ohX0CBiE4Aa8ARg38HANSADUuyRBAAgh3I9wvfBYDFw7GBtB4A9sFix bTDeIBdwuuHwAW0hIABwNSD/fUEEkNqWAiDsk8jQWDPxoX01YC7unuBf4W+3De8AV/UIYGw1IHkI YPGhRqDskO/vwwGgMaD643XToAhQhCD3wUBiAfNzU4YhbZH7MQVA3HdoBvAHkIGhP/Zv93/3+I/5 le6XQQVA7+AJAAfgv/2w/YH0w9eQ8tFOkXn+Rt/vCW0D/aBNwE8gIrPAs6DAIElORk8i7Gb1Bttu 0MHQZARfBnBm+lP9Q9/wARNw5tH0APOCd/oT+qN35HB/cliwafSR9JH+gHn/PcIDFz2w3mL70AOx /JAMgf/sktwwBXlh0Ao1Bu8H8fXP/wknFuBN8dfR/EPysevw7DD+dPyQ+mI1YPBh+vEKMg6Ef4QQ h4H6UvQArWC5AIeQcz8Rd67guHZ/AblJ/lZ9AAIAGbAAAAADABAQAAAAAAMAERABAAAAAwCAEP// //9AAAcwYOt4fiNbvwFAAAgwYOt4fiNbvwELAACACCAGAAAAAADAAAAAAAAARgAAAAADhQAAAAAA AAMAAoAIIAYAAAAAAMAAAAAAAABGAAAAABCFAAAAAAAAAwAFgAggBgAAAAAAwAAAAAAAAEYAAAAA UoUAALcNAAAeACWACCAGAAAAAADAAAAAAAAARgAAAABUhQAAAQAAAAQAAAA4LjAAAwAmgAggBgAA AAAAwAAAAAAAAEYAAAAAAYUAAAAAAAALAC+ACCAGAAAAAADAAAAAAAAARgAAAAAOhQAAAAAAAAMA MIAIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAygAggBgAAAAAAwAAAAAAAAEYAAAAAGIUA AAAAAAAeAEGACCAGAAAAAADAAAAAAAAARgAAAAA2hQAAAQAAAAEAAAAAAAAAHgBCgAggBgAAAAAA wAAAAAAAAEYAAAAAN4UAAAEAAAABAAAAAAAAAB4AQ4AIIAYAAAAAAMAAAAAAAABGAAAAADiFAAAB AAAAAQAAAAAAAAAeAD0AAQAAAAEAAAAAAAAAAwANNP03AABeRg== ------ =_NextPart_000_01BF5B51.B6695C20-- From owner-gsmp@psyton.com Mon Jan 10 03:42:40 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27869 for ; Mon, 10 Jan 2000 03:42:40 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id DAA20298 for gsmp-list; Mon, 10 Jan 2000 03:33:06 -0500 Received: from dent.axion.bt.co.uk (dent.axion.bt.co.uk [132.146.16.161]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id DAA20295 for ; Mon, 10 Jan 2000 03:33:05 -0500 From: adrian.sapwell@bt.com Received: from chqlubnt02.lon.bt.com by dent (local) with ESMTP; Mon, 10 Jan 2000 08:32:12 +0000 Received: by chqlubnt02.lon.bt.com with Internet Mail Service (5.5.2651.23) id ; Mon, 10 Jan 2000 08:31:43 -0000 Message-ID: To: gsmp@psyton.com Subject: RE: Good Luck in the New Millenium Date: Mon, 10 Jan 2000 08:31:42 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2651.23) Content-Type: text/plain Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com REMOVE > -----Original Message----- > From: jeffallen [SMTP:jeffallen@sourcenet.org] > Sent: Sunday, January 09, 2000 5:32 PM > Subject: Good Luck in the New Millenium > > > To be removed from this mailing list immediately press reply and enter > REMOVE on the subject line. > > Would you like to be able to buy Computers and Software at wholesale? > > At below what the stores Pay? > > Reply with "MORE INFO" in the subject field > > If you are a reseller and would like information on paying what the > distributors pay then Reply with Reseller in the subject field. > > If you have computer products you need to sell then email your details From owner-gsmp@psyton.com Mon Jan 10 07:57:49 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01362 for ; Mon, 10 Jan 2000 07:57:48 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id HAA21052 for gsmp-list; Mon, 10 Jan 2000 07:48:04 -0500 Received: from localhost.localdomain (gemini2.ne.mediaone.net [24.128.27.98]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id HAA21049 for ; Mon, 10 Jan 2000 07:48:04 -0500 Received: from mediaone.net (IDENT:kgw@localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.9.3/8.9.3) with ESMTP id HAA00742 for ; Mon, 10 Jan 2000 07:46:32 -0500 Message-ID: <3879D4A7.2A2D53D4@mediaone.net> Date: Mon, 10 Jan 2000 07:46:31 -0500 From: Kenneth Watson X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20smp i686) X-Accept-Language: en MIME-Version: 1.0 To: gsmp@psyton.com Subject: REMOVE References: <573.706997.486296@sourcenet.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit jeffallen@sourcenet.org wrote: > To be removed from this mailing list immediately press reply and enter REMOVE on the subject line. > > Would you like to be able to buy Computers and Software at wholesale? > > At below what the stores Pay? > > Reply with "MORE INFO" in the subject field > > If you are a reseller and would like information on paying what the distributors pay then Reply with Reseller in the subject field. > > If you have computer products you need to sell then email your details REMOVE From owner-gsmp@psyton.com Mon Jan 10 09:54:32 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05156 for ; Mon, 10 Jan 2000 09:54:31 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id JAA21412 for gsmp-list; Mon, 10 Jan 2000 09:28:47 -0500 Received: from mail-dns1-nj.dialogic.com (mail-dns1-nj.dialogic.com [146.152.228.10]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id JAA21409 for ; Mon, 10 Jan 2000 09:28:47 -0500 Received: from mail4.dialogic.com (mail4.dialogic.com [146.152.6.40]) by mail-dns1-nj.dialogic.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.11 1999/11/10 17:27:15 spurcell Exp $) with ESMTP id OAA06657 for ; Mon, 10 Jan 2000 14:29:32 GMT Received: from exchange4nj.dialogic.com (exchange4nj.dialogic.com [146.152.3.19]) by mail4.dialogic.com (PMDF V5.2-31 #40816) with ESMTP id <0FO400A65IVUZG@mail4.dialogic.com> for gsmp@psyton.com; Mon, 10 Jan 2000 09:28:42 -0500 (EST) Received: by exchange4nj.dialogic.com with Internet Mail Service (5.5.2650.21) id ; Mon, 10 Jan 2000 09:28:54 -0500 Content-return: allowed Date: Mon, 10 Jan 2000 09:30:05 -0500 From: "Brown, Walt" Subject: REMOVE To: "'gsmp@psyton.com'" Message-id: <3E006CE92E9AD3119F4E00105A0C38073863F3@exchange1nj.dialogic.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7BIT -----Original Message----- From: jeffallen@sourcenet.org [mailto:jeffallen@sourcenet.org] Sent: Sunday, January 09, 2000 12:32 PM To: Walt.Brown@Dialogic.com Subject: Good Luck in the New Millenium To be removed from this mailing list immediately press reply and enter REMOVE on the subject line. Would you like to be able to buy Computers and Software at wholesale? At below what the stores Pay? Reply with "MORE INFO" in the subject field If you are a reseller and would like information on paying what the distributors pay then Reply with Reseller in the subject field. If you have computer products you need to sell then email your details From owner-gsmp@psyton.com Mon Jan 10 10:25:30 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05958 for ; Mon, 10 Jan 2000 10:25:27 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id KAA21704 for gsmp-list; Mon, 10 Jan 2000 10:10:28 -0500 Received: from taumsauk.cs.wustl.edu (cs.wustl.edu [128.252.165.15]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id KAA21701 for ; Mon, 10 Jan 2000 10:10:27 -0500 Received: from acme.cs.wustl.edu (acme.cs.wustl.edu [128.252.165.105]) by taumsauk.cs.wustl.edu (8.9.1/8.9.1) with ESMTP id JAA10952 for ; Mon, 10 Jan 2000 09:10:26 -0600 (CST) Received: (from fredk@localhost) by acme.cs.wustl.edu (8.9.1/8.9.1) id JAA12831 for gsmp@psyton.com; Mon, 10 Jan 2000 09:10:25 -0600 (CST) Date: Mon, 10 Jan 2000 09:10:25 -0600 From: Fred Kuhns To: gsmp@psyton.com Subject: REMOVE Message-ID: <20000110091025.A12827@acme.cs.wustl.edu> References: <573.706997.486296@sourcenet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <573.706997.486296@sourcenet.org>; from jeffallen@sourcenet.org on Sun, Jan 09, 2000 at 05:32:11PM +0000 Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com On Sun, Jan 09, 2000 at 05:32:11PM +0000, jeffallen@sourcenet.org wrote: > > To be removed from this mailing list immediately press reply and enter REMOVE on the subject line. > > Would you like to be able to buy Computers and Software at wholesale? > > At below what the stores Pay? > > Reply with "MORE INFO" in the subject field > > If you are a reseller and would like information on paying what the distributors pay then Reply with Reseller in the subject field. > > If you have computer products you need to sell then email your details From owner-gsmp@psyton.com Mon Jan 10 12:49:27 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09228 for ; Mon, 10 Jan 2000 12:49:26 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id MAA22207 for gsmp-list; Mon, 10 Jan 2000 12:32:42 -0500 Received: from home.gis.net ([208.218.130.20]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id MAA22204 for ; Mon, 10 Jan 2000 12:32:41 -0500 Received: from gis.net (ppp48-179.gis.net [216.41.48.179]) by home.gis.net (8.8.8/8.9.3) with ESMTP id MAA20838; Mon, 10 Jan 2000 12:32:35 -0500 (EST) Message-ID: <387A17C9.5B2E2D94@gis.net> Date: Mon, 10 Jan 2000 12:32:57 -0500 From: Stephan & Lisa X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: gsmp@psyton.com Subject: REMOVE References: <573.706997.486296@sourcenet.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit jeffallen@sourcenet.org wrote: > To be removed from this mailing list immediately press reply and enter REMOVE on the subject line. > > Would you like to be able to buy Computers and Software at wholesale? > > At below what the stores Pay? > > Reply with "MORE INFO" in the subject field > > If you are a reseller and would like information on paying what the distributors pay then Reply with Reseller in the subject field. > > If you have computer products you need to sell then email your details From owner-gsmp@psyton.com Tue Jan 11 17:03:54 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22019 for ; Tue, 11 Jan 2000 17:03:49 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id QAA27181 for gsmp-list; Tue, 11 Jan 2000 16:35:33 -0500 Received: from cplane.com (IDENT:qmailr@[63.193.105.226]) by nighthawk.psyton.com (8.9.0/8.9.0) with SMTP id QAA27178 for ; Tue, 11 Jan 2000 16:35:31 -0500 Received: (qmail 7296 invoked from network); 11 Jan 2000 21:23:07 -0000 Received: from unknown (HELO texas.cplane.com) (unknown) by unknown with SMTP; 11 Jan 2000 21:23:07 -0000 Received: (qmail 25422 invoked from network); 11 Jan 2000 21:34:39 -0000 Received: from unknown (HELO capetown) (unknown) by unknown with SMTP; 11 Jan 2000 21:34:39 -0000 From: "Simon Crosby" To: Subject: FW: Joint IETF/MSF GSMP meeting Date: Tue, 11 Jan 2000 13:35:35 -0800 Message-ID: <000b01bf5c7b$cc3c4d20$0e02a8c0@capetown.cplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit Some suggestions follow for accomodation for the joint MSF IETF GSMP working group meeting on Wednesday Feb 2. I strongly encourage IETF folks to attend; attendence for GSMP experts is free of charge. Regards Simon -----Original Message----- From: Alysia Johnson [mailto:ajohnson@msforum.org] Sent: Tuesday, January 11, 2000 11:46 AM To: simon@cplane.com Cc: Dave McDysan Subject: Joint IETF/MSF GSMP meeting From your last message, I believe you would like the joint meeting to occur on Wednesday, February 2. The hotel is sold out on the night of Wednesday, February 2. Alternative suggestions are listed below. across the street: Wyndham - 504-524-8200 Sheraton Four Points - 504-525-1615 or approx. 2 blocks away: Holiday Inn Select - 504-525-1881 Dave is in Italy this week and may or may not be checking email. If further invitation is required, you or I can provide one on his behalf. I look forward to hearing from you. Hope you are enjoying this "soup" weather today! Kind regards, Alyisa Alysia Stewart Johnson Executive Director, Multiservice Switching Forum Phone: (510) 608-3993, Fax: (510) 608-3995 39355 California Street, Ste. 307 Fremont, CA 94538 http://www.msforum.org From owner-gsmp@psyton.com Wed Jan 12 02:29:37 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10590 for ; Wed, 12 Jan 2000 02:29:37 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id CAA28754 for gsmp-list; Wed, 12 Jan 2000 02:14:57 -0500 Received: from gwa2.fe.bosch.de (gwa2.fe.bosch.de [195.71.148.2]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id CAA28751 for ; Wed, 12 Jan 2000 02:14:56 -0500 Received: (from uucp@localhost) by gwa2.fe.bosch.de (8.9.1/8.9.1) id IAA04297 for ; Wed, 12 Jan 2000 08:14:49 +0100 (MET) Received: from fez7358.fe.bosch.de( 10.8.1.102) by gwa2.fe.bosch.de via smap (V2.1) id xma004076; Wed, 12 Jan 00 08:14:39 +0100 Received: by fez7164.server.bosch.de with Internet Mail Service (5.5.2448.0) id ; Wed, 12 Jan 2000 08:14:29 +0100 Message-ID: <7DE0D5F41A2FD311AB6B08002BB6B39F47F789@bkmail2.bk.bosch.de> From: "Buerkle Joachim (UC-ON/EMY2) *" To: "'gsmp@psyton.com'" Subject: WG: Interim Editing session Date: Wed, 12 Jan 2000 08:14:24 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nighthawk.psyton.com id CAA28752 Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 8bit > Avri, > > is this session only an one day session or are there further discussions > about GSMP during the other days of the MSF meeting? > How good are the change that my proposal of my draft > sage-01.txt> will be incooperated during this editing session? > > Is this editing session only for the Protocol or also for the MIB? > > Thank You > Best Regards > Joachim > > - - - - - - - - - - - - - - - - - - - - > > > -----Ursprüngliche Nachricht----- > Von: avri.doria@nokia.com [SMTP:avri.doria@nokia.com] > Gesendet am: Freitag, 7. Januar 2000 21:13 > An: gsmp@psyton.com > Cc: simon@cplane.com; Dave.McDysan@wcom.com > Betreff: Interim Editing session > > Hi, > > This is to announce that there will be an interim GSMPv3 > specification editing session held Wednesday 2 Feb 00. This > session will be held jointly with the MSF switch control > working group. The meeting will be held during the > MSF Technical Committee meeting being held in New Orleans. > While the MSF meetings are closed to non MSF members, the > MSF has decided to invite GSMP WG members who want to > participate in this session and who don't happen to be MSF > members to attend the relevant Switch Control WG meeting on > Wed 2 Feb 00 free of charge. > > Anyone interested in attending should notify me as soon > as possible of their interest. > > Please note: In keeping with IETF practice any changes made > to the GSMPv3 specifications at the interim/joint meeting will > be subject to the subsequent approval of the IETF GSMP WG. > > Regards > > a. > ----------------------------------- > avri doria > Office: +1 781 993 4656 > Mobile: +1 781 308 7680 > From owner-gsmp@psyton.com Wed Jan 12 08:35:42 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15514 for ; Wed, 12 Jan 2000 08:35:41 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id IAA29621 for gsmp-list; Wed, 12 Jan 2000 08:17:41 -0500 Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id IAA29618 for ; Wed, 12 Jan 2000 08:17:30 -0500 From: avri.doria@nokia.com Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61]) by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id PAA16209; Wed, 12 Jan 2000 15:17:20 +0200 (EET) Received: from daebh02nok.americas.nokia.com (daebh02nok.americas.nokia.com [172.18.242.183]) by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id PAA29689; Wed, 12 Jan 2000 15:17:15 +0200 (EET) Received: by daebh02nok with Internet Mail Service (5.5.2448.0) id ; Wed, 12 Jan 2000 07:17:14 -0600 Message-ID: To: gsmp@psyton.com Cc: scwg@msforum.org Subject: RE: Joint IETF/MSF GSMP meeting Date: Wed, 12 Jan 2000 07:16:56 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Hi, I echo Simon's encouragement. I also encourage folks to send in, as soon as they can, itemized lists of the problems they wish to see resolved during the meeting. Suggestions of text are most welcome. a. ----------------------------------- avri doria Office: +1 781 993 4656 Mobile: +1 781 308 7680 > -----Original Message----- > From: EXT Simon Crosby [mailto:simon@cplane.com] > Sent: 11 January, 2000 4:36 PM > To: gsmp@psyton.com > Subject: FW: Joint IETF/MSF GSMP meeting > > > > Some suggestions follow for accomodation for the joint MSF > IETF GSMP working > group meeting on Wednesday Feb 2. > > I strongly encourage IETF folks to attend; attendence for > GSMP experts is > free of charge. > > Regards > > Simon > > -----Original Message----- > From: Alysia Johnson [mailto:ajohnson@msforum.org] > Sent: Tuesday, January 11, 2000 11:46 AM > To: simon@cplane.com > Cc: Dave McDysan > Subject: Joint IETF/MSF GSMP meeting > > From your last message, I believe you would like the joint meeting to > occur on Wednesday, February 2. The hotel is sold out on the night > of Wednesday, February 2. Alternative suggestions are listed below. > > across the street: > Wyndham - 504-524-8200 > Sheraton Four Points - 504-525-1615 > > or approx. 2 blocks away: > Holiday Inn Select - 504-525-1881 > > Dave is in Italy this week and may or may not be checking email. If > further invitation is required, you or I can provide one on his > behalf. I look forward to hearing from you. Hope you are enjoying > this "soup" weather today! > > Kind regards, > Alyisa > > > Alysia Stewart Johnson > Executive Director, Multiservice Switching Forum > Phone: (510) 608-3993, Fax: (510) 608-3995 > 39355 California Street, Ste. 307 > Fremont, CA 94538 > http://www.msforum.org > From owner-gsmp@psyton.com Wed Jan 12 16:30:34 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25082 for ; Wed, 12 Jan 2000 16:30:32 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id QAA31191 for gsmp-list; Wed, 12 Jan 2000 16:06:46 -0500 Received: from cplane.com (IDENT:qmailr@[63.193.105.226]) by nighthawk.psyton.com (8.9.0/8.9.0) with SMTP id QAA31188 for ; Wed, 12 Jan 2000 16:06:45 -0500 Received: (qmail 10343 invoked from network); 12 Jan 2000 20:54:23 -0000 Received: from unknown (HELO texas.cplane.com) (unknown) by unknown with SMTP; 12 Jan 2000 20:54:23 -0000 Received: (qmail 31608 invoked from network); 12 Jan 2000 21:06:00 -0000 Received: from unknown (HELO capetown) (unknown) by unknown with SMTP; 12 Jan 2000 21:06:00 -0000 From: "Simon Crosby" To: Subject: RE: Interim Editing session Date: Wed, 12 Jan 2000 13:06:36 -0800 Message-ID: <002e01bf5d40$e9f682c0$0e02a8c0@capetown.cplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: <7DE0D5F41A2FD311AB6B08002BB6B39F47F789@bkmail2.bk.bosch.de> Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 8bit The SCWG may have other business during the 3 days, but the Monday is for the architecture WG breakout, Tues is plenary and some breakout for the media control groups and switch control group, and wed will be used for GSMP editing. Simon > -----Original Message----- > From: owner-gsmp@psyton.com [mailto:owner-gsmp@psyton.com]On Behalf Of > Buerkle Joachim (UC-ON/EMY2) * > Sent: Tuesday, January 11, 2000 11:14 PM > To: 'gsmp@psyton.com' > Subject: WG: Interim Editing session > > > > Avri, > > > > is this session only an one day session or are there > further discussions > > about GSMP during the other days of the MSF meeting? > > > How good are the change that my proposal of my draft > > > e-branch-mes > > sage-01.txt> will be incooperated during this editing session? > > > > Is this editing session only for the Protocol or also for the MIB? > > > > Thank You > > Best Regards > > Joachim > > > > - - - - - - - - - - - - - - - - - - - - > > > > > > -----Ursprüngliche Nachricht----- > > Von: avri.doria@nokia.com [SMTP:avri.doria@nokia.com] > > Gesendet am: Freitag, 7. Januar 2000 21:13 > > An: gsmp@psyton.com > > Cc: simon@cplane.com; Dave.McDysan@wcom.com > > Betreff: Interim Editing session > > > > Hi, > > > > This is to announce that there will be an interim GSMPv3 > > specification editing session held Wednesday 2 Feb 00. This > > session will be held jointly with the MSF switch control > > working group. The meeting will be held during the > > MSF Technical Committee meeting being held in New Orleans. > > While the MSF meetings are closed to non MSF members, the > > MSF has decided to invite GSMP WG members who want to > > participate in this session and who don't happen to be MSF > > members to attend the relevant Switch Control WG meeting on > > Wed 2 Feb 00 free of charge. > > > > Anyone interested in attending should notify me as soon > > as possible of their interest. > > > > Please note: In keeping with IETF practice any changes made > > to the GSMPv3 specifications at the interim/joint meeting will > > be subject to the subsequent approval of the IETF GSMP WG. > > > > Regards > > > > a. > > ----------------------------------- > > avri doria > > Office: +1 781 993 4656 > > Mobile: +1 781 308 7680 > > > From owner-gsmp@psyton.com Wed Jan 12 19:18:53 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27147 for ; Wed, 12 Jan 2000 19:18:45 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id SAA31653 for gsmp-list; Wed, 12 Jan 2000 18:34:16 -0500 Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id SAA31650 for ; Wed, 12 Jan 2000 18:34:14 -0500 From: avri.doria@nokia.com Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61]) by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id BAA09904 for ; Thu, 13 Jan 2000 01:34:13 +0200 (EET) Received: from daebh01nok.americas.nokia.com (daebh01nok.americas.nokia.com [172.18.242.182]) by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id BAA24288 for ; Thu, 13 Jan 2000 01:34:04 +0200 (EET) Received: by daebh01nok with Internet Mail Service (5.5.2448.0) id ; Wed, 12 Jan 2000 17:33:51 -0600 Message-ID: To: gsmp@psyton.com Subject: Interim Editing Session Date: Wed, 12 Jan 2000 17:33:44 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Hi, I was informed that by calling the editing session a joint meeting I was transgressing on the charter and rules of the IETF, and quite possibly of the MSF as well. The event is an editing session which will be held simultaneously with the MSF switch control WG meeting. As far as the IETF is concerned it is an interim editing session, and as far as the MSF is concerned, GSMP WG members are being invited to the MSF meeting as technical specialists on GSMP. As indicated in my original note, any changes made to the document will need to be approved by the GSMP WG using standard IETF practice. If anyone objects to handling the editing process in this manner, please let me know as soon as possible. Thank you, and apologies for any confusion. a. ----------------------------------- avri doria Office: +1 781 993 4656 Mobile: +1 781 308 7680 From owner-gsmp@psyton.com Wed Jan 12 20:15:19 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27530 for ; Wed, 12 Jan 2000 20:15:13 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id TAA31904 for gsmp-list; Wed, 12 Jan 2000 19:31:00 -0500 Received: from cplane.com (IDENT:qmailr@[63.193.105.226]) by nighthawk.psyton.com (8.9.0/8.9.0) with SMTP id TAA31901 for ; Wed, 12 Jan 2000 19:30:59 -0500 Received: (qmail 10975 invoked from network); 13 Jan 2000 00:18:36 -0000 Received: from unknown (HELO texas.cplane.com) (unknown) by unknown with SMTP; 13 Jan 2000 00:18:36 -0000 Received: (qmail 21572 invoked from network); 13 Jan 2000 00:30:14 -0000 Received: from unknown (HELO capetown) (unknown) by unknown with SMTP; 13 Jan 2000 00:30:14 -0000 From: "Simon Crosby" To: Subject: RE: Interim Editing Session Date: Wed, 12 Jan 2000 16:30:21 -0800 Message-ID: <005201bf5d5d$60753920$0e02a8c0@capetown.cplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit Storm in a teacup. On we go! Thanks Simon > -----Original Message----- > From: owner-gsmp@psyton.com [mailto:owner-gsmp@psyton.com]On Behalf Of > avri.doria@nokia.com > Sent: Wednesday, January 12, 2000 3:34 PM > To: gsmp@psyton.com > Subject: Interim Editing Session > > > Hi, > > I was informed that by calling the editing session > a joint meeting I was transgressing on the charter and > rules of the IETF, and quite possibly of the MSF as > well. > > The event is an editing session which will be held > simultaneously with the MSF switch control WG > meeting. As far as the IETF is concerned it is > an interim editing session, and as far as the MSF > is concerned, GSMP WG members are being invited to > the MSF meeting as technical specialists on GSMP. > > As indicated in my original note, any changes made to > the document will need to be approved by the GSMP WG > using standard IETF practice. > > If anyone objects to handling the editing process in > this manner, please let me know as soon as possible. > > Thank you, and apologies for any confusion. > > a. > ----------------------------------- > avri doria > Office: +1 781 993 4656 > Mobile: +1 781 308 7680 > > From owner-gsmp@psyton.com Sun Jan 16 19:38:14 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12078 for ; Sun, 16 Jan 2000 19:38:13 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id TAA13730 for gsmp-list; Sun, 16 Jan 2000 19:09:21 -0500 Received: from thefsb.org (216-59-34-200.usa.flashcom.net [216.59.34.200]) by nighthawk.psyton.com (8.9.0/8.9.0) with SMTP id TAA13727 for ; Sun, 16 Jan 2000 19:09:20 -0500 Received: (qmail 25648 invoked from network); 17 Jan 2000 00:09:01 -0000 Received: from unknown (HELO fsbwife) (192.168.65.2) by 216-59-34-200.usa.flashcom.net with SMTP; 17 Jan 2000 00:09:01 -0000 From: "tom worster" To: Subject: RE: Question on Connection Management Messages Date: Sun, 16 Jan 2000 19:04:21 -0500 Message-ID: <001101bf607e$6c149fe0$0241a8c0@fsbwife> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <000501bf5934$3ca549e0$8a817aa5@pc25811.wcom.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit From: owner-gsmp@psyton.com [mailto:owner-gsmp@psyton.com]On Behalf Of Clint Bishard > > I would consider policing a function of QoS, and this would > occur at the > ingress port, or ingress traffic shaping may be another > function that would > need to be controlled at the ingress port. Therefore, I can > see were we > would need to specify the service parameters for each port > individually > given the specific service. > For example, say a switch has two UNI ports to a customer. > One of the UNI > ports is a FR port and the other UNI port is an ATM port. We > want to build > a connection between these ports and offer a FR to ATM > interworking service. > We want policing on both ingress ports. A CIR and EIR is > specified for the > FR port and a PCR, SCR, MBS is specified for the ATM port. > Instead of being > constrained to just providing ATM parameters or FR parameters > and the switch > doing a conversion to the others, we want to explicitly state these > parameters to the switch for each port. How could we do this with the > current GSMP framework? Could this be done by building the > connection with > two GSMP connections and specifying FR in one and ATM in another? explicit control of policing parameters is an interesting question. you mentioned interworking examples which are valid but, thinking about it, explicit control of policing parameters is useful in general. it was perhaps a mistake to assume that the policing parameters to be used for a connection would be the same as the parameters used for resource allocation. i'm not keen on the idea of using two add branch messages as you suggest. wouldn't it make more sense to allow policing parameters to be specified in the add branch message? by the nature of policing, they would apply at the input. c u tom From owner-gsmp@psyton.com Wed Jan 19 08:23:54 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28234 for ; Wed, 19 Jan 2000 08:23:54 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id HAA24029 for gsmp-list; Wed, 19 Jan 2000 07:59:30 -0500 Received: from old-callisto.ftel.co.uk (big-relay-1.ftel.co.uk [192.65.220.123]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id HAA24026 for ; Wed, 19 Jan 2000 07:59:28 -0500 Received: (from root@localhost) by old-callisto.ftel.co.uk (8.9.3/8.9.3/Revision:1.42) id MAA08848 for gsmp@revnetworks.com; Wed, 19 Jan 2000 12:59:27 GMT Received: from ftel.co.uk (dm@callisto.ftel.co.uk [172.16.2.99]) by old-callisto.ftel.co.uk (8.9.3/8.9.3/Revision:1.42/scanin/yp) with ESMTP id MAA08842; Wed, 19 Jan 2000 12:59:25 GMT Message-ID: <3885B52B.3F9CECFA@ftel.co.uk> Date: Wed, 19 Jan 2000 12:59:23 +0000 From: David Moreland Organization: Fujitsu Telecommunications Europe Ltd X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: gsmp@psyton.com Subject: GSMP API Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit As a general enquiry, does anyone know of the existence of a GSMP API and where I moght be able to acquire one? Kind Regards, Dr D.Moreland (Network Solutions Group), Fujitsu Telecomm's Europe Ltd., Solihull Parkway, Birmingham Business Park, Birmingham B37 7YU, United Kingdom Tel:+44 (0)121 717 6174 Fax:+44 (0)121 717 6018 Email: D.Moreland@ftel.co.uk From owner-gsmp@psyton.com Wed Jan 19 09:26:16 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29305 for ; Wed, 19 Jan 2000 09:26:16 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id JAA24328 for gsmp-list; Wed, 19 Jan 2000 09:09:28 -0500 Received: from external.xbind.com ([207.51.60.10]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id JAA24325 for ; Wed, 19 Jan 2000 09:09:27 -0500 Received: from katja.xbind.com (katja.xbind.com [207.51.60.34] (may be forged)) by external.xbind.com (8.9.0/8.9.0) with SMTP id JAA03835; Wed, 19 Jan 2000 09:19:38 -0500 (EST) From: "Aurel A. Lazar" To: Cc: "Aurel A. Lazar" Subject: RE: GSMP API Date: Wed, 19 Jan 2000 09:02:53 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: <3885B52B.3F9CECFA@ftel.co.uk> Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit The IEEE PIN ATM subworking group has a draft doc for the API. It is called the CCM Interface and can be found on the http://www.ieee-pin.org web site. Aurel -----Original Message----- From: owner-gsmp@psyton.com [mailto:owner-gsmp@psyton.com]On Behalf Of David Moreland Sent: Wednesday, January 19, 2000 7:59 AM To: gsmp@psyton.com Subject: GSMP API As a general enquiry, does anyone know of the existence of a GSMP API and where I moght be able to acquire one? Kind Regards, Dr D.Moreland (Network Solutions Group), Fujitsu Telecomm's Europe Ltd., Solihull Parkway, Birmingham Business Park, Birmingham B37 7YU, United Kingdom Tel:+44 (0)121 717 6174 Fax:+44 (0)121 717 6018 Email: D.Moreland@ftel.co.uk From owner-gsmp@psyton.com Thu Jan 20 11:11:03 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04976 for ; Thu, 20 Jan 2000 11:10:55 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id KAA29027 for gsmp-list; Thu, 20 Jan 2000 10:49:08 -0500 Received: from qhars002.nortel.com (qhars002.NortelNetworks.com [192.100.101.19]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id KAA29023 for ; Thu, 20 Jan 2000 10:49:07 -0500 Received: from zhard00d.europe.nortel.com (actually zhard00d) by qhars002.nortel.com; Thu, 20 Jan 2000 15:47:17 +0000 Received: from zvb1c004.corpemea.baynetworks.com (ZVB1C004 [141.251.160.84]) by zhard00d.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id D1TKTZ9B; Thu, 20 Jan 2000 15:47:18 -0000 Received: from europem01.nt.com (KSUNDELL [141.251.192.214]) by zvb1c004.corpemea.baynetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id DBYCYAG9; Thu, 20 Jan 2000 16:47:15 +0100 Message-ID: <38872D6F.952A5F@europem01.nt.com> Date: Thu, 20 Jan 2000 16:44:48 +0100 From: "Kenneth Sundell" X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: gsmp-list Subject: GSMPv3 review Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit Hi, This is a review of the work currently being done on the GSMPV3 Specification. We are working down to the last minute trying to get as many of the changes in before the editing session in New Orleans on Week 5. It is our intention to submit the current version to the IETF I-D editor and the MSF repository on 24 Jan. Review of document status: - Re: Reservations. Support for reservations is being added and will be available for review in New Orleans. - Re: Changing the method of listing label stacks as well as the addition of specific operations for pushing and popping labels onto the stack. This will remain unchanged in the next version of the spec. It is not clear that the current method is insufficient; the current chaining techniques allows for as deep a stack as may be desired. Also the operations of push and pop are implicit in that in cases where the number of input labels is greater than the number of output labels you have a push, and in cases where the number of output labels is greater then the number of input labels, you have a pop. - Re: Addition of a service selector to the input label. This has been added to connection messages. However, this change will require further discussion, and will probably cause changes to the default service model capability set definitions. This should be discussed both on the list and at the editing session. - Re: Addition of label length and a sub-message number field to all messages other then the adjacency message. This is being added in the current version. - Re: Changes to Delete All to support a distinction for connection that originate, that terminate or both. This is being added in this version. It is, however, recommended, that while the protocol should support this, that only deletion of all connection originating on the port be required. - Re: Addition of the label length as suggested by Cplane. This is not being included in this version of the spec. The editors did not have a clear understanding of which supported label types required a length larger then 28 bits. Thus, we did not see a reason to incur the extra processing required to support the length field for labels. - Re: Changes to the the Port Event Alarm, i.e. not incrementing the session id for some events. This is not being included in this version. The editor's felt that this would be risky. In the example of transition from carrier to no carrier and back to carrier, it seems that this could be an occasion where a cable was unplugged and another cable was subsequently plugged in to the same port. Assuming that this was still the same session could be problematic. It seems safer to force the controller to determine what the cause of the event was, as opposed to just ignoring the event in all cases. - Re: Changing the default behavior for traps. Changes in support of this proposal are being included in the next version. I.e. the default will changed so that all traps are sent unless the controller has explicitly requested that no traps of a particular variety be sent. All other items are still pending discussions and should be discussed at the interim editing session and on the list. Regards, Avri, Tom, Fiffi and Kenneth From owner-gsmp@psyton.com Mon Jan 24 14:07:38 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19567 for ; Mon, 24 Jan 2000 14:07:38 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id MAA06817 for gsmp-list; Mon, 24 Jan 2000 12:29:10 -0500 Received: from nic.bme.hu (nic.bme.hu [152.66.115.1]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id MAA06814 for ; Mon, 24 Jan 2000 12:29:08 -0500 Received: from akkord (akkord.sch.bme.hu [152.66.224.208]) by nic.bme.hu (Postfix) with SMTP id 8D84F39ADE for ; Mon, 24 Jan 2000 18:28:41 +0100 (MET) Message-ID: <003e01bf6690$72e1fd00$d0e04298@akkord.sch.bme.hu> From: "Maliosz Markosz" To: Subject: GSMP controller question Date: Mon, 24 Jan 2000 18:28:36 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Content-Transfer-Encoding: 7bit Hi, We want to implement a GSMP controller on Linux. Is there any free source code, or some kind of framework that is possibly usable? Thanks in advance Markosz Maliosz PhD Student in Informatics, High Speed Networks Laboratory Department of Telecommunications and Telematics Technical University of Budapest, Hungary From owner-gsmp@psyton.com Mon Jan 24 19:04:31 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00193 for ; Mon, 24 Jan 2000 19:04:30 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id SAA08259 for gsmp-list; Mon, 24 Jan 2000 18:14:31 -0500 Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id SAA08254 for ; Mon, 24 Jan 2000 18:12:11 -0500 From: avri.doria@nokia.com Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61]) by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id BAA11923; Tue, 25 Jan 2000 01:12:07 +0200 (EET) Received: from daebh02nok.americas.nokia.com (daebh02nok.americas.nokia.com [172.18.242.183]) by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id BAA16368; Tue, 25 Jan 2000 01:12:06 +0200 (EET) Received: by daebh02nok with Internet Mail Service (5.5.2448.0) id ; Mon, 24 Jan 2000 17:12:05 -0600 Message-ID: To: gsmp@psyton.com Cc: msf-scwg@msforum.org Subject: GSMPv3 update for next week's editing session. Date: Mon, 24 Jan 2000 17:11:24 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Hi, The GSMPv3 Rev 03 Specification and the separate Encapsulation specifications have been submitted to the I-D editor. They should be posted in due course. In the meantime, copies of the txt, pdf, and doc files can be found on: www.apocalypse.org/~avri/gsmp-specs/ . The changes include: - Support for reservations has been added. - An input label service selector has been added to connection messages. However, this change will require further discussion, and will probably require changes to the default service model capability set definitions. This should be discussed both on the list and at the editing session. - A label length and a sub-message number field has been added to all messages other then the adjacency message. - Delete All has been removed. In its place 2 messages have been added: Delete All Input Port and Delete All Output Port. - While the default for Alarms remains No Ack, a result value has been added (ReturnReceipt) which, when set, demands an ACK. - A capability to turn flow control on or off for the Alarm mechanism has been added. - The Encapsulation sections have been moved to a separate document - Additional work has been done on labels, including the addition of Frame Relay labels and the MPLS generic label. Regards, a. ----------------------------------- avri doria Office: +1 781 993 4656 Mobile: +1 781 308 7680 From owner-gsmp@psyton.com Thu Jan 27 07:26:14 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03111 for ; Thu, 27 Jan 2000 07:26:12 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id HAA18048 for gsmp-list; Thu, 27 Jan 2000 07:00:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id HAA18045 for ; Thu, 27 Jan 2000 07:00:04 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02701; Thu, 27 Jan 2000 07:00:03 -0500 (EST) Message-Id: <200001271200.HAA02701@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: gsmp@psyton.com From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-gsmp-03.txt Date: Thu, 27 Jan 2000 07:00:03 -0500 Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com --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 Author(s) : T. Worster, A. Doria, F. Hellstrand, K. Sundell Filename : draft-ietf-gsmp-03.txt Pages : 121 Date : 25-Jan-00 This memo provides the second draft of the standards track specification of GSMP. It is a revision of draft-worster-gsmp-00 which itself was based on GSMP V2 [7]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-gsmp-03.txt 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-03.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-03.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: <20000125075008.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-gsmp-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-gsmp-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000125075008.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-gsmp@psyton.com Thu Jan 27 07:38:30 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03112 for ; Thu, 27 Jan 2000 07:26:12 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id HAA18043 for gsmp-list; Thu, 27 Jan 2000 07:00:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id GAA18032 for ; Thu, 27 Jan 2000 06:59:57 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02678; Thu, 27 Jan 2000 06:59:55 -0500 (EST) Message-Id: <200001271159.GAA02678@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: gsmp@psyton.com From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-gsmp-encaps-00.txt Date: Thu, 27 Jan 2000 06:59:55 -0500 Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com --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 : GSMP Packet Encapsulations for ATM, Ethernet and TCP Author(s) : T. Worster Filename : draft-ietf-gsmp-encaps-00.txt Pages : 7 Date : 25-Jan-00 This memo specifies the encapsulation of GSMP packets in ATM, Ethernet and TCP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-gsmp-encaps-00.txt 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-encaps-00.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-encaps-00.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: <20000125074958.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-gsmp-encaps-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-gsmp-encaps-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000125074958.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-gsmp@psyton.com Fri Jan 28 08:58:15 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10482 for ; Fri, 28 Jan 2000 08:58:14 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id IAA22503 for gsmp-list; Fri, 28 Jan 2000 08:38:39 -0500 Received: from hue.jadn.com (IDENT:root@r82aap002309.sbo-arl.ma.cable.rcn.com [146.115.124.109]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id IAA22499 for ; Fri, 28 Jan 2000 08:38:33 -0500 From: avri.doria@nokia.com Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by hue.jadn.com (8.9.3/8.9.3) with ESMTP id IAA22743 for ; Fri, 28 Jan 2000 08:38:34 -0500 Received: from mgw-i1.ntc.nokia.com (mgw-i1.ntc.nokia.com [131.228.118.60]) by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id PAA26589 for ; Fri, 28 Jan 2000 15:33:26 +0200 (EET) Received: from daebh01nok.americas.nokia.com (daebh01nok.americas.nokia.com [172.18.242.182]) by mgw-i1.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id PAA00573 for ; Fri, 28 Jan 2000 15:33:24 +0200 (EET) Received: by daebh01nok with Internet Mail Service (5.5.2448.0) id ; Fri, 28 Jan 2000 07:32:59 -0600 Message-ID: To: gsmp@psyton.com Subject: RE: GSMP controller question Date: Fri, 28 Jan 2000 07:32:41 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="windows-1250" Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Hi, I know there are few implementation efforts underway, but don't know if anyone is willing to offer code. I think a Linux implementation is a wonderful idea, and encourage it strongly. In terms of implementations, I would like to get a few of the folks in the process of implementing to give short reports on their efforts in Adelaide. Anyone who is willing, should let me know so we can set the agenda. Even if someone is not planning to attend the meeting, I would appreciate having a few self-explanatory slides which we could show. Regards, a. ----------------------------------- avri doria Office: +1 781 993 4656 Mobile: +1 781 308 7680 > -----Original Message----- > From: EXT Maliosz Markosz [mailto:s5041mal@ural2.hszk.bme.hu] > Sent: 24 January, 2000 12:29 PM > To: gsmp@psyton.com > Subject: GSMP controller question > > > Hi, > > We want to implement a GSMP controller on Linux. > Is there any free source code, or some kind of framework that > is possibly > usable? > > Thanks in advance > > Markosz Maliosz > PhD Student in Informatics, High Speed Networks Laboratory > Department of Telecommunications and Telematics > Technical University of Budapest, Hungary > > From owner-gsmp@psyton.com Sun Jan 30 11:44:17 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09787 for ; Sun, 30 Jan 2000 11:44:16 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id LAA29744 for gsmp-list; Sun, 30 Jan 2000 11:21:16 -0500 Received: from cplane.com (IDENT:qmailr@[63.193.105.226]) by nighthawk.psyton.com (8.9.0/8.9.0) with SMTP id LAA29741 for ; Sun, 30 Jan 2000 11:21:14 -0500 Received: (qmail 22882 invoked from network); 30 Jan 2000 16:07:51 -0000 Received: from unknown (HELO texas.cplane.com) (unknown) by unknown with SMTP; 30 Jan 2000 16:07:51 -0000 Received: (qmail 10082 invoked from network); 30 Jan 2000 16:21:36 -0000 Received: from unknown (HELO texas.cplane.com) (unknown) by unknown with SMTP; 30 Jan 2000 16:21:36 -0000 Date: Sun, 30 Jan 2000 08:21:36 -0800 (PST) From: Balaji Srinivasan To: gsmp-list Subject: Re: GSMPv3 review In-Reply-To: <38872D6F.952A5F@europem01.nt.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com Hi Everyone, I just read the new GSMP draft and here are some of my comments. On Thu, 20 Jan 2000, Kenneth Sundell wrote: > - Re: Addition of label length and a sub-message number > field to all messages other then the adjacency message. > This is being added in the current version. I assume instead of label length u meant to say message length. The only addition that we would like to make is in the first PDU of a multiple PDU message the total length of all the data elements of all the sub-messages should be mentioned. Also the number of sub-messages to follow. This would allow an efficient implementation of reading in all the sub-messages and then parsing them as a complete buffer. This can be achieved by setting the result flag to indicate that its the first message and then the sub-message number field can have the total number of submessages. The total length of all the messages can be a 2 byte field immediately after the length field. This field is present only on the first message. > - Re: Addition of the label length as suggested by Cplane. > This is not being included in this version of the spec. The > editors did not have a clear understanding of which supported > label types required a length larger then 28 bits. Thus, > we did not see a reason to incur the extra processing > required to support the length field for labels. I beleive that even though most labels might not extend 28 bits it might be better to have a 8 bit or 4 bit label length (which indicates the label length in bytes (the labels can be padded with 0s if the label length is not a multiple of bytes) This makes it so that the controller/switch does not have to check bit masks to see if there is an extended label and then collecting all of them and then decoding what the label means. > - Re: Changes to the the Port Event Alarm, i.e. not incrementing > the session id for some events. This is not being included in > this version. The editor's felt that this would be risky. > In the example of transition from carrier to no carrier and back > to carrier, it seems that this could be an occasion where a > cable was unplugged and another cable was subsequently > plugged in to the same port. Assuming that this was still the > same session could be problematic. It seems safer to force > the controller to determine what the cause of the event was, as > opposed to just ignoring the event in all cases. How about a way for the controller to tell the switch not to change the port session numbers in case of a carrier/noCarrier event? That way connection request messages that have been sent need not fail with an invalidPortSession number code if the controller does not want it to. This can be implemented in the negotiation phase where the controller tells the switch whether it wants to receive all events or flow control the events. Apart from this the whole of section 3 of draft-sydir-cplane-gsmp-enhancements-00 has not been considered. This section allows the controller to rapidly synchronize with the switch as far as port status and events that happened in the time during which communication between switch and controller was down. This section also outlines the way in which multiple label ranges can be specified in the port configuration response. This is essential for partitioned networks. This draft is available at http://www.ietf.org/internet-drafts/draft-sydir-cplane-gsmp-enhancements-00.txt Thanks a lot for all the hard work balaji From owner-gsmp@psyton.com Mon Jan 31 00:25:45 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16697 for ; Mon, 31 Jan 2000 00:25:43 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id AAA31842 for gsmp-list; Mon, 31 Jan 2000 00:08:09 -0500 Received: from fsnt.future.futusoft.com ([203.197.140.35]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id AAA31839 for ; Mon, 31 Jan 2000 00:07:58 -0500 Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Mon, 31 Jan 2000 10:45:40 +0530 Received: from simon.future.futsoft.com ([172.16.1.4]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id KAA25154 for ; Mon, 31 Jan 2000 10:26:08 +0530 Received: by simon.future.futsoft.com with Microsoft Mail id <01BF6BD6.21065620@simon.future.futsoft.com>; Mon, 31 Jan 2000 10:30:01 +0530 Message-Id: <01BF6BD6.21065620@simon.future.futsoft.com> From: Wang Shiming To: "'gsmp@psyton.com'" Subject: RE: GSMPv3 review Date: Mon, 31 Jan 2000 10:29:59 +0530 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="---- =_NextPart_000_01BF6BD6.210F7DE0" Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com ------ =_NextPart_000_01BF6BD6.210F7DE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable hi, Mr. balaji: you said in you mail that each Port Record should contain the Event Sequence Number and the Event Flags for that port because = this section allows the controller to rapidly synchronize with the switch. = How can this be done? To controller, What's the use of shuch = information as Event Number, and Event Flag? How will the controller = process these information? BTW, should the switch hardware keep the = event flag and Event Sequenct Number for every port? If these two are = keeped in Gsmp slave's software, I don't know how your suggestion will = allow quickly synchronization. Could you give me some instruction? =20 Thanks in Advance! wangs =09 >>Apart from this the whole of section 3 of >>>>draft-sydir-cplane-gsmp-enhancements-00 has not been considered. = This >>section allows the controller to rapidly synchronize with the switch >>as far as port status and events that happened in the time during >>which communication between switch and controller was down.=20 ------ =_NextPart_000_01BF6BD6.210F7DE0 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+IgEFAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEkAYAgAEAAAEAAAAQAAAAAwAAMAIAAAAL AA8OAAAAAAIB/w8BAAAAPQAAAAAAAACBKx+kvqMQGZ1uAN0BD1QCAAAAAGdzbXBAcHN5dG9uLmNv bQBTTVRQAGdzbXBAcHN5dG9uLmNvbQAAAAAeAAIwAQAAAAUAAABTTVRQAAAAAB4AAzABAAAAEAAA AGdzbXBAcHN5dG9uLmNvbQADABUMAQAAAAMA/g8GAAAAHgABMAEAAAASAAAAJ2dzbXBAcHN5dG9u LmNvbScAAAACAQswAQAAABUAAABTTVRQOkdTTVBAUFNZVE9OLkNPTQAAAAADAAA5AAAAAAsAQDoB AAAAHgD2XwEAAAAQAAAAZ3NtcEBwc3l0b24uY29tAAIB918BAAAAPQAAAAAAAACBKx+kvqMQGZ1u AN0BD1QCAAAAAGdzbXBAcHN5dG9uLmNvbQBTTVRQAGdzbXBAcHN5dG9uLmNvbQAAAAADAP1fAQAA AAMA/18AAAAAAgH2DwEAAAAEAAAAAAAAAiFLAQSAAQASAAAAUkU6IEdTTVB2MyByZXZpZXcAgwUB BYADAA4AAADQBwEAHwAKAB0AOwABAFoBASCAAwAOAAAA0AcBAB8ACgAHADsAAQBEAQEJgAEAIQAA ADY0ODE3Qzk4QzJEN0QzMTFBODlCMDA2MDk0NUMwREM4ABUHAQOQBgCcCgAAIQAAAAsAAgABAAAA CwAjAAAAAAADACYAAAAAAAsAKQAAAAAAAwAuAAAAAAADADYAAAAAAEAAOQAguBAGqGu/AR4AcAAB AAAAEgAAAFJFOiBHU01QdjMgcmV2aWV3AAAAAgFxAAEAAAAWAAAAAb9rqAXvmHyBZdfCEdOomwBg lFwNyAAAHgAeDAEAAAAFAAAAU01UUAAAAAAeAB8MAQAAABkAAAB3YW5nc0BmdXR1cmUuZnV0c29m dC5jb20AAAAAAwAGEGazACEDAAcQGAMAAB4ACBABAAAAZQAAAEhJLE1SQkFMQUpJOllPVVNBSURJ TllPVU1BSUxUSEFURUFDSFBPUlRSRUNPUkRTSE9VTERDT05UQUlOVEhFRVZFTlRTRVFVRU5DRU5V TUJFUkFORFRIRUVWRU5URkxBR1NGT1IAAAAAAgEJEAEAAAB9BwAAeQcAAOgQAABMWkZ19c1PSAMA CgByY3BnMTI1cjIMYGMxAzABBwtgbpEOEDAzMw8WZmUPkk8B9wKkA2MCAGNoCsBzhGV0AtFwcnEy AACSKgqhbm8SUCAwAdCFAdA2D6AwNTA0FCHzAdAUEDR9B20CgwBQA9T7Ef8TC2IT4RRQE7IY9BTQ rwcTAoACkQjmOwlvMBrf+mUOMDUcCh0hHN8d6Rv0/x4SHH8gTyANH48dvxwPEGD8Mjgl2ibxJq8n uRv0J+K/Jk8qHyndKV8njytUOQ5QHy6kMAEoIzAAAoJzdHnqbAeQaAngdAAAE1AD8FBkY3RsCrFc MlhhmGRqdTFwBRBnaAVCOxYyDAFjCcAyYAMwc258ZXgXMAewBbAAwAJzc7EAUHNiMhRQMWBhE/D0 XGsJ4HALkDI/MqMIYOsykAuAZTGgdjlgAUAzm78MMDRkKAA3QASgC4BnJ/HpNOZiYRcQZAIgNaA1 Rucx0DOQO5EgMTEzDlA2n/83rzi/AFE5/ACgNG48fz2G/zEkD8A+jz+fQK8OUDnvQw/bRB89szMC ghMQYzZgS6GTM5A9sHRpOZAgRAEQqGF1bAVAUArAYQnA4GFwaCBGAiE2JCVA6GZpLQ+QOAFAOTBQ M+tHDzKjYgsgcglQUlIWoNlSUnc0JUEXAHAB0E1yfzO/Sp9Lpk/QTpAFEAIwLUNPMANhOiBUb1ew Uyh1YmoFkHRXsERh6HRlOjYkNk//UQ9SH/9TL1Q5McA9ow4hS6E6tg5Qm1VvVn5SOYEXASBIPZH7 BJA2JDdZb1p/W49cnTkPL12/D5BpcAjQYgqwdDj/SfoPVEYQX79gxmoAYdALULx5L09AXLALEWJF czYk/ygAYz9kT2VfXK9UT2tfbG/vbXVX0ld0WKk5b78zPwMwHWmzOXOfdK96oERvY/51B4ACMAXQ TwAaAxMQGvCCdgJRIHtVbmt4Ie0V0lcPYQYAaAdwO5EaAd940ngweHBxUQGAblgwAGC/CfBNoH0A AgE14F5SZQDwS30AMYBwHoBcdgiQd3prC4Bka0CC8gTwB0Bl5jklQILyemsOUA4AcSL3PYKExQIQ bwVCFyES8ljABm0LUVjAIEM6XFz1VwBvTuFtTzADEAeQh3AmTQ3gA2BzbwGAIE/XASAN4IJAXIkm RQDAAxD6LktwdIAgFxB4cDUhZ3L2eAFAgVFuMdAa8IrETjSeY35xEwIAgAWQbHZBof9G0A5wNeCN UgGQACCN4oNB/31BAcGNURbgD3AAAEbQDND5AZAgLn3EjWaEsY4RTnD/eMCOf4+PkJ8PwEbQBYGS P9uTT5RfbGtARtBskf+Wv32XxSmQzCVAlZ+af5e0YvwgKAKRm5+Nk1lQmU+eD/+fH6AvjcBjEKFy jk+i36Pv/5DMKAChf6b/qA+pH43AeAD/pf+rj6yfraQK+QMweC95PxV6zXt/oCwF0HIuIGNLMAtg amk6CoYBkSD6eQhgIEZQNRGzAbgSijL4ICB0FuAFQAKQPZAW0H9OkAkRYcEFoTUgMcAIYGx/NSAF oAIwC3EKhblSE4BF12fQfVEGYHEKUG6JYAewdX0gYgSQIABwNSC8aEbdC2BnBCCBwblkcAkRApC/ ttAFkE5QE3HAAX+gcwqFr7Jksy+0PwVAe4rSaQIg/b3wbAkAg8C8U7tiA2DE0PG90XRvIE7xwkBt MLhA2nm9UGgDYAMAehOAA/BvuXC8UwPhjOBoApC2wEi/wiC7UAORuXAEAMAxIEtxfGU/ubFX0MVp ApC2gCD6V7mBJ8UUwIKI4LrhDnD/TyALgIHCWLDEgwQgvKS9lP+2gL4CvojKAMjCA/DE0MUufxdw fQAHkMUTE3HM6coAQvxUV7aAuvXH6D1wCxFtkf8TgEaivFNnwX1RD0E94M64f70Fzha/M2HixrC/ 0soASfPMYNG0dHfGMNSmCYC4kvxHc4bguEALYGfQy6GI0uvUkraAScmyJwVAfsI9cIfI0bgRBcBz dWdnB5C3xHPP88TDIL0gDeBrxqvfzUO2wAhRuzG4EmdN4geAv9sx4SELgLThDnDShCC3Wmvi/7fh VJdhawQgswFB7GR2AHCJYCHij+Zv5yb/bZAPcMEfwi/DP+cP7H+3tP8CkOiW7kfpFWdwsGLpj+qf /wABZ8AEAAmAfhJOULlwAFBFfiFkAkBtNjR1oDWOOC/wDpAS8mJrbeTAOa+CIF99gAMQWKFhffQ+ PgKQQQqx1bEDYck0vbxid7sAMaDMQ8RVM8xB/+7v7//xD/If8y/0NPYQ9hI1cUBhAYAtxtA9sHIt sw3wD1FlLb8QhuAtCfDnl2GJYH0ycy1pcNRBBCD/E1AFQL3ACfC7Ug3QBIEJgP+2wOSAwQj8X/1v /nIV8MRP/8Vfxm/HfwNPBF8FbM2hTkDfveHJcL/SuEC7kHTMEL3z79VzBxK5kRbgcIKwNWC4g/e8 Yk3Q4XFk3RA7kQqPC58fBWz3kInQTyC6oG1tdf+v8IPgBnO9wNlQAgLT5b4C/wd5bZDJcIBh4AHl pe5X9JZngVH1aeiWfQAbQBtwAAAAAwAQEAAAAAADABEQAQAAAAMAgBD/////QAAHMABITfOka78B QAAIMABITfOka78BCwAAgAggBgAAAAAAwAAAAAAAAEYAAAAAA4UAAAAAAAADAAKACCAGAAAAAADA AAAAAAAARgAAAAAQhQAAAAAAAAMABYAIIAYAAAAAAMAAAAAAAABGAAAAAFKFAAC3DQAAHgAlgAgg BgAAAAAAwAAAAAAAAEYAAAAAVIUAAAEAAAAEAAAAOC4wAAMAJoAIIAYAAAAAAMAAAAAAAABGAAAA AAGFAAAAAAAACwAvgAggBgAAAAAAwAAAAAAAAEYAAAAADoUAAAAAAAADADCACCAGAAAAAADAAAAA AAAARgAAAAARhQAAAAAAAAMAMoAIIAYAAAAAAMAAAAAAAABGAAAAABiFAAAAAAAAHgBBgAggBgAA AAAAwAAAAAAAAEYAAAAANoUAAAEAAAABAAAAAAAAAB4AQoAIIAYAAAAAAMAAAAAAAABGAAAAADeF AAABAAAAAQAAAAAAAAAeAEOACCAGAAAAAADAAAAAAAAARgAAAAA4hQAAAQAAAAEAAAAAAAAAHgA9 AAEAAAAFAAAAUkU6IAAAAAADAA00/TcAACOA ------ =_NextPart_000_01BF6BD6.210F7DE0-- From owner-gsmp@psyton.com Mon Jan 31 19:10:21 2000 Received: from nighthawk.psyton.com (IDENT:root@psyton.ne.mediaone.net [24.128.29.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18745 for ; Mon, 31 Jan 2000 19:10:17 -0500 (EST) Received: (from majordomo@localhost) by nighthawk.psyton.com (8.9.0/8.9.0) id SAA01961 for gsmp-list; Mon, 31 Jan 2000 18:40:05 -0500 Received: from hue.jadn.com (IDENT:root@r82aap002309.sbo-arl.ma.cable.rcn.com [146.115.124.109]) by nighthawk.psyton.com (8.9.0/8.9.0) with ESMTP id SAA01948 for ; Mon, 31 Jan 2000 18:39:59 -0500 Received: from cplane.com (IDENT:qmailr@[63.193.105.226]) by hue.jadn.com (8.9.3/8.9.3) with SMTP id NAA17278 for ; Mon, 31 Jan 2000 13:55:14 -0500 Received: (qmail 25677 invoked from network); 31 Jan 2000 18:40:40 -0000 Received: from unknown (HELO texas.cplane.com) (unknown) by unknown with SMTP; 31 Jan 2000 18:40:40 -0000 Received: (qmail 12554 invoked from network); 31 Jan 2000 18:54:31 -0000 Received: from unknown (HELO texas.cplane.com) (unknown) by unknown with SMTP; 31 Jan 2000 18:54:31 -0000 Date: Mon, 31 Jan 2000 10:54:31 -0800 (PST) From: Balaji Srinivasan To: "'gsmp@psyton.com'" Subject: RE: GSMPv3 review In-Reply-To: <01BF6BD6.21065620@simon.future.futsoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-gsmp@psyton.com Precedence: bulk Reply-To: gsmp@psyton.com > hi, Mr. balaji: > you said in you mail that each Port Record should contain > the Event Sequence Number and the Event Flags for that port because > this section allows the controller to rapidly synchronize with the > switch. How can this be done? To controller, What's the use of shuch > information as Event Number, and Event Flag? How will the controller > process these information? BTW, should the switch hardware keep the > event flag and Event Sequenct Number for every port? If these two are > keeped in Gsmp slave's software, I don't know how your suggestion will > allow quickly synchronization. Could you give me some instruction? The reason we want each port record to contain the event sequence number and the event flags is so that the controller knows which events it has missed in the time during which the communication to the switch was down. In the current GSMP spec since this information is not included the controller on noticing that the port session number has changed has to issue a port management pdu to find out what the event flags are and then maybe another to reset the flags. Since this has to be done for each port that the port session number has changed it becomes problematic if another event happens in the meantime. The slave anyway is required to keep this information I hope this clears some of the confusion. Please let me know if i can clarify it further thanks blalaji