Definitions of Managed Objects for Frame Relay Service Level Definitions June 23, 1999 draft-steinberger-frmrelay-service-00.txt Robert A. Steinberger Paradyne Corporation rsteinberger@paradyne.com Orly Nicklass, Ph.D RAD Data Communications Ltd. orly@radmail.rad.co.il Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This memo defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service Level Definitions. This memo does not specify a standard for the Internet community. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. Expires December 1999 Steinberger & Nicklass [Page 1] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 Table of Contents 1. The SNMP Management Framework .................... .......... 3 2. Overview .................................................... 4 2.1. Frame Relay Service Level Definitions ..................... 4 2.2. Terminology ............................................... 5 2.3. Network Model ............................................. 5 2.4. Reference Points .......................................... 6 2.5. Measurement Methodology ................................... 8 2.6. Collection Location ....................................... 8 2.7. Use of MIB in Calculation of Service Level Definitions .... 10 2.7.1. Delay ................................................... 11 2.7.2. Frame Delivery Ratio .................................... 11 2.7.3. Data Delivery Ratio ..................................... 11 2.7.4. Service Availability .................................... 12 3. Object Definitions .......................................... 12 4. Acknowledgments ............................................. 32 5. References .................................................. 33 6. Security Considerations ..................................... 35 7. Authors' Addresses .......................................... 35 8. Copyright Section ........................................... 36 Expires December 1999 Steinberger & Nicklass [Page 2] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 1. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [1]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13]. o A set of fundamental applications described in RFC 2573 [14] and the view-based access control mechanism described in RFC 2575 [15]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [16]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in Expires December 1999 Steinberger & Nicklass [Page 3] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 2. Overview This MIB addresses the items required to manage the Frame Relay Forum's Implementation Agreement for Service Level Definitions (FRF.13 [17]). At present, this applies to these values of the ifType variable in the Internet-standard MIB: o frameRelay (32) o frameRelayService (44) This section provides an overview and background of how to use this MIB. 2.1. Frame Relay Service Level Definitions The frame relay service level definitions address specific characteristics of a frame relay service facilitate the following tasks: o Evaluation of frame relay service providers, offerings or products. o Measurement of Quality of Service. o Enforcement of Service Level Agreements. o Planning or describing a frame relay network. The following parameters are defined in FRF.13 [17] as a sufficient set of values to values to accomplish the tasks previously stated. o Delay - The amount of time elapsed, in milliseconds, from the time a frame exits the source to the time it reaches the destination. o Frame Delivery Ratio - The ratio of the number of frames delivered to the destination versus the number of frames sent by the source. This ratio can be further divided by Expires December 1999 Steinberger & Nicklass [Page 4] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 inspecting either only the frames within the CIR or only the frames in excess of the CIR. o Data Delivery Ratio - The ratio of the amount of data delivered to the destination versus the amount of data sent by the source. This ratio can be further divided by inspecting either only the data within the CIR or only the data in excess of the CIR. o Service Availability - The amount of time the frame relay service was not unavailable. There are three types of availability statistics defined in FRF.13 [17]: Virtual Connection Availabity, Mean Time to Repair, and Mean Time Between Service Outages. The later two require information about the scheduled outage time that should be maintained by the management software used in calculation of the values. Consult FRF.13 [17] for more details. 2.2. Terminology o CIR - The Committed Information Rate (CIR) is the subscriber data rate (expressed in bits/second) that the network commits to deliver under normal network conditions. [18] o DLCI - Data Link Connection Identifier. [18] o Logical Port - This term is used to model the Frame Relay interface on a device. [18] o NNI - Network to Network Interface. [18] o Permanent Virtual Connection (PVC) - A virtual connection that has its end-points and bearer capabilities defined at subscription time. [18] o Reference Point (RP) - The point of reference within the network model at which the calculations or data collection takes place. o UNI - User to Network Interface. [18] 2.3. Network Model The basic model, as illustrated in figure 1 below, contains two frame relay DTE endpoints connected to a network cloud via a frame relay Expires December 1999 Steinberger & Nicklass [Page 5] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 UNI interface. The network cloud can contain zero or more internal frame relay NNI connections that interconnect multiple networks. The calculations and data collection can be performed at any reference point within the network. +-------------+ +-------------+ | Frame Relay | | Frame Relay | | DTE Device | | DTE Device | +------+------+ +------+------+ | | UNI UNI Connection Connection | | +-------------+ NNI +-------------+ NNI +-------------+ | Network A +------------+ Network B +------------+ Network C | +-------------+ Connection +-------------+ Connection +-------------+ Figure 1 Frame Relay Network Reference Model 2.4. Reference Points The collection and calculations of the service level definitons apply to two reference points within the network. These two points are the locations where the frames are referenced in the collection of the service level specific information. The refernce points used in the MIB are shown in figure 2 below. For completeness, the MIB also allows for a proprietary reference point which can exist anywhere in the network that is not a previously defined reference point. Its meaning is insignificant unless defined by the device manufacturer. Expires December 1999 Steinberger & Nicklass [Page 6] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 +---------------------------+ |+-----------+ +-----------+| || | |Measurement|| ||Frame Relay|-|Engine |-(Source RP)----+ ||DTE | |(If Exists)|| | |+-----------+ +-----------+| | +---------------------------+ | Frame Relay Source | +------------------------------------------+ | Frame Relay Network | +----------------------------------+ | | +------------------------------+ | | | | +---------+ +---------+ | | | | | | | | Traffic | | | +--(Ingress RP)--+ L1 / L2 +-+ Policing| | | | | | Control | | Engine | | | | | +---------+ +----+----+ | | | | | | | | | (Traffic Policing RP)| | | +------------------|-----------+ | | Ingress Node | | | | | | +-----------|-----------+ | | | Intermediate Nodes | | | +-----------|-----------+ | | | | | Egress Node | | | +--------------|-----------+ | | | (Egress Queue Input RP) | | | | | | | | | +-------+------+ | | | | | Egress Queue | | | | | +-------+------+ | | | | | | | | | (Egress Queue Output RP) | | | +--------------|-----------+ | +--------------------|-------------+ Frame Relay Destination | +---------------------------+ +-----------+ |+-----------+ +-----------+| | || | |Measurement|| | ||Frame Relay|-|Engine |-(Destination RP)--+ ||DTE | |(If Exists)|| |+-----------+ +-----------+| +---------------------------+ Figure 2 Reference Points (FRF.13 [17]) Expires December 1999 Steinberger & Nicklass [Page 7] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 The MIB variables frsldPvcCtrlSrcRP and frsldPvcCtrlDstRP allow the user to view and, if supported, configure the reference points at which the calculations occur. These variables are specific to the device on which they are located. Frame relay devices act as both frame sources and frame destinations. The definitions in this MIB apply to the interaction of a pair of devices on the network path. The same device can potentially use different reference points for calculatation and collection of the statistics based on whether the referenced frame is sent or received by the device. When the device is acting as a frame source, the value of frsldPvcCtrkSrcRP reflects the reference point used for all source calculations pertaining to the specified PVC. When the device is acting as a frame destination, the value of frsldPvcCtrlDstRP reflects the reference point used for all destination calculations pertaining to the specified PVC. For example, FRF.13 [17] defines an Edge-to-Edge Egress Queue measurement domain as a domain in which measurement is performed between an Ingress Reference Point and an Egress Queue Input Reference Point. For this domain between a source device and a destination device, the value of frsldPvcCtrkSrcRP for the source device would be set to ingRP(2) and the value of frsldPvcCtrlDstRP for the destination device would be set to eqiRP(4). While it is usually the case that the reference points would simply swap when looking at frames going in the opposite direction, there is no requirement for them to do so. 2.5. Measurement Methodology This document neither recommends nor suggests a method of implementation. This is left to the device manufacturer and should be independent of the data that is actually collected. Periodic collection of this data can be performed through either polling of the data table, use of the sample tables or use of the user history group of RFC 2021 [19]. 2.6. Collection Location In order to facilitate implementation independence, the location at which the calculations are performed must be reported. In that these statistics correlate information between two devices (a source- destination node pair), there are multiple locations at which this calculation can actually take place. These locations are specified using the MIB variables frsldPvcCtrlDelayLoc and frsldPvcCtrlDeliveryLoc. The potential values for these variables have the following meanings: o source - All calculations are performed at the source node Expires December 1999 Steinberger & Nicklass [Page 8] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 given statistics from the destination node. This means that the source node collects information from the destination node and reports values that are consistent with the current state of the network. There may be some delay in updating these values due to the cross-network correlation. However, all values should synchronized such that they act as if collected simultaneously. The method of cross-network communication is implementation independent. The network node being queried is acting as the source node. The network node at the far end of the PVC is the destination node. The values of the "offered" statistics are associated with those frames sent by this node. The values of the "delivered" statistics are associated with those frames actually reaching the destination node. The one-way delay statistics are associated with packets sent from this node to the far-end node. The round-trip delay statistics are associated with packets sent by this node and received by this node. o destination - All calculations are performed at the destination node given statistics from the source node. This means that the destination node collects information from the source node and reports values that are consistent with the current state of the network. There may be some delay in updating these values due to the cross-network correlation. However, all values should synchronized such that they act as if collected simultaneously. The method of cross-network communication is implementation independent. The network node being queried is acting as the destination node. The network node at the far end of the PVC is the source node. The values of the "offered" statistics are associated with those frames sent by this the source node. The values of the "delivered" statistics are associated with those frames actually received by this node. The one-way delay statistics are associated with packets sent by the far end node and received by this node. The round-trip delay statistics are associated with packets sent by the far end node, received by the far end node and reported to this node. o intermediate - All calculations are performed at some intermediate node such as a probe. This means that both the source and the destination node are referenced such that the values reported are consistent with the current state of the network. There may be some delay in updating these values due to the cross-network correlation. However, all values should synchronized such that they act as if collected Expires December 1999 Steinberger & Nicklass [Page 9] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 simultaneously. The method of cross-network communication is implementation independent. The network node being queried is acting as neither the source nor the destination node. The network node at one far end of the PVC is the source node while the other far end node is the destination node. The values of the "offered" statistics are associated with those frames sent by this the source node. The values of the "delivered" statistics are associated with those frames actually received by the destination node. The one-way delay statistics are associated with packets travelling from the source reference point to the destination reference point. The round-trip delay statistics are associated with packets that leave and return to this node. o distributed - There is no cross-network communication performed by the device in the collection of statistics. The values in the MIB objects on this device reflect only information that this device knows about itself. The source specific values reflect information about this device when it acts as the source. Likewise, the destination specific values reflect information about this device when it acts as a destination. It is up to the network management software to communicate to each device to collect the statistics. The network node being queried is acting as both a source and a destination node for separate source-destination node pairs. The values of the "offered" statistics are associated with those frames sent by this the source node and are valid in the context of the source-destination node pair for which this node is the source. The values of the "delivered" statistics are associated with those frames actually received by this node and are valid in the context of the source- destination node pair for which this node is the destination. All delay statistics for this node are deferred to the node at the far end. 2.7. Use of MIB in Calculation of Service Level Definitions The MIB variables can be used to calculate statistics defined in FRF.13 [17]. For the following explanation, it is assumed that statistics can both be collected from the same device, i.e. the location type is not distributed. Should the location be distributed, the manager should collect the source information from the source node and the network information from the network node. Expires December 1999 Steinberger & Nicklass [Page 10] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 Otherwise, all information should be collected from the single device representing the correct end of the PVC. 2.7.1. Delay The frame transfer delay is defined as the amount of time elapsed, in milliseconds, from the time a frame exits the source to the time it reaches the destination. This value can be found using the frsldPvcDataDelayAvg MIB variable. The delay may be calculated as either round trip or one way, and this information is held in the frsldPvcCtrlDelayType MIB variable. Should the delay be calculated as round trip, the value of frsldPvcDataDelayAvg represents the average of the total delay of the round trips. In this case, the value should be divided by two to obtain the frame transfer delay. In the case that frsldPvcCtrlDelayType is oneWay, the value of frsldPvcDataDelayAvg represents the average of the frame transfer delays. 2.7.2. Frame Delivery Ratio The frame delivery ratio is defined as the total number of frames delivered to the destination divided by the frames offered by the source. The destination values can be obtained using FrDeliveredC and FrDeliveredE. The source values can be obtained using FrOfferedC and FrOfferedE. FrDeliveredC + FrDeliveredE Frame Delivery Ratio = --------------------------- FrOfferedC + FrOfferedE FrDeliveredC Committed Frame Delivery Ratio = ------------ FrOfferedC FrDeliveredE Excess Frame Delivery Ratio = ------------ FrOfferedE 2.7.3. Data Delivery Ratio The data delivery ratio is defined as the total number of data delivered to the destination divided by the data offered by the source. The destination values can be obtained using DataDeliveredC and DataDeliveredE. The source values can be obtained using DataOfferedC and DataOfferedE. Expires December 1999 Steinberger & Nicklass [Page 11] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 DataDeliveredC + DataDeliveredE Data Delivery Ratio = ------------------------------- DataOfferedC + DataOfferedE DataDeliveredC Committed Data Delivery Ratio = -------------- DataOfferedC DataDeliveredE Excess Data Delivery Ratio = -------------- DataOfferedE 2.7.4. Service Availability Mean Time to Repair (FRMTTR) = 0 if Unavailables is 0. UnavailableTime Otherwise, FRMTTR = --------------- Unavailables 3. Object Definitions FRSLD-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32, Integer32, TimeTicks FROM SNMPv2-SMI transmission FROM RFC1213-MIB TEXTUAL-CONVENTION, RowStatus FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF ifIndex FROM IF-MIB; frsldMIB MODULE-IDENTITY LAST-UPDATED "9906230000Z" ORGANIZATION "IETF TBD Working Group" CONTACT-INFO "Robert Steinberger Postal: Paradyne Corporation Mailstop: LG-132 8545 126th Avenue North Largo, FL USA 33773 TEL: +1 813 530 2395 FAX +1 813 532 5244 E-mail: rsteinberger@paradyne.com Expires December 1999 Steinberger & Nicklass [Page 12] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 Orly Nicklass, Ph.D Postal: RAD Data Commincations Ltd. 12 Hanechoshet Street Tel Aviv, Israel 69710 TEL: +972 3 6459588 FAX: +972 3 6472675 E-mail: orly@radmail.rad.co.il" DESCRIPTION "The MIB module to describe generic objects for Frame Relay Service Level Definitions." ::= { transmission xxx } FrsldLocation ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The location at which the calucations occur." SYNTAX INTEGER { source(1), -- Calculations occur at the -- source device. destination(2), -- Calculations occur at the -- destination device. intermediate(3), -- Calculations occur at some -- intermediate device such as -- a probe. distributed(4) -- Calculations are distributed -- between source and destination -- devices. } FrsldRP ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Reference points for calculation of service level defintions." SYNTAX INTEGER { srcRP(1), -- Source Reference Point ingRP(2), -- Ingress Reference Point tpRP(3), -- Traffic Policing Reference Point eqiRP(4), -- Egress Queue Input Reference Point eqoRP(5), -- Egress Queue Output Reference Point desRP(6), -- Destination Reference Point propRP(7) -- Proprietary Reference Point } frsldTables OBJECT IDENTIFIER ::= { frsldMIB 1 } frsldConformance OBJECT IDENTIFIER ::= { frsldMIB 2 } -- The Frame Relay Service Level Definitions PVC Control Table Expires December 1999 Steinberger & Nicklass [Page 13] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 -- -- This table is used to define and display the parameters of -- service level definitions on individual PVCs. frsldPvcCtrlTable OBJECT-TYPE SYNTAX SEQUENCE OF FrsldPvcCtrlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay Service Level Definitions control table." ::= { frsldTables 1 } frsldPvcCtrlEntry OBJECT-TYPE SYNTAX FrsldPvcCtrlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Frame Relay Service Level Definitions control table." INDEX { ifIndex, frsldPvcCtrlDlci } ::= { frsldPvcCtrlTable 1 } FrsldPvcCtrlEntry ::= SEQUENCE { -- -- Index Control Variables -- frsldPvcCtrlDlci Integer32, frsldPvcCtrlStatus RowStatus, -- -- Service Level Definitions Setup Variables -- frsldPvcCtrlSrcRP FrsldRP, frsldPvcCtrlDstRP FrsldRP, frsldPvcCtrlPacketFreq Integer32, -- -- Delay Specific Setup Variables -- frsldPvcCtrlDelayLoc FrsldLocation, frsldPvcCtrlDelayFrSize Integer32, frsldPvcCtrlDelayType INTEGER, frsldPvcCtrlDelayTimeOut Integer32, -- -- Delivery Specific Setup Variables -- frsldPvcCtrlDeliveryLoc FrsldLocation, -- Expires December 1999 Steinberger & Nicklass [Page 14] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 -- Sampling Control Variables: Delay and Delivery -- frsldPvcCtrlDataColPackets Integer32, frsldPvcCtrlDataBuckets Integer32, frsldPvcCtrlDataBucketsGranted Integer32, -- -- Sampling Control Variables: Availability -- frsldPvcCtrlAvailColPeriod Integer32, frsldPvcCtrlAvailBuckets Integer32, frsldPvcCtrlAvailBucketsGranted Integer32 } frsldPvcCtrlDlci OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to the DLCI value for this PVC." ::= { frsldPvcCtrlEntry 1 } frsldPvcCtrlStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of the current row. This object is used to add, delete, and disable rows in this table. When the status changes to active, a row will also be added to the data table below. This row should not be removed until the status is changed to deleted." ::= { frsldPvcCtrlEntry 2 } frsldPvcCtrlSrcRP OBJECT-TYPE SYNTAX FrsldRP MAX-ACCESS read-create STATUS current DESCRIPTION "The reference point this PVC uses for calculation when it is acting as a source. This object together with frsldPvcCtrlDstRp define the measurement domain." ::= { frsldPvcCtrlEntry 3 } frsldPvcCtrlDstRP OBJECT-TYPE SYNTAX FrsldRP Expires December 1999 Steinberger & Nicklass [Page 15] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 MAX-ACCESS read-create STATUS current DESCRIPTION "The reference point this PVC uses for calculation when it is acting as a destination. This object together with frsldPvcCtrlDstRP define the measurement domain." ::= { frsldPvcCtrlEntry 4 } frsldPvcCtrlPacketFreq OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The frequency in seconds between initiation of specialized packets used to collect delay and / or delivery information as supported by the device." DEFVAL { 60 } ::= { frsldPvcCtrlEntry 5 } frsldPvcCtrlDelayLoc OBJECT-TYPE SYNTAX FrsldLocation MAX-ACCESS read-create STATUS current DESCRIPTION "The location at which the calculation of delay for this PVC occurs." ::= { frsldPvcCtrlEntry 6 } frsldPvcCtrlDelayFrSize OBJECT-TYPE SYNTAX Integer32 (1..8188) MAX-ACCESS read-create STATUS current DESCRIPTION "The size of the payload in the frame used for calculation of network delay." DEFVAL { 128 } ::= { frsldPvcCtrlEntry 7 } frsldPvcCtrlDelayType OBJECT-TYPE SYNTAX INTEGER { oneWay(1), roundTrip(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The type of delay measurement performed." Expires December 1999 Steinberger & Nicklass [Page 16] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 ::= { frsldPvcCtrlEntry 8 } frsldPvcCtrlDelayTimeOut OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "A delay frame will count as a missed poll if it is not updated in the time specified by frsldPvcCtrlDelayTimeOut." DEFVAL { 60 } ::= { frsldPvcCtrlEntry 9 } frsldPvcCtrlDeliveryLoc OBJECT-TYPE SYNTAX FrsldLocation MAX-ACCESS read-create STATUS current DESCRIPTION "The location at which the collection of delivery parameters for this PVC occur." ::= { frsldPvcCtrlEntry 10 } frsldPvcCtrlDataColPackets OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The number of specialized packets used to collect delay and / or delivery information that will be considered in a historical period. During each period a row is added to the data sample table." DEFVAL { 15 } ::= { frsldPvcCtrlEntry 11 } frsldPvcCtrlDataBuckets OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The number of discrete buckets over which the delay and delivery data statistics are sampled. A value of zero indicates that no samples are desired for the delay and delivery statistics. When this object is created or modified, the device should attempt to set the frsldCtrlDataBuckets- Granted to a value as close as is possible Expires December 1999 Steinberger & Nicklass [Page 17] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 depending upon the implementation and the available resources." DEFVAL { 60 } ::= { frsldPvcCtrlEntry 12 } frsldPvcCtrlDataBucketsGranted OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of discrete buckets granted. This object will return 0 until frsldPvcCtrlStatus is set to active(1). At that time the buckets will be allocated depending upon implementation and available resources." ::= { frsldPvcCtrlEntry 13 } frsldPvcCtrlAvailColPeriod OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The amount of time in seconds that defines a period of collection of the availability statistics. At the end of each period, the availability statistics will be sampled and the change in their values will be added to a new row in the availability sample table." DEFVAL { 86400 } -- 24 hours ::= { frsldPvcCtrlEntry 14 } frsldPvcCtrlAvailBuckets OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The number of discrete buckets over which the availability statistics are sampled. A value of zero indicates that no samples are desired for the availability statistics. When this object is created or modified, the device should attempt to set the frsldCtrlAvailBuckets- Granted to a value as close as is possible depending upon the implementation and the available resources." Expires December 1999 Steinberger & Nicklass [Page 18] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 DEFVAL { 31 } -- One month ::= { frsldPvcCtrlEntry 15 } frsldPvcCtrlAvailBucketsGranted OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of discrete buckets granted. This object will return 0 until frsldPvcCtrlStatus is set to active(1). At that time the buckets will be allocated depending upon the implementation and available resources." ::= { frsldPvcCtrlEntry 16 } -- The Frame Relay Service Level Definitions PVC Data Table -- -- This table contains the accumulated values of -- the collected data. This table is the table that should -- be referenced by external polling mechanism should time -- based polling be desired. frsldPvcDataTable OBJECT-TYPE SYNTAX SEQUENCE OF FrsldPvcDataEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay Service Level Definitions data table." ::= { frsldTables 2 } frsldPvcDataEntry OBJECT-TYPE SYNTAX FrsldPvcDataEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Frame Relay Service Level Definitions data table." INDEX { ifIndex, frsldPvcCtrlDlci } ::= { frsldPvcDataTable 1 } FrsldPvcDataEntry ::= SEQUENCE { frsldPvcDataDelayMin Gauge32, frsldPvcDataDelayMax Gauge32, frsldPvcDataDelayAvg Gauge32, frsldPvcDataMissedPolls Counter32, frsldPvcDataFrDeliveredC Counter32, Expires December 1999 Steinberger & Nicklass [Page 19] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 frsldPvcDataFrDeliveredE Counter32, frsldPvcDataFrOfferedC Counter32, frsldPvcDataFrOfferedE Counter32, frsldPvcDataDataDeliveredC Counter32, frsldPvcDataDataDeliveredE Counter32, frsldPvcDataDataOfferedC Counter32, frsldPvcDataDataOfferedE Counter32, frsldPvcDataUnavailableTime TimeTicks, frsldPvcDataUnavailables Counter32 } frsldPvcDataDelayMin OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The minimum delay measured in the period defined by frsldPvcCtrlDataColPackets. A value of zero means that no data is available." ::= { frsldPvcDataEntry 1 } frsldPvcDataDelayMax OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The largest delay measured in the period defined by frsldPvcCtrlDataColPackets. A value of zero means that no data is available." ::= { frsldPvcDataEntry 2 } frsldPvcDataDelayAvg OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The average delay measured in the period defined by frsldPvcCtrlColPackets. A value of zero means that no data is available." ::= { frsldPvcDataEntry 3 } frsldPvcDataMissedPolls OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of polls that have been missed." Expires December 1999 Steinberger & Nicklass [Page 20] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 ::= { frsldPvcDataEntry 4 } frsldPvcDataFrDeliveredC OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames that were delivered within CIR. If the location of calculation is distributed(4), this value represents the number of committed frames the far end sent that reached this device." ::= { frsldPvcDataEntry 5 } frsldPvcDataFrDeliveredE OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames that were delivered in excess of the CIR. If the location of calculation is distributed(4), this value represents the number of excess frames the far end sent that reached this device." ::= { frsldPvcDataEntry 6 } frsldPvcDataFrOfferedC OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames that were offered with CIR. If the location of calculation is distributed(4), this value represents the number of committed frames the near end sent." ::= { frsldPvcDataEntry 7 } frsldPvcDataFrOfferedE OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames that were offered in excess of the CIR. If the location of calculation is distributed(4), this value represents the number of excess frames the near end sent." ::= { frsldPvcDataEntry 8 } Expires December 1999 Steinberger & Nicklass [Page 21] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 frsldPvcDataDataDeliveredC OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets that were delivered within CIR. If the location of calculation is distributed(4), this value represents the number of committed octets the far end sent that reached this device." ::= { frsldPvcDataEntry 9 } frsldPvcDataDataDeliveredE OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets that were delivered in excess of the CIR. If the location of calculation is distributed(4), this value represents the number of excess octets the far end sent that reached this device." ::= { frsldPvcDataEntry 10 } frsldPvcDataDataOfferedC OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets that were offered with CIR. If the location of calculation is distributed(4), this value represents the number of committed octets the near end sent." ::= { frsldPvcDataEntry 11 } frsldPvcDataDataOfferedE OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets that were offered in excess of the CIR. If the location of calculation is distributed(4), this value represents the number of excess octets the near end sent." ::= { frsldPvcDataEntry 12 } frsldPvcDataUnavailableTime OBJECT-TYPE SYNTAX TimeTicks Expires December 1999 Steinberger & Nicklass [Page 22] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 MAX-ACCESS read-only STATUS current DESCRIPTION "The amount of time this PVC was declared unavailable for any reason." ::= { frsldPvcDataEntry 13 } frsldPvcDataUnavailables OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times this PVC was declared unavailable for any reason." ::= { frsldPvcDataEntry 14 } -- The Frame Relay Service Level Definitions PVC -- Data Sample Table -- -- This table contains the sampled delay and delivery -- information. frsldPvcDataSampleTable OBJECT-TYPE SYNTAX SEQUENCE OF FrsldPvcDataSampleEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay Service Level Definitions data sample table." ::= { frsldTables 3 } frsldPvcDataSampleEntry OBJECT-TYPE SYNTAX FrsldPvcDataSampleEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Frame Relay Service Level Definitions data sample table." INDEX { ifIndex, frsldPvcCtrlDlci, frsldPvcDataSmplIdx } ::= { frsldPvcDataSampleTable 1 } FrsldPvcDataSampleEntry ::= SEQUENCE { frsldPvcDataSmplIdx Integer32, frsldPvcDataDelaySmplMin Gauge32, frsldPvcDataDelaySmplMax Gauge32, frsldPvcDataDelaySmplAvg Gauge32, Expires December 1999 Steinberger & Nicklass [Page 23] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 frsldPvcDataSmplMissedPolls Gauge32, frsldPvcDataSmplFrDeliveredC Gauge32, frsldPvcDataSmplFrDeliveredE Gauge32, frsldPvcDataSmplFrOfferedC Gauge32, frsldPvcDataSmplFrOfferedE Gauge32, frsldPvcDataSmplDataDeliveredC Gauge32, frsldPvcDataSmplDataDeliveredE Gauge32, frsldPvcDataSmplDataOfferedC Gauge32, frsldPvcDataSmplDataOfferedE Gauge32, frsldPvcDataSmplStartTime TimeTicks, frsldPvcDataSmplEndTime TimeTicks } frsldPvcDataSmplIdx OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The bucket index of the current sample. This increment once for each new bucket in the table." ::= { frsldPvcDataSampleEntry 1 } frsldPvcDataDelaySmplMin OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The minimum delay measured for any information packet that arrived in this interval. A value of zero means that no data is available." ::= { frsldPvcDataSampleEntry 2 } frsldPvcDataDelaySmplMax OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The largest delay measured for any inforamtion packet that arrived in this interval. A value of zero means that no data is available." ::= { frsldPvcDataSampleEntry 3 } frsldPvcDataDelaySmplAvg OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION Expires December 1999 Steinberger & Nicklass [Page 24] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 "The average delay measured for all delay packets that arrived in this interval. A value of zero means that no data is available." ::= { frsldPvcDataSampleEntry 4 } frsldPvcDataSmplMissedPolls OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of polls that were missed during this polling period." ::= { frsldPvcDataSampleEntry 5 } frsldPvcDataSmplFrDeliveredC OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The change in the value of frsldPvcDataFr- DeliveredC during this sample interval." ::= { frsldPvcDataSampleEntry 6 } frsldPvcDataSmplFrDeliveredE OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The change in the value of frsldPvcDataFr- DeliveredE during this sample interval." ::= { frsldPvcDataSampleEntry 7 } frsldPvcDataSmplFrOfferedC OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The change in the value of frsldPvcDataFrOfferedC during this sample interval." ::= { frsldPvcDataSampleEntry 8 } frsldPvcDataSmplFrOfferedE OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The change in the value of frsldPvcDataFrOfferedE during this sample interval." Expires December 1999 Steinberger & Nicklass [Page 25] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 ::= { frsldPvcDataSampleEntry 9 } frsldPvcDataSmplDataDeliveredC OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The change in the value of frsldPvcDataData- DeliveredC during this sample interval." ::= { frsldPvcDataSampleEntry 10 } frsldPvcDataSmplDataDeliveredE OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The change in the value of frsldPvcDataData- DeliveredE during this sample interval." ::= { frsldPvcDataSampleEntry 11 } frsldPvcDataSmplDataOfferedC OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The change in the value of frsldPvcDataDataOfferedC during this sample interval." ::= { frsldPvcDataSampleEntry 12 } frsldPvcDataSmplDataOfferedE OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The change in the value of frsldPvcDataData- OfferedE during this sample interval." ::= { frsldPvcDataSampleEntry 13 } frsldPvcDataSmplStartTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this sample period started." ::= { frsldPvcDataSampleEntry 14 } frsldPvcDataSmplEndTime OBJECT-TYPE Expires December 1999 Steinberger & Nicklass [Page 26] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this sample period end. No data will be reported and the row will not appear in the table until the sample has been collected." ::= { frsldPvcDataSampleEntry 15 } -- The Frame Relay Service Level Definitions PVC -- Availability Sample Table -- -- This table contains the sampled availability information. frsldPvcAvailSampleTable OBJECT-TYPE SYNTAX SEQUENCE OF FrsldPvcAvailSampleEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay Service Level Definitions availability sample table." ::= { frsldTables 4 } frsldPvcAvailSampleEntry OBJECT-TYPE SYNTAX FrsldPvcAvailSampleEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Frame Relay Service Level Definitions availibility sample table." INDEX { ifIndex, frsldPvcCtrlDlci, frsldPvcAvailSmplIdx } ::= { frsldPvcAvailSampleTable 1 } FrsldPvcAvailSampleEntry ::= SEQUENCE { frsldPvcAvailSmplIdx Integer32, frsldPvcAvailSmplUnavailableTime TimeTicks, frsldPvcAvailSmplUnavailables Gauge32, frsldPvcAvailSmplStartTime TimeTicks, frsldPvcAvailSmplEndTime TimeTicks } frsldPvcAvailSmplIdx OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION Expires December 1999 Steinberger & Nicklass [Page 27] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 "The bucket index of the current sample. This increment once for each new bucket in the table." ::= { frsldPvcAvailSampleEntry 1 } frsldPvcAvailSmplUnavailableTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The change in the value of frsldPvcData- UnavailableTime during this sample interval." ::= { frsldPvcAvailSampleEntry 2 } frsldPvcAvailSmplUnavailables OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The change in the value of frsldPvcData- Unavailables during this sample interval." ::= { frsldPvcAvailSampleEntry 3 } frsldPvcAvailSmplStartTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this sample period started." ::= { frsldPvcAvailSampleEntry 4 } frsldPvcAvailSmplEndTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this sample period end. No data will be reported and the row will not appear in the table until the sample has been collected." ::= { frsldPvcAvailSampleEntry 5 } -- Conformance Information frsldMIBGroups OBJECT IDENTIFIER ::= { frsldConformance 1 } frsldMIBCompliances OBJECT IDENTIFIER ::= { frsldConformance 2 } Expires December 1999 Steinberger & Nicklass [Page 28] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 -- -- Compliance Statements -- frsldCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMPv2 entities which support Frame Relay Service Level Definitions." MODULE -- this module MANDATORY-GROUPS { frsldPvcReqCtrlGroup, frsldPvcReqDataGroup} OBJECT frsldPvcCtrlSrcRP MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frsldPvcCtrlDstRP MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frsldPvcCtrlDelayFrSize MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frsldPvcCtrlDelayLoc MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frsldPvcCtrlDeliveryLoc MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { frsldMIBCompliances 1 } -- -- Units of Conformance -- frsldPvcReqCtrlGroup OBJECT-GROUP OBJECTS { frsldPvcCtrlSrcRP, frsldPvcCtrlDstRP, Expires December 1999 Steinberger & Nicklass [Page 29] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 frsldPvcCtrlDelayLoc, frsldPvcCtrlDelayFrSize, frsldPvcCtrlDelayType, frsldPvcCtrlDeliveryLoc } STATUS current DESCRIPTION "A collection of required objects providing control information applicable to a PVC which implements Service Level Definitions." ::= { frsldMIBGroups 1 } frsldPvcOptCtrlGroup OBJECT-GROUP OBJECTS { frsldPvcCtrlStatus, frsldPvcCtrlPacketFreq, frsldPvcCtrlDelayTimeOut, frsldPvcCtrlDataColPackets, frsldPvcCtrlAvailColPeriod, frsldPvcCtrlDataBuckets, frsldPvcCtrlDataBucketsGranted, frsldPvcCtrlAvailBuckets, frsldPvcCtrlAvailBucketsGranted } STATUS current DESCRIPTION "A collection of optional objects providing control information applicable to a PVC which implements Service Level Definitions." ::= { frsldMIBGroups 2 } frsldPvcReqDataGroup OBJECT-GROUP OBJECTS { frsldPvcDataDelayAvg, frsldPvcDataFrDeliveredC, frsldPvcDataFrDeliveredE, frsldPvcDataFrOfferedC, frsldPvcDataFrOfferedE, frsldPvcDataDataDeliveredC, frsldPvcDataDataDeliveredE, frsldPvcDataDataOfferedC, frsldPvcDataDataOfferedE, frsldPvcDataUnavailableTime, frsldPvcDataUnavailables } STATUS current DESCRIPTION "A collection of required objects providing data Expires December 1999 Steinberger & Nicklass [Page 30] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 collected on a a PVC which implements Service Level Definitions." ::= { frsldMIBGroups 3 } frsldPvcDataOptGroup OBJECT-GROUP OBJECTS { frsldPvcDataDelayMin, frsldPvcDataDelayMax, frsldPvcDataMissedPolls } STATUS current DESCRIPTION "A collection of optional objects providing data collected on a a PVC which implements Service Level Definitions." ::= { frsldMIBGroups 4 } frsldPvcSampleOptGroup OBJECT-GROUP OBJECTS { frsldPvcDataDelaySmplMin, frsldPvcDataDelaySmplMax, frsldPvcDataDelaySmplAvg, frsldPvcDataSmplMissedPolls, frsldPvcDataSmplFrDeliveredC, frsldPvcDataSmplFrDeliveredE, frsldPvcDataSmplFrOfferedC, frsldPvcDataSmplFrOfferedE, frsldPvcDataSmplDataDeliveredC, frsldPvcDataSmplDataDeliveredE, frsldPvcDataSmplDataOfferedC, frsldPvcDataSmplDataOfferedE, frsldPvcDataSmplStartTime, frsldPvcDataSmplEndTime, frsldPvcAvailSmplUnavailableTime, frsldPvcAvailSmplUnavailables, frsldPvcAvailSmplStartTime, frsldPvcAvailSmplEndTime } STATUS current DESCRIPTION "A collection of optional objects providing the ability to sample the data collected on a PVC which implements Service Level Definitions." ::= { frsldMIBGroups 5 } END Expires December 1999 Steinberger & Nicklass [Page 31] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 4. Acknowledgments This document was produced by the Frame Relay Service MIB Working Group. It is based on the Frame Relay Forum's implementation agreement on service level definations, FRF.13 [17]. Expires December 1999 Steinberger & Nicklass [Page 32] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 5. References [1] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture for Describing SNMP Management Frameworks, RFC 2571, Cabletron Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 [2] Rose, M., and K. McCloghrie, Structure and Identification of Management Information for TCP/IP-based Internets, RFC 1155, STD 16, Performance Systems International, Hughes LAN Systems, May 1990 [3] Rose, M., and K. McCloghrie, Concise MIB Definitions, RFC 1212, STD 16, Performance Systems International, Hughes LAN Systems, March 1991 [4] M. Rose, A Convention for Defining Traps for use with the SNMP, RFC 1215, Performance Systems International, March 1991 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, Structure of Management Information Version 2 (SMIv2), RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First Virtual Holdings, International Network Services, April 1999 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, Textual Conventions for SMIv2, RFC 2579, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First Virtual Holdings, International Network Services, April 1999 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, Conformance Statements for SMIv2, RFC 2580, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First Virtual Holdings, International Network Services, April 1999 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, Simple Network Management Protocol, RFC 1157, STD 15, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990. [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, Introduction to Community-based SNMPv2, RFC 1901, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [10]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2), RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January Expires December 1999 Steinberger & Nicklass [Page 33] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 1996. [11]Case, J., Harrington D., Presuhn R., and B. Wijnen, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP), RFC 2572, SNMP Research, Inc., Cabletron Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 [12]Blumenthal, U., and B. Wijnen, User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3), RFC 2574, IBM T. J. Watson Research, April 1999 [13]Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2), RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [14]Levi, D., Meyer, P., and B. Stewart, SNMPv3 Applications, RFC 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, April 1999 [15]Wijnen, B., Presuhn, R., and K. McCloghrie, View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., Cisco Systems, Inc., April 1999 [16]Case, J., Mundy, R., Partain, D., and B. Stewart, Introduction to Version 3 of the Internet-standard Network Management Framework, RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc., Ericsson, Cisco Systems, April 1999 [17]Frame Relay Forum Technical Committee, Service Level Definitions Implementations Agreement, FRF.13, August 1998. [18]Brown, T., Definitions of Managed Objects for Frame Relay Service, RFC 1604, Bell Communications Research, March 1994. [19]Waldbusser, S., Remote Network Monitoring Management Information Base Version 2 using SMIv2, RFC 2021, INS, January 1997. Expires December 1999 Steinberger & Nicklass [Page 34] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 6. Security Considerations There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2274 [12] and the View-based Access Control Model RFC 2275 [15] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 7. Authors' Addresses Robert Steinberger Paradyne Corporation Mailstop: LG-132 8545 126th Avenue North Largo, FL USA 33773 Phone: 1(813)530-2395 Email: rsteinberger@paradyne.com Orly Nicklass, Ph.D RAD Data Commincations Ltd. 12 Hanechoshet Street Tel Aviv, Israel 69710 Phone: 972 3 6459588 Email: orly@radmail.rad.co.il Expires December 1999 Steinberger & Nicklass [Page 35] Internet Draft Frame Relay Service Level Definitions MIB June 23, 1999 8. Copyright Section Copyright (C) The Internet Society (1999). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an AS IS basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Expires December 1999 Steinberger & Nicklass [Page 36]