INTERNET-DRAFT EXPIRATION DATE: APRIL 28 1996 Management Information Base for Frame Relay DCP DTE Extensions for Data Compression over Frame Relay draft-kashef-frmib-dte-dcp-00.txt Moji Kashef Cabletron Sys, Inc. 35E Industrial Way, 1st Floor Rochester New Hampshire, 03867 kashef@ctron.com 1. Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months. Internet-Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet-Drafts as reference material or to cite them other than as a ``working draft'' or ``work in progress.'' To learn the current status of any Internet-Draft, please check the 1id-abstracts.txt listing contained in the Internet-Drafts Shadow Directories on ds.internic.net, nic.nordu.net, ftp.nisc.sri.com, or munnari.oz.au. This draft document will be submitted to the RFC editor as an extension to the SNMP MIB. Please send comments to the authors, copying iplpdn@cnri.reston.va.us. It expires Dec 1996. 2. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP- based internets. In particular, it defines objects for managing Data Compression over a Frame Relay virtual circuit. This memo does not specify a standard for the Internet community. Kashef [Page 1] Draft Frame Relay DCP DTE Extensions MIB October 1996 3. The SNMPv2 Network Management Framework The major components of the SNMPv2 Network Management framework are described in the documents listed below. o RFC 1902 [1] defines the Structure of Management Information (SMI), the mechanisms used for describing and naming objects for the purpose of management. o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed objects (MO) for the Internet suite of protocols. o RFC 1905 [3] defines the protocol used for network access to managed objects. o RFC 1315 [4] defines the protocol used for managing Frame Relay DTE's. The framework is adaptable/extensible by defining new MIBs to suit the requirements of specific applications/protocols/situations. Managed objects are accessed via a virtual information store, the MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, which is an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, often a textual string, termed the descriptor, is used to refer to the object type. 4. Overview 4.1. Frame Relay Extensions for SVC's and Data Compression This MIB addresses the instances needed to be able to manage both the Frame Relay Forum's Implementation agreements for Data Compression (FRF.9). Kashef [Page 2] Draft Frame Relay DCP DTE Extensions MIB October 1996 5. Definitions FRAME-RELAY-DTE-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, NOTIFICATION-TYPE FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, TimeStamp FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF transmission FROM RFC1213-MIB InterfaceIndex FROM IF-MIB; -- 5.1 Extensions For Data Compression over Frame Relay Table frDcpTable OBJECT-TYPE SYNTAX SEQUENCE OF FrDcpEntry ACCESS not-accessible STATUS current DESCRIPTION "A table containing information about specific Data Link Connection Identifiers and corresponding virtual circuits in reference to Data Compression over Frame Relay. " ::= { frame-relay 9 } frDcpEntry OBJECT-TYPE SYNTAX FrDcpEntry ACCESS not-accessible STATUS current DESCRIPTION "The information regarding a single switched Data Link Connection Identifier." INDEX { frDcpIfIndex, frDcpDlci } ::= { frDcpTable 1 } Kashef [Page 3] Draft Frame Relay DCP DTE Extensions MIB October 1996 FrDcpEntry ::= SEQUENCE { -- -- Data Compression Circuit parameters -- frDcpIfIndex Index, frDcpDlci DLCI, frDcpEnable INTEGER, frDcpStatus INTEGER, frDcpRatio OCTET STRING } frDcpIfIndex OBJECT-TYPE SYNTAX Index ACCESS read-only STATUS current DESCRIPTION "The ifIndex Value of the ifEntry this virtual circuit is layered onto." ::= { frDcpEntry 1 } frDcpDlci OBJECT-TYPE SYNTAX DLCI ACCESS read-only STATUS current DESCRIPTION "The Data Link Connection Identifier for this virtual circuit." ::= { frDcpEntry 2 } frDcpEnable OBJECT-TYPE SYNTAX INTEGER { on (1), off (2) -- default } ACCESS read-write STATUS mandatory DESCRIPTION "Indicates whether data compression should take place on this particular end side virtual circuit. ::= { frDcpEntry 3 } Kashef [Page 4] Draft Frame Relay DCP DTE Extensions MIB October 1996 frDcpStatus OBJECT-TYPE SYNTAX INTEGER { on (1), off (2) } ACCESS read-only STATUS mandatory DESCRIPTION "On indicates that the compression has been successfully negotiated and is operating. Off indicates that the compression negotiation has failed and compression is not operating at this time, or compression has been terminated by either peer." ::= { frDcpEntry 4 } frDcpRatio OBJECT-TYPE SYNTAX OCTET STRING (SIZE (5)) ACCESS read-only STATUS mandatory DESCRIPTION "The ratio of uncompressed to compressed transmitted data. If data compression status is off, 1:1 will be displayed" ::= { frDcpEntry 5 } Kashef [Page 5] Draft Frame Relay DCP DTE Extensions MIB October 1996 6. Acknowledgements Special thanks to Don Cochrane of Cabletron Sys Inc for his assistance. 7. References [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996. [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991. [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin. " A Simple Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP Research, Performance Systems International, MIT Lab for Computer Science, May 1990. [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [5] McCloghrie, K. and F. Kastenholz, "Evolution of the Interfaces Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, January 1994. [6] T. Bradley, C. Brown, A. Malis, "Multiprotocol Interconnect over Frame Relay", RFC 1490, 07/26/1993. Table of Contents 1 Status of this Memo ................................... 1 2 Abstract .............................................. 1 3 The SNMPv2 Network Management Framework ............... 2 4 Overview .............................................. 2 4.1 Frame Relay DCP DTE Extensions for Data Compression over Frame Relay ....................... 2 5 Definitions ........................................... 3 5.1 Data Compression over Frame Relay Table .............. 3 6 Acknowledgements ....................................... 6 7 References ............................................. 6 Kashef [Page 6]