HTTP/1.1 200 OK Date: Tue, 09 Apr 2002 02:28:27 GMT Server: Apache/1.3.20 (Unix) Last-Modified: Thu, 27 Mar 1997 13:55:00 GMT ETag: "2ed9f4-3703-333a7c34" Accept-Ranges: bytes Content-Length: 14083 Connection: close Content-Type: text/plain INTERNET-DRAFT EXPIRATION DATE: September 3 1997 Management Information Base for Frame Relay Data Compression Moji Kashef Cabletron Sys, Inc. 35E Industrial Way, 1st Floor Rochester New Hampshire, 03867 kashef@ctron.com Jaime A Colom Paradyne Corp 8545 126th Ave. N. Mail Stop LG 134 Largo, FL 34649-2826 jaime@eng.paradyne.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. Please send comments to the authors, copying iplpdn@cnri.reston.va.us. It expires September 1997. Kashef & Colom [Page 1] Internet Draft Frame Relay DCP MIB September 1997 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. 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 Data Compression This MIB addresses the instances needed to be able to manage the Frame Relay Forum's Implementation agreements for Data Compression (FRF.9). Kashef & Colom [Page 2] Internet Draft Frame Relay DCP MIB September 1997 5. Definitions FRAME-RELAY-DCP-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32,Counter32, Gauge32 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC transmission FROM RFC1213-MIB InterfaceIndex FROM IF-MIB frameRelayDcp MODULE-IDENTITY LAST-UPDATED "9311161200Z" ORGANIZATION "IETF Frame Relay Service MIB Working Group" CONTACT-INFO " Moji Kashef Cabletron Sys, Inc. 35E Industrial Way, 1st Floor Rochester New Hampshire, 03867 Tel: Fax: E-mail: kashef@ctron.com Jaime A Colom Paradyne Corp 8545 126th Ave. N. Mail Stop LG 134 Largo, FL 33773 Tel: +1 813 530 2914 Fax: +1 813 532 5244 E-mail: jaime@eng.paradyne.com" DESCRIPTION "Management Information Base for Frame Relay DCP DTE Extensionsafor Data Compression over Frame Relay." ::= { transmission 5 } Kashef & Colom [Page 3] Internet Draft Frame Relay DCP MIB September 1997 -- -- the range of a Data Link Connection Identifier -- DLCI ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The range of DLCI values. Note that this varies by interface configuration; normally, interfaces may use 0..1023, but may be configured to use ranges as large as 0..2^23." SYNTAX INTEGER (0..8388607) -- 5.1 Data Compression Protocol Table frDcpTable OBJECT-TYPE SYNTAX SEQUENCE OF FrDcpEntry MAX-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. " ::= { frameRelayDcp 1 } frDcpEntry OBJECT-TYPE SYNTAX FrDcpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The information regarding a single switched Data Link Connection Identifier." INDEX { frDcpIfIndex, frDcpDlci } ::= { frDcpTable 1 } Kashef & Colom [Page 4] Internet Draft Frame Relay DCP MIB September 1997 FrDcpEntry ::= SEQUENCE { -- -- Data Compression Circuit parameters -- frDcpIfIndex InterfaceIndex, frDcpDlci DLCI, frDcpEnable INTEGER, frDcpConnectStatus INTEGER, frDcpTxRatio Integer32, frDcpTxThrPut Gauge32, frDcpRxSeqError Counter32, frDcpRxLcbError Counter32, frDcpHistReset Counter32 } frDcpIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The ifIndex value of the corresponding ifEntry." ::= { frDcpEntry 1 } frDcpDlci OBJECT-TYPE SYNTAX DLCI MAX-ACCESS read-only STATUS current DESCRIPTION "The Data Link Connection Identifier for this virtual circuit." ::= { frDcpEntry 2 } Kashef & Colom [Page 5] Internet Draft Frame Relay DCP MIB September 1997 frDcpEnable OBJECT-TYPE SYNTAX INTEGER { enable (1), disable (2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether data compression should take place on this particular end side virtual circuit." DEFVAL { disable } ::= { frDcpEntry 3 } frDcpConnectStatus OBJECT-TYPE SYNTAX INTEGER { connected (1), disconnected (2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Connected indicates that the compression has been successifully negotiated and is operating. Disconnected indicates that the compression is not operating at this time because compression negotiation has failed and , or compression has been terminated by either peer." ::= { frDcpEntry 4 } frDcpTxRatio OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This field displays the ratio of uncompressed to compressed transmitted data. The returned value is ratio * 10, where ration is in the range of 0 to 9.9. (Example, a 2:1 ratio will return 2*10 = 20, 2.5:1 will return 2.5*10 = 25)." ::= { frDcpEntry 5 } Kashef & Colom [Page 6] Internet Draft Frame Relay DCP MIB September 1997 frDcpTxThrPut OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "This field displays the measured throughput in bits per second of the compressed Tx data." ::= { frDcpEntry 6 } frDcpRxSeqError OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the received sequence # errors frames on the Network Interface by the compression engine for the selected DLCI." ::= { frDcpEntry 7 } frDcpRxLcbError OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the received LCB errors frames on the Network Interface by the compression engine for the selected DLCI." ::= { frDcpEntry 8 } frDcpHistReset OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of compression history resets by the compression engine for the selected DLCI." ::= { frDcpEntry 9 } END Kashef & Colom [Page 7] Internet Draft Frame Relay DCP MIB September 1997 6. Acknowledgements Special thanks to Don Cochrane of Cabletron Sys Inc and Sussan Hassel of Paradyne Corp for their 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 .............................................. 2 3 The SNMPv2 Network Management Framework ............... 2 4 Overview .............................................. 3 4.1 Frame Relay Data Compression ....................... 3 5 Definitions ........................................... 3 5.1 Data Compression over Frame Relay Table .............. 3 6 Acknowledgements ....................................... 6 7 References ............................................. 7 Kashef & Colom [Page 8] --------------21CD373482C--