2.3.3 Frame Relay Service MIB (frnetmib)

NOTE: This charter is a snapshot of the 44th IETF Meeting in Minneapolis, Minnesota. It may now be out-of-date. Last Modified: 06-Jan-99


Andy Malis <malis@ascend.com>

Internet Area Director(s):

Jeffrey Burgan <burgan@corp.home.net>
Thomas Narten <narten@raleigh.ibm.com>

Internet Area Advisor:

Jeffrey Burgan <burgan@corp.home.net>

Technical Advisor(s):

Fred Baker <fred@cisco.com>

Mailing Lists:

General Discussion:frnetmib@sunroof.eng.sun.com
To Subscribe: majordomo@sunroof.eng.sun.com
In Body: subscribe frnetmib
Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/

Description of Working Group:

The Frame Relay Service MIB Working Group is chartered to define an initial 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 and the ATM MIB Working Group.

The working group is chartered to complete four tasks:

a) consider revisions to the existing 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.

In all cases, the working group will keep the Frame Relay and ATM Forums informed of its progress and will actively solicit input from those Fora.

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:



Post the initial Internet-Draft for discussion.



Submit the Frame Relay Service MIB to the IESG for consideration as a Proposed Standard.

Apr 96


Solicit implementation experience for the IWF and SVC cases and 'requirements' for IWF and SVC cases/

Apr 96


Post summary of SVC requirements, issues, and a basic proposal for the structure of the SVC instrumentation.

May 96


Post first draft of RFC1604 update as an Intenet-Draft.

May 96


Post IWF MIB document and SVC MIB document as Internet-Drafts.

Jun 96


Post revised version of RFC1604 update Internet-Draft.

Jun 96


Meet at Montreal IETF to review RFC1604 update document and develop recommendation on advancement.

Jul 96


Submit final version of RFC1604 Internet-Draft to Area Director, requesting Directorate review.

Jul 96


Post revisions of IWF MIB and SVC MIB as Internet-Drafts.

Sep 96


WG Last Call for IWF MIB and SVC MIB.

Sep 96


Submit IWF MIB and SVC MIB Internet-Drafts to Area Director for referral to Directorate.


Request For Comments:







Definitions of Managed Objects for Frame Relay Service

Current Meeting Report

Frame Relay Service MIB (frnetmib) Working Group Minutes
IETF-44, Minneapolis (March 15-19, 1999)

Date: Tuesday, March 16, 1015-1115

Chair: Andrew Malis, Ascend Communications, malis@ascend.com

Minutes recorded by Andrew Malis

Mailing List Information:
Discussion: frnetmib@sunroof.eng.sun.com
E-Mail-Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/
(un)subscribe requests to: majordomo@sunroof.eng.sun.com


1. Administrivia, current documents status

2. Definitions of Managed Objects for Frame Relay Service
- draft-ietf-frnetmib-frs-mib-04.txt

3. Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function
- draft-ietf-frnetmib-atmiwf-01.txt

4. Open discussion

Agenda Item 1: Administrivia, current document status

Andy Malis 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:

- Definitions of Managed Objects for Frame Relay Service, Ken Rehbehn, Dave Fowler
- We heard about this draft later in the meeting.

- Frame Relay Switched PVC MIB, Bill Coutts
- This was forwarded to IESG for publication as Proposed Standard RFC, and last week comments were returned from the IESG. Bill will update the draft based upon the comments.

- 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.

- Don Cochrane
- Don had indicated that he was still interested in pursuing this draft. Andy will contact him to determine his current intentions.

draft-ietf-frnetmib-dcp-02.txt, Moji Kashef, Jaime Colom
- Rob Steinberger will contact Jaime to determine his intentions.

Agenda Item 2: Definitions of Managed Objects for Frame Relay Service, draft-ietf-frnetmib-frs-mib-04.txt

Ken Rehbehn presented the changes since the last meeting. He updated the boilerplate, added fragmentation objects, changed notification prefix for SMIv1 compiles, removed text citing service level agreements, and got a clean compile with smicng.

He plans to revise the MIB based upon comments he has received from Bert Wijnen, including apply to both this MIB and the SPVC MIB.

Agenda Item 3: Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function, draft-ietf-frnetmib-atmiwf-01.txt

Ken Rehbehn also presented this MIB. He began by describing the MIB's structure. During the structure discussion, some open issues came up that Ken had also listed later in his presentation. Changes from the previous version included boilerplate, additional connection indices and descriptors, changed TimeTicks to TimeStamp, updated the compliance statement, updated to SMIv2, and compiled cleanly with smicng.

There are still a number of open issues, including the relationships with other MIBs, saving the last failed translation packet header, security boilerplate, connection entry DESCRIPTION text needs to clarify system behavior, "Big Picture" descriptive text is needed, it needs text describing creation/destruction of IWF connections or components, explicit point-to-multipoint text is needed (both when supported and when not), and an IANA MIB leaf is required.

David Perkins asked if there extra objects in the frAtmIwfConnStatusChange notification. Ken will update the notification based upon the discussion. Rob Steinberger suggested that Ken remove the comment that this will lead to an SVC MIB, which Ken will do.

Ken's plan is to continue to work with Orly Nicklass and put out a new draft in the May time frame. Randy Presuhn asked about the MIB's persistance characteristics over reboots - will table entries remain over device reboots? This was discused in the meeting, but no conclusions were reached. This will be further discussed on the list.

Agenda Item 4: Open Discussion

Rob and Orly are going to think about working on an SLA MIB based on FRF.13.

No additional items were brought up, and the group adjourned.


Frame Relay Service MIB Working Group Agenda
Atmiwf Draft
Frs Draft