Internet Draft RSVP MIB November 1996 RSVP Management Information Base draft-ietf-rsvp-mib-03.txt Fri Nov 1 14:17:05 PST 1996 Fred Baker Cisco Systems 519 Lado Drive Santa Barbara, California 93111 fred@cisco.com John Krawczyk Bay Networks, Inc 2 Federal Street Billerica, Massachusetts 01821 jj@BayNetworks.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." Please check the I-D abstract listing contained in each Internet Draft directory to learn the current status of this or any other Internet Draft. Baker and Krawczyk Expires May 1997 [Page 1] Internet Draft RSVP MIB November 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 the Resource Reservation Protocol (RSVP) within the interface attributes defined in the Integrated Services Model. Thus, the Integrated Services MIB is directly relevant to and cross-referenced by this MIB. Comments should be made to the RSVP Working Group, rsvp@isi.edu. This memo does not, in its draft form, specify a standard for the Internet community. Baker and Krawczyk Expires May 1997 [Page 2] Internet Draft RSVP MIB November 1996 3. The SNMPv2 Network Management Framework The SNMPv2 Network Management Framework consists of four major components. They are: o RFC 1441 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. o RFC 1213 defines MIB-II, the core set of managed objects for the Internet suite of protocols. o RFC 1445 which defines the administrative and other architectural aspects of the framework. o RFC 1448 which defines the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 3.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or 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, 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, we often use a textual string, termed the descriptor, to refer to the object type. 4. Overview 4.1. Textual Conventions Several new data types are introduced as a textual convention in this MIB document. These textual conventions enhance the readability of the specification and can ease comparison with other specifications if appropriate. It should be noted that the introduction of the these textual conventions has no effect on either the syntax nor the semantics of any managed Baker and Krawczyk Expires May 1997 [Page 3] Internet Draft RSVP MIB November 1996 objects. The use of these is merely an artifact of the explanatory method used. Objects defined in terms of one of these methods are always encoded by means of the rules that define the primitive type. Hence, no changes to the SMI or the SNMP are necessary to accommodate these textual conventions which are adopted merely for the convenience of readers and writers in pursuit of the elusive goal of clear, concise, and unambiguous MIB documents. 4.2. Structure of MIB The MIB is composed of the following sections: General Objects Session Statistics Table Session Sender Table Reservation Requests Received Table Reservation Requests Forwarded Table RSVP Active Flows Table RSVP Interface Attributes Table RSVP Neighbor Table As a general rule, it is difficult in SNMP to describe arbitrarily long of complex messages; this MIB therefore seeks to describe the Path State Database and the Reservation State Database as though each flow and filter description received in an aggregate message had been received in a separate reservation message. Thus, if a RESV message is received for session 224.1.2.3+UDP+4455 with two filter/flow spec groups describing a sender 1.2.3.4 and another sender 1.2.7.8, these two will show in the MIB as two separate rows: one for 224.1.2.3+UDP+4455 from 1.2.3.4 and the other for 224.1.2.3+UDP+4455 from 1.2.7.8. Baker and Krawczyk Expires May 1997 [Page 4] Internet Draft RSVP MIB November 1996 5. Definitions RSVP-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Gauge32, NOTIFICATION-TYPE, Integer32, experimental FROM SNMPv2-SMI TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeStamp, TestAndIncr, TimeInterval FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF BitRate, BurstSize FROM INTEGRATED-SERVICES-MIB ifIndex, InterfaceIndex FROM IF-MIB; rsvp MODULE-IDENTITY LAST-UPDATED "9511030500Z" -- Fri Nov 1 14:17:05 PST 1996 ORGANIZATION "IETF RSVP Working Group" CONTACT-INFO " Fred Baker Postal: Cisco Systems 519 Lado Drive Santa Barbara, California 93111 Tel: +1 805 681 0115 E-Mail: fred@cisco.com John Krawczyk Postal: Bay Networks, Inc 2 Federal Street Billerica, Massachusetts 01821 Tel: +1 508 916 3811 E-Mail: jj@BayNetworks.com" DESCRIPTION "The MIB module to describe the RSVP Protocol" ::= { experimental 71 } rsvpObjects OBJECT IDENTIFIER ::= { rsvp 1 } -- tables rsvpGenObjects OBJECT IDENTIFIER ::= { rsvp 2 } -- global objects rsvpNotifications OBJECT IDENTIFIER ::= { rsvp 3 } -- traps rsvpConformance OBJECT IDENTIFIER ::= { rsvp 4 } -- conformance Baker and Krawczyk Expires May 1997 [Page 5] Internet Draft RSVP MIB November 1996 SessionNumber ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The Session Number convention is used for numbers identifying sessions or saved PATH or RESV information. It is a number in the range returned by a TestAndIncr variable, having no protocol meaning whatsoever but serving instead as simple identifier. The alternative was a very complex instance or instance object that became unwieldy." SYNTAX INTEGER (0..2147483647) Protocol ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The value of the IP Protocol field of an IP Datagram Header. This identifies the protocol layer above IP. For example, the value 6 is used for TCP and the value 17 is used for UDP. The values of this field are defined in the As- signed Numbers RFC." SYNTAX INTEGER (1..255) SessionType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The value of the C-Type field of a Session ob- ject, as defined in the RSVP specification. This value determines the lengths of octet strings and use of certain objects such as the 'port' variables. If the C-Type calls for an IP6 address, one would expect all source, des- tination, and next/previous hop addresses to be 16 bytes long, and for the ports to be UDP/TCP port numbers, for example." SYNTAX INTEGER (1..255) Baker and Krawczyk Expires May 1997 [Page 6] Internet Draft RSVP MIB November 1996 Port ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The value of the UDP or TCP Source or Destina- tion Port field, a virtual destination port or generalized port identifier used with the IPSEC Authentication Header or Encapsulating Security Payload, or other session discriminator. If it is not used, the value should be of length 0. This pair, when coupled with the IP Addresses of the source and destination system and the IP protocol field, uniquely identifies a data stream." SYNTAX OCTET STRING RsvpEncapsulation ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This indicates the encapsulation that an RSVP Neighbor is perceived to be using." SYNTAX INTEGER { ip (1), -- IP Protocol 46 udp (2), -- UDP Encapsulation both (3) -- neighbor is using both encapsulations } RefreshInterval ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The number of milliseconds that are expected to elapse between refreshes of path or reserva- tion state. Unrefreshed Path or reservation state is removed after a small multiple of this period." SYNTAX INTEGER (0..'7FFFFFFF'h) Baker and Krawczyk Expires May 1997 [Page 7] Internet Draft RSVP MIB November 1996 QosService ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The class of service in use by a flow." SYNTAX INTEGER { guaranteedDelay (2), -- Guaranteed Delay controlledLoad (5) -- Controlled Load } MessageSize ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The size of a message in bytes. This is used to specify the minimum and maximum size of a message along an integrated services route." SYNTAX INTEGER (0..'7FFFFFFF'h) Baker and Krawczyk Expires May 1997 [Page 8] Internet Draft RSVP MIB November 1996 -- The RSVP Session Statistics Database displays statistics -- relating to the number of senders and receivers in each -- session. rsvpSessionNewIndex OBJECT-TYPE SYNTAX TestAndIncr MAX-ACCESS read-write STATUS current DESCRIPTION "This object is used to assign values to rsvpSessionNumber as described in 'Textual Con- ventions for SNMPv2'. The network manager reads the object, and then writes the value back in the SET that creates a new instance of rsvpSessionEntry. If the SET fails with the code 'inconsistentValue', then the process must be repeated; If the SET succeeds, then the ob- ject is incremented, and the new instance is created according to the manager's directions." ::= { rsvpGenObjects 1 } rsvpSessionTable OBJECT-TYPE SYNTAX SEQUENCE OF RsvpSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Statistics concerning the sessions seen by a given system." ::= { rsvpObjects 1 } rsvpSessionEntry OBJECT-TYPE SYNTAX RsvpSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Statistics concerning a single RSVP session seen by a given system." INDEX { rsvpSessionNumber } ::= { rsvpSessionTable 1 } Baker and Krawczyk Expires May 1997 [Page 9] Internet Draft RSVP MIB November 1996 RsvpSessionEntry ::= SEQUENCE { rsvpSessionNumber SessionNumber, rsvpSessionType SessionType, rsvpSessionDestAddr OCTET STRING, rsvpSessionProtocol Protocol, rsvpSessionPort Port, rsvpSessionSenders Gauge32, rsvpSessionReceivers Gauge32, rsvpSessionRequests Gauge32 } rsvpSessionNumber OBJECT-TYPE SYNTAX SessionNumber MAX-ACCESS not-accessible STATUS current DESCRIPTION "The number of this session. This is for SNMP Indexing purposes only and has no relation to any protocol value." ::= { rsvpSessionEntry 1 } rsvpSessionType OBJECT-TYPE SYNTAX SessionType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of session (IP4, IP6, IP6 with flow information, etc)." ::= { rsvpSessionEntry 2 } rsvpSessionDestAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The destination address used by all senders in this session." ::= { rsvpSessionEntry 3 } Baker and Krawczyk Expires May 1997 [Page 10] Internet Draft RSVP MIB November 1996 rsvpSessionProtocol OBJECT-TYPE SYNTAX Protocol MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Protocol used by this session." ::= { rsvpSessionEntry 4 } rsvpSessionPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a destina- tion port for all senders in this session. If the IP protocol in use, specified by rsvpSen- derProtocol, is 50 (ESP) or 51 (AH), this represents a virtual destination port number. A value of zero indicates that the IP protocol in use does not have ports." ::= { rsvpSessionEntry 5 } rsvpSessionSenders OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of senders currently known to be part of this session." ::= { rsvpSessionEntry 6 } rsvpSessionReceivers OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of reservations being requested of this system for this session." ::= { rsvpSessionEntry 7 } Baker and Krawczyk Expires May 1997 [Page 11] Internet Draft RSVP MIB November 1996 rsvpSessionRequests OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of reservation requests this system is sending upstream for this session." ::= { rsvpSessionEntry 8 } -- Note that this is a read only table. If the corresponding -- rsvpSenderTable, rsvpResvTable, and rsvpReqTable entries all -- are removed, this entry goes away also. Baker and Krawczyk Expires May 1997 [Page 12] Internet Draft RSVP MIB November 1996 -- The RSVP Session Sender Database contains the information -- displayed by senders regarding their potential contribution -- to session data content. It is in essence a list of the -- valid PATH messages that the RSVP Router or Host is receiving. rsvpSenderNewIndex OBJECT-TYPE SYNTAX TestAndIncr MAX-ACCESS read-write STATUS current DESCRIPTION "This object is used to assign values to rsvpSenderNumber as described in 'Textual Con- ventions for SNMPv2'. The network manager reads the object, and then writes the value back in the SET that creates a new instance of rsvpSenderEntry. If the SET fails with the code 'inconsistentValue', then the process must be repeated; If the SET succeeds, then the ob- ject is incremented, and the new instance is created according to the manager's directions." ::= { rsvpGenObjects 2 } rsvpSenderTable OBJECT-TYPE SYNTAX SEQUENCE OF RsvpSenderEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the state information displayed by senders in PATH messages." ::= { rsvpObjects 2 } rsvpSenderEntry OBJECT-TYPE SYNTAX RsvpSenderEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the state information displayed by a single sender's PATH message." INDEX { rsvpSessionNumber, rsvpSenderNumber } ::= { rsvpSenderTable 1 } RsvpSenderEntry ::= Baker and Krawczyk Expires May 1997 [Page 13] Internet Draft RSVP MIB November 1996 SEQUENCE { rsvpSenderNumber SessionNumber, rsvpSenderType SessionType, rsvpSenderDestAddr OCTET STRING, rsvpSenderSenderAddr OCTET STRING, rsvpSenderProtocol Protocol, rsvpSenderDestPort Port, rsvpSenderPort Port, rsvpSenderHopAddr OCTET STRING, rsvpSenderHopLih Integer32, rsvpSenderInterface InterfaceIndex, rsvpSenderTSpecRate BitRate, rsvpSenderTSpecPeakRate BitRate, rsvpSenderTSpecBurst BurstSize, rsvpSenderTSpecMinTU MessageSize, rsvpSenderTSpecMaxTU MessageSize, rsvpSenderInterval RefreshInterval, rsvpSenderRSVPHop TruthValue, rsvpSenderLastChange TimeStamp, rsvpSenderPolicy OCTET STRING, rsvpSenderAdspecBreak TruthValue, rsvpSenderAdspecHopCount INTEGER, rsvpSenderAdspecPathBw BitRate, rsvpSenderAdspecMinLatency Integer32, rsvpSenderAdspecMtu INTEGER, rsvpSenderAdspecGuaranteedSvc TruthValue, rsvpSenderAdspecGuaranteedBreak TruthValue, rsvpSenderAdspecGuaranteedCtot Integer32, rsvpSenderAdspecGuaranteedDtot Integer32, rsvpSenderAdspecGuaranteedCsum Integer32, rsvpSenderAdspecGuaranteedDsum Integer32, rsvpSenderAdspecGuaranteedHopCount INTEGER, rsvpSenderAdspecGuaranteedPathBw BitRate, rsvpSenderAdspecGuaranteedMinLatency Integer32, rsvpSenderAdspecGuaranteedMtu INTEGER, rsvpSenderAdspecCtrlLoadSvc TruthValue, rsvpSenderAdspecCtrlLoadBreak TruthValue, rsvpSenderAdspecCtrlLoadHopCount INTEGER, rsvpSenderAdspecCtrlLoadPathBw BitRate, rsvpSenderAdspecCtrlLoadMinLatency Integer32, rsvpSenderAdspecCtrlLoadMtu INTEGER, rsvpSenderStatus RowStatus } Baker and Krawczyk Expires May 1997 [Page 14] Internet Draft RSVP MIB November 1996 rsvpSenderNumber OBJECT-TYPE SYNTAX SessionNumber MAX-ACCESS not-accessible STATUS current DESCRIPTION "The number of this sender. This is for SNMP Indexing purposes only and has no relation to any protocol vaalue." ::= { rsvpSenderEntry 1 } rsvpSenderType OBJECT-TYPE SYNTAX SessionType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of session (IP4, IP6, IP6 with flow information, etc)." ::= { rsvpSenderEntry 2 } rsvpSenderDestAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The destination address used by all senders in this session." ::= { rsvpSenderEntry 3 } rsvpSenderSenderAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The source address used by this sender in this session." ::= { rsvpSenderEntry 4 } Baker and Krawczyk Expires May 1997 [Page 15] Internet Draft RSVP MIB November 1996 rsvpSenderProtocol OBJECT-TYPE SYNTAX Protocol MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Protocol used by this session." ::= { rsvpSenderEntry 5 } rsvpSenderDestPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a destina- tion port for all senders in this session. If the IP protocol in use, specified by rsvpSen- derProtocol, is 50 (ESP) or 51 (AH), this represents a virtual destination port number. A value of zero indicates that the IP protocol in use does not have ports." ::= { rsvpSenderEntry 6 } rsvpSenderPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a source port for this sender in this session. If the IP protocol in use, specified by rsvpSenderPro- tocol is 50 (ESP) or 51 (AH), this represents a generalized port identifier (GPI). A value of zero indicates that the IP protocol in use does not have ports." ::= { rsvpSenderEntry 7 } Baker and Krawczyk Expires May 1997 [Page 16] Internet Draft RSVP MIB November 1996 rsvpSenderHopAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The address used by the previous RSVP hop (which may be the original sender)." ::= { rsvpSenderEntry 8 } rsvpSenderHopLih OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The Logical Interface Handle used by the pre- vious RSVP hop (which may be the original sender)." ::= { rsvpSenderEntry 9 } rsvpSenderInterface OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-create STATUS current DESCRIPTION "The ifIndex value of the interface on which this PATH message was most recently received." ::= { rsvpSenderEntry 10 } Baker and Krawczyk Expires May 1997 [Page 17] Internet Draft RSVP MIB November 1996 rsvpSenderTSpecRate OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The Average Bit Rate of the sender's data stream. Within a transmission burst, the ar- rival rate may be as fast as rsvpSenderTSpec- PeakRate (if supported by the service model); however, averaged across two or more burst in- tervals, the rate should not exceed rsvpSen- derTSpecRate. Note that this is a prediction, often based on the general capability of a type of codec or particular encoding; the measured average rate may be significantly lower." ::= { rsvpSenderEntry 11 } rsvpSenderTSpecPeakRate OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The Peak Bit Rate of the sender's data stream. Traffic arrival is not expected to exceed this rate at any time, apart from the effects of jitter in the network. If not specified in the TSpec, this returns zero or noSuchValue." ::= { rsvpSenderEntry 12 } rsvpSenderTSpecBurst OBJECT-TYPE SYNTAX BurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The size of the largest burst expected from the sender at a time." ::= { rsvpSenderEntry 13 } Baker and Krawczyk Expires May 1997 [Page 18] Internet Draft RSVP MIB November 1996 rsvpSenderTSpecMinTU OBJECT-TYPE SYNTAX MessageSize MAX-ACCESS read-create STATUS current DESCRIPTION "The minimum message size for this flow. The policing algorithm will treat smaller messages as though they are this size." ::= { rsvpSenderEntry 14 } rsvpSenderTSpecMaxTU OBJECT-TYPE SYNTAX MessageSize MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum message size for this flow. The admission algorithm will reject TSpecs whose Maximum Transmission Unit, plus the interface headers, exceed the interface MTU." ::= { rsvpSenderEntry 15 } rsvpSenderInterval OBJECT-TYPE SYNTAX RefreshInterval MAX-ACCESS read-create STATUS current DESCRIPTION "The interval between refresh messages as ad- vertised by the Previous Hop." ::= { rsvpSenderEntry 16 } rsvpSenderRSVPHop OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, the node believes that the previous IP hop is an RSVP hop. If FALSE, the node be- lieves that the previous IP hop may not be an RSVP hop." ::= { rsvpSenderEntry 17 } Baker and Krawczyk Expires May 1997 [Page 19] Internet Draft RSVP MIB November 1996 rsvpSenderLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The time of the last change in this PATH mes- sage; This is either the first time it was re- ceived or the time of the most recent change in parameters." ::= { rsvpSenderEntry 18 } rsvpSenderPolicy OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The contents of the policy object, displayed as an uninterpreted string of octets, including the object header. In the absence of such an object, this should be of zero length." ::= { rsvpSenderEntry 19 } rsvpSenderAdspecBreak OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "The global break bit general characterization parameter from the ADSPEC. If TRUE, at least one non-IS hop was detected in the path. If FALSE, no non-IS hops were detected." ::= { rsvpSenderEntry 20 } Baker and Krawczyk Expires May 1997 [Page 20] Internet Draft RSVP MIB November 1996 rsvpSenderAdspecHopCount OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The hop count general characterization parame- ter from the ADSPEC. A return of zero or noSuchValue indicates one of the following con- ditions: the invalid bit was set the parameter was not present" ::= { rsvpSenderEntry 21 } rsvpSenderAdspecPathBw OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The path bandwidth estimate general character- ization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the fol- lowing conditions: the invalid bit was set the parameter was not present" ::= { rsvpSenderEntry 22 } Baker and Krawczyk Expires May 1997 [Page 21] Internet Draft RSVP MIB November 1996 rsvpSenderAdspecMinLatency OBJECT-TYPE SYNTAX Integer32 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The minimum path latency general characteriza- tion parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the fol- lowing conditions: the invalid bit was set the parameter was not present" ::= { rsvpSenderEntry 23 } rsvpSenderAdspecMtu OBJECT-TYPE SYNTAX INTEGER (0..65535) UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The composed Maximum Transmission Unit general characterization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following conditions: the invalid bit was set the parameter was not present" ::= { rsvpSenderEntry 24 } rsvpSenderAdspecGuaranteedSvc OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, the ADSPEC contains a Guaranteed Ser- vice fragment. If FALSE, the ADSPEC does not contain a Guaranteed Service fragment." ::= { rsvpSenderEntry 25 } Baker and Krawczyk Expires May 1997 [Page 22] Internet Draft RSVP MIB November 1996 rsvpSenderAdspecGuaranteedBreak OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, the Guaranteed Service fragment has its 'break' bit set, indicating that one or more nodes along the path do not support the guaranteed service. If FALSE, and rsvpSen- derAdspecGuaranteedSvc is TRUE, the 'break' bit is not set. If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns FALSE or noSuchValue." ::= { rsvpSenderEntry 26 } rsvpSenderAdspecGuaranteedCtot OBJECT-TYPE SYNTAX Integer32 UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the end-to-end composed value for the guaranteed service 'C' parameter. A return of zero or noSuchValue indicates one of the fol- lowing conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 27 } Baker and Krawczyk Expires May 1997 [Page 23] Internet Draft RSVP MIB November 1996 rsvpSenderAdspecGuaranteedDtot OBJECT-TYPE SYNTAX Integer32 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the end-to-end composed value for the guaranteed service 'D' parameter. A return of zero or noSuchValue indicates one of the fol- lowing conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 28 } rsvpSenderAdspecGuaranteedCsum OBJECT-TYPE SYNTAX Integer32 UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the composed value for the guaranteed ser- vice 'C' parameter since the last reshaping point. A return of zero or noSuchValue indi- cates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 29 } Baker and Krawczyk Expires May 1997 [Page 24] Internet Draft RSVP MIB November 1996 rsvpSenderAdspecGuaranteedDsum OBJECT-TYPE SYNTAX Integer32 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the composed value for the guaranteed ser- vice 'D' parameter since the last reshaping point. A return of zero or noSuchValue indi- cates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 30 } rsvpSenderAdspecGuaranteedHopCount OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the service-specific override of the hop count general characterization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 31 } Baker and Krawczyk Expires May 1997 [Page 25] Internet Draft RSVP MIB November 1996 rsvpSenderAdspecGuaranteedPathBw OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the service-specific override of the path bandwidth estimate general characterization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following con- ditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 32 } rsvpSenderAdspecGuaranteedMinLatency OBJECT-TYPE SYNTAX Integer32 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the service-specific override of the minimum path latency general characterization parameter from the ADSPEC. A return of zero or noSuch- Value indicates one of the following condi- tions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 33 } Baker and Krawczyk Expires May 1997 [Page 26] Internet Draft RSVP MIB November 1996 rsvpSenderAdspecGuaranteedMtu OBJECT-TYPE SYNTAX INTEGER (0..65535) UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the service-specific override of the com- posed Maximum Transmission Unit general charac- terization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 34 } rsvpSenderAdspecCtrlLoadSvc OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, the ADSPEC contains a Controlled Load Service fragment. If FALSE, the ADSPEC does not contain a Controlled Load Service frag- ment." ::= { rsvpSenderEntry 35 } Baker and Krawczyk Expires May 1997 [Page 27] Internet Draft RSVP MIB November 1996 rsvpSenderAdspecCtrlLoadBreak OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, the Controlled Load Service fragment has its 'break' bit set, indicating that one or more nodes along the path do not support the controlled load service. If FALSE, and rsvpSenderAdspecCtrlLoadSvc is TRUE, the 'break' bit is not set. If rsvpSenderAdspecCtrlLoadSvc is FALSE, this returns FALSE or noSuchValue." ::= { rsvpSenderEntry 36 } rsvpSenderAdspecCtrlLoadHopCount OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this is the service-specific override of the hop count general characterization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecCtrlLoadSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 37 } Baker and Krawczyk Expires May 1997 [Page 28] Internet Draft RSVP MIB November 1996 rsvpSenderAdspecCtrlLoadPathBw OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this is the service-specific override of the path bandwidth estimate general characterization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following con- ditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecCtrlLoadSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 38 } rsvpSenderAdspecCtrlLoadMinLatency OBJECT-TYPE SYNTAX Integer32 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this is the service-specific override of the minimum path latency general characterization parameter from the ADSPEC. A return of zero or noSuch- Value indicates one of the following condi- tions: the invalid bit was set the parameter was not present If rsvpSenderAdspecCtrlLoadSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 39 } Baker and Krawczyk Expires May 1997 [Page 29] Internet Draft RSVP MIB November 1996 rsvpSenderAdspecCtrlLoadMtu OBJECT-TYPE SYNTAX INTEGER (0..65535) UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this is the service-specific override of the com- posed Maximum Transmission Unit general charac- terization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecCtrlLoadSvc is FALSE, this returns zero or noSuchValue." ::= { rsvpSenderEntry 40 } rsvpSenderStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "'valid' for all active PATH messages. This object may be used to install static PATH in- formation or delete PATH information." ::= { rsvpSenderEntry 41 } Baker and Krawczyk Expires May 1997 [Page 30] Internet Draft RSVP MIB November 1996 -- The RSVP Reservation Requests Received Table contains the -- information displayed by receivers regarding their needs with -- respect to sessions and senders. It is in essence a list of the -- valid RESV messages that the RSVP Router or Host is receiving. rsvpResvNewIndex OBJECT-TYPE SYNTAX TestAndIncr MAX-ACCESS read-write STATUS current DESCRIPTION "This object is used to assign values to rsvpResvNumber as described in 'Textual Conven- tions for SNMPv2'. The network manager reads the object, and then writes the value back in the SET that creates a new instance of rsvpResvEntry. If the SET fails with the code 'inconsistentValue', then the process must be repeated; If the SET succeeds, then the object is incremented, and the new instance is created according to the manager's directions." ::= { rsvpGenObjects 3 } rsvpResvTable OBJECT-TYPE SYNTAX SEQUENCE OF RsvpResvEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the state information displayed by receivers in RESV messages." ::= { rsvpObjects 3 } rsvpResvEntry OBJECT-TYPE SYNTAX RsvpResvEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the state information displayed by a single receiver's RESV message concerning a single sender." INDEX { rsvpSessionNumber, rsvpResvNumber } ::= { rsvpResvTable 1 } Baker and Krawczyk Expires May 1997 [Page 31] Internet Draft RSVP MIB November 1996 RsvpResvEntry ::= SEQUENCE { rsvpResvNumber SessionNumber, rsvpResvType SessionType, rsvpResvDestAddr OCTET STRING, rsvpResvSenderAddr OCTET STRING, rsvpResvProtocol Protocol, rsvpResvDestPort Port, rsvpResvPort Port, rsvpResvHopAddr OCTET STRING, rsvpResvHopLih Integer32, rsvpResvInterface InterfaceIndex, rsvpResvService QosService, rsvpResvTSpecRate BitRate, rsvpResvTSpecPeakRate BitRate, rsvpResvTSpecBurst BurstSize, rsvpResvTSpecMinTU MessageSize, rsvpResvTSpecMaxTU MessageSize, rsvpResvRSpecRate BitRate, rsvpResvRSpecSlack Integer32, rsvpResvInterval RefreshInterval, rsvpResvScope OCTET STRING, rsvpResvShared TruthValue, rsvpResvExplicit TruthValue, rsvpResvRSVPHop TruthValue, rsvpResvLastChange TimeStamp, rsvpResvPolicy OCTET STRING, rsvpResvStatus RowStatus } rsvpResvNumber OBJECT-TYPE SYNTAX SessionNumber MAX-ACCESS not-accessible STATUS current DESCRIPTION "The number of this reservation request. This is for SNMP Indexing purposes only and has no relation to any protocol value." ::= { rsvpResvEntry 1 } Baker and Krawczyk Expires May 1997 [Page 32] Internet Draft RSVP MIB November 1996 rsvpResvType OBJECT-TYPE SYNTAX SessionType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of session (IP4, IP6, IP6 with flow information, etc)." ::= { rsvpResvEntry 2 } rsvpResvDestAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The destination address used by all senders in this session." ::= { rsvpResvEntry 3 } rsvpResvSenderAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The source address of the sender selected by this reservation. The value of all zeroes in- dicates 'all senders'." ::= { rsvpResvEntry 4 } rsvpResvProtocol OBJECT-TYPE SYNTAX Protocol MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Protocol used by this session." ::= { rsvpResvEntry 5 } Baker and Krawczyk Expires May 1997 [Page 33] Internet Draft RSVP MIB November 1996 rsvpResvDestPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a destina- tion port for all senders in this session. If the IP protocol in use, specified by rsvpResvProtocol, is 50 (ESP) or 51 (AH), this represents a virtual destination port number. A value of zero indicates that the IP protocol in use does not have ports." ::= { rsvpResvEntry 6 } rsvpResvPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a source port for this sender in this session. If the IP protocol in use, specified by rsvpResvProto- col is 50 (ESP) or 51 (AH), this represents a generalized port identifier (GPI). A value of zero indicates that the IP protocol in use does not have ports." ::= { rsvpResvEntry 7 } rsvpResvHopAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The address used by the next RSVP hop (which may be the ultimate receiver)." ::= { rsvpResvEntry 8 } Baker and Krawczyk Expires May 1997 [Page 34] Internet Draft RSVP MIB November 1996 rsvpResvHopLih OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The Logical Interface Handle received from the previous RSVP hop (which may be the ultimate receiver)." ::= { rsvpResvEntry 9 } rsvpResvInterface OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-create STATUS current DESCRIPTION "The ifIndex value of the interface on which this RESV message was most recently received." ::= { rsvpResvEntry 10 } rsvpResvService OBJECT-TYPE SYNTAX QosService MAX-ACCESS read-create STATUS current DESCRIPTION "The QoS Service classification requested by the receiver." ::= { rsvpResvEntry 11 } Baker and Krawczyk Expires May 1997 [Page 35] Internet Draft RSVP MIB November 1996 rsvpResvTSpecRate OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The Average Bit Rate of the sender's data stream. Within a transmission burst, the ar- rival rate may be as fast as rsvpResvTSpec- PeakRate (if supported by the service model); however, averaged across two or more burst in- tervals, the rate should not exceed rsvpResvTSpecRate. Note that this is a prediction, often based on the general capability of a type of codec or particular encoding; the measured average rate may be significantly lower." ::= { rsvpResvEntry 12 } rsvpResvTSpecPeakRate OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The Peak Bit Rate of the sender's data stream. Traffic arrival is not expected to exceed this rate at any time, apart from the effects of jitter in the network. If not specified in the TSpec, this returns zero or noSuchValue." ::= { rsvpResvEntry 13 } Baker and Krawczyk Expires May 1997 [Page 36] Internet Draft RSVP MIB November 1996 rsvpResvTSpecBurst OBJECT-TYPE SYNTAX BurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The size of the largest burst expected from the sender at a time. If this is less than the sender's advertised burst size, the receiver is asking the network to provide flow pacing beyond what would be provided under normal circumstances. Such pac- ing is at the network's option." ::= { rsvpResvEntry 14 } rsvpResvTSpecMinTU OBJECT-TYPE SYNTAX MessageSize MAX-ACCESS read-create STATUS current DESCRIPTION "The minimum message size for this flow. The policing algorithm will treat smaller messages as though they are this size." ::= { rsvpResvEntry 15 } rsvpResvTSpecMaxTU OBJECT-TYPE SYNTAX MessageSize MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum message size for this flow. The admission algorithm will reject TSpecs whose Maximum Transmission Unit, plus the interface headers, exceed the interface MTU." ::= { rsvpResvEntry 16 } Baker and Krawczyk Expires May 1997 [Page 37] Internet Draft RSVP MIB November 1996 rsvpResvRSpecRate OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "If the requested service is Guaranteed, as specified by rsvpResvService, this is the clearing rate that is being requested. Other- wise, it is zero, or the agent may return noSuchValue." ::= { rsvpResvEntry 17 } rsvpResvRSpecSlack OBJECT-TYPE SYNTAX Integer32 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "If the requested service is Guaranteed, as specified by rsvpResvService, this is the delay slack. Otherwise, it is zero, or the agent may return noSuchValue." ::= { rsvpResvEntry 18 } rsvpResvInterval OBJECT-TYPE SYNTAX RefreshInterval MAX-ACCESS read-create STATUS current DESCRIPTION "The interval between refresh messages as ad- vertised by the Next Hop." ::= { rsvpResvEntry 19 } Baker and Krawczyk Expires May 1997 [Page 38] Internet Draft RSVP MIB November 1996 rsvpResvScope OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The contents of the scope object, displayed as an uninterpreted string of octets, including the object header. In the absence of such an object, this should be of zero length. If the length is non-zero, this contains a series of IP4 or IP6 addresses." ::= { rsvpResvEntry 20 } rsvpResvShared OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, a reservation shared among senders is requested. If FALSE, a reservation specific to this sender is requested." ::= { rsvpResvEntry 21 } rsvpResvExplicit OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, individual senders are listed using Filter Specifications. If FALSE, all senders are implicitly selected. The Scope Object will contain a list of senders that need to receive this reservation request for the purpose of routing the RESV message." ::= { rsvpResvEntry 22 } Baker and Krawczyk Expires May 1997 [Page 39] Internet Draft RSVP MIB November 1996 rsvpResvRSVPHop OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, the node believes that the previous IP hop is an RSVP hop. If FALSE, the node be- lieves that the previous IP hop may not be an RSVP hop." ::= { rsvpResvEntry 23 } rsvpResvLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The time of the last change in this reserva- tion request; This is either the first time it was received or the time of the most recent change in parameters." ::= { rsvpResvEntry 24 } rsvpResvPolicy OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The contents of the policy object, displayed as an uninterpreted string of octets, including the object header. In the absence of such an object, this should be of zero length." ::= { rsvpResvEntry 25 } Baker and Krawczyk Expires May 1997 [Page 40] Internet Draft RSVP MIB November 1996 rsvpResvStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "'valid' for all active RESV messages. This object may be used to install static RESV in- formation or delete RESV information." ::= { rsvpResvEntry 26 } Baker and Krawczyk Expires May 1997 [Page 41] Internet Draft RSVP MIB November 1996 -- The RSVP Reservation Requests Forwarded Table contains the -- information displayed by receivers regarding their needs with -- respect to sessions and senders. It is in essence a list of the -- valid RESV messages that the RSVP Router or Host is sending -- to its upstream neighbors. rsvpResvFwdNewIndex OBJECT-TYPE SYNTAX TestAndIncr MAX-ACCESS read-write STATUS current DESCRIPTION "This object is used to assign values to rsvpResvFwdNumber as described in 'Textual Con- ventions for SNMPv2'. The network manager reads the object, and then writes the value back in the SET that creates a new instance of rsvpResvFwdEntry. If the SET fails with the code 'inconsistentValue', then the process must be repeated; If the SET succeeds, then the ob- ject is incremented, and the new instance is created according to the manager's directions." ::= { rsvpGenObjects 4 } rsvpResvFwdTable OBJECT-TYPE SYNTAX SEQUENCE OF RsvpResvFwdEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the state information displayed upstream in RESV messages." ::= { rsvpObjects 4 } Baker and Krawczyk Expires May 1997 [Page 42] Internet Draft RSVP MIB November 1996 rsvpResvFwdEntry OBJECT-TYPE SYNTAX RsvpResvFwdEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the state information displayed upstream in an RESV message concern- ing a single sender." INDEX { rsvpSessionNumber, rsvpResvFwdNumber } ::= { rsvpResvFwdTable 1 } RsvpResvFwdEntry ::= SEQUENCE { rsvpResvFwdNumber SessionNumber, rsvpResvFwdType SessionType, rsvpResvFwdDestAddr OCTET STRING, rsvpResvFwdSenderAddr OCTET STRING, rsvpResvFwdProtocol Protocol, rsvpResvFwdDestPort Port, rsvpResvFwdPort Port, rsvpResvFwdHopAddr OCTET STRING, rsvpResvFwdHopLih Integer32, rsvpResvFwdInterface InterfaceIndex, rsvpResvFwdService QosService, rsvpResvFwdTSpecRate BitRate, rsvpResvFwdTSpecPeakRate BitRate, rsvpResvFwdTSpecBurst BurstSize, rsvpResvFwdTSpecMinTU MessageSize, rsvpResvFwdTSpecMaxTU MessageSize, rsvpResvFwdRSpecRate BitRate, rsvpResvFwdRSpecSlack Integer32, rsvpResvFwdInterval RefreshInterval, rsvpResvFwdScope OCTET STRING, rsvpResvFwdShared TruthValue, rsvpResvFwdExplicit TruthValue, rsvpResvFwdRSVPHop TruthValue, rsvpResvFwdLastChange TimeStamp, rsvpResvFwdPolicy OCTET STRING, rsvpResvFwdStatus RowStatus } Baker and Krawczyk Expires May 1997 [Page 43] Internet Draft RSVP MIB November 1996 rsvpResvFwdNumber OBJECT-TYPE SYNTAX SessionNumber MAX-ACCESS not-accessible STATUS current DESCRIPTION "The number of this reservation request. This is for SNMP Indexing purposes only and has no relation to any protocol vaalue." ::= { rsvpResvFwdEntry 1 } rsvpResvFwdType OBJECT-TYPE SYNTAX SessionType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of session (IP4, IP6, IP6 with flow information, etc)." ::= { rsvpResvFwdEntry 2 } rsvpResvFwdDestAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The destination address used by all senders in this session." ::= { rsvpResvFwdEntry 3 } rsvpResvFwdSenderAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The source address of the sender selected by this reservation. The value of all zeroes in- dicates 'all senders'." ::= { rsvpResvFwdEntry 4 } Baker and Krawczyk Expires May 1997 [Page 44] Internet Draft RSVP MIB November 1996 rsvpResvFwdProtocol OBJECT-TYPE SYNTAX Protocol MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Protocol used by a session. for secure sessions, this indicates IP Security." ::= { rsvpResvFwdEntry 5 } rsvpResvFwdDestPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a destina- tion port for all senders in this session. If the IP protocol in use, specified by rsvpResvFwdProtocol, is 50 (ESP) or 51 (AH), this represents a virtual destination port number. A value of zero indicates that the IP protocol in use does not have ports." ::= { rsvpResvFwdEntry 6 } rsvpResvFwdPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a source port for this sender in this session. If the IP protocol in use, specified by rsvpResvFwdProtocol is 50 (ESP) or 51 (AH), this represents a generalized port identifier (GPI). A value of zero indicates that the IP protocol in use does not have ports." ::= { rsvpResvFwdEntry 7 } Baker and Krawczyk Expires May 1997 [Page 45] Internet Draft RSVP MIB November 1996 rsvpResvFwdHopAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The address of the (previous) RSVP that will receive this message." ::= { rsvpResvFwdEntry 8 } rsvpResvFwdHopLih OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The Logical Interface Handle sent to the (pre- vious) RSVP that will receive this message." ::= { rsvpResvFwdEntry 9 } rsvpResvFwdInterface OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-create STATUS current DESCRIPTION "The ifIndex value of the interface on which this RESV message was most recently sent." ::= { rsvpResvFwdEntry 10 } rsvpResvFwdService OBJECT-TYPE SYNTAX QosService MAX-ACCESS read-create STATUS current DESCRIPTION "The QoS Service classification requested." ::= { rsvpResvFwdEntry 11 } Baker and Krawczyk Expires May 1997 [Page 46] Internet Draft RSVP MIB November 1996 rsvpResvFwdTSpecRate OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The Average Bit Rate of the sender's data stream. Within a transmission burst, the ar- rival rate may be as fast as rsvpResvFwdTSpec- PeakRate (if supported by the service model); however, averaged across two or more burst in- tervals, the rate should not exceed rsvpResvFwdTSpecRate. Note that this is a prediction, often based on the general capability of a type of codec or particular encoding; the measured average rate may be significantly lower." ::= { rsvpResvFwdEntry 12 } rsvpResvFwdTSpecPeakRate OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The Peak Bit Rate of the sender's data stream Traffic arrival is not expected to exceed this rate at any time, apart from the effects of jitter in the network. If not specified in the TSpec, this returns zero or noSuchValue." ::= { rsvpResvFwdEntry 13 } Baker and Krawczyk Expires May 1997 [Page 47] Internet Draft RSVP MIB November 1996 rsvpResvFwdTSpecBurst OBJECT-TYPE SYNTAX BurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The size of the largest burst expected from the sender at a time. If this is less than the sender's advertised burst size, the receiver is asking the network to provide flow pacing beyond what would be provided under normal circumstances. Such pac- ing is at the network's option." ::= { rsvpResvFwdEntry 14 } rsvpResvFwdTSpecMinTU OBJECT-TYPE SYNTAX MessageSize MAX-ACCESS read-create STATUS current DESCRIPTION "The minimum message size for this flow. The policing algorithm will treat smaller messages as though they are this size." ::= { rsvpResvFwdEntry 15 } rsvpResvFwdTSpecMaxTU OBJECT-TYPE SYNTAX MessageSize MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum message size for this flow. The admission algorithm will reject TSpecs whose Maximum Transmission Unit, plus the interface headers, exceed the interface MTU." ::= { rsvpResvFwdEntry 16 } Baker and Krawczyk Expires May 1997 [Page 48] Internet Draft RSVP MIB November 1996 rsvpResvFwdRSpecRate OBJECT-TYPE SYNTAX BitRate UNITS "bytes per second" MAX-ACCESS read-create STATUS current DESCRIPTION "If the requested service is Guaranteed, as specified by rsvpResvService, this is the clearing rate that is being requested. Other- wise, it is zero, or the agent may return noSuchValue." ::= { rsvpResvFwdEntry 17 } rsvpResvFwdRSpecSlack OBJECT-TYPE SYNTAX Integer32 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "If the requested service is Guaranteed, as specified by rsvpResvService, this is the delay slack. Otherwise, it is zero, or the agent may return noSuchValue." ::= { rsvpResvFwdEntry 18 } rsvpResvFwdInterval OBJECT-TYPE SYNTAX RefreshInterval MAX-ACCESS read-create STATUS current DESCRIPTION "The interval between refresh messages adver- tised to the Previous Hop." ::= { rsvpResvFwdEntry 19 } Baker and Krawczyk Expires May 1997 [Page 49] Internet Draft RSVP MIB November 1996 rsvpResvFwdScope OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The contents of the scope object, displayed as an uninterpreted string of octets, including the object header. In the absence of such an object, this should be of zero length." ::= { rsvpResvFwdEntry 20 } rsvpResvFwdShared OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, a reservation shared among senders is requested. If FALSE, a reservation specific to this sender is requested." ::= { rsvpResvFwdEntry 21 } rsvpResvFwdExplicit OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, individual senders are listed using Filter Specifications. If FALSE, all senders are implicitly selected. The Scope Object will contain a list of senders that need to receive this reservation request for the purpose of routing the RESV message." ::= { rsvpResvFwdEntry 22 } Baker and Krawczyk Expires May 1997 [Page 50] Internet Draft RSVP MIB November 1996 rsvpResvFwdRSVPHop OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, the node believes that the next IP hop is an RSVP hop. If FALSE, the node be- lieves that the next IP hop may not be an RSVP hop." ::= { rsvpResvFwdEntry 23 } rsvpResvFwdLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The time of the last change in this request; This is either the first time it was sent or the time of the most recent change in parame- ters." ::= { rsvpResvFwdEntry 24 } rsvpResvFwdPolicy OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The contents of the policy object, displayed as an uninterpreted string of octets, including the object header. In the absence of such an object, this should be of zero length." ::= { rsvpResvFwdEntry 25 } Baker and Krawczyk Expires May 1997 [Page 51] Internet Draft RSVP MIB November 1996 rsvpResvFwdStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "'valid' for all active RESV messages. This object may be used to install static RESV in- formation or delete RESV information." ::= { rsvpResvFwdEntry 26 } Baker and Krawczyk Expires May 1997 [Page 52] Internet Draft RSVP MIB November 1996 -- The RSVP Active Flows Database -- lists all flows active on an outgoing interface, including -- relevant attributes. rsvpFlowTable OBJECT-TYPE SYNTAX SEQUENCE OF RsvpFlowEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the reserved flows us- ing the system's interfaces." ::= { rsvpObjects 5 } rsvpFlowEntry OBJECT-TYPE SYNTAX RsvpFlowEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the use of a given in- terface by a given flow." INDEX { rsvpFlowNumber } ::= { rsvpFlowTable 1 } RsvpFlowEntry ::= SEQUENCE { rsvpFlowNumber SessionNumber, rsvpFlowType SessionType, rsvpFlowDestAddr OCTET STRING, rsvpFlowSenderAddr OCTET STRING, rsvpFlowProtocol Protocol, rsvpFlowDestPort Port, rsvpFlowPort Port, rsvpFlowInterface InterfaceIndex, rsvpFlowRate BitRate, rsvpFlowBurst BurstSize, rsvpFlowWeight Integer32, rsvpFlowQueue Integer32, rsvpFlowMinTU MessageSize, rsvpFlowDontAsk TimeInterval, rsvpFlowStatus RowStatus } Baker and Krawczyk Expires May 1997 [Page 53] Internet Draft RSVP MIB November 1996 rsvpFlowNumber OBJECT-TYPE SYNTAX SessionNumber MAX-ACCESS not-accessible STATUS current DESCRIPTION "The number of this flow. This is for SNMP In- dexing purposes only and has no relation to any protocol value." ::= { rsvpFlowEntry 1 } rsvpFlowType OBJECT-TYPE SYNTAX SessionType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of session (IP4, IP6, IP6 with flow information, etc)." ::= { rsvpFlowEntry 2 } rsvpFlowDestAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The destination address used by all senders in this session." ::= { rsvpFlowEntry 3 } rsvpFlowSenderAddr OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-create STATUS current DESCRIPTION "The source address of the sender selected by this reservation. The value of all zeroes in- dicates 'all senders'." ::= { rsvpFlowEntry 4 } Baker and Krawczyk Expires May 1997 [Page 54] Internet Draft RSVP MIB November 1996 rsvpFlowProtocol OBJECT-TYPE SYNTAX Protocol MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Protocol used by a session." ::= { rsvpFlowEntry 5 } rsvpFlowDestPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a destina- tion port for all senders in this session. If the IP protocol in use, specified by rsvpResvFwdProtocol, is 50 (ESP) or 51 (AH), this represents a virtual destination port number. A value of zero indicates that the IP protocol in use does not have ports." ::= { rsvpFlowEntry 6 } rsvpFlowPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a source port for this sender in this session. If the IP protocol in use, specified by rsvpResvFwdProtocol is 50 (ESP) or 51 (AH), this represents a generalized port identifier (GPI). A value of zero indicates that the IP protocol in use does not have ports." ::= { rsvpFlowEntry 7 } Baker and Krawczyk Expires May 1997 [Page 55] Internet Draft RSVP MIB November 1996 rsvpFlowInterface OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-create STATUS current DESCRIPTION "The ifIndex value of the interface on which this reservation exists." ::= { rsvpFlowEntry 8 } rsvpFlowRate OBJECT-TYPE SYNTAX BitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The Reserved Rate of the sender's data stream. If this is a Controlled Load service flow, this rate is derived from the Tspec rate parameter (r). If this is a Guaranteed service flow, this rate is derived from the Rspec clearing rate parameter (R)." ::= { rsvpFlowEntry 9 } rsvpFlowBurst OBJECT-TYPE SYNTAX BurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The size of the largest burst expected from the sender at a time. If this is less than the sender's advertised burst size, the receiver is asking the network to provide flow pacing beyond what would be provided under normal circumstances. Such pac- ing is at the network's option." ::= { rsvpFlowEntry 10 } Baker and Krawczyk Expires May 1997 [Page 56] Internet Draft RSVP MIB November 1996 rsvpFlowWeight OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The weight used to prioritize the traffic. Note that the interpretation of this object is implementation-specific, as implementations vary in their use of weighting procedures." ::= { rsvpFlowEntry 11 } rsvpFlowQueue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The number of the queue used by this traffic. Note that the interpretation of this object is implementation-specific, as implementations vary in their use of queue identifiers." ::= { rsvpFlowEntry 12 } rsvpFlowMinTU OBJECT-TYPE SYNTAX MessageSize MAX-ACCESS read-create STATUS current DESCRIPTION "The minimum message size for this flow. The policing algorithm will treat smaller messages as though they are this size." ::= { rsvpFlowEntry 13 } Baker and Krawczyk Expires May 1997 [Page 57] Internet Draft RSVP MIB November 1996 rsvpFlowDontAsk OBJECT-TYPE SYNTAX TimeInterval MAX-ACCESS read-create STATUS current DESCRIPTION "A period of time, measured in hundredths of a second, during which the agent is precluded from sending a newFlow notification for this conversation. If an authorizing application leaves rsvpFlowS- tatus in a state other than 'valid' and sets rsvpFlowDontAsk to a non-zero value, the agent must neither consider the flow active for ad- mission or queuing purposes, or re-request au- thorization to install it, until the indicated amount of time has elapsed." ::= { rsvpFlowEntry 14 } rsvpFlowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "'valid' for all active flows. This object may be used to install static classifier informa- tion, delete classifier information, or author- ize such." ::= { rsvpFlowEntry 15 } Baker and Krawczyk Expires May 1997 [Page 58] Internet Draft RSVP MIB November 1996 -- The RSVP Interface Attributes Database contains the -- RSVP-specific information for an interface. Information -- that is shared with other reservation procedures such -- as ST-II is in the Integrated Interface Attributes -- Database. rsvpIfTable OBJECT-TYPE SYNTAX SEQUENCE OF RsvpIfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The RSVP-specific attributes of the system's interfaces." ::= { rsvpObjects 6 } rsvpIfEntry OBJECT-TYPE SYNTAX RsvpIfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The RSVP-specific attributes of the a given interface." INDEX { ifIndex } ::= { rsvpIfTable 1 } RsvpIfEntry ::= SEQUENCE { rsvpIfUdpNbrs Gauge32, rsvpIfIpNbrs Gauge32, rsvpIfNbrs Gauge32, rsvpIfEnabled TruthValue, rsvpIfUdpRequired TruthValue, rsvpIfRefreshBlockadeMultiple INTEGER, rsvpIfRefreshMultiple INTEGER, rsvpIfTTL INTEGER, rsvpIfRefreshInterval TimeInterval, rsvpIfRouteDelay TimeInterval, rsvpIfStatus RowStatus } Baker and Krawczyk Expires May 1997 [Page 59] Internet Draft RSVP MIB November 1996 rsvpIfUdpNbrs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of neighbors perceived to be using only the RSVP UDP Encapsulation." ::= { rsvpIfEntry 1 } rsvpIfIpNbrs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of neighbors perceived to be using only the RSVP IP Encapsulation." ::= { rsvpIfEntry 2 } rsvpIfNbrs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of neighbors currently perceived; this will exceed rsvpIfIpNbrs + rsvpIfUdpNbrs by the number of neighbors using both encapsu- lations." ::= { rsvpIfEntry 3 } rsvpIfRefreshBlockadeMultiple OBJECT-TYPE SYNTAX INTEGER (1..65536) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of the RSVP value 'Kb', Which is the minimum number of refresh intervals that blockade state will last once entered." DEFVAL { 4 } ::= { rsvpIfEntry 4 } Baker and Krawczyk Expires May 1997 [Page 60] Internet Draft RSVP MIB November 1996 rsvpIfRefreshMultiple OBJECT-TYPE SYNTAX INTEGER (1..65536) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of the RSVP value 'K', which is the number of refresh intervals which must elapse (minimum) before a PATH or RESV message which is not being refreshed will be aged out." DEFVAL { 3 } ::= { rsvpIfEntry 5 } rsvpIfTTL OBJECT-TYPE SYNTAX INTEGER (0..255) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of SEND_TTL used on this interface for messages this node originates. If set to zero, the node determines the TTL via other means." DEFVAL { 0 } -- which is to say, no override ::= { rsvpIfEntry 6 } rsvpIfRefreshInterval OBJECT-TYPE SYNTAX TimeInterval UNITS "hundredths of a second" MAX-ACCESS read-create STATUS current DESCRIPTION "The value of the RSVP value 'R', which is the minimum period between refresh transmissions of a given PATH or RESV message on an interface." DEFVAL { 3000 } -- 30 seconds ::= { rsvpIfEntry 7 } Baker and Krawczyk Expires May 1997 [Page 61] Internet Draft RSVP MIB November 1996 rsvpIfRouteDelay OBJECT-TYPE SYNTAX TimeInterval UNITS "hundredths of a second" MAX-ACCESS read-create STATUS current DESCRIPTION "The approximate period from the time a route is changed to the time a resulting message ap- pears on the interface." DEFVAL { 200 } -- 2 seconds ::= { rsvpIfEntry 8 } rsvpIfEnabled OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, RSVP is enabled on this Interface. If FALSE, RSVP is not enabled on this inter- face." ::= { rsvpIfEntry 9 } rsvpIfUdpRequired OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, manual configuration forces the use of UDP encapsulation on the interface. If FALSE, UDP encapsulation is only used if rsvpI- fUdpNbrs is not zero." ::= { rsvpIfEntry 10 } Baker and Krawczyk Expires May 1997 [Page 62] Internet Draft RSVP MIB November 1996 rsvpIfStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "'valid' on interfaces that are configured for RSVP." ::= { rsvpIfEntry 11 } Baker and Krawczyk Expires May 1997 [Page 63] Internet Draft RSVP MIB November 1996 -- The RSVP Neighbor Database lists the neighbors the RSVP -- process currently is receiving messages from. rsvpNbrTable OBJECT-TYPE SYNTAX SEQUENCE OF RsvpNbrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the Neighbors of an RSVP system." ::= { rsvpObjects 7 } rsvpNbrEntry OBJECT-TYPE SYNTAX RsvpNbrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing a single RSVP Neigh- bor." INDEX { ifIndex, rsvpNbrAddress } ::= { rsvpNbrTable 1 } RsvpNbrEntry ::= SEQUENCE { rsvpNbrAddress OCTET STRING, rsvpNbrProtocol RsvpEncapsulation, rsvpNbrStatus RowStatus } rsvpNbrAddress OBJECT-TYPE SYNTAX OCTET STRING (SIZE(4..16)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP4 or IP6 Address used by this neighbor." ::= { rsvpNbrEntry 1 } Baker and Krawczyk Expires May 1997 [Page 64] Internet Draft RSVP MIB November 1996 rsvpNbrProtocol OBJECT-TYPE SYNTAX RsvpEncapsulation MAX-ACCESS read-create STATUS current DESCRIPTION "The encapsulation being used by this neigh- bor." ::= { rsvpNbrEntry 2 } rsvpNbrStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "'valid' for all neighbors. This object may be used to configure neighbors. In the presence of configured neighbors, the implementation may (but is not required to) limit the set of valid neighbors to those configured." ::= { rsvpNbrEntry 3 } Baker and Krawczyk Expires May 1997 [Page 65] Internet Draft RSVP MIB November 1996 -- -- Notifications used to signal events -- newFlow NOTIFICATION-TYPE OBJECTS { rsvpFlowNumber, rsvpFlowType, rsvpFlowDestAddr, rsvpFlowSenderAddr, rsvpFlowProtocol, rsvpFlowDestPort, rsvpFlowPort, rsvpFlowInterface, rsvpFlowRate, rsvpFlowBurst, rsvpFlowWeight, rsvpFlowQueue, rsvpFlowMinTU } STATUS current DESCRIPTION "The newFlow trap indicates that the originat- ing system has installed a new flow in its classifier, or (when reservation authorization is in view) is prepared to install such a flow in the classifier and is requesting authoriza- tion. The objects included with the Notifica- tion may be used to read further information using the RSVP MIB. Authorization or non- authorization may be enacted by a write to the variable rsvpFlowStatus." ::= { rsvpNotifications 1 } lostFlow NOTIFICATION-TYPE OBJECTS { rsvpFlowNumber, rsvpFlowType, rsvpFlowDestAddr, rsvpFlowSenderAddr, rsvpFlowProtocol, rsvpFlowDestPort, rsvpFlowPort, rsvpFlowInterface } STATUS current DESCRIPTION "The lostFlow trap indicates that the originat- ing system has removed a flow in its classif- ier." ::= { rsvpNotifications 2 } Baker and Krawczyk Expires May 1997 [Page 66] Internet Draft RSVP MIB November 1996 -- conformance information rsvpGroups OBJECT IDENTIFIER ::= { rsvpConformance 1 } rsvpCompliances OBJECT IDENTIFIER ::= { rsvpConformance 2 } -- compliance statements rsvpCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement. Note that the im- plementation of this module requires implemen- tation of the Integrated Services MIB as well." MODULE -- this module MANDATORY-GROUPS { rsvpSessionGroup, rsvpSenderGroup, rsvpResvGroup, rsvpResvFwdGroup, rsvpFlowGroup, rsvpIfGroup, rsvpNbrGroup } ::= { rsvpCompliances 1 } rsvpSessionGroup OBJECT-GROUP OBJECTS { rsvpSessionNewIndex, rsvpSessionType, rsvpSessionDestAddr, rsvpSessionProtocol, rsvpSessionPort, rsvpSessionSenders, rsvpSessionReceivers, rsvpSessionRequests } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 1 } Baker and Krawczyk Expires May 1997 [Page 67] Internet Draft RSVP MIB November 1996 rsvpSenderGroup OBJECT-GROUP OBJECTS { rsvpSenderType, rsvpSenderDestAddr, rsvpSenderSenderAddr, rsvpSenderProtocol, rsvpSenderDestPort, rsvpSenderPort, rsvpSenderHopAddr, rsvpSenderHopLih, rsvpSenderInterface, rsvpSenderTSpecRate, rsvpSenderTSpecPeakRate, rsvpSenderTSpecBurst, rsvpSenderTSpecMinTU, rsvpSenderTSpecMaxTU, rsvpSenderInterval, rsvpSenderLastChange, rsvpSenderStatus, rsvpSenderRSVPHop, rsvpSenderPolicy, rsvpSenderAdspecBreak, rsvpSenderAdspecHopCount, rsvpSenderAdspecPathBw, rsvpSenderAdspecMinLatency, rsvpSenderAdspecMtu, rsvpSenderAdspecGuaranteedSvc, rsvpSenderAdspecGuaranteedBreak, rsvpSenderAdspecGuaranteedCtot, rsvpSenderAdspecGuaranteedDtot, rsvpSenderAdspecGuaranteedCsum, rsvpSenderAdspecGuaranteedDsum, rsvpSenderAdspecGuaranteedHopCount, rsvpSenderAdspecGuaranteedPathBw, rsvpSenderAdspecGuaranteedMinLatency, rsvpSenderAdspecGuaranteedMtu, rsvpSenderAdspecCtrlLoadSvc, rsvpSenderAdspecCtrlLoadBreak, rsvpSenderAdspecCtrlLoadHopCount, rsvpSenderAdspecCtrlLoadPathBw, rsvpSenderAdspecCtrlLoadMinLatency, rsvpSenderAdspecCtrlLoadMtu, rsvpSenderNewIndex } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 2 } Baker and Krawczyk Expires May 1997 [Page 68] Internet Draft RSVP MIB November 1996 rsvpResvGroup OBJECT-GROUP OBJECTS { rsvpResvType, rsvpResvDestAddr, rsvpResvSenderAddr, rsvpResvProtocol, rsvpResvDestPort, rsvpResvPort, rsvpResvHopAddr, rsvpResvHopLih, rsvpResvInterface, rsvpResvService, rsvpResvTSpecRate, rsvpResvTSpecBurst, rsvpResvTSpecPeakRate, rsvpResvTSpecMinTU, rsvpResvTSpecMaxTU, rsvpResvRSpecRate, rsvpResvRSpecSlack, rsvpResvInterval, rsvpResvScope, rsvpResvShared, rsvpResvExplicit, rsvpResvRSVPHop, rsvpResvLastChange, rsvpResvPolicy, rsvpResvStatus, rsvpResvNewIndex } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 3 } rsvpResvFwdGroup OBJECT-GROUP OBJECTS { rsvpResvFwdType, rsvpResvFwdDestAddr, rsvpResvFwdSenderAddr, rsvpResvFwdProtocol, rsvpResvFwdDestPort, rsvpResvFwdPort, rsvpResvFwdHopAddr, rsvpResvFwdHopLih, rsvpResvFwdInterface, rsvpResvFwdNewIndex, rsvpResvFwdService, rsvpResvFwdTSpecPeakRate, rsvpResvFwdTSpecMinTU, rsvpResvFwdTSpecMaxTU, rsvpResvFwdTSpecRate, rsvpResvFwdTSpecBurst, rsvpResvFwdRSpecRate, rsvpResvFwdRSpecSlack, rsvpResvFwdInterval, rsvpResvFwdScope, rsvpResvFwdShared, rsvpResvFwdExplicit, rsvpResvFwdRSVPHop, rsvpResvFwdLastChange, rsvpResvFwdPolicy, rsvpResvFwdStatus } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 4 } Baker and Krawczyk Expires May 1997 [Page 69] Internet Draft RSVP MIB November 1996 rsvpFlowGroup OBJECT-GROUP OBJECTS { rsvpFlowType, rsvpFlowDestAddr, rsvpFlowSenderAddr, rsvpFlowProtocol, rsvpFlowDestPort, rsvpFlowPort, rsvpFlowInterface, rsvpFlowDontAsk, rsvpFlowRate, rsvpFlowBurst, rsvpFlowWeight, rsvpFlowQueue, rsvpFlowMinTU, rsvpFlowStatus } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 5 } rsvpIfGroup OBJECT-GROUP OBJECTS { rsvpIfUdpNbrs, rsvpIfIpNbrs, rsvpIfNbrs, rsvpIfEnabled, rsvpIfUdpRequired, rsvpIfRefreshBlockadeMultiple, rsvpIfRefreshMultiple, rsvpIfRefreshInterval, rsvpIfTTL, rsvpIfRouteDelay, rsvpIfStatus } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 6 } rsvpNbrGroup OBJECT-GROUP OBJECTS { rsvpNbrProtocol, rsvpNbrStatus } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 7 } END Baker and Krawczyk Expires May 1997 [Page 70] Internet Draft RSVP MIB November 1996 6. Acknowledgements This document was produced by the RSVP Working Group. Baker and Krawczyk Expires May 1997 [Page 71] Internet Draft RSVP MIB November 1996 7. References [1] M.T. Rose (editor), Management Information Base for Network Management of TCP/IP-based internets, Internet Working Group Request for Comments 1213. Network Information Center, SRI International, Menlo Park, California, (May, 1990). [2] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8824, (December, 1987). [3] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), International Organization for Standardization. International Standard 8825, (December, 1987). Baker and Krawczyk Expires May 1997 [Page 72] Internet Draft RSVP MIB November 1996 Table of Contents 1 Status of this Memo ................................... 1 2 Abstract .............................................. 2 3 The SNMPv2 Network Management Framework ............... 3 3.1 Object Definitions .................................. 3 4 Overview .............................................. 3 4.1 Textual Conventions ................................. 3 4.2 Structure of MIB .................................... 4 5 Definitions ........................................... 5 5.1 RSVP Session Statistics Database .................... 8 5.1 RSVP Session Sender Database ........................ 12 5.2 RSVP Reservations Requested Database ................ 30 5.3 RSVP Reservation Requests Database .................. 41 5.3 RSVP Interface Flows Database ....................... 52 5.4 RSVP Interface Attributes Database .................. 58 5.5 RSVP Neighbor Database .............................. 63 5.4 Notifications ....................................... 65 6 Acknowledgements ...................................... 71 7 References ............................................ 72 Baker and Krawczyk Expires May 1997 [Page 73]