idnits 2.17.1 draft-ietf-rsvp-mib-02.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 261 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 7 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 168 has weird spacing: '...escribe the ...' == Line 179 has weird spacing: '... Number conve...' == Line 180 has weird spacing: '...numbers ident...' == Line 181 has weird spacing: '...mber in the ...' == Line 182 has weird spacing: '...eturned by a...' == (256 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 1996) is 10269 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 1941 looks like a reference -- Missing reference section? '2' on line 1947 looks like a reference -- Missing reference section? '3' on line 1953 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 7 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft RSVP MIB March 1996 4 RSVP Management Information Base 5 draft-ietf-rsvp-mib-02.txt 7 Fri Jun 14 15:30:52 PDT 1996 9 Fred Baker 11 Cisco Systems 12 519 Lado Drive 13 Santa Barbara, California 93111 15 fred@cisco.com 17 John Krawczyk 19 Bay Networks, Inc 20 2 Federal Street 21 Billerica, Massachusetts 01821 23 jj@BayNetworks.com 25 1. Status of this Memo 27 This document is an Internet Draft. Internet Drafts are 28 working documents of the Internet Engineering Task Force 29 (IETF), its Areas, and its Working Groups. Note that other 30 groups may also distribute working documents as Internet 31 Drafts. 33 Internet Drafts are draft documents valid for a maximum of six 34 months. Internet Drafts may be updated, replaced, or obsoleted 35 by other documents at any time. It is not appropriate to use 36 Internet Drafts as reference material or to cite them other 37 than as a "working draft" or "work in progress." 39 Please check the I-D abstract listing contained in each 40 Internet Draft directory to learn the current status of this 41 or any other Internet Draft. 43 2. Abstract 45 This memo defines a portion of the Management Information Base 46 (MIB) for use with network management protocols in TCP/IP- 47 based internets. In particular, it defines objects for 48 managing the Resource Reservation Protocol (RSVP) within the 49 interface attributes defined in the Integrated Services Model. 50 Thus, the Integrated Services MIB is directly relevant to and 51 cross-referenced by this MIB. Comments should be made to the 52 RSVP Working Group, rsvp@isi.edu. 54 This memo does not, in its draft form, specify a standard for 55 the Internet community. 57 3. The SNMPv2 Network Management Framework 59 The SNMPv2 Network Management Framework consists of four major 60 components. They are: 62 o RFC 1441 which defines the SMI, the mechanisms used for 63 describing and naming objects for the purpose of 64 management. 66 o RFC 1213 defines MIB-II, the core set of managed objects 67 for the Internet suite of protocols. 69 o RFC 1445 which defines the administrative and other 70 architectural aspects of the framework. 72 o RFC 1448 which defines the protocol used for network 73 access to managed objects. 75 The Framework permits new objects to be defined for the 76 purpose of experimentation and evaluation. 78 3.1. Object Definitions 80 Managed objects are accessed via a virtual information store, 81 termed the Management Information Base or MIB. Objects in the 82 MIB are defined using the subset of Abstract Syntax Notation 83 One (ASN.1) defined in the SMI. In particular, each object 84 type is named by an OBJECT IDENTIFIER, an administratively 85 assigned name. The object type together with an object 86 instance serves to uniquely identify a specific instantiation 87 of the object. For human convenience, we often use a textual 88 string, termed the descriptor, to refer to the object type. 90 4. Overview 92 4.1. Textual Conventions 94 Several new data types are introduced as a textual convention 95 in this MIB document. These textual conventions enhance the 96 readability of the specification and can ease comparison with 97 other specifications if appropriate. It should be noted that 98 the introduction of the these textual conventions has no 99 effect on either the syntax nor the semantics of any managed 100 objects. The use of these is merely an artifact of the 101 explanatory method used. Objects defined in terms of one of 102 these methods are always encoded by means of the rules that 103 define the primitive type. Hence, no changes to the SMI or 104 the SNMP are necessary to accommodate these textual 105 conventions which are adopted merely for the convenience of 106 readers and writers in pursuit of the elusive goal of clear, 107 concise, and unambiguous MIB documents. 109 4.2. Structure of MIB 111 The MIB is composed of the following sections: 112 General Objects 113 Session Statistics Table 114 Session Sender Table 115 Reservation Requests Received Table 116 Reservation Requests Forwarded Table 117 RSVP Active Flows Table 118 RSVP Interface Attributes Table 119 RSVP Neighbor Table 121 As a general rule, it is difficult in SNMP to describe 122 arbitrarily long of complex messages; this MIB therefore seeks 123 to describe the Path State Database and the Reservation State 124 Database as though each flow and filter description received 125 in an aggregate message had been received in a separate 126 reservation message. 128 Thus, if a RESV message is received for session 129 224.1.2.3+UDP+4455 with two filter/flow spec groups describing 130 a sender 1.2.3.4 and another sender 1.2.7.8, these two will 131 show in the MIB as two separate rows: one for 132 224.1.2.3+UDP+4455 from 1.2.3.4 and the other for 133 224.1.2.3+UDP+4455 from 1.2.7.8. 135 5. Definitions 137 RSVP-MIB DEFINITIONS ::= BEGIN 139 IMPORTS 140 MODULE-IDENTITY, OBJECT-TYPE, Gauge32, NOTIFICATION-TYPE, 141 Integer32, experimental FROM SNMPv2-SMI 143 TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeStamp, 144 TestAndIncr, TimeInterval FROM SNMPv2-TC 146 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 147 BitRate, BurstSize FROM INTEGRATED-SERVICES-MIB 148 ifIndex, InterfaceIndex FROM IF-MIB; 150 rsvp MODULE-IDENTITY 151 LAST-UPDATED "9511030500Z" -- Fri Jun 14 15:30:52 PDT 1996 152 ORGANIZATION "IETF RSVP Working Group" 153 CONTACT-INFO 154 " Fred Baker 155 Postal: Cisco Systems 156 519 Lado Drive 157 Santa Barbara, California 93111 158 Tel: +1 805 681 0115 159 E-Mail: fred@cisco.com 161 John Krawczyk 162 Postal: Bay Networks, Inc 163 2 Federal Street 164 Billerica, Massachusetts 01821 165 Tel: +1 508 436 3811 166 E-Mail: jj@BayNetworks.com" 167 DESCRIPTION 168 "The MIB module to describe the RSVP and In- 169 tegrated Services Protocol" 170 ::= { experimental 71 } 172 rsvpObjects OBJECT IDENTIFIER ::= { rsvp 1 } -- tables 173 rsvpGenObjects OBJECT IDENTIFIER ::= { rsvp 2 } -- global objects 174 rsvpNotifications OBJECT IDENTIFIER ::= { rsvp 3 } -- traps 175 rsvpConformance OBJECT IDENTIFIER ::= { rsvp 4 } -- conformance 176 SessionNumber ::= TEXTUAL-CONVENTION 177 STATUS current 178 DESCRIPTION 179 "The Session Number convention is used for 180 numbers identifying sessions or saved PATH or 181 RESV information. It is a number in the range 182 returned by a TestAndIncr variable, having no 183 protocol meaning whatsoever but serving instead 184 as simple identifier. 186 The alternative was a very complex instance or 187 instance object that became unwieldy." 188 SYNTAX INTEGER (0..2147483647) 190 Protocol ::= TEXTUAL-CONVENTION 191 DISPLAY-HINT "d" 192 STATUS current 193 DESCRIPTION 194 "The value of the IP Protocol field of an IP 195 Datagram Header. This identifies the protocol 196 layer above IP. For example, the value 6 is 197 used for TCP and the value 17 is used for UDP. 198 The values of this field are defined in the As- 199 signed Numbers RFC." 200 SYNTAX INTEGER (1..255) 202 SessionType ::= TEXTUAL-CONVENTION 203 STATUS current 204 DESCRIPTION 205 "The value of the C-Type field of a Session ob- 206 ject, as defined in the RSVP specification. 207 This value determines the lengths of octet 208 strings and use of certain objects such as the 209 'port' variables. If the C-Type calls for an 210 IP6 address, one would expect all source, des- 211 tination, and next/previous hop addresses to be 212 16 bytes long, and for the ports to be UDP/TCP 213 port numbers, for example." 214 SYNTAX INTEGER (1..255) 216 Port ::= TEXTUAL-CONVENTION 217 DISPLAY-HINT "d" 218 STATUS current 219 DESCRIPTION 220 "The value of the UDP or TCP Source or Destina- 221 tion Port field, IPSEC SPI, or other session 222 discriminator. If it is not used, the value 223 should be of length 0. This pair, when coupled 224 with the IP Addresses of the source and desti- 225 nation system and the IP protocol field, 226 uniquely identifies a data stream." 227 SYNTAX OCTET STRING 229 RsvpEncapsulation ::= TEXTUAL-CONVENTION 230 STATUS current 231 DESCRIPTION 232 "This indicates the encapsulation that an RSVP 233 Neighbor is perceived to be using." 234 SYNTAX INTEGER { 235 ip (1), -- IP Protocol 46 236 udp (2), -- UDP Encapsulation 237 both (3) -- neighbor is using both encapsulations 238 } 240 RefreshInterval ::= TEXTUAL-CONVENTION 241 DISPLAY-HINT "d" 242 STATUS current 243 DESCRIPTION 244 "The number of milliseconds that are expected 245 to elapse between refreshes of path or reserva- 246 tion state. Unrefreshed Path or reservation 247 state is removed after a small multiple of this 248 period." 249 SYNTAX INTEGER (0..'7FFFFFFF'h) 251 QosService ::= TEXTUAL-CONVENTION 252 STATUS current 253 DESCRIPTION 254 "The class of service in use by a flow." 255 SYNTAX INTEGER { 256 controlledDelay (1), -- Controlled Delay 257 guaranteedDelay (2), -- Guaranteed Delay 258 predictiveDelay (3), -- Predictive Delay 259 controlledLoad (5) -- Controlled Load 260 } 262 DelayClass ::= TEXTUAL-CONVENTION 263 DISPLAY-HINT "d" 264 STATUS current 265 DESCRIPTION 266 "The class of delay used by the Controlled De- 267 lay Service." 268 SYNTAX INTEGER (1..3) 270 MessageSize ::= TEXTUAL-CONVENTION 271 DISPLAY-HINT "d" 272 STATUS current 273 DESCRIPTION 274 "The size of a message in bytes. This is used 275 to specify the minimum and maximum size of a 276 message along an integrated services route." 277 SYNTAX INTEGER (0..'7FFFFFFF'h) 279 -- The RSVP Session Statistics Database displays statistics 280 -- relating to the number of senders and receivers in each 281 -- session. 283 rsvpSessionNewIndex OBJECT-TYPE 284 SYNTAX TestAndIncr 285 MAX-ACCESS read-write 286 STATUS current 287 DESCRIPTION 288 "This object is used to assign values to 289 rsvpSessionNumber as described in 'Textual Con- 290 ventions for SNMPv2'. The network manager 291 reads the object, and then writes the value 292 back in the SET that creates a new instance of 293 rsvpSessionEntry. If the SET fails with the 294 code 'inconsistentValue', then the process must 295 be repeated; If the SET succeeds, then the ob- 296 ject is incremented, and the new instance is 297 created according to the manager's directions." 298 ::= { rsvpGenObjects 1 } 300 rsvpSessionTable OBJECT-TYPE 301 SYNTAX SEQUENCE OF RsvpSessionEntry 302 MAX-ACCESS not-accessible 303 STATUS current 304 DESCRIPTION 305 "Statistics concerning the sessions seen by a 306 given system." 307 ::= { rsvpObjects 1 } 309 rsvpSessionEntry OBJECT-TYPE 310 SYNTAX RsvpSessionEntry 311 MAX-ACCESS not-accessible 312 STATUS current 313 DESCRIPTION 314 "Statistics concerning a single RSVP session 315 seen by a given system." 316 INDEX { rsvpSessionNumber } 317 ::= { rsvpSessionTable 1 } 319 RsvpSessionEntry ::= 320 SEQUENCE { 321 rsvpSessionNumber SessionNumber, 322 rsvpSessionType SessionType, 323 rsvpSessionDestAddr OCTET STRING, 324 rsvpSessionProtocol Protocol, 325 rsvpSessionPort Port, 326 rsvpSessionSenders Gauge32, 327 rsvpSessionReceivers Gauge32, 328 rsvpSessionRequests Gauge32 329 } 331 rsvpSessionNumber OBJECT-TYPE 332 SYNTAX SessionNumber 333 MAX-ACCESS not-accessible 334 STATUS current 335 DESCRIPTION 336 "The number of this session. This is for SNMP 337 Indexing purposes only and has no relation to 338 any protocol vaalue." 339 ::= { rsvpSessionEntry 1 } 341 rsvpSessionType OBJECT-TYPE 342 SYNTAX SessionType 343 MAX-ACCESS read-create 344 STATUS current 345 DESCRIPTION 346 "The type of session (IP4, IP6, IP6 with flow 347 information, etc), and therefore the structure 348 of the information." 349 ::= { rsvpSessionEntry 2 } 351 rsvpSessionDestAddr OBJECT-TYPE 352 SYNTAX OCTET STRING 353 MAX-ACCESS read-create 354 STATUS current 355 DESCRIPTION 356 "The Destination Address used used by for all 357 senders in this session." 358 ::= { rsvpSessionEntry 3 } 360 rsvpSessionProtocol OBJECT-TYPE 361 SYNTAX Protocol 362 MAX-ACCESS read-create 363 STATUS current 364 DESCRIPTION 365 "The IP Protocol used by a session." 366 ::= { rsvpSessionEntry 4 } 368 rsvpSessionPort OBJECT-TYPE 369 SYNTAX Port 370 MAX-ACCESS read-create 371 STATUS current 372 DESCRIPTION 373 "The UDP or TCP port number used as a destina- 374 tion port for all senders in this session. A 375 value of zero indicates that the IP protocol in 376 use, specified by rsvpSessionProtocol, does not 377 have ports." 378 ::= { rsvpSessionEntry 5 } 380 rsvpSessionSenders OBJECT-TYPE 381 SYNTAX Gauge32 382 MAX-ACCESS read-only 383 STATUS current 384 DESCRIPTION 385 "The number of senders currently known to be 386 part of this session." 387 ::= { rsvpSessionEntry 6 } 389 rsvpSessionReceivers OBJECT-TYPE 390 SYNTAX Gauge32 391 MAX-ACCESS read-only 392 STATUS current 393 DESCRIPTION 394 "The number of reservations being requested of 395 this system for this session." 396 ::= { rsvpSessionEntry 7 } 398 rsvpSessionRequests OBJECT-TYPE 399 SYNTAX Gauge32 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "The number of reservation requests this system 404 is sending upstream for this session." 405 ::= { rsvpSessionEntry 8 } 407 -- Note that this is a read only table. If the corresponding 408 -- rsvpSenderTable, rsvpResvTable, and rsvpReqTable entries all 409 -- are removed, this entry goes away also. 411 -- The RSVP Session Sender Database contains the information 412 -- displayed by senders regarding their potential contribution 413 -- to session data content. It is in essence a list of the 414 -- valid PATH messages that the RSVP Router or Host is receiving. 416 rsvpSenderNewIndex OBJECT-TYPE 417 SYNTAX TestAndIncr 418 MAX-ACCESS read-write 419 STATUS current 420 DESCRIPTION 421 "This object is used to assign values to 422 rsvpSenderNumber as described in 'Textual Con- 423 ventions for SNMPv2'. The network manager 424 reads the object, and then writes the value 425 back in the SET that creates a new instance of 426 rsvpSenderEntry. If the SET fails with the 427 code 'inconsistentValue', then the process must 428 be repeated; If the SET succeeds, then the ob- 429 ject is incremented, and the new instance is 430 created according to the manager's directions." 431 ::= { rsvpGenObjects 2 } 433 rsvpSenderTable OBJECT-TYPE 434 SYNTAX SEQUENCE OF RsvpSenderEntry 435 MAX-ACCESS not-accessible 436 STATUS current 437 DESCRIPTION 438 "Information describing the state information 439 displayed by senders in PATH messages." 440 ::= { rsvpObjects 2 } 442 rsvpSenderEntry OBJECT-TYPE 443 SYNTAX RsvpSenderEntry 444 MAX-ACCESS not-accessible 445 STATUS current 446 DESCRIPTION 447 "Information describing the state information 448 displayed by a single sender's PATH message." 449 INDEX { rsvpSessionNumber, rsvpSenderNumber } 450 ::= { rsvpSenderTable 1 } 452 RsvpSenderEntry ::= 453 SEQUENCE { 454 rsvpSenderNumber SessionNumber, 455 rsvpSenderType SessionType, 456 rsvpSenderDestAddr OCTET STRING, 457 rsvpSenderSenderAddr OCTET STRING, 458 rsvpSenderProtocol Protocol, 459 rsvpSenderDestPort Port, 460 rsvpSenderPort Port, 461 rsvpSenderHopAddr OCTET STRING, 462 rsvpSenderInterface InterfaceIndex, 463 rsvpSenderTSpecRate BitRate, 464 rsvpSenderTSpecPeakRate BitRate, 465 rsvpSenderTSpecBurst BurstSize, 466 rsvpSenderTSpecMinTU MessageSize, 467 rsvpSenderTSpecMaxTU MessageSize, 468 rsvpSenderInterval RefreshInterval, 469 rsvpSenderRSVPHop TruthValue, 470 rsvpSenderLastChange TimeStamp, 471 rsvpSenderPolicy OCTET STRING, 472 rsvpSenderAdspec OCTET STRING, 473 rsvpSenderStatus RowStatus 474 } 476 rsvpSenderNumber OBJECT-TYPE 477 SYNTAX SessionNumber 478 MAX-ACCESS not-accessible 479 STATUS current 480 DESCRIPTION 481 "The number of this session. This is for SNMP 482 Indexing purposes only and has no relation to 483 any protocol vaalue." 484 ::= { rsvpSenderEntry 1 } 486 rsvpSenderType OBJECT-TYPE 487 SYNTAX SessionType 488 MAX-ACCESS read-create 489 STATUS current 490 DESCRIPTION 491 "The type of session (IP4, IP6, IP6 with flow 492 information, etc), and therefore the structure 493 of the information." 494 ::= { rsvpSenderEntry 2 } 496 rsvpSenderDestAddr OBJECT-TYPE 497 SYNTAX OCTET STRING 498 MAX-ACCESS read-create 499 STATUS current 500 DESCRIPTION 501 "The Address used as a destination address by 502 all senders in this session." 503 ::= { rsvpSenderEntry 3 } 505 rsvpSenderSenderAddr OBJECT-TYPE 506 SYNTAX OCTET STRING 507 MAX-ACCESS read-create 508 STATUS current 509 DESCRIPTION 510 "The Address used as a source address by this 511 sender in this session." 512 ::= { rsvpSenderEntry 4 } 514 rsvpSenderProtocol OBJECT-TYPE 515 SYNTAX Protocol 516 MAX-ACCESS read-create 517 STATUS current 518 DESCRIPTION 519 "The IP Protocol used by a session. for secure 520 sessions, this indicates IP Security." 521 ::= { rsvpSenderEntry 5 } 523 rsvpSenderDestPort OBJECT-TYPE 524 SYNTAX Port 525 MAX-ACCESS read-create 526 STATUS current 527 DESCRIPTION 528 "The UDP or TCP port number used as a destina- 529 tion port for all senders in this session. A 530 value of zero indicates that the IP protocol in 531 use, specified by rsvpSessionProtocol, does not 532 have ports." 533 ::= { rsvpSenderEntry 6 } 535 rsvpSenderPort OBJECT-TYPE 536 SYNTAX Port 537 MAX-ACCESS read-create 538 STATUS current 539 DESCRIPTION 540 "The UDP or TCP port number used as a source 541 port for this sender in this session. A value 542 of zero indicates that the IP protocol in use, 543 specified by rsvpSessionProtocol, does not have 544 ports." 545 ::= { rsvpSenderEntry 7 } 547 rsvpSenderHopAddr OBJECT-TYPE 548 SYNTAX OCTET STRING 549 MAX-ACCESS read-create 550 STATUS current 551 DESCRIPTION 552 "The address used by the previous RSVP hop 553 (which may be the original sender)." 554 ::= { rsvpSenderEntry 8 } 556 rsvpSenderInterface OBJECT-TYPE 557 SYNTAX InterfaceIndex 558 MAX-ACCESS read-create 559 STATUS current 560 DESCRIPTION 561 "The ifIndex value of the interface on which 562 this PATH message was most recently received." 563 ::= { rsvpSenderEntry 9 } 565 rsvpSenderTSpecRate OBJECT-TYPE 566 SYNTAX BitRate 567 UNITS "kilobits per second" 568 MAX-ACCESS read-create 569 STATUS current 570 DESCRIPTION 571 "The Average Bit Rate of the sender's data 572 stream, in kilobits/second. Within a transmis- 573 sion burst, the arrival rate may be as fast as 574 rsvpSenderTSpecPeakRate (if supported by the 575 service model); however, averaged across two or 576 more burst intervals, the rate should not 577 exceed rsvpSenderTSpecRate. 579 Note that this is a prediction, often based on 580 the general capability of a type of codec or 581 particular encoding; the measured average rate 582 may be significantly lower." 583 ::= { rsvpSenderEntry 10 } 585 rsvpSenderTSpecPeakRate OBJECT-TYPE 586 SYNTAX BitRate 587 UNITS "kilobits per second" 588 MAX-ACCESS read-create 589 STATUS current 590 DESCRIPTION 591 "The Peak Bit Rate of the sender's data stream, 592 in kilobits/second. Traffic arrival is not ex- 593 pected to exceed this rate at any time, apart 594 from the effects of jitter in the network. If 595 not specified in the TSpec, this returns zero 596 or noSuchValue." 597 ::= { rsvpSenderEntry 11 } 599 rsvpSenderTSpecBurst OBJECT-TYPE 600 SYNTAX BurstSize 601 UNITS "bits" 602 MAX-ACCESS read-create 603 STATUS current 604 DESCRIPTION 605 "The size of the largest burst expected from 606 the sender at a time." 607 ::= { rsvpSenderEntry 12 } 609 rsvpSenderTSpecMinTU OBJECT-TYPE 610 SYNTAX MessageSize 611 MAX-ACCESS read-create 612 STATUS current 613 DESCRIPTION 614 "The minimum message size for this flow. The 615 policing algorithm will treat smaller messages 616 as though they are this size." 617 ::= { rsvpSenderEntry 13 } 619 rsvpSenderTSpecMaxTU OBJECT-TYPE 620 SYNTAX MessageSize 621 MAX-ACCESS read-create 622 STATUS current 623 DESCRIPTION 624 "The maximum message size for this flow. The 625 admission algorithm will reject TSpecs whose 626 Maximum Transmission Unit, plus the interface 627 headers, exceed the interface MTU." 628 ::= { rsvpSenderEntry 14 } 630 rsvpSenderInterval OBJECT-TYPE 631 SYNTAX RefreshInterval 632 MAX-ACCESS read-create 633 STATUS current 634 DESCRIPTION 635 "The interval between PATH receipt of refresh 636 messages as advertised by the Previous Hop." 637 ::= { rsvpSenderEntry 15 } 639 rsvpSenderRSVPHop OBJECT-TYPE 640 SYNTAX TruthValue 641 MAX-ACCESS read-create 642 STATUS current 643 DESCRIPTION 644 "If TRUE, the node believes that the previous 645 hop is an RSVP hop. If FALSE, the node be- 646 lieves that the previous hop may not be an RSVP 647 hop." 648 ::= { rsvpSenderEntry 16 } 650 rsvpSenderLastChange OBJECT-TYPE 651 SYNTAX TimeStamp 652 MAX-ACCESS read-only 653 STATUS current 654 DESCRIPTION 655 "The time of the last change in this PATH mes- 656 sage; This includes the first time it was sent, 657 or time of the most recent change in parame- 658 ters." 659 ::= { rsvpSenderEntry 17 } 661 rsvpSenderPolicy OBJECT-TYPE 662 SYNTAX OCTET STRING 663 MAX-ACCESS read-create 664 STATUS current 665 DESCRIPTION 666 "The contents of the policy object, displayed 667 as an uninterpreted string of octets, including 668 the object header. In the absence of such an 669 object, this should be of zero length." 670 ::= { rsvpSenderEntry 18 } 672 rsvpSenderAdspec OBJECT-TYPE 673 SYNTAX OCTET STRING 674 MAX-ACCESS read-create 675 STATUS current 676 DESCRIPTION 677 "The contents of the Advertising Specification 678 object, displayed as an uninterpreted string of 679 octets, including the object header. In the 680 absence of such an object, this should be of 681 zero length." 682 ::= { rsvpSenderEntry 19 } 684 rsvpSenderStatus OBJECT-TYPE 685 SYNTAX RowStatus 686 MAX-ACCESS read-create 687 STATUS current 688 DESCRIPTION 689 "'valid' for all active PATH messages. This 690 object may be used to install static PATH in- 691 formation or delete PATH information." 692 ::= { rsvpSenderEntry 20 } 694 -- The RSVP Reservation Requests Received Table contains the 695 -- information displayed by receivers regarding their needs with 696 -- respect to sessions and senders. It is in essence a list of the 697 -- valid RESV messages that the RSVP Router or Host is receiving. 699 rsvpResvNewIndex OBJECT-TYPE 700 SYNTAX TestAndIncr 701 MAX-ACCESS read-write 702 STATUS current 703 DESCRIPTION 704 "This object is used to assign values to 705 rsvpResvNumber as described in 'Textual Conven- 706 tions for SNMPv2'. The network manager reads 707 the object, and then writes the value back in 708 the SET that creates a new instance of 709 rsvpResvEntry. If the SET fails with the code 710 'inconsistentValue', then the process must be 711 repeated; If the SET succeeds, then the object 712 is incremented, and the new instance is created 713 according to the manager's directions." 714 ::= { rsvpGenObjects 3 } 716 rsvpResvTable OBJECT-TYPE 717 SYNTAX SEQUENCE OF RsvpResvEntry 718 MAX-ACCESS not-accessible 719 STATUS current 720 DESCRIPTION 721 "Information describing the state information 722 displayed by receivers in RESV messages." 723 ::= { rsvpObjects 3 } 725 rsvpResvEntry OBJECT-TYPE 726 SYNTAX RsvpResvEntry 727 MAX-ACCESS not-accessible 728 STATUS current 729 DESCRIPTION 730 "Information describing the state information 731 displayed by a single receiver's RESV message 732 concerning a single sender." 733 INDEX { rsvpSessionNumber, rsvpResvNumber } 734 ::= { rsvpResvTable 1 } 736 RsvpResvEntry ::= 737 SEQUENCE { 738 rsvpResvNumber SessionNumber, 739 rsvpResvType SessionType, 740 rsvpResvDestAddr OCTET STRING, 741 rsvpResvSenderAddr OCTET STRING, 742 rsvpResvProtocol Protocol, 743 rsvpResvDestPort Port, 744 rsvpResvPort Port, 745 rsvpResvHopAddr OCTET STRING, 746 rsvpResvInterface InterfaceIndex, 747 rsvpResvService QosService, 748 rsvpResvTSpecRate BitRate, 749 rsvpResvTSpecPeakRate BitRate, 750 rsvpResvTSpecBurst BurstSize, 751 rsvpResvTSpecLevel DelayClass, 752 rsvpResvTSpecMinTU MessageSize, 753 rsvpResvTSpecMaxTU MessageSize, 754 rsvpResvInterval RefreshInterval, 755 rsvpResvScope OCTET STRING, 756 rsvpResvShared TruthValue, 757 rsvpResvExplicit TruthValue, 758 rsvpResvRSVPHop TruthValue, 759 rsvpResvLastChange TimeStamp, 760 rsvpResvPolicy OCTET STRING, 761 rsvpResvStatus RowStatus 762 } 764 rsvpResvNumber OBJECT-TYPE 765 SYNTAX SessionNumber 766 MAX-ACCESS not-accessible 767 STATUS current 768 DESCRIPTION 769 "The number of this session. This is for SNMP 770 Indexing purposes only and has no relation to 771 any protocol vaalue." 772 ::= { rsvpResvEntry 1 } 774 rsvpResvType OBJECT-TYPE 775 SYNTAX SessionType 776 MAX-ACCESS read-create 777 STATUS current 778 DESCRIPTION 779 "The type of session (IP4, IP6, IP6 with flow 780 information, etc), and therefore the structure 781 of the information." 782 ::= { rsvpResvEntry 2 } 784 rsvpResvDestAddr OBJECT-TYPE 785 SYNTAX OCTET STRING 786 MAX-ACCESS read-create 787 STATUS current 788 DESCRIPTION 789 "The Address used as a destination address by 790 all senders in this session." 791 ::= { rsvpResvEntry 3 } 793 rsvpResvSenderAddr OBJECT-TYPE 794 SYNTAX OCTET STRING 795 MAX-ACCESS read-create 796 STATUS current 797 DESCRIPTION 798 "The Address used as a source address by this 799 sender in this session. The value of all 800 zeroes indicates 'any sender'." 801 ::= { rsvpResvEntry 4 } 803 rsvpResvProtocol OBJECT-TYPE 804 SYNTAX Protocol 805 MAX-ACCESS read-create 806 STATUS current 807 DESCRIPTION 808 "The IP Protocol used by a session. for secure 809 sessions, this indicates IP Security." 810 ::= { rsvpResvEntry 5 } 812 rsvpResvDestPort OBJECT-TYPE 813 SYNTAX Port 814 MAX-ACCESS read-create 815 STATUS current 816 DESCRIPTION 817 "The UDP or TCP port number used as a destina- 818 tion port for all senders in this session. A 819 value of zero indicates that the IP protocol in 820 use, specified by rsvpSessionProtocol, does not 821 have ports." 822 ::= { rsvpResvEntry 6 } 824 rsvpResvPort OBJECT-TYPE 825 SYNTAX Port 826 MAX-ACCESS read-create 827 STATUS current 828 DESCRIPTION 829 "The UDP or TCP port number used as a source 830 port for this sender in this session. A value 831 of zero indicates that the IP protocol in use, 832 specified by rsvpSessionProtocol, does not have 833 ports or the port is being ignored." 834 ::= { rsvpResvEntry 7 } 836 rsvpResvHopAddr OBJECT-TYPE 837 SYNTAX OCTET STRING 838 MAX-ACCESS read-create 839 STATUS current 840 DESCRIPTION 841 "The address used by the next RSVP hop (which 842 may be the ultimate receiver)." 843 ::= { rsvpResvEntry 8 } 845 rsvpResvInterface OBJECT-TYPE 846 SYNTAX InterfaceIndex 847 MAX-ACCESS read-create 848 STATUS current 849 DESCRIPTION 850 "The ifIndex value of the interface on which 851 this RESV message was most recently received." 852 ::= { rsvpResvEntry 9 } 854 rsvpResvService OBJECT-TYPE 855 SYNTAX QosService 856 MAX-ACCESS read-create 857 STATUS current 858 DESCRIPTION 859 "The QoS Service classification requested by 860 the receiver." 861 ::= { rsvpResvEntry 10 } 863 rsvpResvTSpecRate OBJECT-TYPE 864 SYNTAX BitRate 865 UNITS "kilobits per second" 866 MAX-ACCESS read-create 867 STATUS current 868 DESCRIPTION 869 "The Average Bit Rate of the sender's data 870 stream, in kilobits/second. Within a transmis- 871 sion burst, the arrival rate may be as fast as 872 rsvpResvTSpecPeakRate (if supported by the ser- 873 vice model); however, averaged across two or 874 more burst intervals, the rate should not 875 exceed rsvpResvTSpecRate. 877 Note that this is a prediction, often based on 878 the general capability of a type of codec or 879 particular encoding; the measured average rate 880 may be significantly lower." 881 ::= { rsvpResvEntry 11 } 883 rsvpResvTSpecPeakRate OBJECT-TYPE 884 SYNTAX BitRate 885 UNITS "kilobits per second" 886 MAX-ACCESS read-create 887 STATUS current 888 DESCRIPTION 889 "The Peak Bit Rate of the sender's data stream, 890 in kilobits/second. Traffic arrival is not ex- 891 pected to exceed this rate at any time, apart 892 from the effects of jitter in the network. If 893 not specified in the TSpec, this returns zero 894 or noSuchValue." 895 ::= { rsvpResvEntry 12 } 897 rsvpResvTSpecBurst OBJECT-TYPE 898 SYNTAX BurstSize 899 UNITS "bits" 900 MAX-ACCESS read-create 901 STATUS current 902 DESCRIPTION 903 "The size of the largest burst expected from 904 the sender at a time. 906 If this is less than the sender's advertised 907 burst size, the receiver is asking the network 908 to provide flow pacing beyond what would be 909 provided under normal circumstances. Such pac- 910 ing is at the network's option." 911 ::= { rsvpResvEntry 13 } 913 rsvpResvTSpecLevel OBJECT-TYPE 914 SYNTAX DelayClass 915 MAX-ACCESS read-create 916 STATUS current 917 DESCRIPTION 918 "If the service is predictive or controlled- 919 delay, this is the service level that is being 920 requested. Otherwise, it is zero, or the agent 921 may return noSuchValue." 922 ::= { rsvpResvEntry 14 } 924 rsvpResvTSpecMinTU OBJECT-TYPE 925 SYNTAX MessageSize 926 MAX-ACCESS read-create 927 STATUS current 928 DESCRIPTION 929 "The minimum message size for this flow. The 930 policing algorithm will treat smaller messages 931 as though they are this size." 932 ::= { rsvpResvEntry 15 } 934 rsvpResvTSpecMaxTU OBJECT-TYPE 935 SYNTAX MessageSize 936 MAX-ACCESS read-create 937 STATUS current 938 DESCRIPTION 939 "The maximum message size for this flow. The 940 admission algorithm will reject TSpecs whose 941 Maximum Transmission Unit, plus the interface 942 headers, exceed the interface MTU." 943 ::= { rsvpResvEntry 16 } 945 rsvpResvInterval OBJECT-TYPE 946 SYNTAX RefreshInterval 947 MAX-ACCESS read-create 948 STATUS current 949 DESCRIPTION 950 "The interval between RESV receipt of refresh 951 messages as advertised by the Next Hop." 952 ::= { rsvpResvEntry 17 } 954 rsvpResvScope OBJECT-TYPE 955 SYNTAX OCTET STRING 956 MAX-ACCESS read-create 957 STATUS current 958 DESCRIPTION 959 "The contents of the scope object, displayed as 960 an uninterpreted string of octets, including 961 the object header. In the absence of such an 962 object, this should be of zero length." 963 ::= { rsvpResvEntry 18 } 965 rsvpResvShared OBJECT-TYPE 966 SYNTAX TruthValue 967 MAX-ACCESS read-create 968 STATUS current 969 DESCRIPTION 970 "If TRUE, a reservation shared among senders is 971 requested. If FALSE, a reservation specific to 972 this sender is requested." 973 ::= { rsvpResvEntry 19 } 975 rsvpResvExplicit OBJECT-TYPE 976 SYNTAX TruthValue 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "If TRUE, individual senders are listed using 981 Filter Specifications. If FALSE, senders are 982 listed in the Scope Object." 983 ::= { rsvpResvEntry 20 } 985 rsvpResvRSVPHop OBJECT-TYPE 986 SYNTAX TruthValue 987 MAX-ACCESS read-create 988 STATUS current 989 DESCRIPTION 990 "If TRUE, the node believes that the next hop 991 is an RSVP hop. If FALSE, the node believes 992 that the next hop may not be an RSVP hop." 993 ::= { rsvpResvEntry 21 } 995 rsvpResvLastChange OBJECT-TYPE 996 SYNTAX TimeStamp 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "The time of the last change in this reserva- 1001 tion request; This includes the first time it 1002 was received, or time of the most recent change 1003 in parameters." 1004 ::= { rsvpResvEntry 22 } 1006 rsvpResvPolicy OBJECT-TYPE 1007 SYNTAX OCTET STRING 1008 MAX-ACCESS read-create 1009 STATUS current 1010 DESCRIPTION 1011 "The contents of the policy object, displayed 1012 as an uninterpreted string of octets, including 1013 the object header. In the absence of such an 1014 object, this should be of zero length." 1015 ::= { rsvpResvEntry 23 } 1017 rsvpResvStatus OBJECT-TYPE 1018 SYNTAX RowStatus 1019 MAX-ACCESS read-create 1020 STATUS current 1021 DESCRIPTION 1022 "'valid' for all active RESV messages. This 1023 object may be used to install static RESV in- 1024 formation or delete RESV information." 1025 ::= { rsvpResvEntry 24 } 1027 -- The RSVP Reservation Requests Forwarded Table contains the 1028 -- information displayed by receivers regarding their needs with 1029 -- respect to sessions and senders. It is in essence a list of the 1030 -- valid RESV messages that the RSVP Router or Host is sending 1031 -- to its upstream neighbors. 1033 rsvpResvFwdNewIndex OBJECT-TYPE 1034 SYNTAX TestAndIncr 1035 MAX-ACCESS read-write 1036 STATUS current 1037 DESCRIPTION 1038 "This object is used to assign values to 1039 rsvpResvFwdNumber as described in 'Textual Con- 1040 ventions for SNMPv2'. The network manager 1041 reads the object, and then writes the value 1042 back in the SET that creates a new instance of 1043 rsvpResvFwdEntry. If the SET fails with the 1044 code 'inconsistentValue', then the process must 1045 be repeated; If the SET succeeds, then the ob- 1046 ject is incremented, and the new instance is 1047 created according to the manager's directions." 1048 ::= { rsvpGenObjects 4 } 1050 rsvpResvFwdTable OBJECT-TYPE 1051 SYNTAX SEQUENCE OF RsvpResvFwdEntry 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "Information describing the state information 1056 displayed upstream in RESV messages." 1057 ::= { rsvpObjects 4 } 1059 rsvpResvFwdEntry OBJECT-TYPE 1060 SYNTAX RsvpResvFwdEntry 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "Information describing the state information 1065 displayed upstream in an RESV message concern- 1066 ing a single sender." 1067 INDEX { rsvpSessionNumber, rsvpResvFwdNumber } 1068 ::= { rsvpResvFwdTable 1 } 1070 RsvpResvFwdEntry ::= 1071 SEQUENCE { 1072 rsvpResvFwdNumber SessionNumber, 1073 rsvpResvFwdType SessionType, 1074 rsvpResvFwdDestAddr OCTET STRING, 1075 rsvpResvFwdSenderAddr OCTET STRING, 1076 rsvpResvFwdProtocol Protocol, 1077 rsvpResvFwdDestPort Port, 1078 rsvpResvFwdPort Port, 1079 rsvpResvFwdInterface InterfaceIndex, 1080 rsvpResvFwdService QosService, 1081 rsvpResvFwdTSpecRate BitRate, 1082 rsvpResvFwdTSpecPeakRate BitRate, 1083 rsvpResvFwdTSpecBurst BurstSize, 1084 rsvpResvFwdTSpecLevel DelayClass, 1085 rsvpResvFwdTSpecMinTU MessageSize, 1086 rsvpResvFwdTSpecMaxTU MessageSize, 1087 rsvpResvFwdInterval RefreshInterval, 1088 rsvpResvFwdScope OCTET STRING, 1089 rsvpResvFwdShared TruthValue, 1090 rsvpResvFwdExplicit TruthValue, 1091 rsvpResvFwdRSVPHop TruthValue, 1092 rsvpResvFwdLastChange TimeStamp, 1093 rsvpResvFwdPolicy OCTET STRING, 1094 rsvpResvFwdStatus RowStatus 1095 } 1097 rsvpResvFwdNumber OBJECT-TYPE 1098 SYNTAX SessionNumber 1099 MAX-ACCESS not-accessible 1100 STATUS current 1101 DESCRIPTION 1102 "The number of this session. This is for SNMP 1103 Indexing purposes only and has no relation to 1104 any protocol vaalue." 1105 ::= { rsvpResvFwdEntry 1 } 1107 rsvpResvFwdType OBJECT-TYPE 1108 SYNTAX SessionType 1109 MAX-ACCESS read-create 1110 STATUS current 1111 DESCRIPTION 1112 "The type of session (IP4, IP6, IP6 with flow 1113 information, etc), and therefore the structure 1114 of the information." 1115 ::= { rsvpResvFwdEntry 2 } 1117 rsvpResvFwdDestAddr OBJECT-TYPE 1118 SYNTAX OCTET STRING 1119 MAX-ACCESS read-create 1120 STATUS current 1121 DESCRIPTION 1122 "The Address used as a destination address by 1123 all senders in this session." 1124 ::= { rsvpResvFwdEntry 3 } 1126 rsvpResvFwdSenderAddr OBJECT-TYPE 1127 SYNTAX OCTET STRING 1128 MAX-ACCESS read-create 1129 STATUS current 1130 DESCRIPTION 1131 "The Address used as a source address by this 1132 sender in this session. The value 0 designates 1133 'any sender'." 1134 ::= { rsvpResvFwdEntry 4 } 1136 rsvpResvFwdProtocol OBJECT-TYPE 1137 SYNTAX Protocol 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION 1141 "The IP Protocol used by a session. for secure 1142 sessions, this indicates IP Security." 1143 ::= { rsvpResvFwdEntry 5 } 1145 rsvpResvFwdDestPort OBJECT-TYPE 1146 SYNTAX Port 1147 MAX-ACCESS read-create 1148 STATUS current 1149 DESCRIPTION 1150 "The UDP or TCP port number used as a destina- 1151 tion port for all senders in this session. A 1152 value of zero indicates that the IP protocol in 1153 use, specified by rsvpSessionProtocol, does not 1154 have ports." 1155 ::= { rsvpResvFwdEntry 6 } 1157 rsvpResvFwdPort OBJECT-TYPE 1158 SYNTAX Port 1159 MAX-ACCESS read-create 1160 STATUS current 1161 DESCRIPTION 1162 "The UDP or TCP port number used as a source 1163 port for this sender in this session. A value 1164 of zero indicates that the IP protocol in use, 1165 specified by rsvpSessionProtocol, does not have 1166 ports." 1167 ::= { rsvpResvFwdEntry 7 } 1169 rsvpResvFwdInterface OBJECT-TYPE 1170 SYNTAX InterfaceIndex 1171 MAX-ACCESS read-create 1172 STATUS current 1173 DESCRIPTION 1174 "The ifIndex value of the interface on which 1175 this RESV message was most recently sent." 1176 ::= { rsvpResvFwdEntry 8 } 1178 rsvpResvFwdService OBJECT-TYPE 1179 SYNTAX QosService 1180 MAX-ACCESS read-create 1181 STATUS current 1182 DESCRIPTION 1183 "The QoS Service classification requested." 1184 ::= { rsvpResvFwdEntry 9 } 1186 rsvpResvFwdTSpecRate OBJECT-TYPE 1187 SYNTAX BitRate 1188 UNITS "kilobits per second" 1189 MAX-ACCESS read-create 1190 STATUS current 1191 DESCRIPTION 1192 "The Average Bit Rate of the sender's data 1193 stream, in kilobits/second. Within a transmis- 1194 sion burst, the arrival rate may be as fast as 1195 rsvpResvFwdTSpecPeakRate (if supported by the 1196 service model); however, averaged across two or 1197 more burst intervals, the rate should not 1198 exceed rsvpResvFwdTSpecRate. 1200 Note that this is a prediction, often based on 1201 the general capability of a type of codec or 1202 particular encoding; the measured average rate 1203 may be significantly lower." 1204 ::= { rsvpResvFwdEntry 10 } 1206 rsvpResvFwdTSpecPeakRate OBJECT-TYPE 1207 SYNTAX BitRate 1208 UNITS "kilobits per second" 1209 MAX-ACCESS read-create 1210 STATUS current 1211 DESCRIPTION 1212 "The Peak Bit Rate of the sender's data stream, 1213 in kilobits/second. Traffic arrival is not ex- 1214 pected to exceed this rate at any time, apart 1215 from the effects of jitter in the network. If 1216 not specified in the TSpec, this returns zero 1217 or noSuchValue." 1218 ::= { rsvpResvFwdEntry 11 } 1220 rsvpResvFwdTSpecBurst OBJECT-TYPE 1221 SYNTAX BurstSize 1222 UNITS "bits" 1223 MAX-ACCESS read-create 1224 STATUS current 1225 DESCRIPTION 1226 "The size of the largest burst expected from 1227 the sender at a time. 1229 If this is less than the sender's advertised 1230 burst size, the receiver is asking the network 1231 to provide flow pacing beyond what would be 1232 provided under normal circumstances. Such pac- 1233 ing is at the network's option." 1234 ::= { rsvpResvFwdEntry 12 } 1236 rsvpResvFwdTSpecLevel OBJECT-TYPE 1237 SYNTAX DelayClass 1238 MAX-ACCESS read-create 1239 STATUS current 1240 DESCRIPTION 1241 "If the service is predictive or controlled- 1242 delay, this is the service level that is being 1243 requested. Otherwise, it is zero, or the agent 1244 may return noSuchValue." 1245 ::= { rsvpResvFwdEntry 13 } 1247 rsvpResvFwdTSpecMinTU OBJECT-TYPE 1248 SYNTAX MessageSize 1249 MAX-ACCESS read-create 1250 STATUS current 1251 DESCRIPTION 1252 "The minimum message size for this flow. The 1253 policing algorithm will treat smaller messages 1254 as though they are this size." 1255 ::= { rsvpResvFwdEntry 14 } 1257 rsvpResvFwdTSpecMaxTU OBJECT-TYPE 1258 SYNTAX MessageSize 1259 MAX-ACCESS read-create 1260 STATUS current 1261 DESCRIPTION 1262 "The maximum message size for this flow. The 1263 admission algorithm will reject TSpecs whose 1264 Maximum Transmission Unit, plus the interface 1265 headers, exceed the interface MTU." 1266 ::= { rsvpResvFwdEntry 15 } 1268 rsvpResvFwdInterval OBJECT-TYPE 1269 SYNTAX RefreshInterval 1270 MAX-ACCESS read-create 1271 STATUS current 1272 DESCRIPTION 1273 "The interval between RESV receipt of refresh 1274 messages advertised to the Previous Hop." 1275 ::= { rsvpResvFwdEntry 16 } 1277 rsvpResvFwdScope OBJECT-TYPE 1278 SYNTAX OCTET STRING 1279 MAX-ACCESS read-create 1280 STATUS current 1281 DESCRIPTION 1282 "The contents of the scope object, displayed as 1283 an uninterpreted string of octets, including 1284 the object header. In the absence of such an 1285 object, this should be of zero length." 1286 ::= { rsvpResvFwdEntry 17 } 1288 rsvpResvFwdShared OBJECT-TYPE 1289 SYNTAX TruthValue 1290 MAX-ACCESS read-create 1291 STATUS current 1292 DESCRIPTION 1293 "If TRUE, a reservation shared among senders is 1294 requested. If FALSE, a reservation specific to 1295 this sender is requested." 1296 ::= { rsvpResvFwdEntry 18 } 1298 rsvpResvFwdExplicit OBJECT-TYPE 1299 SYNTAX TruthValue 1300 MAX-ACCESS read-create 1301 STATUS current 1302 DESCRIPTION 1303 "If TRUE, individual senders are listed using 1304 Filter Specifications. If FALSE, senders are 1305 listed in the Scope Object." 1306 ::= { rsvpResvFwdEntry 19 } 1308 rsvpResvFwdRSVPHop OBJECT-TYPE 1309 SYNTAX TruthValue 1310 MAX-ACCESS read-create 1311 STATUS current 1312 DESCRIPTION 1313 "If TRUE, the node believes that the next hop 1314 is an RSVP hop. If FALSE, the node believes 1315 that the next hop may not be an RSVP hop." 1316 ::= { rsvpResvFwdEntry 20 } 1318 rsvpResvFwdLastChange OBJECT-TYPE 1319 SYNTAX TimeStamp 1320 MAX-ACCESS read-only 1321 STATUS current 1322 DESCRIPTION 1323 "The time of the last change in this request; 1324 This includes the first time it was requested, 1325 or time of the most recent change in parameters 1326 requested." 1327 ::= { rsvpResvFwdEntry 21 } 1329 rsvpResvFwdPolicy OBJECT-TYPE 1330 SYNTAX OCTET STRING 1331 MAX-ACCESS read-create 1332 STATUS current 1333 DESCRIPTION 1334 "The contents of the policy object, displayed 1335 as an uninterpreted string of octets, including 1336 the object header. In the absence of such an 1337 object, this should be of zero length." 1338 ::= { rsvpResvFwdEntry 22 } 1340 rsvpResvFwdStatus OBJECT-TYPE 1341 SYNTAX RowStatus 1342 MAX-ACCESS read-create 1343 STATUS current 1344 DESCRIPTION 1345 "'valid' for all active RESV messages. This 1346 object may be used to install static RESV in- 1347 formation or delete RESV information." 1348 ::= { rsvpResvFwdEntry 23 } 1350 -- The RSVP Active Flows Database 1351 -- lists all flows active on an outgoing interface, including 1352 -- relevant attributes. 1354 rsvpFlowTable OBJECT-TYPE 1355 SYNTAX SEQUENCE OF RsvpFlowEntry 1356 MAX-ACCESS not-accessible 1357 STATUS current 1358 DESCRIPTION 1359 "Information describing the reserved flows us- 1360 ing the system's interfaces." 1361 ::= { rsvpObjects 5 } 1363 rsvpFlowEntry OBJECT-TYPE 1364 SYNTAX RsvpFlowEntry 1365 MAX-ACCESS not-accessible 1366 STATUS current 1367 DESCRIPTION 1368 "Information describing the use of a given in- 1369 terface by a given flow." 1370 INDEX { rsvpFlowNumber } 1371 ::= { rsvpFlowTable 1 } 1373 RsvpFlowEntry ::= 1374 SEQUENCE { 1375 rsvpFlowNumber SessionNumber, 1376 rsvpFlowType SessionType, 1377 rsvpFlowDestAddr OCTET STRING, 1378 rsvpFlowSenderAddr OCTET STRING, 1379 rsvpFlowProtocol Protocol, 1380 rsvpFlowDestPort Port, 1381 rsvpFlowPort Port, 1382 rsvpFlowInterface InterfaceIndex, 1383 rsvpFlowRate BitRate, 1384 rsvpFlowBurst BurstSize, 1385 rsvpFlowWeight Integer32, 1386 rsvpFlowQueue Integer32, 1387 rsvpFlowMinTU MessageSize, 1388 rsvpFlowDontAsk TimeInterval, 1389 rsvpFlowStatus RowStatus 1390 } 1392 rsvpFlowNumber OBJECT-TYPE 1393 SYNTAX SessionNumber 1394 MAX-ACCESS not-accessible 1395 STATUS current 1396 DESCRIPTION 1397 "The number of this session. This is for SNMP 1398 Indexing purposes only and has no relation to 1399 any protocol vaalue." 1400 ::= { rsvpFlowEntry 1 } 1402 rsvpFlowType OBJECT-TYPE 1403 SYNTAX SessionType 1404 MAX-ACCESS read-create 1405 STATUS current 1406 DESCRIPTION 1407 "The type of session (IP4, IP6, IP6 with flow 1408 information, etc), and therefore the structure 1409 of the information." 1410 ::= { rsvpFlowEntry 2 } 1412 rsvpFlowDestAddr OBJECT-TYPE 1413 SYNTAX OCTET STRING 1414 MAX-ACCESS read-create 1415 STATUS current 1416 DESCRIPTION 1417 "The Address used as a destination address by 1418 all senders in this session." 1419 ::= { rsvpFlowEntry 3 } 1421 rsvpFlowSenderAddr OBJECT-TYPE 1422 SYNTAX OCTET STRING 1423 MAX-ACCESS read-create 1424 STATUS current 1425 DESCRIPTION 1426 "The Address used as a source address by this 1427 sender in this session." 1428 ::= { rsvpFlowEntry 4 } 1430 rsvpFlowProtocol OBJECT-TYPE 1431 SYNTAX Protocol 1432 MAX-ACCESS read-create 1433 STATUS current 1434 DESCRIPTION 1435 "The IP Protocol used by a session. for secure 1436 sessions, this indicates IP Security." 1437 ::= { rsvpFlowEntry 5 } 1439 rsvpFlowDestPort OBJECT-TYPE 1440 SYNTAX Port 1441 MAX-ACCESS read-create 1442 STATUS current 1443 DESCRIPTION 1444 "The UDP or TCP port number used as a destina- 1445 tion port for all senders in this session. A 1446 value of zero indicates that the IP protocol in 1447 use, specified by rsvpSessionProtocol, does not 1448 have ports." 1449 ::= { rsvpFlowEntry 6 } 1451 rsvpFlowPort OBJECT-TYPE 1452 SYNTAX Port 1453 MAX-ACCESS read-create 1454 STATUS current 1455 DESCRIPTION 1456 "The UDP or TCP port number used as a source 1457 port for this sender in this session. A value 1458 of zero indicates that the IP protocol in use, 1459 specified by rsvpSessionProtocol, does not have 1460 ports." 1461 ::= { rsvpFlowEntry 7 } 1463 rsvpFlowInterface OBJECT-TYPE 1464 SYNTAX InterfaceIndex 1465 MAX-ACCESS read-create 1466 STATUS current 1467 DESCRIPTION 1468 "The ifIndex value of the interface on which 1469 this PATH message was most recently received." 1470 ::= { rsvpFlowEntry 8 } 1472 rsvpFlowRate OBJECT-TYPE 1473 SYNTAX BitRate 1474 UNITS "kilobits per second" 1475 MAX-ACCESS read-create 1476 STATUS current 1477 DESCRIPTION 1478 "The Average Bit Rate of the sender's data 1479 stream, in Kilobits. The rate may be arbi- 1480 trarily fast during a short interval such as 1481 the duration of a video frame. However, over 1482 any two such intervals it will not average fas- 1483 ter than the average rate as transmitted by the 1484 sender." 1485 ::= { rsvpFlowEntry 9 } 1487 rsvpFlowBurst OBJECT-TYPE 1488 SYNTAX BurstSize 1489 UNITS "bits" 1490 MAX-ACCESS read-create 1491 STATUS current 1492 DESCRIPTION 1493 "The size of the largest burst expected from 1494 the sender at a time. 1496 If this is less than the sender's advertised 1497 burst size, the receiver is asking the network 1498 to provide flow pacing beyond what would be 1499 provided under normal circumstances. Such pac- 1500 ing is at the network's option." 1501 ::= { rsvpFlowEntry 10 } 1503 rsvpFlowWeight OBJECT-TYPE 1504 SYNTAX Integer32 1505 MAX-ACCESS read-create 1506 STATUS current 1507 DESCRIPTION 1508 "The weight used to prioritize the traffic. 1509 Note that the interpretation of this object is 1510 implementation-specific, as implementations 1511 vary in their use of weighting procedures." 1512 ::= { rsvpFlowEntry 11 } 1514 rsvpFlowQueue OBJECT-TYPE 1515 SYNTAX Integer32 1516 MAX-ACCESS read-create 1517 STATUS current 1518 DESCRIPTION 1519 "The number of the queue used by this traffic. 1520 Note that the interpretation of this object is 1521 implementation-specific, as implementations 1522 vary in their use of queue identifiers." 1523 ::= { rsvpFlowEntry 12 } 1525 rsvpFlowMinTU OBJECT-TYPE 1526 SYNTAX MessageSize 1527 MAX-ACCESS read-create 1528 STATUS current 1529 DESCRIPTION 1530 "The minimum message size for this flow. The 1531 policing algorithm will treat smaller messages 1532 as though they are this size." 1533 ::= { rsvpFlowEntry 13 } 1535 rsvpFlowDontAsk OBJECT-TYPE 1536 SYNTAX TimeInterval 1537 MAX-ACCESS read-create 1538 STATUS current 1539 DESCRIPTION 1540 "A period of time, measured in hundredths of a 1541 second, during which the agent is precluded 1542 from sending a newFlow notification for this 1543 conversation. 1545 If an authorizing application leaves rsvpFlowS- 1546 tatus in a state other than 'valid' and sets 1547 rsvpFlowDontAsk to a non-zero value, the agent 1548 must neither consider the flow active for ad- 1549 mission or queuing purposes, or re-request au- 1550 thorization to install it, until the indicated 1551 amount of time has elapsed." 1552 ::= { rsvpFlowEntry 14 } 1554 rsvpFlowStatus OBJECT-TYPE 1555 SYNTAX RowStatus 1556 MAX-ACCESS read-create 1557 STATUS current 1558 DESCRIPTION 1559 "'valid' for all active flows. This object may 1560 be used to install static classifier informa- 1561 tion, delete classifier information, or author- 1562 ize such." 1563 ::= { rsvpFlowEntry 15 } 1565 -- The RSVP Interface Attributes Database contains the 1566 -- RSVP-specific information for an interface. Information 1567 -- that is shared with other reservation procedures such 1568 -- as ST-II is in the Integrated Interface Attributes 1569 -- Database. 1571 rsvpIfTable OBJECT-TYPE 1572 SYNTAX SEQUENCE OF RsvpIfEntry 1573 MAX-ACCESS not-accessible 1574 STATUS current 1575 DESCRIPTION 1576 "The RSVP-specific attributes of the system's 1577 interfaces." 1578 ::= { rsvpObjects 6 } 1580 rsvpIfEntry OBJECT-TYPE 1581 SYNTAX RsvpIfEntry 1582 MAX-ACCESS not-accessible 1583 STATUS current 1584 DESCRIPTION 1585 "The RSVP-specific attributes of the a given 1586 interface." 1587 INDEX { ifIndex } 1589 ::= { rsvpIfTable 1 } 1591 RsvpIfEntry ::= 1592 SEQUENCE { 1593 rsvpIfUdpNbrs Gauge32, 1594 rsvpIfIpNbrs Gauge32, 1595 rsvpIfNbrs Gauge32, 1596 rsvpIfEnabled TruthValue, 1597 rsvpIfUdpRequired TruthValue, 1598 rsvpIfRefreshBlockadeMultiple INTEGER, 1599 rsvpIfRefreshMultiple INTEGER, 1600 rsvpIfTTL INTEGER, 1601 rsvpIfRefreshInterval TimeInterval, 1602 rsvpIfRouteDelay TimeInterval, 1603 rsvpIfStatus RowStatus 1604 } 1605 rsvpIfUdpNbrs OBJECT-TYPE 1606 SYNTAX Gauge32 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "The number of neighbors perceived to be using 1611 only the RSVP UDP Encapsulation." 1612 ::= { rsvpIfEntry 1 } 1614 rsvpIfIpNbrs OBJECT-TYPE 1615 SYNTAX Gauge32 1616 MAX-ACCESS read-only 1617 STATUS current 1618 DESCRIPTION 1619 "The number of neighbors perceived to be using 1620 only the RSVP IP Encapsulation." 1621 ::= { rsvpIfEntry 2 } 1623 rsvpIfNbrs OBJECT-TYPE 1624 SYNTAX Gauge32 1625 MAX-ACCESS read-only 1626 STATUS current 1627 DESCRIPTION 1628 "The number of neighbors currently perceived; 1629 this will exceed rsvpIfIpNbrs + rsvpIfUdpNbrs 1630 by the number of neighbors using both encapsu- 1631 lations." 1632 ::= { rsvpIfEntry 3 } 1634 rsvpIfRefreshBlockadeMultiple OBJECT-TYPE 1635 SYNTAX INTEGER (1..65536) 1636 MAX-ACCESS read-create 1637 STATUS current 1638 DESCRIPTION 1639 "The value of the RSVP value 'Kb', Which is the 1640 minimum number of refresh intervals that 1641 blockade state will last once entered." 1642 DEFVAL { 4 } 1643 ::= { rsvpIfEntry 4 } 1645 rsvpIfRefreshMultiple OBJECT-TYPE 1646 SYNTAX INTEGER (1..65536) 1647 MAX-ACCESS read-create 1648 STATUS current 1649 DESCRIPTION 1650 "The value of the RSVP value 'K', which is the 1651 number of refresh intervals which must elapse 1652 (minimum) before a PATH or RESV message which 1653 is not being refreshed will be aged out." 1654 DEFVAL { 4 } 1655 ::= { rsvpIfEntry 5 } 1657 rsvpIfTTL OBJECT-TYPE 1658 SYNTAX INTEGER (0..255) 1659 MAX-ACCESS read-create 1660 STATUS current 1661 DESCRIPTION 1662 "The value of SEND_TTL used on this interface. 1663 If set to zero, then the TTL in RSVP messages 1664 is not overridden." 1665 DEFVAL { 0 } -- which is to say, no override 1666 ::= { rsvpIfEntry 6 } 1668 rsvpIfRefreshInterval OBJECT-TYPE 1669 SYNTAX TimeInterval 1670 UNITS "hundredths of a second" 1671 MAX-ACCESS read-create 1672 STATUS current 1673 DESCRIPTION 1674 "The value of the RSVP value 'R', which is the 1675 minimum period between refresh transmissions of 1676 a given PATH or RESV message on an interface." 1677 DEFVAL { 3000 } -- 30 seconds 1678 ::= { rsvpIfEntry 7 } 1680 rsvpIfRouteDelay OBJECT-TYPE 1681 SYNTAX TimeInterval 1682 UNITS "hundredths of a second" 1683 MAX-ACCESS read-create 1684 STATUS current 1685 DESCRIPTION 1686 "The approximate period from the time a route 1687 is changed to the time that a route is changed 1688 to the time a resulting message appears on the 1689 interface." 1690 DEFVAL { 200 } -- 2 seconds 1691 ::= { rsvpIfEntry 8 } 1693 rsvpIfEnabled OBJECT-TYPE 1694 SYNTAX TruthValue 1695 MAX-ACCESS read-create 1696 STATUS current 1697 DESCRIPTION 1698 "If TRUE, RSVP is enabled on this Interface. 1699 If FALSE, RSVP is not enabled on this inter- 1700 face." 1701 ::= { rsvpIfEntry 9 } 1703 rsvpIfUdpRequired OBJECT-TYPE 1704 SYNTAX TruthValue 1705 MAX-ACCESS read-create 1706 STATUS current 1707 DESCRIPTION 1708 "If TRUE, manual configuration forces the use 1709 of UDP encapsulation on the interface. If 1710 FALSE, UDP encapsulation is only used if rsvpI- 1711 fUdpNbrs is not zero." 1713 ::= { rsvpIfEntry 10 } 1715 rsvpIfStatus OBJECT-TYPE 1716 SYNTAX RowStatus 1717 MAX-ACCESS read-create 1718 STATUS current 1719 DESCRIPTION 1720 "'valid' on interfaces that are configured for 1721 RSVP." 1722 ::= { rsvpIfEntry 11 } 1724 -- The RSVP Neighbor Database lists the neighbors the RSVP 1725 -- process currently is receiving messages from. 1727 rsvpNbrTable OBJECT-TYPE 1728 SYNTAX SEQUENCE OF RsvpNbrEntry 1729 MAX-ACCESS not-accessible 1730 STATUS current 1731 DESCRIPTION 1732 "Information describing the Neighbors of an 1733 RSVP system." 1734 ::= { rsvpObjects 7 } 1736 rsvpNbrEntry OBJECT-TYPE 1737 SYNTAX RsvpNbrEntry 1738 MAX-ACCESS not-accessible 1739 STATUS current 1740 DESCRIPTION 1741 "Information describing a single RSVP Neigh- 1742 bor." 1743 INDEX { ifIndex, rsvpNbrAddress } 1744 ::= { rsvpNbrTable 1 } 1746 RsvpNbrEntry ::= 1747 SEQUENCE { 1748 rsvpNbrAddress OCTET STRING, 1749 rsvpNbrProtocol RsvpEncapsulation, 1750 rsvpNbrStatus RowStatus 1751 } 1753 rsvpNbrAddress OBJECT-TYPE 1754 SYNTAX OCTET STRING (SIZE(4..16)) 1755 MAX-ACCESS not-accessible 1756 STATUS current 1757 DESCRIPTION 1758 "The IP4 or IP6 Address used by this neighbor." 1759 ::= { rsvpNbrEntry 1 } 1761 rsvpNbrProtocol OBJECT-TYPE 1762 SYNTAX RsvpEncapsulation 1763 MAX-ACCESS read-create 1764 STATUS current 1765 DESCRIPTION 1766 "The encapsulation being used by this neigh- 1767 bor." 1768 ::= { rsvpNbrEntry 2 } 1770 rsvpNbrStatus OBJECT-TYPE 1771 SYNTAX RowStatus 1772 MAX-ACCESS read-create 1773 STATUS current 1774 DESCRIPTION 1775 "'valid' for all neighbors. This object may be 1776 used to configure neighbors. In the presence 1777 of configured neighbors, the implementation may 1778 (but is not required to) limit the set of valid 1779 neighbors to those configured." 1780 ::= { rsvpNbrEntry 3 } 1782 -- 1783 -- Notifications used to signal events 1784 -- 1786 newFlow NOTIFICATION-TYPE 1787 OBJECTS { 1788 rsvpFlowNumber, rsvpFlowType, rsvpFlowDestAddr, 1789 rsvpFlowSenderAddr, rsvpFlowProtocol, rsvpFlowDestPort, 1790 rsvpFlowPort, rsvpFlowInterface, rsvpFlowRate, rsvpFlowBurst, 1791 rsvpFlowWeight, rsvpFlowQueue, rsvpFlowMinTU 1792 } 1793 STATUS current 1794 DESCRIPTION 1795 "The newFlow trap indicates that the originat- 1796 ing system has installed a new flow in its 1797 classifier, or (when reservation authorization 1798 is in view) is prepared to install such a flow 1799 in the classifier and is requesting authoriza- 1800 tion. The objects included with the Notifica- 1801 tion may be used to read further information 1802 using the RSVP MIB. Authorization or non- 1803 authorization may be enacted by a write to the 1804 variable rsvpFlowStatus." 1805 ::= { rsvpNotifications 1 } 1807 lostFlow NOTIFICATION-TYPE 1808 OBJECTS { 1809 rsvpFlowNumber, rsvpFlowType, rsvpFlowDestAddr, 1810 rsvpFlowSenderAddr, rsvpFlowProtocol, rsvpFlowDestPort, 1811 rsvpFlowPort, rsvpFlowInterface 1812 } 1813 STATUS current 1814 DESCRIPTION 1815 "The lostFlow trap indicates that the originat- 1816 ing system has removed a flow in its classif- 1817 ier." 1818 ::= { rsvpNotifications 2 } 1820 -- conformance information 1822 rsvpGroups OBJECT IDENTIFIER ::= { rsvpConformance 1 } 1823 rsvpCompliances OBJECT IDENTIFIER ::= { rsvpConformance 2 } 1825 -- compliance statements 1827 rsvpCompliance MODULE-COMPLIANCE 1828 STATUS current 1829 DESCRIPTION 1830 "The compliance statement. Note that the im- 1831 plementation of this module requires implemen- 1832 tation of the Integrated Services MIB as well." 1833 MODULE -- this module 1834 MANDATORY-GROUPS { 1835 rsvpSessionGroup, rsvpSenderGroup, rsvpResvGroup, 1836 rsvpResvFwdGroup, rsvpFlowGroup, rsvpIfGroup, 1837 rsvpNbrGroup 1838 } 1839 ::= { rsvpCompliances 1 } 1841 rsvpSessionGroup OBJECT-GROUP 1842 OBJECTS { 1843 rsvpSessionNewIndex, rsvpSessionType, rsvpSessionDestAddr, 1844 rsvpSessionProtocol, rsvpSessionPort, rsvpSessionSenders, 1845 rsvpSessionReceivers, rsvpSessionRequests 1846 } 1847 STATUS current 1848 DESCRIPTION 1849 "These objects are required for RSVP Systems." 1850 ::= { rsvpGroups 1 } 1852 rsvpSenderGroup OBJECT-GROUP 1853 OBJECTS { 1854 rsvpSenderType, rsvpSenderDestAddr, rsvpSenderSenderAddr, 1855 rsvpSenderProtocol, rsvpSenderDestPort, rsvpSenderPort, 1856 rsvpSenderHopAddr, rsvpSenderInterface, rsvpSenderTSpecRate, 1857 rsvpSenderTSpecPeakRate, rsvpSenderTSpecBurst, 1858 rsvpSenderTSpecMinTU, rsvpSenderTSpecMaxTU, rsvpSenderInterval, 1859 rsvpSenderLastChange, rsvpSenderStatus, rsvpSenderRSVPHop, 1860 rsvpSenderPolicy, rsvpSenderAdspec, rsvpSenderNewIndex 1861 } 1862 STATUS current 1863 DESCRIPTION 1864 "These objects are required for RSVP Systems." 1865 ::= { rsvpGroups 2 } 1867 rsvpResvGroup OBJECT-GROUP 1868 OBJECTS { 1869 rsvpResvType, rsvpResvDestAddr, rsvpResvSenderAddr, 1870 rsvpResvProtocol, rsvpResvDestPort, rsvpResvPort, 1871 rsvpResvHopAddr, rsvpResvInterface, rsvpResvService, 1872 rsvpResvTSpecRate, rsvpResvTSpecBurst, rsvpResvTSpecPeakRate, 1873 rsvpResvTSpecMinTU, rsvpResvTSpecMaxTU, rsvpResvTSpecLevel, 1874 rsvpResvInterval, rsvpResvScope, rsvpResvShared, 1875 rsvpResvExplicit, rsvpResvRSVPHop, rsvpResvLastChange, 1876 rsvpResvPolicy, rsvpResvStatus, rsvpResvNewIndex 1877 } 1878 STATUS current 1879 DESCRIPTION 1880 "These objects are required for RSVP Systems." 1881 ::= { rsvpGroups 3 } 1883 rsvpResvFwdGroup OBJECT-GROUP 1884 OBJECTS { 1885 rsvpResvFwdType, rsvpResvFwdDestAddr, rsvpResvFwdSenderAddr, 1886 rsvpResvFwdProtocol, rsvpResvFwdDestPort, rsvpResvFwdPort, 1887 rsvpResvFwdInterface, rsvpResvFwdNewIndex, rsvpResvFwdService, 1888 rsvpResvFwdTSpecPeakRate, rsvpResvFwdTSpecMinTU, 1889 rsvpResvFwdTSpecMaxTU, rsvpResvFwdTSpecRate, 1890 rsvpResvFwdTSpecBurst, rsvpResvFwdTSpecLevel, 1891 rsvpResvFwdInterval, rsvpResvFwdScope, rsvpResvFwdShared, 1892 rsvpResvFwdExplicit, rsvpResvFwdRSVPHop, rsvpResvFwdLastChange, 1893 rsvpResvFwdPolicy, rsvpResvFwdStatus 1894 } 1895 STATUS current 1896 DESCRIPTION 1897 "These objects are required for RSVP Systems." 1898 ::= { rsvpGroups 4 } 1900 rsvpFlowGroup OBJECT-GROUP 1901 OBJECTS { 1902 rsvpFlowType, rsvpFlowDestAddr, rsvpFlowSenderAddr, 1903 rsvpFlowProtocol, rsvpFlowDestPort, rsvpFlowPort, 1904 rsvpFlowInterface, rsvpFlowDontAsk, rsvpFlowRate, 1905 rsvpFlowBurst, rsvpFlowWeight, rsvpFlowQueue, rsvpFlowMinTU, 1906 rsvpFlowStatus 1907 } 1908 STATUS current 1909 DESCRIPTION 1910 "These objects are required for RSVP Systems." 1911 ::= { rsvpGroups 5 } 1913 rsvpIfGroup OBJECT-GROUP 1914 OBJECTS { 1915 rsvpIfUdpNbrs, rsvpIfIpNbrs, rsvpIfNbrs, rsvpIfEnabled, 1916 rsvpIfUdpRequired, rsvpIfRefreshBlockadeMultiple, 1917 rsvpIfRefreshMultiple, rsvpIfRefreshInterval, rsvpIfTTL, 1918 rsvpIfRouteDelay, rsvpIfStatus 1919 } 1920 STATUS current 1921 DESCRIPTION 1922 "These objects are required for RSVP Systems." 1923 ::= { rsvpGroups 6 } 1925 rsvpNbrGroup OBJECT-GROUP 1926 OBJECTS { 1927 rsvpNbrProtocol, rsvpNbrStatus 1928 } 1929 STATUS current 1930 DESCRIPTION 1931 "These objects are required for RSVP Systems." 1932 ::= { rsvpGroups 7 } 1934 END 1935 6. Acknowledgements 1937 This document was produced by the RSVP Working Group. 1939 7. References 1941 [1] M.T. Rose (editor), Management Information Base for 1942 Network Management of TCP/IP-based internets, Internet 1943 Working Group Request for Comments 1213. Network 1944 Information Center, SRI International, Menlo Park, 1945 California, (May, 1990). 1947 [2] Information processing systems - Open Systems 1948 Interconnection - Specification of Abstract Syntax 1949 Notation One (ASN.1), International Organization for 1950 Standardization. International Standard 8824, (December, 1951 1987). 1953 [3] Information processing systems - Open Systems 1954 Interconnection - Specification of Basic Encoding Rules 1955 for Abstract Notation One (ASN.1), International 1956 Organization for Standardization. International Standard 1957 8825, (December, 1987). 1959 Table of Contents 1961 1 Status of this Memo ................................... 1 1962 2 Abstract .............................................. 2 1963 3 The SNMPv2 Network Management Framework ............... 3 1964 3.1 Object Definitions .................................. 3 1965 4 Overview .............................................. 3 1966 4.1 Textual Conventions ................................. 3 1967 4.2 Structure of MIB .................................... 4 1968 5 Definitions ........................................... 5 1969 5.1 RSVP Session Statistics Database .................... 8 1970 5.1 RSVP Session Sender Database ........................ 12 1971 5.2 RSVP Reservations Requested Database ................ 20 1972 5.3 RSVP Reservation Requests Database .................. 29 1973 5.3 RSVP Interface Flows Database ....................... 38 1974 5.4 RSVP Interface Attributes Database .................. 44 1975 5.5 RSVP Neighbor Database .............................. 49 1976 5.4 Notifications ....................................... 51 1977 6 Acknowledgements ...................................... 57 1978 7 References ............................................ 58