NOTE: This charter is a snapshot of the 49th IETF Meeting in San Diego, California. It may now be out-of-date. Last Modified: 17-Oct-00
Chair(s):
Andy Malis <Andy.Malis@vivacenetworks.com>
Internet Area Director(s):
Thomas Narten <narten@raleigh.ibm.com>
Erik Nordmark <nordmark@eng.sun.com>
Internet Area Advisor:
Erik Nordmark <nordmark@eng.sun.com>
Technical Advisor(s):
David Perkins <dperkins@dsperkins.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 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 Intenet-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-Drafts to Area Director for referral to Directorate. |
Done |
|
WG last call on IWF MIB, submit Internet Draft to IESG for publication. |
Done |
|
Post revised version of SLD draft. |
Done |
|
WG last call on SLD MIB, submit Internet Draft to IESG for publication. |
Internet-Drafts:
· Definitions of Managed Objects for Frame Relay Service Level Definitions
· Definitions of Managed Objects for Circuit to Interface Translation
Request For Comments:
RFC |
Status |
Title |
RFC2954 |
PS |
Definitions of Managed Objects for Frame Relay Service |
RFC2955 |
PS |
Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function |
Frame Relay Service MIB WG (frnetmib) Minutes
Chair: Andy Malis <Andy.Malis@vivacenetworks.com>
Guest Chair: Ken Rehbehn <krehbehn@megisto.com>
The frnetmib working group met Tuesday, December 12, 2000 from 1700 to 1800.
AGENDA:
1. Administrivia, current WG status
- The following working group documents have been published as RFCs:
RFC 2954, Definitions of Managed Objects for Frame Relay Service
RFC 2955, Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function
RFC 3020, Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function
- The working group expects to go into maintenance mode (i.e. just be the email list) once the two on-going working group documents (frmrelay-service and frsi MIBs) are complete.
2. Ken Rehbehn, quick overview of the final revisions to RFC 3020 (was draft-ietf-frnetmib-mfrmib-04.txt), Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function
Ken presented the major changes to the MFR MIB resulting from the IESG review prior to publication. The main changes were:
o A variety of clarifications regarding MIB operation
o Changed location from experimental to under mib-2 transmission
o Added ranges and descriptions of the meaning of a value -1
o Changed descriptors starting with "bundleXxxx" to "mfrBundleXxx"
o Eliminated intermediate nodes mfrMibScalarObjects, mfrMibBundleObjects and mfrMibBundleLinkObjects
3. Rob Steinberger and Orly Nicklass, draft-ietf-frnetmib-frmrelay-service-02.txt, Definitions of Managed Objects for Frame Relay Service Level Definitions (FRF.13)
Rob reviewed the changes made since the conclusion of the Working Group Last Call and the Pittsburgh meeting. The major changes included the removal of the free running counters, the merger of the availability and data tables, the use of a consistent prefix for the MIB object names, and new ASCII figures.
An additional clarification will be provided in the next version of the MIB (.03) to replace Section 3.6.2. The new text describes 2 half-duplex flows evaluated with a total of 4 reference points. Randy Presuhn recommended use of the term "uni-directional" instead of half-duplex to characterize the flow. The new draft will be published in the next several weeks.
The working group consensus is to forward the draft to IETF Last Call following a short review period for the new changes.
4. Rob Steinberger and Orly Nicklass, Rob Steinberger and Orly Nicklass, draft-ietf-frnetmib-frsi-00.txt, Frame Relay Circuit Interface MIB
This MIB provides the ability to generate ifEntries for frame circuits.
The motivation is that neither RFC 2115 nor RFC 1604 create ifEntries for DLCIs. RMON requires an ifIndex to monitor a data source, so the RMON WG requested that we do this work during the Adelaide meeting.
In addition, routing MIBs (such as the CIDR Routing Table and Net to Media table) require ifIndex to control routing. Without it, you cannot control or display the routing to or on virtual circuits in a non-proprietary manner. There is not a need to create ifIndex for every circuit, but it would be nice to have one for the interesting circuits.
Rob described recent changes to the MIB. Frame relay specific terms were changed to allow application of the MIB to ATM connections. A specific ATM example was added to the MIB to illustrate usage in an ATM application. Rob will obtain new ifType codepoints from IANA for both frame relay and ATM connections. He will then publish the updated MIB. The consensus of the working group is that Working Group Last Call should begin when the updated MIB is available.
4. Open discussion
There being none, the group adjourned.
Circuit Interfaces
Agenda
MFR MIB Changes from IESG Review
'draft-ietf-frnetmib-frmrelay-service-02'