From owner-frnetmib@sunroof.eng.sun.com Fri Jul 2 05:35:07 1999 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01126; Fri, 2 Jul 1999 05:35:07 -0400 (EDT) Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA12355; Fri, 2 Jul 1999 02:35:01 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id CAA05377; Fri, 2 Jul 1999 02:35:00 -0700 (PDT) Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id CAA04381 for frnetmib-dist; Fri, 2 Jul 1999 02:34:42 -0700 (PDT) Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13]) by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA04374 for ; Fri, 2 Jul 1999 02:34:35 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id CAA05300 for ; Fri, 2 Jul 1999 02:34:33 -0700 (PDT) Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA15907 for ; Fri, 2 Jul 1999 02:34:33 -0700 (PDT) Received: from fw-ext.ascend.com (fw-ext [198.4.92.5]) by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id CAA29692; Fri, 2 Jul 1999 02:30:29 -0700 (PDT) Received: from russet.ascend.com by fw-ext.ascend.com via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 2 Jul 1999 09:34:32 UT Received: from spud.ascend.com (spud [192.207.23.51]) by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id CAA12965; Fri, 2 Jul 1999 02:34:28 -0700 (PDT) Received: from amalis ([134.112.245.86]) by spud.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id CAA06318; Fri, 2 Jul 1999 02:34:26 -0700 (PDT) Message-Id: <4.2.0.56.19990702051443.02648770@alpo.casc.com> X-Sender: amalis@alpo.casc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta) Date: Fri, 02 Jul 1999 05:16:06 -0400 To: agenda@ietf.org, frnetmib@sunroof.eng.sun.com From: "Andrew G. Malis" Subject: (FRNETMIB) frnetmib agenda for Oslo Cc: "Andrew G. Malis" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ Frame Relay Service MIB WG (frnetmib) Tuesday, July 13, 1700 - 1800 ============================= Chair: Andy Malis AGENDA: 1. Administrivia, current documents status 2. Ken Rehbehn and Orly Nicklass, draft-ietf-frnetmib-atmiwf-02.txt, Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function 3. Rob Steinberger and Orly Nicklass, draft-steinberger-frmrelay- service-00.txt, Definitions of Managed Objects for Frame Relay Service Level Definitions 4. Open discussion X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Thu Jul 8 19:15:50 1999 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19907; Thu, 8 Jul 1999 19:15:48 -0400 (EDT) Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA06844; Thu, 8 Jul 1999 16:15:47 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA11194; Thu, 8 Jul 1999 16:15:46 -0700 (PDT) Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id QAA11056 for frnetmib-dist; Thu, 8 Jul 1999 16:15:10 -0700 (PDT) Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13]) by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA11049 for ; Thu, 8 Jul 1999 16:15:05 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA03695 for ; Thu, 8 Jul 1999 16:15:04 -0700 (PDT) Received: from mail.visualnetworks.com ([208.22.72.43]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id QAA11972 for ; Thu, 8 Jul 1999 16:15:03 -0700 (PDT) Received: from shemp by mail.visualnetworks.com via smtpd (for venus.Sun.COM [192.9.25.5]) with SMTP; 8 Jul 1999 23:23:27 UT Received: by shemp.visualnetworks.com with Internet Mail Service (5.5.2448.0) id <3FDB6JL9>; Thu, 8 Jul 1999 19:21:23 -0400 Message-ID: <0F9AE864A5ECD011B3100060977F354A012D00EC@shemp.visualnetworks.com> From: "Rehbehn, Kenneth" To: "'atommib@research.telcordia.com'" , "'frnetmib@sunroof.eng.sun.com'" Subject: (FRNETMIB) ATM and Frame Relay Cross Connections Date: Thu, 8 Jul 1999 19:21:16 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ A draft of the Frame Relay/ATM IWF MIB is now available. In the course of designing the IWF MIB it became clear that the cross-connect paradigms of the ATM MIB and Frame Relay Service MIBs do not extend adequately to support the case of the interworking function. The authors of the Frame Relay/ATM IWF MIB and the ATM MIB have come up with two approaches to extending these MIBs. We want the working groups to settle on an approach so that the FR/ATM MIB can be completed. The FR/ATM IWF MIB can be found at: http://www.ietf.org/internet-drafts/draft-ietf-frnetmib-atmiwf-02.txt What do folks think: Option 1 or Option 2? Thanks, Ken Rehbehn = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = OPTION 1 - Generic IWF Support In this approach, the ATM and Frame Relay (Service) MIBs are changed to indicate an interworked connection. The exact type of IWF is identified with the OID of the IWF MIB that applies to the connection. In the case of the frame relay to ATM PVC Service IWF it would be frAtmIwfMIB { experimental 97 }. This approach is used to enable addition of new IWF types: CES and transparent LAN bridges. The advantage of this approach is that new IWF MIBs do not impact the ATM MIB. RFC 2514, the ATM Textual Conventions, would be modified to extend the AtmConnKind TC to add a new enumeration: genericIWF(6) ATM virtual link of a PVC cross-connected to a non-ATM virtual link (e.g. Frame Relay Service Interworking Function). The specific IWF is identified by an associated object containing the OID of the IWF MIB. In the case of the VC link table, the IWF MIB is identified in atmVclIwfOID. RFC 2515, the ATM MIB, would be modified to add the following new object to the atmVclTable: atmVclIwfOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The OID of the cross-connect MIB controlling this connection (e.g. frAtmIwfMIB in the case of the Frame Relay/ATM PVC Service Interworking MIB). This object is set to a non-zero value when the atmVclConnKind object is set to genericIWF(6)." DEFVAL { 0 } ::= {atmVclEntry 15} RFC 1604, the Frame Relay Service MIB, would be modified to add the following new object to the PVC Endpoint table: frPVCEndptIwfOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The OID of the cross-connect MIB controlling this connection (e.g. frAtmIwfMIB in the case of the Frame Relay/ATM PVC Service Interworking MIB). This object is set to a non-zero value when the PVC is interconnected to an IWF. This object is set to zero when the endpoint is connected to another FR PVC endpoint." DEFVAL { 0 } ::= { frPVCEndptEntry 31 } = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = OPTION 2 - Enumerated Types In this option, an enumerated type is used to flag a particular IWF cross connection. Each new IWF supported requires a new spin of the ATM Textual Conventions. RFC 2514, the ATM Textual Conventions, would be modified to extend the AtmConnKind TC to add a new enumeration: frServiceIWF(6) Virtual link at the PVC side of an Frame Relay/ATM Service PVC IWF crossconnect. RFC 1604, the Frame Relay Service MIB, would be modified to add the following new object to the PVC Endpoint table: frPVCEndptIwf OBJECT-TYPE SYNTAX INTEGER { none(1), frAtmService(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The Frame Relay PVC endpoint cross-connect type. none(1) Frame relay PVC endpoint is cross- connected via the frPVCConnectTable. frAtmService(2) Frame relay PVC endpoint is cross- connected via the FR/ATM Service IWF." DEFVAL { none } ::= { frPVCEndptEntry 31 } X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Wed Jul 14 06:18:02 1999 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02840; Wed, 14 Jul 1999 06:18:01 -0400 (EDT) Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA10255; Wed, 14 Jul 1999 03:18:00 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id DAA27472; Wed, 14 Jul 1999 03:17:58 -0700 (PDT) Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id DAA15694 for frnetmib-dist; Wed, 14 Jul 1999 03:17:43 -0700 (PDT) Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25]) by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA15686 for ; Wed, 14 Jul 1999 03:17:31 -0700 (PDT) Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31]) by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id DAA27931; Wed, 14 Jul 1999 03:17:30 -0700 (PDT) Received: from foo.ietf.uninett.no (foo.ietf.uninett.no [128.39.10.31]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA06980; Wed, 14 Jul 1999 04:17:29 -0600 (MDT) Received: from wistatic1065 (wlstatic1065.ietf.uninett.no [128.39.10.65]) by foo.ietf.uninett.no (8.9.3/8.9.3) with ESMTP id MAA09733; Wed, 14 Jul 1999 12:17:18 +0200 Message-Id: <4.2.0.56.19990714060705.01f1e480@alpo.casc.com> X-Sender: amalis@alpo.casc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta) Date: Wed, 14 Jul 1999 06:08:27 -0400 To: frnetmib@sunroof.eng.sun.com From: "Andrew G. Malis" Subject: (FRNETMIB) frnetmib draft minutes Cc: "Andrew G. Malis" , thomas Narten , Erik Nordmark Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ Here are the draft minutes from yesterday's frnetmib meeting. Please send comments and corrections to the list. Thanks, Andy -------- Frame Relay Service MIB (frnetmib) Working Group Minutes IETF-45, Oslo Date: Tuesday, July 13, 1700 - 1800 Chair: Andrew Malis, Lucent Technologies, amalis@lucent.com Minutes recorded by Andrew Malis Mailing List Information: Discussion: frnetmib@sunroof.eng.sun.com EMail Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ (un)subscribe requests to: majordomo@sunroof.eng.sun.com Agenda: 1. Administrivia, current documents status 2. Ken Rehbehn and Orly Nicklass, draft-ietf-frnetmib-atmiwf- 02.txt, Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function 3. Rob Steinberger and Orly Nicklass, draft-steinberger-frmrelay- service-00.txt, Definitions of Managed Objects for Frame Relay Service Level Definitions 4. Open discussion Agenda Item 1: Administrivia, current document status Andy presented the agenda. There were no request for changes or additional agenda items. Following the review of the agenda, Andy presented on overview of the status of work in the frnetmib group. The following drafts are in progress: - draft-ietf-frnetmib-frs-mib-06.txt, Definitions of Managed Objects for Frame Relay Service, Ken Rehbehn, Dave Fowler This draft is in IESG review following WG last call, and has already been revised based on IESG comments. It will need another small change to support the FR/ATM IWF MIB. This was discussed later in the meeting. - draft-ietf-frnetmib-spvc-02.txt, Frame Relay Switched PVC MIB, Bill Coutts This was forwarded to IESG for publication as Proposed Standard RFC, and comments were returned from the IESG. Bill has been busy, but plans to update the draft based upon the comments. - draft-ietf-frnetmib-atmiwf-02.txt, Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking, Ken Rehbehn, Orly Nicklass, George Mouradian We heard about this draft later in the meeting. - Rob Steinberger and Orly Nicklass, draft-steinberger-frmrelay- service-00.txt, Definitions of Managed Objects for Frame Relay Service Level Definitions We heard about this draft later in the meeting. - draft-ietf-frnetmib-dte-svc-00.txt, Don Cochrane - draft-ietf-frnetmib-dcp-02.txt, Moji Kashef, Jaime Colom Andy has been in contact with the authors, and they have expressed interest in reviving these drafts. Andy also presented proposed updates to the WG's charter, goals, and milestones, since the current charter and milestones are very out of date. They were accepted by the group, and will be sent out by Andy to the frnetmib email list in a separate message. Agenda Item 2: Ken Rehbehn and Orly Nicklass, draft-ietf- frnetmib-atmiwf-02.txt, Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function Ken discussed the outstanding issues from the last meeting and the changes since then. There was only one remaining outstanding issue from the last meeting that Ken still plans to add to the MIB, ATM fault code and location objects. Outstanding issues to be resolved: - Polish descriptive text - Alter MIB name to reflect experimental status - Prepare draft for technical advisor review - Address cross connection model changes for ATM MIB and FRS MIB Ken reviewed the cross-connection model, and discussed possible changes to the ATM and FRS MIB to accommodate the IWF MIB. He presented two options for changes to the ATM and FRS MIB models (these had already been presented on the email list as well). The WG reached consensus on Ken's first proposed model. Andy will take the action of discussing the AtoM MIB changes with the chair of the AtoM MIB WG and the Internet and Management Area Directors. The group also agreed upon a similar change to the Frame Relay Service MIB. Agenda Item 3: Rob Steinberger and Orly Nicklass, draft- steinberger-frmrelay-service-00.txt, Definitions of Managed Objects for Frame Relay Service Level Definitions Rob presented an overview of the SLD MIB, which is based on FRF.13 from the Frame Relay Forum (Frame Relay Service Level Definitions), and uses the model and reference points defined in that document. Ken noted that there is a somewhat similar MIB, draft-white- slapm-mib-04.txt. He suggested that we study it and decide whether we should be doing something on our own, or should do work in conjunction with that MIB. We noted that it was an individual submission, and it was unclear to us which (if any) WG is considering or working on it. Opportunities for synergy will be investigated. Rob and Orly will continue work on the MIB. Comments to the list are invited. Agenda Item 4: Open Discussion No additional items were brought up, and the group adjourned. ________________________________________________________________________ Andrew G. Malis amalis@lucent.com phone:978 952-7414 fax:978 392-2074 Lucent Technologies 1 Robbins Road Westford, MA 01886 X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Wed Jul 14 06:18:07 1999 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02853; Wed, 14 Jul 1999 06:18:06 -0400 (EDT) Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA10279; Wed, 14 Jul 1999 03:18:06 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id DAA27966; Wed, 14 Jul 1999 03:18:06 -0700 (PDT) Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id DAA15704 for frnetmib-dist; Wed, 14 Jul 1999 03:17:55 -0700 (PDT) Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25]) by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA15687 for ; Wed, 14 Jul 1999 03:17:31 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id DAA27933; Wed, 14 Jul 1999 03:17:31 -0700 (PDT) Received: from foo.ietf.uninett.no (foo.ietf.uninett.no [128.39.10.31]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA00899; Wed, 14 Jul 1999 03:17:29 -0700 (PDT) Received: from wistatic1065 (wlstatic1065.ietf.uninett.no [128.39.10.65]) by foo.ietf.uninett.no (8.9.3/8.9.3) with ESMTP id MAA09737; Wed, 14 Jul 1999 12:17:18 +0200 Message-Id: <4.2.0.56.19990714060923.01f1d2c0@alpo.casc.com> X-Sender: amalis@alpo.casc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta) Date: Wed, 14 Jul 1999 06:17:21 -0400 To: frnetmib@sunroof.eng.sun.com From: "Andrew G. Malis" Subject: (FRNETMIB) Proposed revised frnetmib charter and milestones Cc: "Andrew G. Malis" , Thomas Narten , Erik Nordmark Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ At yesterday's frnetmib meeting, I presented proposed updates to the charter and milestones, and I'm also sending them out to the email list for your information and comments. Please send any comments back to the list. The final revisions will be sent to the ADs for their approval, and then put on the WG's charter web page. Thanks, Andy ------- Description of Working Group: The Frame Relay Service MIB Working Group is chartered to define a set of managed objects which will be useful for customer network management of a provider's Frame Relay Service. The working group will consider existing definitions, including the Frame Relay Forum's work in this area. The objects defined by the working group will be consistent with the SNMP framework. The working group will coordinate with both the Frame Relay Forum, the ATM MIB Working Group, and other relevant groups. The working group is chartered to complete four tasks: a) consider revisions to the FRS MIB (currently published as a Proposed Standard in RFC 1604) in light of implementation experience, changes to the interface MIBs (e.g. IF-MIB, DS1-MIB, DS3-MIB, FR-DTE-MIB, creation of the DS0 and DS0 Bundle MIB modules), and evolution of the relevant non-IETF standards, b) prepare a Recommendation to the Area Director as to the appropriate disposition of the (updated) FRS MIB, i.e. that it be advanced to Draft Standard status or that it cycle at Proposed Status, c) develop a set of managed objects to provide the instrumentation required to manage switched-virtual circuits in a frame-relay environment. d) develop a set of managed objects to provide the instrumentation required to manage connections that terminate on a mixture of ATM and Frame Relay interfaces, i.e. interworked connections. These objects will be the minimum necessary to provide the ability to monitor and control interworked connections and shall use existing definitions (e.g. IF-MIB, FRS-MIB, ATM-MIB, etc.) to instrument the interfaces and the "native" parts of the connections. e) develop a set of managed object for the management of Frame Relay Service Level Definitions. f) consider other closely related future work items. In all cases, the working group will keep the Frame Relay and ATM Forums and the ATM MIB WG informed of its progress and will actively solicit their input. All output of the group will be consistent with the existing SNMPv2c framework and standards, including the SNMPv2c Structure of Management Information (SMI). Goals and Milestones: Done Post the initial Internet-Draft for discussion. Done Submit the Frame Relay Service MIB to the IESG for consideration as a Proposed Standard. Done Solicit implementation experience for the IWF and SVC cases and 'requirements' for IWF and SVC cases. Done Post summary of SVC requirements, issues, and a basic proposal for the structure of the SVC instrumentation. Done Post first draft of RFC1604 update as an Internet-Draft. Done Post IWF MIB document and SVC MIB document as Internet-Drafts. Done Post revised version of RFC1604 update Internet-Draft. Done Meet at Montreal IETF to review RFC1604 update document and develop recommendation on advancement. Done Submit final version of RFC1604 Internet-Draft to Area Director, requesting Directorate review. Done Post revisions of IWF MIB and SVC MIB as Internet-Drafts. Done WG Last Call for SVC MIB. Done Submit SVC MIB Internet-Draft to Area Director for referral to Directorate. July 99 Discuss updated version of IWF MIB. July 99 Discuss initial draft of managed objects for FR SLDs. Sept 99 WG last call on IWF MIB, submit Internet-Draft to Area Director for referral to Directorate. Sept 99 Post revised version of SLD draft. Nov 99 Discuss SLD draft Dec 99 WG last call on SLD MIB, submit Internet-Draft to Area Director for referral to Directorate. ________________________________________________________________________ Andrew G. Malis amalis@lucent.com phone:978 952-7414 fax:978 392-2074 Lucent Technologies 1 Robbins Road Westford, MA 01886 X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Fri Jul 23 08:41:01 1999 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01869; Fri, 23 Jul 1999 08:41:01 -0400 (EDT) Received: from engmail1.Eng.Sun.COM ([129.146.1.13]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA16964; Fri, 23 Jul 1999 05:40:52 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id FAA24550; Fri, 23 Jul 1999 05:40:51 -0700 (PDT) Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id FAA04285 for frnetmib-dist; Fri, 23 Jul 1999 05:40:38 -0700 (PDT) Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6]) by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA04278 for ; Fri, 23 Jul 1999 05:40:33 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id FAA21380 for ; Fri, 23 Jul 1999 05:40:31 -0700 (PDT) Received: from services.paradyne.com (services.paradyne.com [135.90.253.90]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA02970 for ; Fri, 23 Jul 1999 05:40:31 -0700 (PDT) Received: from hermes.eng.paradyne.com ([135.26.1.14]) by services.paradyne.com (Netscape Messaging Server 3.6) with ESMTP id AAA32AF; Fri, 23 Jul 1999 08:40:21 -0400 Received: from eng.paradyne.com (graysnapper.eng.paradyne.com [135.26.4.16]) by hermes.eng.paradyne.com (8.7.5/8.7.3) with ESMTP id IAA16124; Fri, 23 Jul 1999 08:40:20 -0400 (EDT) Message-ID: <379862B7.85F7F854@eng.paradyne.com> Date: Fri, 23 Jul 1999 08:40:23 -0400 From: Rob Steinberger Organization: Paradyne Corporation X-Mailer: Mozilla 4.61 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Frame Services MIB CC: Orly Nicklass Subject: (FRNETMIB) Service Level Definition MIB Issues Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ Content-Transfer-Encoding: 7bit The following are the issues concerning the Service Level Definitions MIB pointed out during the Oslo meeting and by various people since the draft was published. 1. There are several typos in the document that need to be corrected. RESOLUTION: This will be taken care of in the next version of the draft. 2. It was pointed out that draft-white-slapm-mib-04.txt contains similar information. RESOLUTION: This MIB pertains to TCP/IP policy monitoring. We did not see a strong correlation between what is in this MIB and what we want in the SLD MIB. However, there are some conceptual ideas that we will borrow from the MIB. 3. Behaviors of MIB row objects and relations to other Frame Relay tables are not explained in the text. RESOLUTION: This information will be expanded to include behaviors for DLCI delete, and other status changes as well as further information concerning relation to RFC 2115 and RFC 1604. 4. There can only be one sample group per PVC. RESOLUTION: We will separate all of the sample controls into a different table. This will allow us to control more than one sampling group per PVC. 5. Using sample packets instead of sample period for the data sample table is a bit funny. RESOLUTION: Will switch to sample period. 6. The network delay information should be reported in microseconds instead of milliseconds to ensure future use of MIB. RESOLUTION: This will be changed. These problems will be addressed in the next version of the draft. Thanks for any comments. Rob Steinberger X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Fri Jul 23 10:11:28 1999 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06713; Fri, 23 Jul 1999 10:11:28 -0400 (EDT) Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA12344; Fri, 23 Jul 1999 07:11:25 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id HAA03454; Fri, 23 Jul 1999 07:11:21 -0700 (PDT) Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id HAA04363 for frnetmib-dist; Fri, 23 Jul 1999 07:11:06 -0700 (PDT) Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5]) by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA04356 for ; Fri, 23 Jul 1999 07:10:58 -0700 (PDT) Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31]) by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id HAA24864 for ; Fri, 23 Jul 1999 07:10:57 -0700 (PDT) Received: from alpo.casc.com (alpo.casc.com [152.148.10.6]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA01584 for ; Fri, 23 Jul 1999 08:10:56 -0600 (MDT) Received: from amalis (amalis [152.148.13.74]) by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id KAA26208; Fri, 23 Jul 1999 10:10:01 -0400 (EDT) Message-Id: <4.2.0.58.19990723100756.0468eee0@alpo.casc.com> X-Sender: amalis@alpo.casc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 23 Jul 1999 10:09:39 -0400 To: minutes@ietf.org, frnetmib@sunroof.eng.sun.com From: "Andrew G. Malis" Subject: (FRNETMIB) Final frnetmib minutes from Oslo Cc: "Andrew G. Malis" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ Frame Relay Service MIB (frnetmib) Working Group Minutes IETF-45, Oslo Date: Tuesday, July 13, 1700 - 1800 Chair: Andrew Malis, Lucent Technologies, amalis@lucent.com Minutes recorded by Andrew Malis Mailing List Information: Discussion: frnetmib@sunroof.eng.sun.com EMail Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ (un)subscribe requests to: majordomo@sunroof.eng.sun.com Agenda: 1. Administrivia, current documents status 2. Ken Rehbehn and Orly Nicklass, draft-ietf-frnetmib-atmiwf- 02.txt, Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function 3. Rob Steinberger and Orly Nicklass, draft-steinberger-frmrelay- service-00.txt, Definitions of Managed Objects for Frame Relay Service Level Definitions 4. Open discussion Agenda Item 1: Administrivia, current document status Andy presented the agenda. There were no request for changes or additional agenda items. Following the review of the agenda, Andy presented on overview of the status of work in the frnetmib group. The following drafts are in progress: - draft-ietf-frnetmib-frs-mib-06.txt, Definitions of Managed Objects for Frame Relay Service, Ken Rehbehn, Dave Fowler This draft is in IESG review following WG last call, and has already been revised based on IESG comments. It will need another small change to support the FR/ATM IWF MIB. This was discussed later in the meeting. - draft-ietf-frnetmib-spvc-02.txt, Frame Relay Switched PVC MIB, Bill Coutts This was forwarded to IESG for publication as Proposed Standard RFC, and comments were returned from the IESG. Bill has been busy, but plans to update the draft based upon the comments. - draft-ietf-frnetmib-atmiwf-02.txt, Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking, Ken Rehbehn, Orly Nicklass, George Mouradian We heard about this draft later in the meeting. - Rob Steinberger and Orly Nicklass, draft-steinberger-frmrelay- service-00.txt, Definitions of Managed Objects for Frame Relay Service Level Definitions We heard about this draft later in the meeting. - draft-ietf-frnetmib-dte-svc-00.txt, Don Cochrane - draft-ietf-frnetmib-dcp-02.txt, Moji Kashef, Jaime Colom Andy has been in contact with the authors, and they have expressed interest in reviving these drafts. Andy also presented proposed updates to the WG's charter, goals, and milestones, since the current charter and milestones are very out of date. They were accepted by the group, and will be sent out by Andy to the frnetmib email list in a separate message. Agenda Item 2: Ken Rehbehn and Orly Nicklass, draft-ietf- frnetmib-atmiwf-02.txt, Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function Ken discussed the outstanding issues from the last meeting and the changes since then. There was only one remaining outstanding issue from the last meeting that Ken still plans to add to the MIB, ATM fault code and location objects. Outstanding issues to be resolved: - Polish descriptive text - Alter MIB name to reflect experimental status - Prepare draft for technical advisor review - Address cross connection model changes for ATM MIB and FRS MIB Ken reviewed the cross-connection model, and discussed possible changes to the ATM and FRS MIB to accommodate the IWF MIB. He presented two options for changes to the ATM and FRS MIB models (these had already been presented on the email list as well). The WG reached consensus on Ken's first proposed model. Andy will take the action of discussing the AtoM MIB changes with the chair of the AtoM MIB WG and the Internet and Management Area Directors. The group also agreed upon a similar change to the Frame Relay Service MIB. Agenda Item 3: Rob Steinberger and Orly Nicklass, draft- steinberger-frmrelay-service-00.txt, Definitions of Managed Objects for Frame Relay Service Level Definitions Rob presented an overview of the SLD MIB, which is based on FRF.13 from the Frame Relay Forum (Frame Relay Service Level Definitions), and uses the model and reference points defined in that document. Ken noted that there is a somewhat similar MIB, draft-white- slapm-mib-04.txt. He suggested that we study it and decide whether we should be doing something on our own, or should do work in conjunction with that MIB. We noted that it was an individual submission, and it was unclear to us which (if any) WG is considering or working on it. Opportunities for synergy will be investigated. Rob and Orly will continue work on the MIB. Comments to the list are invited. Agenda Item 4: Open Discussion No additional items were brought up, and the group adjourned. ________________________________________________________________________ Andrew G. Malis amalis@lucent.com phone:978 952-7414 fax:978 392-2074 Lucent Technologies 1 Robbins Road Westford, MA 01886 X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message.