Internet Draft RSVP MIB December 1995 RSVP Management Information Base draft-ietf-rsvp-mib-00.txt Tue Nov 21 14:57:46 PST 1995 Fred Baker Cisco Systems 519 Lado Drive Santa Barbara, California 93111 fred@cisco.com John Krawczyk Bay Networks, Inc 2 Federal Street Billerica, Massachusetts 01021 jkrawczyk@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 1996 [Page 1] Internet Draft RSVP MIB December 1995 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 directy 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 1996 [Page 2] Internet Draft RSVP MIB December 1995 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 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 Baker and Krawczyk Expires May 1996 [Page 3] Internet Draft RSVP MIB December 1995 effect on either the syntax nor the semantics of any managed 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. The new data types are ... 4.2. Structure of MIB The MIB is composed of the following sections: Integrated Services Interface Attributes Table Interface Flows Table Notifications RSVP Session Statistics Table Session Sender Table Reservations Requested Table Reservation Requests Table RSVP Interface Attributes Table RSVP Neighbor Table 5. Definitions RSVP-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Gauge32, IpAddress, experimental FROM SNMPv2-SMI TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeStamp FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF Protocol, Port, BitRate FROM INTEGRATED-SERVICES-MIB ifIndex, InterfaceIndex FROM IF-MIB; -- This MIB module uses the extended OBJECT-TYPE macro as -- defined in [9]. rsvp MODULE-IDENTITY LAST-UPDATED "9511211457Z" -- Tue Nov 21 14:57:46 PST 1995 Baker and Krawczyk Expires May 1996 [Page 4] Internet Draft RSVP MIB December 1995 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 01021 Tel: +1 508 436 3811 E-Mail: jkrawczyk@BayNetworks.com" DESCRIPTION "The MIB module to describe the RSVP and Integrated Services Protocol" ::= { experimental 9999 } -- he who uses this gets what he deserves rsvpObjects OBJECT IDENTIFIER ::= { rsvp 1 } rsvpNotifications OBJECT IDENTIFIER ::= { rsvp 2 } rsvpConformance OBJECT IDENTIFIER ::= { rsvp 3 } RsvpEncapsulation ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This indicates the encapsulation that an RSVP Neighbor is percieved to be using." SYNTAX INTEGER { ip (1), -- IP Protocol 46 udp (2), -- UDP Encapsulation both (3) -- neighbor is using both encapsulations } Baker and Krawczyk Expires May 1996 [Page 5] Internet Draft RSVP MIB December 1995 RefreshInterval ::= TEXTUAL-CONVENTION 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) QosService ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The class of service in use by a flow." SYNTAX INTEGER { predictive (1), -- Predictive Service controlledDelay (2), -- Controlled Delay guaranteedDelay (3) -- Guaranteed Service } DelayClass ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The class of delay used by the Controlled De- lay Service." SYNTAX INTEGER (1..3) BurstSize ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The number of octets of IP Data, including IP Headers, that a stream may send without concern for policing." SYNTAX INTEGER (0..'7FFFFFFF'h) Ttl ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The value of the IP Time To Live field." SYNTAX INTEGER (0..'FF'h) Baker and Krawczyk Expires May 1996 [Page 6] Internet Draft RSVP MIB December 1995 IpAddressString ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A list of IP Addresses as found in the RSVP Scope Object." SYNTAX OCTET STRING Baker and Krawczyk Expires May 1996 [Page 7] Internet Draft RSVP MIB December 1995 -- 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. 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 1 } 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 { rsvpSenderSession, rsvpSenderSessionProtocol, rsvpSenderSessionPort, rsvpSenderSource, rsvpSenderPort} ::= { rsvpSenderTable 1 } RsvpSenderEntry ::= SEQUENCE { rsvpSenderSession IpAddress, rsvpSenderSessionProtocol Protocol, rsvpSenderSessionPort Port, rsvpSenderSource IpAddress, rsvpSenderPort Port, rsvpSenderTSpecRate BitRate, rsvpSenderTSpecBurst BurstSize, rsvpSenderTtl Ttl, rsvpSenderIf InterfaceIndex, rsvpSenderPreviousHop IpAddress, rsvpSenderInterval RefreshInterval, rsvpSenderMaxInterval RefreshInterval, -- place holder for Policy information -- place holder for OPWA Advertisement rsvpSenderLastChange TimeStamp, Baker and Krawczyk Expires May 1996 [Page 8] Internet Draft RSVP MIB December 1995 rsvpSenderStatus RowStatus } rsvpSenderSession OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Address used as a destination address for all senders in this session." ::= { rsvpSenderEntry 1 } rsvpSenderSessionProtocol OBJECT-TYPE SYNTAX Protocol MAX-ACCESS read-create STATUS current DESCRIPTION "The value of the IP Protocol field in this session, typically UDP or TCP. A value of zero indicates that any protocol is accepted; it also implies that rsvpSenderSessionPort and rsvpSenderPort must be zero." ::= { rsvpSenderEntry 2 } rsvpSenderSessionPort 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. A value of zero indicates that any port is ac- cepted or an IP Protocol other than UDP or TCP is in use. The IP protocol in use is specified by rsvpSenderProtocol." ::= { rsvpSenderEntry 3 } Baker and Krawczyk Expires May 1996 [Page 9] Internet Draft RSVP MIB December 1995 rsvpSenderSource OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Address used as a source address by this sender in this session." ::= { rsvpSenderEntry 4 } rsvpSenderPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a source port by this sender in this session. A value of zero indicates that any port is accepted or an IP Protocol other than UDP or TCP is in use. The IP protocol in use is specified by rsvpSen- derProtocol." ::= { rsvpSenderEntry 5 } rsvpSenderTSpecRate OBJECT-TYPE SYNTAX BitRate UNITS "kilobits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The Average Bit Rate of the sender's data stream, in Kilobits. The rate may be arbi- trarily fast during a short interval such as the duration of a video frame. However, over any two such intervals it will not average fas- ter than the average rate as transmitted by the sender." ::= { rsvpSenderEntry 6 } Baker and Krawczyk Expires May 1996 [Page 10] Internet Draft RSVP MIB December 1995 rsvpSenderTSpecBurst OBJECT-TYPE SYNTAX BurstSize UNITS "bits" MAX-ACCESS read-create STATUS current DESCRIPTION "The size of the largest burst the sender will send at a time." ::= { rsvpSenderEntry 7 } rsvpSenderTtl OBJECT-TYPE SYNTAX Ttl MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Time To Live that the sender is using on the first hop." ::= { rsvpSenderEntry 8 } rsvpSenderIf OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-create STATUS current DESCRIPTION "The value of IfIndex for the interface on which the PATH message was most recently re- cieved." ::= { rsvpSenderEntry 9 } rsvpSenderPreviousHop OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Address of the sender, or the router next closer to the sender, from which the PATH message was most recently recieved." ::= { rsvpSenderEntry 10 } Baker and Krawczyk Expires May 1996 [Page 11] Internet Draft RSVP MIB December 1995 rsvpSenderInterval OBJECT-TYPE SYNTAX RefreshInterval MAX-ACCESS read-create STATUS current DESCRIPTION "The interval between PATH receipt of refresh messages as advertised by the Previous Hop." ::= { rsvpSenderEntry 11 } rsvpSenderMaxInterval OBJECT-TYPE SYNTAX RefreshInterval MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum interval between our sending PATH refresh messages permitted by the Previous Hop." ::= { rsvpSenderEntry 12 } rsvpSenderLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The time of the last change in this PATH mes- sage; This includes the first time it was sent, or time of the most recent change in parame- ters." ::= { rsvpSenderEntry 13 } 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 14 } Baker and Krawczyk Expires May 1996 [Page 12] Internet Draft RSVP MIB December 1995 -- The RSVP Reservations Requested Database 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. rsvpResvTable OBJECT-TYPE SYNTAX SEQUENCE OF RsvpResvEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the state information displayed by recievers in RESV messages." ::= { rsvpObjects 2 } rsvpResvEntry OBJECT-TYPE SYNTAX RsvpResvEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the state information displayed by a single reciever's RESV message concerning a single sender." INDEX { rsvpResvSession, rsvpResvSessionProtocol, rsvpResvSessionPort, rsvpResvAddress, rsvpResvPort, rsvpResvIf, rsvpResvNextHop} ::= { rsvpResvTable 1 } RsvpResvEntry ::= SEQUENCE { rsvpResvSession IpAddress, rsvpResvSessionPort Port, rsvpResvAddress IpAddress, rsvpResvSessionProtocol Protocol, rsvpResvPort Port, rsvpResvService QosService, rsvpResvRSpecRate BitRate, rsvpResvRSpecBurst BurstSize, rsvpResvRSpecDelay DelayClass, rsvpResvIf InterfaceIndex, rsvpResvNextHop IpAddress, rsvpResvInterval RefreshInterval, rsvpResvMaxInterval RefreshInterval, rsvpResvScope IpAddressString, rsvpResvShared TruthValue, Baker and Krawczyk Expires May 1996 [Page 13] Internet Draft RSVP MIB December 1995 rsvpResvExplicit TruthValue, -- place holder for Policy information rsvpResvLastChange TimeStamp, rsvpResvStatus RowStatus } rsvpResvSession OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Address used as a destination address for all senders in this session." ::= { rsvpResvEntry 1 } rsvpResvSessionProtocol OBJECT-TYPE SYNTAX Protocol MAX-ACCESS read-create STATUS current DESCRIPTION "The value of the IP Protocol field in this session, typically UDP or TCP. A value of zero indicates that any protocol is accepted; it also implies that rsvpResvSessionPort and rsvpResvPort must be zero." ::= { rsvpResvEntry 2 } rsvpResvSessionPort 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. A value of zero indicates that any port is ac- cepted or an IP Protocol other than UDP or TCP is in use. The IP protocol in use is specified by rsvpResvSessionProtocol." ::= { rsvpResvEntry 3 } Baker and Krawczyk Expires May 1996 [Page 14] Internet Draft RSVP MIB December 1995 rsvpResvAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Address used as a source address by this sender in this session." ::= { rsvpResvEntry 4 } rsvpResvPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP or TCP port number used as a source port by this sender in this session. A value of zero indicates that any port is accepted or an IP Protocol other than UDP or TCP is in use. The IP protocol in use is specified by rsvpResvSessionProtocol." ::= { rsvpResvEntry 5 } rsvpResvService OBJECT-TYPE SYNTAX QosService MAX-ACCESS read-create STATUS current DESCRIPTION "The QoS Service classification requested by the reciever." ::= { rsvpResvEntry 6 } Baker and Krawczyk Expires May 1996 [Page 15] Internet Draft RSVP MIB December 1995 rsvpResvRSpecRate OBJECT-TYPE SYNTAX BitRate UNITS "kilobits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "In theory, the Average Bit Rate of the sender's data stream, in Kilobits. The rate may be arbitrarily fast during a short interval such as the duration of a video frame. Howev- er, over any two such intervals it will not average faster than the average rate as transmitted by the sender. Note, however, that there is no requirement that the number be the same number that the sender advertised in its PATH message." ::= { rsvpResvEntry 7 } rsvpResvRSpecBurst OBJECT-TYPE SYNTAX BurstSize UNITS "bits" 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 reciever 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 8 } Baker and Krawczyk Expires May 1996 [Page 16] Internet Draft RSVP MIB December 1995 rsvpResvRSpecDelay OBJECT-TYPE SYNTAX DelayClass UNITS "bits" MAX-ACCESS read-create STATUS current DESCRIPTION "The delay classification requested by the re- ciever." ::= { rsvpResvEntry 9 } rsvpResvIf OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-create STATUS current DESCRIPTION "The value of IfIndex for the interface on which the RESV message was most recently re- cieved." ::= { rsvpResvEntry 10 } rsvpResvNextHop OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Address of the sender, or the router next closer to the sender, from which the RESV message was most recently recieved." ::= { rsvpResvEntry 11 } rsvpResvInterval OBJECT-TYPE SYNTAX RefreshInterval MAX-ACCESS read-create STATUS current DESCRIPTION "The interval between RESV receipt of refresh messages as advertised by the Next Hop." ::= { rsvpResvEntry 12 } Baker and Krawczyk Expires May 1996 [Page 17] Internet Draft RSVP MIB December 1995 rsvpResvMaxInterval OBJECT-TYPE SYNTAX RefreshInterval MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum interval between our sending RESV refresh messages permitted by the Next Hop." ::= { rsvpResvEntry 13 } rsvpResvScope OBJECT-TYPE SYNTAX IpAddressString MAX-ACCESS read-create STATUS current DESCRIPTION "A list of zero or more Sender IP Addresses, indicating to which senders a Wildcard Style Filter applies." ::= { rsvpResvEntry 14 } 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 15 } rsvpResvExplicit OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If TRUE, individual senders are listed using Filter Specifications. If FALSE, senders are listed in the Scope Object." ::= { rsvpResvEntry 16 } Baker and Krawczyk Expires May 1996 [Page 18] Internet Draft RSVP MIB December 1995 rsvpResvLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The time of the last change in this reserva- tion request; This includes the first time it was received, or time of the most recent change in parameters." ::= { rsvpResvEntry 17 } 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 18 } Baker and Krawczyk Expires May 1996 [Page 19] Internet Draft RSVP MIB December 1995 -- The RSVP Reservations Requested Database 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. rsvpReqTable OBJECT-TYPE SYNTAX SEQUENCE OF RsvpReqEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the state information displayed upstream in RESV messages." ::= { rsvpObjects 3 } rsvpReqEntry OBJECT-TYPE SYNTAX RsvpReqEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the state information displayed upstream in an RESV message concern- ing a single sender." INDEX { rsvpReqSession, rsvpReqSessionProtocol, rsvpReqSessionPort, rsvpReqAddress, rsvpReqPort, rsvpReqIf, rsvpReqPreviousHop} ::= { rsvpReqTable 1 } RsvpReqEntry ::= SEQUENCE { rsvpReqSession IpAddress, rsvpReqSessionProtocol Protocol, rsvpReqSessionPort Port, rsvpReqAddress IpAddress, rsvpReqPort Port, rsvpReqService QosService, rsvpReqRSpecRate BitRate, rsvpReqRSpecBurst BurstSize, rsvpReqRSpecDelay DelayClass, rsvpReqIf InterfaceIndex, rsvpReqPreviousHop IpAddress, rsvpReqInterval RefreshInterval, rsvpReqMaxInterval RefreshInterval, rsvpReqScope IpAddressString, Baker and Krawczyk Expires May 1996 [Page 20] Internet Draft RSVP MIB December 1995 rsvpReqShared TruthValue, rsvpReqExplicit TruthValue, -- place holder for Policy information rsvpReqLastChange TimeStamp, rsvpReqStatus RowStatus } rsvpReqSession OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP Address used as a destination address for all senders in this session." ::= { rsvpReqEntry 1 } rsvpReqSessionProtocol OBJECT-TYPE SYNTAX Protocol MAX-ACCESS read-only STATUS current DESCRIPTION "The value of the IP Protocol field in this session, typically UDP or TCP. A value of zero indicates that any protocol is accepted; it also implies that rsvpReqSessionPort and rsvpReqPort must be zero." ::= { rsvpReqEntry 2 } rsvpReqSessionPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-only STATUS current DESCRIPTION "The UDP or TCP port number used as a destina- tion port for all senders in this session. A value of zero indicates that any port is ac- cepted or an IP Protocol other than UDP or TCP is in use. The IP protocol in use is specified by rsvpReqSessionProtocol." ::= { rsvpReqEntry 3 } Baker and Krawczyk Expires May 1996 [Page 21] Internet Draft RSVP MIB December 1995 rsvpReqAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP Address used as a source address by this sender in this session. For sessions for which rsvpReqExplicit is FALSE, this value will be 0.0.0.0" ::= { rsvpReqEntry 4 } rsvpReqPort OBJECT-TYPE SYNTAX Port MAX-ACCESS read-only STATUS current DESCRIPTION "The UDP or TCP port number used as a source port by this sender in this session. A value of zero indicates that any port is accepted or an IP Protocol other than UDP or TCP is in use. The IP protocol in use is specified by rsvpReqSessionProtocol." ::= { rsvpReqEntry 5 } rsvpReqService OBJECT-TYPE SYNTAX QosService MAX-ACCESS read-only STATUS current DESCRIPTION "The QoS Service classification requested." ::= { rsvpReqEntry 6 } Baker and Krawczyk Expires May 1996 [Page 22] Internet Draft RSVP MIB December 1995 rsvpReqRSpecRate OBJECT-TYPE SYNTAX BitRate UNITS "kilobits per second" MAX-ACCESS read-only STATUS current DESCRIPTION "In theory, the Average Bit Rate of the sender's data stream, in Kilobits. The rate may be arbitrarily fast during a short interval such as the duration of a video frame. Howev- er, over any two such intervals it will not average faster than the average rate as transmitted by the sender. Note, however, that there is no requirement that the number be the same number that the sender advertised in its PATH message." ::= { rsvpReqEntry 7 } rsvpReqRSpecBurst OBJECT-TYPE SYNTAX BurstSize UNITS "bits" MAX-ACCESS read-only 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 reciever 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." ::= { rsvpReqEntry 8 } Baker and Krawczyk Expires May 1996 [Page 23] Internet Draft RSVP MIB December 1995 rsvpReqRSpecDelay OBJECT-TYPE SYNTAX DelayClass UNITS "bits" MAX-ACCESS read-only STATUS current DESCRIPTION "The delay classification requested." ::= { rsvpReqEntry 9 } rsvpReqIf OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The value of IfIndex for the interface on which the RESV message is being sent, which should correspond to the interface from which the PATH message was most recently received." ::= { rsvpReqEntry 10 } rsvpReqPreviousHop OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP Address of the sender, or the router next closer to the sender, to which the RESV message is being sent." ::= { rsvpReqEntry 11 } rsvpReqInterval OBJECT-TYPE SYNTAX RefreshInterval MAX-ACCESS read-only STATUS current DESCRIPTION "The interval between RESV receipt of refresh messages advertised to the Previous Hop." ::= { rsvpReqEntry 12 } Baker and Krawczyk Expires May 1996 [Page 24] Internet Draft RSVP MIB December 1995 rsvpReqMaxInterval OBJECT-TYPE SYNTAX RefreshInterval MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum interval between our sending RESV refresh messages permitted to the Previous Hop." ::= { rsvpReqEntry 13 } rsvpReqScope OBJECT-TYPE SYNTAX IpAddressString MAX-ACCESS read-only STATUS current DESCRIPTION "A list of zero or more Sender IP Addresses, indicating to which senders a non-explicit reservation applies." ::= { rsvpReqEntry 14 } rsvpReqShared OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "If TRUE, a reservation shared among senders is requested. If FALSE, a reservation specific to this sender is requested." ::= { rsvpReqEntry 15 } rsvpReqExplicit OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "If TRUE, individual senders are listed using Filter Specifications. If FALSE, senders are listed in the Scope Object." ::= { rsvpReqEntry 16 } Baker and Krawczyk Expires May 1996 [Page 25] Internet Draft RSVP MIB December 1995 rsvpReqLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The time of the last change in this request; This includes the first time it was requested, or time of the most recent change in parameters requested." ::= { rsvpReqEntry 17 } rsvpReqStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-write STATUS current DESCRIPTION "'valid' for all active RESV messages. This object may be used to install static RESV in- formation or delete RESV information." ::= { rsvpReqEntry 18 } Baker and Krawczyk Expires May 1996 [Page 26] Internet Draft RSVP MIB December 1995 -- 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. rsvpIfAttribTable OBJECT-TYPE SYNTAX SEQUENCE OF RsvpIfAttribEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The RSVP-specific attributes of the system's interfaces." ::= { rsvpObjects 4 } rsvpIfAttribEntry OBJECT-TYPE SYNTAX RsvpIfAttribEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The RSVP-specific attributes of the a given interface." INDEX { ifIndex } ::= { rsvpIfAttribTable 1 } RsvpIfAttribEntry ::= SEQUENCE { rsvpIfAttribUdpNbrs Gauge32, rsvpIfAttribIpNbrs Gauge32, rsvpIfAttribNbrs Gauge32, rsvpIfAttribEnabled TruthValue, rsvpIfAttribUdpRequired TruthValue, rsvpIfAttribStatus RowStatus } Baker and Krawczyk Expires May 1996 [Page 27] Internet Draft RSVP MIB December 1995 rsvpIfAttribUdpNbrs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of neighbors percieved to be using only the RSVP UDP Encapsulation." ::= { rsvpIfAttribEntry 1 } rsvpIfAttribIpNbrs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of neighbors percieved to be using only the RSVP IP Encapsulation." ::= { rsvpIfAttribEntry 2 } rsvpIfAttribNbrs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of neighbors currently percieved; this will exceed rsvpIfAttribIpNbrs + rsvpIfAt- tribUdpNbrs by the number of neighbors using both encapsulations." ::= { rsvpIfAttribEntry 3 } rsvpIfAttribEnabled 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." ::= { rsvpIfAttribEntry 4 } Baker and Krawczyk Expires May 1996 [Page 28] Internet Draft RSVP MIB December 1995 rsvpIfAttribUdpRequired 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- fAttribUdpNbrs is not zero." ::= { rsvpIfAttribEntry 5 } rsvpIfAttribStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "'valid' on interfaces that are configured for RSVP." ::= { rsvpIfAttribEntry 6 } Baker and Krawczyk Expires May 1996 [Page 29] Internet Draft RSVP MIB December 1995 -- 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 5 } 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 IpAddress, rsvpNbrProtocol RsvpEncapsulation, rsvpNbrStatus RowStatus } rsvpNbrAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The IP Address used by this neighbor." ::= { rsvpNbrEntry 1 } Baker and Krawczyk Expires May 1996 [Page 30] Internet Draft RSVP MIB December 1995 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 1996 [Page 31] Internet Draft RSVP MIB December 1995 -- 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 { rsvpSenderGroup, rsvpResvGroup, rsvpReqGroup, rsvpIfAttribGroup, rsvpNbrGroup } ::= { rsvpCompliances 1 } rsvpSenderGroup OBJECT-GROUP OBJECTS { rsvpSenderSession, rsvpSenderSessionPort, rsvpSenderSource, rsvpSenderSessionProtocol, rsvpSenderPort, rsvpSenderTSpecRate, rsvpSenderTSpecBurst, rsvpSenderTtl, rsvpSenderIf, rsvpSenderPreviousHop, rsvpSenderInterval, rsvpSenderMaxInterval, rsvpSenderLastChange, rsvpSenderStatus } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 2 } Baker and Krawczyk Expires May 1996 [Page 32] Internet Draft RSVP MIB December 1995 rsvpResvGroup OBJECT-GROUP OBJECTS { rsvpResvSession, rsvpResvSessionPort, rsvpResvAddress, rsvpResvSessionProtocol, rsvpResvPort, rsvpResvService, rsvpResvRSpecRate, rsvpResvRSpecBurst, rsvpResvRSpecDelay, rsvpResvIf, rsvpResvNextHop, rsvpResvInterval, rsvpResvMaxInterval, rsvpResvScope, rsvpResvShared, rsvpResvExplicit, rsvpResvLastChange, rsvpResvStatus } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 3 } rsvpReqGroup OBJECT-GROUP OBJECTS { rsvpReqSession, rsvpReqSessionPort, rsvpReqAddress, rsvpReqSessionProtocol, rsvpReqPort, rsvpReqService, rsvpReqRSpecRate, rsvpReqRSpecBurst, rsvpReqRSpecDelay, rsvpReqIf, rsvpReqPreviousHop, rsvpReqInterval, rsvpReqMaxInterval, rsvpReqScope, rsvpReqShared, rsvpReqExplicit, rsvpReqLastChange, rsvpReqStatus } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 4 } Baker and Krawczyk Expires May 1996 [Page 33] Internet Draft RSVP MIB December 1995 rsvpIfAttribGroup OBJECT-GROUP OBJECTS { rsvpIfAttribUdpNbrs, rsvpIfAttribIpNbrs, rsvpIfAttribNbrs, rsvpIfAttribEnabled, rsvpIfAttribUdpRequired, rsvpIfAttribStatus } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 5 } rsvpNbrGroup OBJECT-GROUP OBJECTS { rsvpNbrAddress, rsvpNbrProtocol, rsvpNbrStatus } STATUS current DESCRIPTION "These objects are required for RSVP Systems." ::= { rsvpGroups 6 } END Baker and Krawczyk Expires May 1996 [Page 34] Internet Draft RSVP MIB December 1995 6. Acknowledgements This document was produced by the RSVP Working Group. Baker and Krawczyk Expires May 1996 [Page 35] Internet Draft RSVP MIB December 1995 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 1996 [Page 36] Internet Draft RSVP MIB December 1995 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 ........................................... 4 5.2 RSVP Session Sender Database ........................ 7 5.3 RSVP Reservations Requested Database ................ 12 5.4 RSVP Reservation Requests Database .................. 19 5.5 RSVP Interface Attributes Database .................. 26 5.1 RSVP Neighbor Database .............................. 29 6 Acknowledgements ...................................... 35 7 References ............................................ 36 Baker and Krawczyk Expires May 1996 [Page 37]