idnits 2.17.1 draft-ietf-rsvp-mib-06.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-24) 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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 80 pages 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.) ** There are 377 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 6 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 216 has weird spacing: '...ds that are ...' == Line 218 has weird spacing: '...d Path or r...' == Line 232 has weird spacing: '... given sys-...' == Line 265 has weird spacing: '...ndexing purpo...' == Line 274 has weird spacing: '...6 with flow...' == (372 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 (June 1997) is 9810 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 2784 looks like a reference -- Missing reference section? '2' on line 2790 looks like a reference -- Missing reference section? '3' on line 2796 looks like a reference Summary: 12 errors (**), 0 flaws (~~), 8 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft RSVP MIB June 1997 4 RSVP Management Information Base 5 draft-ietf-rsvp-mib-06.txt 7 Thu May 22 10:17:17 PDT 1997 9 Fred Baker 11 Cisco Systems 12 519 Lado Drive 13 Santa Barbara, California 93111 15 fred@cisco.com 17 John Krawczyk 19 ArrowPoint Communications 20 235 Littleton Road 21 Westford, Massachusetts 01886 23 jjk@tiac.net 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 Interface Attributes Table 118 RSVP Neighbor Table 120 As a general rule, it is difficult in SNMP to describe 121 arbitrarily long of complex messages; this MIB therefore seeks 122 to describe the Path State Database and the Reservation State 123 Database as though each flow and filter description received 124 in an aggregate message had been received in a separate 125 reservation message. 127 Thus, if a RESV message is received for session 128 224.1.2.3+UDP+4455 with two filter/flow spec groups describing 129 a sender 1.2.3.4 and another sender 1.2.7.8, these two will 130 show in the MIB as two separate rows: one for 131 224.1.2.3+UDP+4455 from 1.2.3.4 and the other for 132 224.1.2.3+UDP+4455 from 1.2.7.8. 134 4.3. Semantics of Writing the Path and Reservation State 135 Databases 137 The path and reservation state tables are writeable. The 138 objective of writing one of these table is to insert new state 139 as if it had been received in a valid Path or Resv message. 140 State created in this way by SNMP does not time out and cannot 141 be deleted by receiving an RSVP teardown message; it can only 142 be deleted by SNMP. Deletion is accomplished by writing 143 'destroy' to the associated Row Status object, and this will 144 initiate a teardown message as if the state had timed out. 146 4.4. Intended use of Flow Notifications 148 4.4.1. The lostFlow Notification 150 The Lost Flow notification is an asychronous event that 151 signifies that a flow is no longer being observed. 153 4.4.2. The newFlow Notification 155 The newFlow Notification defined in this MIB can be used to 156 advise a network management system of the state of a flow. 158 5. Definitions 160 RSVP-MIB DEFINITIONS ::= BEGIN 162 IMPORTS 163 MODULE-IDENTITY, OBJECT-TYPE, Gauge32, 164 NOTIFICATION-TYPE, Integer32, experimental 165 FROM SNMPv2-SMI 166 TEXTUAL-CONVENTION, TruthValue, RowStatus, 167 TimeStamp, TestAndIncr, TimeInterval 168 FROM SNMPv2-TC 169 MODULE-COMPLIANCE, OBJECT-GROUP, 170 NOTIFICATION-GROUP FROM SNMPv2-CONF 171 Port, SessionNumber, SessionType, 172 Protocol, QosService, intSrvFlowStatus, 173 MessageSize, BitRate, BurstSize FROM INTEGRATED-SERVICES-MIB 174 ifIndex, InterfaceIndex FROM IF-MIB; 176 rsvp MODULE-IDENTITY 177 LAST-UPDATED "9511030500Z" -- Thu May 22 10:17:17 PDT 1997 178 ORGANIZATION "IETF RSVP Working Group" 179 CONTACT-INFO 180 " Fred Baker 181 Postal: Cisco Systems 182 519 Lado Drive 183 Santa Barbara, California 93111 184 Tel: +1 805 681 0115 185 E-Mail: fred@cisco.com 187 John Krawczyk 188 Postal: ArrowPoint Communications 189 235 Littleton Road 190 Westford, Massachusetts 01886 191 Tel: +1 508 692 5875 192 E-Mail: jjk@tiac.net" 193 DESCRIPTION 194 "The MIB module to describe the RSVP Protocol" 195 ::= { experimental 71 } 197 rsvpObjects OBJECT IDENTIFIER ::= { rsvp 1 } -- tables 198 rsvpGenObjects OBJECT IDENTIFIER ::= { rsvp 2 } -- global objects 199 rsvpNotifications OBJECT IDENTIFIER ::= { rsvp 3 } -- traps 200 rsvpConformance OBJECT IDENTIFIER ::= { rsvp 4 } -- conformance 201 RsvpEncapsulation ::= TEXTUAL-CONVENTION 202 STATUS current 203 DESCRIPTION 204 "This indicates the encapsulation that an RSVP 205 Neighbor is perceived to be using." 206 SYNTAX INTEGER { 207 ip (1), -- IP Protocol 46 208 udp (2), -- UDP Encapsulation 209 both (3) -- neighbor is using both encapsulations 210 } 212 RefreshInterval ::= TEXTUAL-CONVENTION 213 DISPLAY-HINT "d" 214 STATUS current 215 DESCRIPTION 216 "The number of milliseconds that are expected 217 to elapse between refreshes of path or reserva- 218 tion state. Unrefreshed Path or reservation 219 state is removed after a small multiple of this 220 period." 221 SYNTAX INTEGER (0..'7FFFFFFF'h) 223 -- The RSVP Session Statistics Database displays statistics 224 -- relating to the number of senders and receivers in each 225 -- session. 227 rsvpSessionTable OBJECT-TYPE 228 SYNTAX SEQUENCE OF RsvpSessionEntry 229 MAX-ACCESS not-accessible 230 STATUS current 231 DESCRIPTION 232 "A table of all sessions seen by a given sys- 233 tem." 234 ::= { rsvpObjects 1 } 236 rsvpSessionEntry OBJECT-TYPE 237 SYNTAX RsvpSessionEntry 238 MAX-ACCESS not-accessible 239 STATUS current 240 DESCRIPTION 241 "A single session seen by a given system." 242 INDEX { rsvpSessionNumber } 243 ::= { rsvpSessionTable 1 } 245 RsvpSessionEntry ::= 246 SEQUENCE { 247 rsvpSessionNumber SessionNumber, 248 rsvpSessionType SessionType, 249 rsvpSessionDestAddr OCTET STRING, 250 rsvpSessionDestAddrLength INTEGER, 251 rsvpSessionProtocol Protocol, 252 rsvpSessionPort Port, 253 rsvpSessionSenders Gauge32, 254 rsvpSessionReceivers Gauge32, 255 rsvpSessionRequests Gauge32, 256 rsvpSessionFlowId INTEGER 257 } 259 rsvpSessionNumber OBJECT-TYPE 260 SYNTAX SessionNumber 261 MAX-ACCESS not-accessible 262 STATUS current 263 DESCRIPTION 264 "The number of this session. This is for SNMP 265 Indexing purposes only and has no relation to 266 any protocol value." 267 ::= { rsvpSessionEntry 1 } 269 rsvpSessionType OBJECT-TYPE 270 SYNTAX SessionType 271 MAX-ACCESS read-only 272 STATUS current 273 DESCRIPTION 274 "The type of session (IP4, IP6, IP6 with flow 275 information, etc)." 276 ::= { rsvpSessionEntry 2 } 278 rsvpSessionDestAddr OBJECT-TYPE 279 SYNTAX OCTET STRING (SIZE(4..16)) 280 MAX-ACCESS read-only 281 STATUS current 282 DESCRIPTION 283 "The destination address used by all senders in 284 this session. This object may not be changed 285 when the value of the RowStatus object is 'ac- 286 tive'." 287 ::= { rsvpSessionEntry 3 } 289 rsvpSessionDestAddrLength OBJECT-TYPE 290 SYNTAX INTEGER(0..128) 291 MAX-ACCESS read-only 292 STATUS current 293 DESCRIPTION 294 "The CIDR prefix length of the session address, 295 which is 32 for IP4 host and multicast ad- 296 dresses, and 128 for IP6 addresses. This ob- 297 ject may not be changed when the value of the 298 RowStatus object is 'active'." 299 ::= { rsvpSessionEntry 4 } 301 rsvpSessionProtocol OBJECT-TYPE 302 SYNTAX Protocol 303 MAX-ACCESS read-only 304 STATUS current 305 DESCRIPTION 306 "The IP Protocol used by this session. This 307 object may not be changed when the value of the 308 RowStatus object is 'active'." 309 ::= { rsvpSessionEntry 5 } 311 rsvpSessionPort OBJECT-TYPE 312 SYNTAX Port 313 MAX-ACCESS read-only 314 STATUS current 315 DESCRIPTION 316 "The UDP or TCP port number used as a destina- 317 tion port for all senders in this session. If 318 the IP protocol in use, specified by rsvpSen- 319 derProtocol, is 50 (ESP) or 51 (AH), this 320 represents a virtual destination port number. 321 A value of zero indicates that the IP protocol 322 in use does not have ports. This object may 323 not be changed when the value of the RowStatus 324 object is 'active'." 325 ::= { rsvpSessionEntry 6 } 327 rsvpSessionSenders OBJECT-TYPE 328 SYNTAX Gauge32 329 MAX-ACCESS read-only 330 STATUS current 331 DESCRIPTION 332 "The number of distinct senders currently known 333 to be part of this session." 334 ::= { rsvpSessionEntry 7 } 336 rsvpSessionReceivers OBJECT-TYPE 337 SYNTAX Gauge32 338 MAX-ACCESS read-only 339 STATUS current 340 DESCRIPTION 341 "The number of reservations being requested of 342 this system for this session." 343 ::= { rsvpSessionEntry 8 } 345 rsvpSessionRequests OBJECT-TYPE 346 SYNTAX Gauge32 347 MAX-ACCESS read-only 348 STATUS current 349 DESCRIPTION 350 "The number of reservation requests this system 351 is sending upstream for this session." 352 ::= { rsvpSessionEntry 9 } 354 rsvpSessionFlowId OBJECT-TYPE 355 SYNTAX INTEGER(0..16777215) 356 MAX-ACCESS read-only 357 STATUS current 358 DESCRIPTION 359 "The flow ID for this session, if this is an 360 IPv6 session." 361 ::= { rsvpSessionEntry 10 } 363 rsvpBadPackets OBJECT-TYPE 364 SYNTAX Gauge32 365 MAX-ACCESS read-only 366 STATUS current 367 DESCRIPTION 368 "This object keeps a count of the number of bad 369 RSVP packets received." 370 ::= { rsvpGenObjects 1 } 372 -- The RSVP Session Sender Database contains the information 373 -- displayed by senders regarding their potential contribution 374 -- to session data content. It is in essence a list of the 375 -- valid PATH messages that the RSVP Router or Host is receiving. 377 rsvpSenderNewIndex OBJECT-TYPE 378 SYNTAX TestAndIncr 379 MAX-ACCESS read-write 380 STATUS current 381 DESCRIPTION 382 "This object is used to assign values to 383 rsvpSenderNumber as described in 'Textual Con- 384 ventions for SNMPv2'. The network manager 385 reads the object, and then writes the value 386 back in the SET that creates a new instance of 387 rsvpSenderEntry. If the SET fails with the 388 code 'inconsistentValue', then the process must 389 be repeated; If the SET succeeds, then the ob- 390 ject is incremented, and the new instance is 391 created according to the manager's directions." 392 ::= { rsvpGenObjects 2 } 394 rsvpSenderTable OBJECT-TYPE 395 SYNTAX SEQUENCE OF RsvpSenderEntry 396 MAX-ACCESS not-accessible 397 STATUS current 398 DESCRIPTION 399 "Information describing the state information 400 displayed by senders in PATH messages." 401 ::= { rsvpObjects 2 } 403 rsvpSenderEntry OBJECT-TYPE 404 SYNTAX RsvpSenderEntry 405 MAX-ACCESS not-accessible 406 STATUS current 407 DESCRIPTION 408 "Information describing the state information 409 displayed by a single sender's PATH message." 410 INDEX { rsvpSessionNumber, rsvpSenderNumber } 411 ::= { rsvpSenderTable 1 } 413 RsvpSenderEntry ::= 414 SEQUENCE { 415 rsvpSenderNumber SessionNumber, 416 rsvpSenderType SessionType, 417 rsvpSenderDestAddr OCTET STRING, 418 rsvpSenderAddr OCTET STRING, 419 rsvpSenderDestAddrLength INTEGER, 420 rsvpSenderAddrLength INTEGER, 421 rsvpSenderProtocol Protocol, 422 rsvpSenderDestPort Port, 423 rsvpSenderPort Port, 424 rsvpSenderHopAddr OCTET STRING, 425 rsvpSenderHopLih Integer32, 426 rsvpSenderInterface InterfaceIndex, 427 rsvpSenderTSpecRate BitRate, 428 rsvpSenderTSpecPeakRate BitRate, 429 rsvpSenderTSpecBurst BurstSize, 430 rsvpSenderTSpecMinTU MessageSize, 431 rsvpSenderTSpecMaxTU MessageSize, 432 rsvpSenderInterval RefreshInterval, 433 rsvpSenderRSVPHop TruthValue, 434 rsvpSenderLastChange TimeStamp, 435 rsvpSenderPolicy OCTET STRING, 436 rsvpSenderAdspecBreak TruthValue, 437 rsvpSenderAdspecHopCount INTEGER, 438 rsvpSenderAdspecPathBw BitRate, 439 rsvpSenderAdspecMinLatency Integer32, 440 rsvpSenderAdspecMtu INTEGER, 441 rsvpSenderAdspecGuaranteedSvc TruthValue, 442 rsvpSenderAdspecGuaranteedBreak TruthValue, 443 rsvpSenderAdspecGuaranteedCtot Integer32, 444 rsvpSenderAdspecGuaranteedDtot Integer32, 445 rsvpSenderAdspecGuaranteedCsum Integer32, 446 rsvpSenderAdspecGuaranteedDsum Integer32, 447 rsvpSenderAdspecGuaranteedHopCount INTEGER, 448 rsvpSenderAdspecGuaranteedPathBw BitRate, 449 rsvpSenderAdspecGuaranteedMinLatency Integer32, 450 rsvpSenderAdspecGuaranteedMtu INTEGER, 451 rsvpSenderAdspecCtrlLoadSvc TruthValue, 452 rsvpSenderAdspecCtrlLoadBreak TruthValue, 453 rsvpSenderAdspecCtrlLoadHopCount INTEGER, 454 rsvpSenderAdspecCtrlLoadPathBw BitRate, 455 rsvpSenderAdspecCtrlLoadMinLatency Integer32, 456 rsvpSenderAdspecCtrlLoadMtu INTEGER, 457 rsvpSenderStatus RowStatus, 458 rsvpSenderTTL INTEGER 460 } 462 rsvpSenderNumber OBJECT-TYPE 463 SYNTAX SessionNumber 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "The number of this sender. This is for SNMP 468 Indexing purposes only and has no relation to 469 any protocol value." 470 ::= { rsvpSenderEntry 1 } 472 rsvpSenderType OBJECT-TYPE 473 SYNTAX SessionType 474 MAX-ACCESS read-create 475 STATUS current 476 DESCRIPTION 477 "The type of session (IP4, IP6, IP6 with flow 478 information, etc)." 479 ::= { rsvpSenderEntry 2 } 481 rsvpSenderDestAddr OBJECT-TYPE 482 SYNTAX OCTET STRING (SIZE(4..16)) 483 MAX-ACCESS read-create 484 STATUS current 485 DESCRIPTION 486 "The destination address used by all senders in 487 this session. This object may not be changed 488 when the value of the RowStatus object is 'ac- 489 tive'." 490 ::= { rsvpSenderEntry 3 } 492 rsvpSenderAddr OBJECT-TYPE 493 SYNTAX OCTET STRING (SIZE(4..16)) 494 MAX-ACCESS read-create 495 STATUS current 496 DESCRIPTION 497 "The source address used by this sender in this 498 session. This object may not be changed when 499 the value of the RowStatus object is 'active'." 500 ::= { rsvpSenderEntry 4 } 502 rsvpSenderDestAddrLength OBJECT-TYPE 503 SYNTAX INTEGER(0..128) 504 MAX-ACCESS read-create 505 STATUS current 506 DESCRIPTION 507 "The length of the destination address in bits. 508 This is the CIDR Prefix Length, which for IP4 509 hosts and multicast addresses is 32 bits. This 510 object may not be changed when the value of the 511 RowStatus object is 'active'." 512 ::= { rsvpSenderEntry 5 } 514 rsvpSenderAddrLength OBJECT-TYPE 515 SYNTAX INTEGER(0..128) 516 MAX-ACCESS read-create 517 STATUS current 518 DESCRIPTION 519 "The length of the sender's address in bits. 520 This is the CIDR Prefix Length, which for IP4 521 hosts and multicast addresses is 32 bits. This 522 object may not be changed when the value of the 523 RowStatus object is 'active'." 524 ::= { rsvpSenderEntry 6 } 526 rsvpSenderProtocol OBJECT-TYPE 527 SYNTAX Protocol 528 MAX-ACCESS read-create 529 STATUS current 530 DESCRIPTION 531 "The IP Protocol used by this session. This 532 object may not be changed when the value of the 533 RowStatus object is 'active'." 534 ::= { rsvpSenderEntry 7 } 536 rsvpSenderDestPort OBJECT-TYPE 537 SYNTAX Port 538 MAX-ACCESS read-create 539 STATUS current 540 DESCRIPTION 541 "The UDP or TCP port number used as a destina- 542 tion port for all senders in this session. If 543 the IP protocol in use, specified by rsvpSen- 544 derProtocol, is 50 (ESP) or 51 (AH), this 545 represents a virtual destination port number. 546 A value of zero indicates that the IP protocol 547 in use does not have ports. This object may 548 not be changed when the value of the RowStatus 549 object is 'active'." 550 ::= { rsvpSenderEntry 8 } 552 rsvpSenderPort OBJECT-TYPE 553 SYNTAX Port 554 MAX-ACCESS read-create 555 STATUS current 556 DESCRIPTION 557 "The UDP or TCP port number used as a source 558 port for this sender in this session. If the 559 IP protocol in use, specified by rsvpSenderPro- 560 tocol is 50 (ESP) or 51 (AH), this represents a 561 generalized port identifier (GPI). A value of 562 zero indicates that the IP protocol in use does 563 not have ports. This object may not be changed 564 when the value of the RowStatus object is 'ac- 565 tive'." 566 ::= { rsvpSenderEntry 9 } 568 rsvpSenderHopAddr OBJECT-TYPE 569 SYNTAX OCTET STRING (SIZE(4..16)) 570 MAX-ACCESS read-create 571 STATUS current 572 DESCRIPTION 573 "The address used by the previous RSVP hop 574 (which may be the original sender)." 575 ::= { rsvpSenderEntry 10 } 577 rsvpSenderHopLih OBJECT-TYPE 578 SYNTAX Integer32 579 MAX-ACCESS read-create 580 STATUS current 581 DESCRIPTION 582 "The Logical Interface Handle used by the pre- 583 vious RSVP hop (which may be the original 584 sender)." 585 ::= { rsvpSenderEntry 11 } 587 rsvpSenderInterface OBJECT-TYPE 588 SYNTAX InterfaceIndex 589 MAX-ACCESS read-create 590 STATUS current 591 DESCRIPTION 592 "The ifIndex value of the interface on which 593 this PATH message was most recently received." 594 ::= { rsvpSenderEntry 12 } 596 rsvpSenderTSpecRate OBJECT-TYPE 597 SYNTAX BitRate 598 UNITS "bits per second" 599 MAX-ACCESS read-create 600 STATUS current 601 DESCRIPTION 602 "The Average Bit Rate of the sender's data 603 stream. Within a transmission burst, the ar- 604 rival rate may be as fast as rsvpSenderTSpec- 605 PeakRate (if supported by the service model); 606 however, averaged across two or more burst in- 607 tervals, the rate should not exceed rsvpSen- 608 derTSpecRate. 610 Note that this is a prediction, often based on 611 the general capability of a type of codec or 612 particular encoding; the measured average rate 613 may be significantly lower." 614 ::= { rsvpSenderEntry 13 } 616 rsvpSenderTSpecPeakRate OBJECT-TYPE 617 SYNTAX BitRate 618 UNITS "bits per second" 619 MAX-ACCESS read-create 620 STATUS current 621 DESCRIPTION 622 "The Peak Bit Rate of the sender's data stream. 623 Traffic arrival is not expected to exceed this 624 rate at any time, apart from the effects of 625 jitter in the network. If not specified in the 626 TSpec, this returns zero or noSuchValue." 627 ::= { rsvpSenderEntry 14 } 629 rsvpSenderTSpecBurst OBJECT-TYPE 630 SYNTAX BurstSize 631 UNITS "bytes" 632 MAX-ACCESS read-create 633 STATUS current 634 DESCRIPTION 635 "The size of the largest burst expected from 636 the sender at a time." 637 ::= { rsvpSenderEntry 15 } 639 rsvpSenderTSpecMinTU OBJECT-TYPE 640 SYNTAX MessageSize 641 MAX-ACCESS read-create 642 STATUS current 643 DESCRIPTION 644 "The minimum message size for this flow. The 645 policing algorithm will treat smaller messages 646 as though they are this size." 647 ::= { rsvpSenderEntry 16 } 649 rsvpSenderTSpecMaxTU OBJECT-TYPE 650 SYNTAX MessageSize 651 MAX-ACCESS read-create 652 STATUS current 653 DESCRIPTION 654 "The maximum message size for this flow. The 655 admission algorithm will reject TSpecs whose 656 Maximum Transmission Unit, plus the interface 657 headers, exceed the interface MTU." 658 ::= { rsvpSenderEntry 17 } 660 rsvpSenderInterval OBJECT-TYPE 661 SYNTAX RefreshInterval 662 MAX-ACCESS read-create 663 STATUS current 664 DESCRIPTION 665 "The interval between refresh messages as ad- 666 vertised by the Previous Hop." 667 ::= { rsvpSenderEntry 18 } 669 rsvpSenderRSVPHop OBJECT-TYPE 670 SYNTAX TruthValue 671 MAX-ACCESS read-create 672 STATUS current 673 DESCRIPTION 674 "If TRUE, the node believes that the previous 675 IP hop is an RSVP hop. If FALSE, the node be- 676 lieves that the previous IP hop may not be an 677 RSVP hop." 678 ::= { rsvpSenderEntry 19 } 680 rsvpSenderLastChange OBJECT-TYPE 681 SYNTAX TimeStamp 682 MAX-ACCESS read-only 683 STATUS current 684 DESCRIPTION 685 "The time of the last change in this PATH mes- 686 sage; This is either the first time it was re- 687 ceived or the time of the most recent change in 688 parameters." 689 ::= { rsvpSenderEntry 20 } 691 rsvpSenderPolicy OBJECT-TYPE 692 SYNTAX OCTET STRING (SIZE(4..65536)) 693 MAX-ACCESS read-create 694 STATUS current 695 DESCRIPTION 696 "The contents of the policy object, displayed 697 as an uninterpreted string of octets, including 698 the object header. In the absence of such an 699 object, this should be of zero length." 700 ::= { rsvpSenderEntry 21 } 702 rsvpSenderAdspecBreak OBJECT-TYPE 703 SYNTAX TruthValue 704 MAX-ACCESS read-create 705 STATUS current 706 DESCRIPTION 707 "The global break bit general characterization 708 parameter from the ADSPEC. If TRUE, at least 709 one non-IS hop was detected in the path. If 710 FALSE, no non-IS hops were detected." 711 ::= { rsvpSenderEntry 22 } 713 rsvpSenderAdspecHopCount OBJECT-TYPE 714 SYNTAX INTEGER (0..65535) 715 MAX-ACCESS read-create 716 STATUS current 717 DESCRIPTION 718 "The hop count general characterization parame- 719 ter from the ADSPEC. A return of zero or 720 noSuchValue indicates one of the following con- 721 ditions: 723 the invalid bit was set 724 the parameter was not present" 725 ::= { rsvpSenderEntry 23 } 727 rsvpSenderAdspecPathBw OBJECT-TYPE 728 SYNTAX BitRate 729 UNITS "bits per second" 730 MAX-ACCESS read-create 731 STATUS current 732 DESCRIPTION 733 "The path bandwidth estimate general character- 734 ization parameter from the ADSPEC. A return of 735 zero or noSuchValue indicates one of the fol- 736 lowing conditions: 738 the invalid bit was set 739 the parameter was not present" 740 ::= { rsvpSenderEntry 24 } 742 rsvpSenderAdspecMinLatency OBJECT-TYPE 743 SYNTAX Integer32 744 UNITS "microseconds" 745 MAX-ACCESS read-create 746 STATUS current 747 DESCRIPTION 748 "The minimum path latency general characteriza- 749 tion parameter from the ADSPEC. A return of 750 zero or noSuchValue indicates one of the fol- 751 lowing conditions: 753 the invalid bit was set 754 the parameter was not present" 755 ::= { rsvpSenderEntry 25 } 757 rsvpSenderAdspecMtu OBJECT-TYPE 758 SYNTAX INTEGER (0..65535) 759 UNITS "bytes" 760 MAX-ACCESS read-create 761 STATUS current 762 DESCRIPTION 763 "The composed Maximum Transmission Unit general 764 characterization parameter from the ADSPEC. A 765 return of zero or noSuchValue indicates one of 766 the following conditions: 768 the invalid bit was set 769 the parameter was not present" 770 ::= { rsvpSenderEntry 26 } 772 rsvpSenderAdspecGuaranteedSvc OBJECT-TYPE 773 SYNTAX TruthValue 774 MAX-ACCESS read-create 775 STATUS current 776 DESCRIPTION 777 "If TRUE, the ADSPEC contains a Guaranteed Ser- 778 vice fragment. If FALSE, the ADSPEC does not 779 contain a Guaranteed Service fragment." 780 ::= { rsvpSenderEntry 27 } 782 rsvpSenderAdspecGuaranteedBreak OBJECT-TYPE 783 SYNTAX TruthValue 784 MAX-ACCESS read-create 785 STATUS current 786 DESCRIPTION 787 "If TRUE, the Guaranteed Service fragment has 788 its 'break' bit set, indicating that one or 789 more nodes along the path do not support the 790 guaranteed service. If FALSE, and rsvpSen- 791 derAdspecGuaranteedSvc is TRUE, the 'break' bit 792 is not set. 794 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 795 returns FALSE or noSuchValue." 796 ::= { rsvpSenderEntry 28 } 798 rsvpSenderAdspecGuaranteedCtot OBJECT-TYPE 799 SYNTAX Integer32 800 UNITS "bytes" 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 805 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 806 is the end-to-end composed value for the 807 guaranteed service 'C' parameter. A return of 808 zero or noSuchValue indicates one of the fol- 809 lowing conditions: 811 the invalid bit was set 812 the parameter was not present 814 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 815 returns zero or noSuchValue." 816 ::= { rsvpSenderEntry 29 } 818 rsvpSenderAdspecGuaranteedDtot OBJECT-TYPE 819 SYNTAX Integer32 820 UNITS "microseconds" 821 MAX-ACCESS read-create 822 STATUS current 823 DESCRIPTION 824 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 825 is the end-to-end composed value for the 826 guaranteed service 'D' parameter. A return of 827 zero or noSuchValue indicates one of the fol- 828 lowing conditions: 830 the invalid bit was set 831 the parameter was not present 833 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 834 returns zero or noSuchValue." 835 ::= { rsvpSenderEntry 30 } 837 rsvpSenderAdspecGuaranteedCsum OBJECT-TYPE 838 SYNTAX Integer32 839 UNITS "bytes" 840 MAX-ACCESS read-create 841 STATUS current 842 DESCRIPTION 843 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 844 is the composed value for the guaranteed ser- 845 vice 'C' parameter since the last reshaping 846 point. A return of zero or noSuchValue indi- 847 cates one of the following conditions: 849 the invalid bit was set 850 the parameter was not present 852 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 853 returns zero or noSuchValue." 854 ::= { rsvpSenderEntry 31 } 856 rsvpSenderAdspecGuaranteedDsum OBJECT-TYPE 857 SYNTAX Integer32 858 UNITS "microseconds" 859 MAX-ACCESS read-create 860 STATUS current 861 DESCRIPTION 862 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 863 is the composed value for the guaranteed ser- 864 vice 'D' parameter since the last reshaping 865 point. A return of zero or noSuchValue indi- 866 cates one of the following conditions: 868 the invalid bit was set 869 the parameter was not present 871 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 872 returns zero or noSuchValue." 873 ::= { rsvpSenderEntry 32 } 875 rsvpSenderAdspecGuaranteedHopCount OBJECT-TYPE 876 SYNTAX INTEGER (0..65535) 877 MAX-ACCESS read-create 878 STATUS current 879 DESCRIPTION 881 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 882 is the service-specific override of the hop 883 count general characterization parameter from 884 the ADSPEC. A return of zero or noSuchValue 885 indicates one of the following conditions: 887 the invalid bit was set 888 the parameter was not present 890 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 891 returns zero or noSuchValue." 892 ::= { rsvpSenderEntry 33 } 894 rsvpSenderAdspecGuaranteedPathBw OBJECT-TYPE 895 SYNTAX BitRate 896 UNITS "bits per second" 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 901 is the service-specific override of the path 902 bandwidth estimate general characterization 903 parameter from the ADSPEC. A return of zero or 904 noSuchValue indicates one of the following con- 905 ditions: 907 the invalid bit was set 908 the parameter was not present 910 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 911 returns zero or noSuchValue." 912 ::= { rsvpSenderEntry 34 } 914 rsvpSenderAdspecGuaranteedMinLatency OBJECT-TYPE 915 SYNTAX Integer32 916 UNITS "microseconds" 917 MAX-ACCESS read-create 918 STATUS current 919 DESCRIPTION 920 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 921 is the service-specific override of the minimum 922 path latency general characterization parameter 923 from the ADSPEC. A return of zero or noSuch- 924 Value indicates one of the following condi- 925 tions: 927 the invalid bit was set 928 the parameter was not present 930 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 931 returns zero or noSuchValue." 932 ::= { rsvpSenderEntry 35 } 934 rsvpSenderAdspecGuaranteedMtu OBJECT-TYPE 935 SYNTAX INTEGER (0..65535) 936 UNITS "bytes" 937 MAX-ACCESS read-create 938 STATUS current 939 DESCRIPTION 940 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 941 is the service-specific override of the com- 942 posed Maximum Transmission Unit general charac- 943 terization parameter from the ADSPEC. A return 944 of zero or noSuchValue indicates one of the 945 following conditions: 947 the invalid bit was set 948 the parameter was not present 950 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 951 returns zero or noSuchValue." 952 ::= { rsvpSenderEntry 36 } 954 rsvpSenderAdspecCtrlLoadSvc OBJECT-TYPE 955 SYNTAX TruthValue 956 MAX-ACCESS read-create 957 STATUS current 958 DESCRIPTION 959 "If TRUE, the ADSPEC contains a Controlled Load 960 Service fragment. If FALSE, the ADSPEC does 961 not contain a Controlled Load Service frag- 962 ment." 963 ::= { rsvpSenderEntry 37 } 965 rsvpSenderAdspecCtrlLoadBreak OBJECT-TYPE 966 SYNTAX TruthValue 967 MAX-ACCESS read-create 968 STATUS current 969 DESCRIPTION 970 "If TRUE, the Controlled Load Service fragment 971 has its 'break' bit set, indicating that one or 972 more nodes along the path do not support the 973 controlled load service. If FALSE, and 974 rsvpSenderAdspecCtrlLoadSvc is TRUE, the 975 'break' bit is not set. 977 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 978 returns FALSE or noSuchValue." 979 ::= { rsvpSenderEntry 38 } 981 rsvpSenderAdspecCtrlLoadHopCount OBJECT-TYPE 982 SYNTAX INTEGER (0..65535) 983 MAX-ACCESS read-create 984 STATUS current 985 DESCRIPTION 987 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 988 is the service-specific override of the hop 989 count general characterization parameter from 990 the ADSPEC. A return of zero or noSuchValue 991 indicates one of the following conditions: 993 the invalid bit was set 994 the parameter was not present 996 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 997 returns zero or noSuchValue." 998 ::= { rsvpSenderEntry 39 } 1000 rsvpSenderAdspecCtrlLoadPathBw OBJECT-TYPE 1001 SYNTAX BitRate 1002 UNITS "bits per second" 1003 MAX-ACCESS read-create 1004 STATUS current 1005 DESCRIPTION 1006 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1007 is the service-specific override of the path 1008 bandwidth estimate general characterization 1009 parameter from the ADSPEC. A return of zero or 1010 noSuchValue indicates one of the following con- 1011 ditions: 1013 the invalid bit was set 1014 the parameter was not present 1016 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1017 returns zero or noSuchValue." 1018 ::= { rsvpSenderEntry 40 } 1020 rsvpSenderAdspecCtrlLoadMinLatency OBJECT-TYPE 1021 SYNTAX Integer32 1022 UNITS "microseconds" 1023 MAX-ACCESS read-create 1024 STATUS current 1025 DESCRIPTION 1026 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1027 is the service-specific override of the minimum 1028 path latency general characterization parameter 1029 from the ADSPEC. A return of zero or noSuch- 1030 Value indicates one of the following condi- 1031 tions: 1033 the invalid bit was set 1034 the parameter was not present 1036 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1037 returns zero or noSuchValue." 1038 ::= { rsvpSenderEntry 41 } 1040 rsvpSenderAdspecCtrlLoadMtu OBJECT-TYPE 1041 SYNTAX INTEGER (0..65535) 1042 UNITS "bytes" 1043 MAX-ACCESS read-create 1044 STATUS current 1045 DESCRIPTION 1046 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1047 is the service-specific override of the com- 1048 posed Maximum Transmission Unit general charac- 1049 terization parameter from the ADSPEC. A return 1050 of zero or noSuchValue indicates one of the 1051 following conditions: 1053 the invalid bit was set 1054 the parameter was not present 1056 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1057 returns zero or noSuchValue." 1058 ::= { rsvpSenderEntry 42 } 1060 rsvpSenderStatus OBJECT-TYPE 1061 SYNTAX RowStatus 1062 MAX-ACCESS read-create 1063 STATUS current 1064 DESCRIPTION 1065 "'active' for all active PATH messages. This 1066 object may be used to install static PATH in- 1067 formation or delete PATH information." 1068 ::= { rsvpSenderEntry 43 } 1070 rsvpSenderTTL OBJECT-TYPE 1071 SYNTAX INTEGER (0..255) 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "The TTL value in the RSVP header that was last 1076 received." 1077 ::= { rsvpSenderEntry 44 } 1079 rsvpSenderOutInterfaceTable OBJECT-TYPE 1080 SYNTAX SEQUENCE OF RsvpSenderOutInterfaceEntry 1081 MAX-ACCESS not-accessible 1082 STATUS current 1083 DESCRIPTION 1084 "List of outgoing interfaces that PATH messages 1085 use. The ifIndex is the ifIndex value of the 1086 egress interface." 1087 ::= { rsvpObjects 3 } 1089 rsvpSenderOutInterfaceEntry OBJECT-TYPE 1090 SYNTAX RsvpSenderOutInterfaceEntry 1091 MAX-ACCESS not-accessible 1092 STATUS current 1093 DESCRIPTION 1094 "List of outgoing interfaces that a particular 1095 PATH message has." 1096 INDEX { rsvpSessionNumber, rsvpSenderNumber, ifIndex } 1097 ::= { rsvpSenderOutInterfaceTable 1 } 1099 RsvpSenderOutInterfaceEntry ::= 1100 SEQUENCE { 1101 rsvpSenderOutInterfaceStatus RowStatus 1103 } 1105 rsvpSenderOutInterfaceStatus OBJECT-TYPE 1106 SYNTAX RowStatus 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 "'active' for all active PATH messages." 1111 ::= { rsvpSenderOutInterfaceEntry 1 } 1113 -- The RSVP Reservation Requests Received Table contains the 1114 -- information displayed by receivers regarding their needs with 1115 -- respect to sessions and senders. It is in essence a list of the 1116 -- valid RESV messages that the RSVP Router or Host is receiving. 1118 rsvpResvNewIndex OBJECT-TYPE 1119 SYNTAX TestAndIncr 1120 MAX-ACCESS read-write 1121 STATUS current 1122 DESCRIPTION 1123 "This object is used to assign values to 1124 rsvpResvNumber as described in 'Textual Conven- 1125 tions for SNMPv2'. The network manager reads 1126 the object, and then writes the value back in 1127 the SET that creates a new instance of 1128 rsvpResvEntry. If the SET fails with the code 1129 'inconsistentValue', then the process must be 1130 repeated; If the SET succeeds, then the object 1131 is incremented, and the new instance is created 1132 according to the manager's directions." 1133 ::= { rsvpGenObjects 3 } 1135 rsvpResvTable OBJECT-TYPE 1136 SYNTAX SEQUENCE OF RsvpResvEntry 1137 MAX-ACCESS not-accessible 1138 STATUS current 1139 DESCRIPTION 1140 "Information describing the state information 1141 displayed by receivers in RESV messages." 1142 ::= { rsvpObjects 4 } 1144 rsvpResvEntry OBJECT-TYPE 1145 SYNTAX RsvpResvEntry 1146 MAX-ACCESS not-accessible 1147 STATUS current 1148 DESCRIPTION 1149 "Information describing the state information 1150 displayed by a single receiver's RESV message 1151 concerning a single sender." 1152 INDEX { rsvpSessionNumber, rsvpResvNumber } 1153 ::= { rsvpResvTable 1 } 1155 RsvpResvEntry ::= 1156 SEQUENCE { 1157 rsvpResvNumber SessionNumber, 1158 rsvpResvType SessionType, 1159 rsvpResvDestAddr OCTET STRING, 1160 rsvpResvSenderAddr OCTET STRING, 1161 rsvpResvDestAddrLength INTEGER, 1162 rsvpResvSenderAddrLength INTEGER, 1163 rsvpResvProtocol Protocol, 1164 rsvpResvDestPort Port, 1165 rsvpResvPort Port, 1166 rsvpResvHopAddr OCTET STRING, 1167 rsvpResvHopLih Integer32, 1168 rsvpResvInterface InterfaceIndex, 1169 rsvpResvService QosService, 1170 rsvpResvTSpecRate BitRate, 1171 rsvpResvTSpecPeakRate BitRate, 1172 rsvpResvTSpecBurst BurstSize, 1173 rsvpResvTSpecMinTU MessageSize, 1174 rsvpResvTSpecMaxTU MessageSize, 1175 rsvpResvRSpecRate BitRate, 1176 rsvpResvRSpecSlack Integer32, 1177 rsvpResvInterval RefreshInterval, 1178 rsvpResvScope OCTET STRING, 1179 rsvpResvShared TruthValue, 1180 rsvpResvExplicit TruthValue, 1181 rsvpResvRSVPHop TruthValue, 1182 rsvpResvLastChange TimeStamp, 1183 rsvpResvPolicy OCTET STRING, 1184 rsvpResvStatus RowStatus, 1185 rsvpResvTTL INTEGER 1186 } 1188 rsvpResvNumber OBJECT-TYPE 1189 SYNTAX SessionNumber 1190 MAX-ACCESS not-accessible 1191 STATUS current 1192 DESCRIPTION 1193 "The number of this reservation request. This 1194 is for SNMP Indexing purposes only and has no 1195 relation to any protocol value." 1196 ::= { rsvpResvEntry 1 } 1198 rsvpResvType OBJECT-TYPE 1199 SYNTAX SessionType 1200 MAX-ACCESS read-create 1201 STATUS current 1202 DESCRIPTION 1203 "The type of session (IP4, IP6, IP6 with flow 1204 information, etc)." 1205 ::= { rsvpResvEntry 2 } 1207 rsvpResvDestAddr OBJECT-TYPE 1208 SYNTAX OCTET STRING (SIZE(4..16)) 1209 MAX-ACCESS read-create 1210 STATUS current 1211 DESCRIPTION 1212 "The destination address used by all senders in 1213 this session. This object may not be changed 1214 when the value of the RowStatus object is 'ac- 1215 tive'." 1216 ::= { rsvpResvEntry 3 } 1218 rsvpResvSenderAddr OBJECT-TYPE 1219 SYNTAX OCTET STRING (SIZE(4..16)) 1220 MAX-ACCESS read-create 1221 STATUS current 1222 DESCRIPTION 1223 "The source address of the sender selected by 1224 this reservation. The value of all zeroes in- 1225 dicates 'all senders'. This object may not be 1226 changed when the value of the RowStatus object 1227 is 'active'." 1228 ::= { rsvpResvEntry 4 } 1230 rsvpResvDestAddrLength OBJECT-TYPE 1231 SYNTAX INTEGER(0..128) 1232 MAX-ACCESS read-create 1233 STATUS current 1234 DESCRIPTION 1235 "The length of the destination address in bits. 1236 This is the CIDR Prefix Length, which for IP4 1237 hosts and multicast addresses is 32 bits. This 1238 object may not be changed when the value of the 1239 RowStatus object is 'active'." 1240 ::= { rsvpResvEntry 5 } 1242 rsvpResvSenderAddrLength OBJECT-TYPE 1243 SYNTAX INTEGER(0..128) 1244 MAX-ACCESS read-create 1245 STATUS current 1246 DESCRIPTION 1247 "The length of the sender's address in bits. 1248 This is the CIDR Prefix Length, which for IP4 1249 hosts and multicast addresses is 32 bits. This 1250 object may not be changed when the value of the 1251 RowStatus object is 'active'." 1252 ::= { rsvpResvEntry 6 } 1254 rsvpResvProtocol OBJECT-TYPE 1255 SYNTAX Protocol 1256 MAX-ACCESS read-create 1257 STATUS current 1258 DESCRIPTION 1259 "The IP Protocol used by this session. This 1260 object may not be changed when the value of the 1261 RowStatus object is 'active'." 1262 ::= { rsvpResvEntry 7 } 1264 rsvpResvDestPort OBJECT-TYPE 1265 SYNTAX Port 1266 MAX-ACCESS read-create 1267 STATUS current 1268 DESCRIPTION 1269 "The UDP or TCP port number used as a destina- 1270 tion port for all senders in this session. If 1271 the IP protocol in use, specified by 1272 rsvpResvProtocol, is 50 (ESP) or 51 (AH), this 1273 represents a virtual destination port number. 1274 A value of zero indicates that the IP protocol 1275 in use does not have ports. This object may 1276 not be changed when the value of the RowStatus 1277 object is 'active'." 1278 ::= { rsvpResvEntry 8 } 1280 rsvpResvPort OBJECT-TYPE 1281 SYNTAX Port 1282 MAX-ACCESS read-create 1283 STATUS current 1284 DESCRIPTION 1285 "The UDP or TCP port number used as a source 1286 port for this sender in this session. If the 1287 IP protocol in use, specified by rsvpResvProto- 1288 col is 50 (ESP) or 51 (AH), this represents a 1289 generalized port identifier (GPI). A value of 1290 zero indicates that the IP protocol in use does 1291 not have ports. This object may not be changed 1292 when the value of the RowStatus object is 'ac- 1293 tive'." 1294 ::= { rsvpResvEntry 9 } 1296 rsvpResvHopAddr OBJECT-TYPE 1297 SYNTAX OCTET STRING (SIZE(4..16)) 1298 MAX-ACCESS read-create 1299 STATUS current 1300 DESCRIPTION 1301 "The address used by the next RSVP hop (which 1302 may be the ultimate receiver)." 1303 ::= { rsvpResvEntry 10 } 1305 rsvpResvHopLih OBJECT-TYPE 1306 SYNTAX Integer32 1307 MAX-ACCESS read-create 1308 STATUS current 1309 DESCRIPTION 1310 "The Logical Interface Handle received from the 1311 previous RSVP hop (which may be the ultimate 1312 receiver)." 1313 ::= { rsvpResvEntry 11 } 1315 rsvpResvInterface OBJECT-TYPE 1316 SYNTAX InterfaceIndex 1317 MAX-ACCESS read-create 1318 STATUS current 1319 DESCRIPTION 1320 "The ifIndex value of the interface on which 1321 this RESV message was most recently received." 1322 ::= { rsvpResvEntry 12 } 1324 rsvpResvService OBJECT-TYPE 1325 SYNTAX QosService 1326 MAX-ACCESS read-create 1327 STATUS current 1328 DESCRIPTION 1329 "The QoS Service classification requested by 1330 the receiver." 1331 ::= { rsvpResvEntry 13 } 1333 rsvpResvTSpecRate OBJECT-TYPE 1334 SYNTAX BitRate 1335 UNITS "bits per second" 1336 MAX-ACCESS read-create 1337 STATUS current 1338 DESCRIPTION 1339 "The Average Bit Rate of the sender's data 1340 stream. Within a transmission burst, the ar- 1341 rival rate may be as fast as rsvpResvTSpec- 1342 PeakRate (if supported by the service model); 1343 however, averaged across two or more burst in- 1344 tervals, the rate should not exceed 1345 rsvpResvTSpecRate. 1347 Note that this is a prediction, often based on 1348 the general capability of a type of codec or 1349 particular encoding; the measured average rate 1350 may be significantly lower." 1351 ::= { rsvpResvEntry 14 } 1353 rsvpResvTSpecPeakRate OBJECT-TYPE 1354 SYNTAX BitRate 1355 UNITS "bits per second" 1356 MAX-ACCESS read-create 1357 STATUS current 1358 DESCRIPTION 1359 "The Peak Bit Rate of the sender's data stream. 1360 Traffic arrival is not expected to exceed this 1361 rate at any time, apart from the effects of 1362 jitter in the network. If not specified in the 1363 TSpec, this returns zero or noSuchValue." 1364 ::= { rsvpResvEntry 15 } 1366 rsvpResvTSpecBurst OBJECT-TYPE 1367 SYNTAX BurstSize 1368 UNITS "bytes" 1369 MAX-ACCESS read-create 1370 STATUS current 1371 DESCRIPTION 1372 "The size of the largest burst expected from 1373 the sender at a time. 1375 If this is less than the sender's advertised 1376 burst size, the receiver is asking the network 1377 to provide flow pacing beyond what would be 1378 provided under normal circumstances. Such pac- 1379 ing is at the network's option." 1380 ::= { rsvpResvEntry 16 } 1382 rsvpResvTSpecMinTU OBJECT-TYPE 1383 SYNTAX MessageSize 1384 MAX-ACCESS read-create 1385 STATUS current 1386 DESCRIPTION 1387 "The minimum message size for this flow. The 1388 policing algorithm will treat smaller messages 1389 as though they are this size." 1390 ::= { rsvpResvEntry 17 } 1392 rsvpResvTSpecMaxTU OBJECT-TYPE 1393 SYNTAX MessageSize 1394 MAX-ACCESS read-create 1395 STATUS current 1396 DESCRIPTION 1397 "The maximum message size for this flow. The 1398 admission algorithm will reject TSpecs whose 1399 Maximum Transmission Unit, plus the interface 1400 headers, exceed the interface MTU." 1401 ::= { rsvpResvEntry 18 } 1403 rsvpResvRSpecRate OBJECT-TYPE 1404 SYNTAX BitRate 1405 UNITS "bits per second" 1406 MAX-ACCESS read-create 1407 STATUS current 1408 DESCRIPTION 1409 "If the requested service is Guaranteed, as 1410 specified by rsvpResvService, this is the 1411 clearing rate that is being requested. Other- 1412 wise, it is zero, or the agent may return 1413 noSuchValue." 1414 ::= { rsvpResvEntry 19 } 1416 rsvpResvRSpecSlack OBJECT-TYPE 1417 SYNTAX Integer32 1418 UNITS "microseconds" 1419 MAX-ACCESS read-create 1420 STATUS current 1421 DESCRIPTION 1422 "If the requested service is Guaranteed, as 1423 specified by rsvpResvService, this is the delay 1424 slack. Otherwise, it is zero, or the agent may 1425 return noSuchValue." 1426 ::= { rsvpResvEntry 20 } 1428 rsvpResvInterval OBJECT-TYPE 1429 SYNTAX RefreshInterval 1430 MAX-ACCESS read-create 1431 STATUS current 1432 DESCRIPTION 1433 "The interval between refresh messages as ad- 1434 vertised by the Next Hop." 1435 ::= { rsvpResvEntry 21 } 1437 rsvpResvScope OBJECT-TYPE 1438 SYNTAX OCTET STRING (SIZE(0..65536)) 1439 MAX-ACCESS read-create 1440 STATUS current 1441 DESCRIPTION 1443 "The contents of the scope object, displayed as 1444 an uninterpreted string of octets, including 1445 the object header. In the absence of such an 1446 object, this should be of zero length. 1448 If the length is non-zero, this contains a 1449 series of IP4 or IP6 addresses." 1450 ::= { rsvpResvEntry 22 } 1452 rsvpResvShared OBJECT-TYPE 1453 SYNTAX TruthValue 1454 MAX-ACCESS read-create 1455 STATUS current 1456 DESCRIPTION 1457 "If TRUE, a reservation shared among senders is 1458 requested. If FALSE, a reservation specific to 1459 this sender is requested." 1460 ::= { rsvpResvEntry 23 } 1462 rsvpResvExplicit OBJECT-TYPE 1463 SYNTAX TruthValue 1464 MAX-ACCESS read-create 1465 STATUS current 1466 DESCRIPTION 1467 "If TRUE, individual senders are listed using 1468 Filter Specifications. If FALSE, all senders 1469 are implicitly selected. The Scope Object will 1470 contain a list of senders that need to receive 1471 this reservation request for the purpose of 1472 routing the RESV message." 1473 ::= { rsvpResvEntry 24 } 1475 rsvpResvRSVPHop OBJECT-TYPE 1476 SYNTAX TruthValue 1477 MAX-ACCESS read-create 1478 STATUS current 1479 DESCRIPTION 1480 "If TRUE, the node believes that the previous 1481 IP hop is an RSVP hop. If FALSE, the node be- 1482 lieves that the previous IP hop may not be an 1483 RSVP hop." 1484 ::= { rsvpResvEntry 25 } 1486 rsvpResvLastChange OBJECT-TYPE 1487 SYNTAX TimeStamp 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "The time of the last change in this reserva- 1492 tion request; This is either the first time it 1493 was received or the time of the most recent 1494 change in parameters." 1495 ::= { rsvpResvEntry 26 } 1497 rsvpResvPolicy OBJECT-TYPE 1498 SYNTAX OCTET STRING (SIZE(0..65536)) 1499 MAX-ACCESS read-create 1500 STATUS current 1501 DESCRIPTION 1502 "The contents of the policy object, displayed 1503 as an uninterpreted string of octets, including 1504 the object header. In the absence of such an 1505 object, this should be of zero length." 1506 ::= { rsvpResvEntry 27 } 1508 rsvpResvStatus OBJECT-TYPE 1509 SYNTAX RowStatus 1510 MAX-ACCESS read-create 1511 STATUS current 1512 DESCRIPTION 1513 "'active' for all active RESV messages. This 1514 object may be used to install static RESV in- 1515 formation or delete RESV information." 1516 ::= { rsvpResvEntry 28 } 1518 rsvpResvTTL OBJECT-TYPE 1519 SYNTAX INTEGER (0..255) 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "The TTL value in the RSVP header that was last 1524 received." 1525 ::= { rsvpResvEntry 29 } 1527 -- The RSVP Reservation Requests Forwarded Table contains the 1528 -- information displayed by receivers regarding their needs with 1529 -- respect to sessions and senders. It is in essence a list of the 1530 -- valid RESV messages that the RSVP Router or Host is sending 1531 -- to its upstream neighbors. 1533 rsvpResvFwdNewIndex OBJECT-TYPE 1534 SYNTAX TestAndIncr 1535 MAX-ACCESS read-write 1536 STATUS current 1537 DESCRIPTION 1538 "This object is used to assign values to 1539 rsvpResvFwdNumber as described in 'Textual Con- 1540 ventions for SNMPv2'. The network manager 1541 reads the object, and then writes the value 1542 back in the SET that creates a new instance of 1543 rsvpResvFwdEntry. If the SET fails with the 1544 code 'inconsistentValue', then the process must 1545 be repeated; If the SET succeeds, then the ob- 1546 ject is incremented, and the new instance is 1547 created according to the manager's directions." 1548 ::= { rsvpGenObjects 4 } 1550 rsvpResvFwdTable OBJECT-TYPE 1551 SYNTAX SEQUENCE OF RsvpResvFwdEntry 1552 MAX-ACCESS not-accessible 1553 STATUS current 1554 DESCRIPTION 1555 "Information describing the state information 1556 displayed upstream in RESV messages." 1557 ::= { rsvpObjects 5 } 1559 rsvpResvFwdEntry OBJECT-TYPE 1560 SYNTAX RsvpResvFwdEntry 1561 MAX-ACCESS not-accessible 1562 STATUS current 1563 DESCRIPTION 1564 "Information describing the state information 1565 displayed upstream in an RESV message concern- 1566 ing a single sender." 1567 INDEX { rsvpSessionNumber, rsvpResvFwdNumber } 1568 ::= { rsvpResvFwdTable 1 } 1570 RsvpResvFwdEntry ::= 1571 SEQUENCE { 1572 rsvpResvFwdNumber SessionNumber, 1573 rsvpResvFwdType SessionType, 1574 rsvpResvFwdDestAddr OCTET STRING, 1575 rsvpResvFwdSenderAddr OCTET STRING, 1576 rsvpResvFwdDestAddrLength INTEGER, 1577 rsvpResvFwdSenderAddrLength INTEGER, 1578 rsvpResvFwdProtocol Protocol, 1579 rsvpResvFwdDestPort Port, 1580 rsvpResvFwdPort Port, 1581 rsvpResvFwdHopAddr OCTET STRING, 1582 rsvpResvFwdHopLih Integer32, 1583 rsvpResvFwdInterface InterfaceIndex, 1584 rsvpResvFwdService QosService, 1585 rsvpResvFwdTSpecRate BitRate, 1586 rsvpResvFwdTSpecPeakRate BitRate, 1587 rsvpResvFwdTSpecBurst BurstSize, 1588 rsvpResvFwdTSpecMinTU MessageSize, 1589 rsvpResvFwdTSpecMaxTU MessageSize, 1590 rsvpResvFwdRSpecRate BitRate, 1591 rsvpResvFwdRSpecSlack Integer32, 1592 rsvpResvFwdInterval RefreshInterval, 1593 rsvpResvFwdScope OCTET STRING, 1594 rsvpResvFwdShared TruthValue, 1595 rsvpResvFwdExplicit TruthValue, 1596 rsvpResvFwdRSVPHop TruthValue, 1597 rsvpResvFwdLastChange TimeStamp, 1598 rsvpResvFwdPolicy OCTET STRING, 1599 rsvpResvFwdStatus RowStatus, 1600 rsvpResvFwdTTL INTEGER 1601 } 1603 rsvpResvFwdNumber OBJECT-TYPE 1604 SYNTAX SessionNumber 1605 MAX-ACCESS not-accessible 1606 STATUS current 1607 DESCRIPTION 1608 "The number of this reservation request. This 1609 is for SNMP Indexing purposes only and has no 1610 relation to any protocol value." 1611 ::= { rsvpResvFwdEntry 1 } 1613 rsvpResvFwdType OBJECT-TYPE 1614 SYNTAX SessionType 1615 MAX-ACCESS read-only 1616 STATUS current 1617 DESCRIPTION 1618 "The type of session (IP4, IP6, IP6 with flow 1619 information, etc)." 1620 ::= { rsvpResvFwdEntry 2 } 1622 rsvpResvFwdDestAddr OBJECT-TYPE 1623 SYNTAX OCTET STRING (SIZE(4..16)) 1624 MAX-ACCESS read-only 1625 STATUS current 1626 DESCRIPTION 1627 "The destination address used by all senders in 1628 this session. This object may not be changed 1629 when the value of the RowStatus object is 'ac- 1630 tive'." 1631 ::= { rsvpResvFwdEntry 3 } 1633 rsvpResvFwdSenderAddr OBJECT-TYPE 1634 SYNTAX OCTET STRING (SIZE(4..16)) 1635 MAX-ACCESS read-only 1636 STATUS current 1637 DESCRIPTION 1638 "The source address of the sender selected by 1639 this reservation. The value of all zeroes in- 1640 dicates 'all senders'. This object may not be 1641 changed when the value of the RowStatus object 1642 is 'active'." 1643 ::= { rsvpResvFwdEntry 4 } 1645 rsvpResvFwdDestAddrLength OBJECT-TYPE 1646 SYNTAX INTEGER(0..128) 1647 MAX-ACCESS read-only 1648 STATUS current 1649 DESCRIPTION 1650 "The length of the destination address in bits. 1651 This is the CIDR Prefix Length, which for IP4 1652 hosts and multicast addresses is 32 bits. This 1653 object may not be changed when the value of the 1654 RowStatus object is 'active'." 1655 ::= { rsvpResvFwdEntry 5 } 1657 rsvpResvFwdSenderAddrLength OBJECT-TYPE 1658 SYNTAX INTEGER(0..128) 1659 MAX-ACCESS read-only 1660 STATUS current 1661 DESCRIPTION 1662 "The length of the sender's address in bits. 1663 This is the CIDR Prefix Length, which for IP4 1664 hosts and multicast addresses is 32 bits. This 1665 object may not be changed when the value of the 1666 RowStatus object is 'active'." 1667 ::= { rsvpResvFwdEntry 6 } 1669 rsvpResvFwdProtocol OBJECT-TYPE 1670 SYNTAX Protocol 1671 MAX-ACCESS read-only 1672 STATUS current 1673 DESCRIPTION 1674 "The IP Protocol used by a session. for secure 1675 sessions, this indicates IP Security. This ob- 1676 ject may not be changed when the value of the 1677 RowStatus object is 'active'." 1678 ::= { rsvpResvFwdEntry 7 } 1680 rsvpResvFwdDestPort OBJECT-TYPE 1681 SYNTAX Port 1682 MAX-ACCESS read-only 1683 STATUS current 1684 DESCRIPTION 1685 "The UDP or TCP port number used as a destina- 1686 tion port for all senders in this session. If 1687 the IP protocol in use, specified by 1688 rsvpResvFwdProtocol, is 50 (ESP) or 51 (AH), 1689 this represents a virtual destination port 1690 number. A value of zero indicates that the IP 1691 protocol in use does not have ports. This ob- 1692 ject may not be changed when the value of the 1693 RowStatus object is 'active'." 1694 ::= { rsvpResvFwdEntry 8 } 1696 rsvpResvFwdPort OBJECT-TYPE 1697 SYNTAX Port 1698 MAX-ACCESS read-only 1699 STATUS current 1700 DESCRIPTION 1701 "The UDP or TCP port number used as a source 1702 port for this sender in this session. If the 1703 IP protocol in use, specified by 1704 rsvpResvFwdProtocol is 50 (ESP) or 51 (AH), 1705 this represents a generalized port identifier 1706 (GPI). A value of zero indicates that the IP 1707 protocol in use does not have ports. This ob- 1708 ject may not be changed when the value of the 1709 RowStatus object is 'active'." 1710 ::= { rsvpResvFwdEntry 9 } 1712 rsvpResvFwdHopAddr OBJECT-TYPE 1713 SYNTAX OCTET STRING (SIZE(4..16)) 1714 MAX-ACCESS read-only 1715 STATUS current 1716 DESCRIPTION 1717 "The address of the (previous) RSVP that will 1718 receive this message." 1719 ::= { rsvpResvFwdEntry 10 } 1721 rsvpResvFwdHopLih OBJECT-TYPE 1722 SYNTAX Integer32 1723 MAX-ACCESS read-only 1724 STATUS current 1725 DESCRIPTION 1726 "The Logical Interface Handle sent to the (pre- 1727 vious) RSVP that will receive this message." 1728 ::= { rsvpResvFwdEntry 11 } 1730 rsvpResvFwdInterface OBJECT-TYPE 1731 SYNTAX InterfaceIndex 1732 MAX-ACCESS read-only 1733 STATUS current 1734 DESCRIPTION 1735 "The ifIndex value of the interface on which 1736 this RESV message was most recently sent." 1737 ::= { rsvpResvFwdEntry 12 } 1739 rsvpResvFwdService OBJECT-TYPE 1740 SYNTAX QosService 1741 MAX-ACCESS read-only 1742 STATUS current 1743 DESCRIPTION 1744 "The QoS Service classification requested." 1745 ::= { rsvpResvFwdEntry 13 } 1747 rsvpResvFwdTSpecRate OBJECT-TYPE 1748 SYNTAX BitRate 1749 UNITS "bits per second" 1750 MAX-ACCESS read-only 1751 STATUS current 1752 DESCRIPTION 1753 "The Average Bit Rate of the sender's data 1754 stream. Within a transmission burst, the ar- 1755 rival rate may be as fast as rsvpResvFwdTSpec- 1756 PeakRate (if supported by the service model); 1757 however, averaged across two or more burst in- 1758 tervals, the rate should not exceed 1759 rsvpResvFwdTSpecRate. 1761 Note that this is a prediction, often based on 1762 the general capability of a type of codec or 1763 particular encoding; the measured average rate 1764 may be significantly lower." 1765 ::= { rsvpResvFwdEntry 14 } 1767 rsvpResvFwdTSpecPeakRate OBJECT-TYPE 1768 SYNTAX BitRate 1769 UNITS "bits per second" 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1773 "The Peak Bit Rate of the sender's data stream 1774 Traffic arrival is not expected to exceed this 1775 rate at any time, apart from the effects of 1776 jitter in the network. If not specified in the 1777 TSpec, this returns zero or noSuchValue." 1778 ::= { rsvpResvFwdEntry 15 } 1780 rsvpResvFwdTSpecBurst OBJECT-TYPE 1781 SYNTAX BurstSize 1782 UNITS "bytes" 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "The size of the largest burst expected from 1787 the sender at a time. 1789 If this is less than the sender's advertised 1790 burst size, the receiver is asking the network 1791 to provide flow pacing beyond what would be 1792 provided under normal circumstances. Such pac- 1793 ing is at the network's option." 1794 ::= { rsvpResvFwdEntry 16 } 1796 rsvpResvFwdTSpecMinTU OBJECT-TYPE 1797 SYNTAX MessageSize 1798 MAX-ACCESS read-only 1799 STATUS current 1800 DESCRIPTION 1801 "The minimum message size for this flow. The 1802 policing algorithm will treat smaller messages 1803 as though they are this size." 1804 ::= { rsvpResvFwdEntry 17 } 1806 rsvpResvFwdTSpecMaxTU OBJECT-TYPE 1807 SYNTAX MessageSize 1808 MAX-ACCESS read-only 1809 STATUS current 1810 DESCRIPTION 1811 "The maximum message size for this flow. The 1812 admission algorithm will reject TSpecs whose 1813 Maximum Transmission Unit, plus the interface 1814 headers, exceed the interface MTU." 1815 ::= { rsvpResvFwdEntry 18 } 1817 rsvpResvFwdRSpecRate OBJECT-TYPE 1818 SYNTAX BitRate 1819 UNITS "bytes per second" 1820 MAX-ACCESS read-only 1821 STATUS current 1822 DESCRIPTION 1823 "If the requested service is Guaranteed, as 1824 specified by rsvpResvService, this is the 1825 clearing rate that is being requested. Other- 1826 wise, it is zero, or the agent may return 1827 noSuchValue." 1828 ::= { rsvpResvFwdEntry 19 } 1830 rsvpResvFwdRSpecSlack OBJECT-TYPE 1831 SYNTAX Integer32 1832 UNITS "microseconds" 1833 MAX-ACCESS read-only 1834 STATUS current 1835 DESCRIPTION 1836 "If the requested service is Guaranteed, as 1837 specified by rsvpResvService, this is the delay 1838 slack. Otherwise, it is zero, or the agent may 1839 return noSuchValue." 1840 ::= { rsvpResvFwdEntry 20 } 1842 rsvpResvFwdInterval OBJECT-TYPE 1843 SYNTAX RefreshInterval 1844 MAX-ACCESS read-only 1845 STATUS current 1846 DESCRIPTION 1847 "The interval between refresh messages adver- 1848 tised to the Previous Hop." 1849 ::= { rsvpResvFwdEntry 21 } 1851 rsvpResvFwdScope OBJECT-TYPE 1852 SYNTAX OCTET STRING (SIZE(0..65536)) 1853 MAX-ACCESS read-only 1854 STATUS current 1855 DESCRIPTION 1856 "The contents of the scope object, displayed as 1857 an uninterpreted string of octets, including 1858 the object header. In the absence of such an 1859 object, this should be of zero length." 1860 ::= { rsvpResvFwdEntry 22 } 1862 rsvpResvFwdShared OBJECT-TYPE 1863 SYNTAX TruthValue 1864 MAX-ACCESS read-only 1865 STATUS current 1866 DESCRIPTION 1867 "If TRUE, a reservation shared among senders is 1868 requested. If FALSE, a reservation specific to 1869 this sender is requested." 1870 ::= { rsvpResvFwdEntry 23 } 1872 rsvpResvFwdExplicit OBJECT-TYPE 1873 SYNTAX TruthValue 1874 MAX-ACCESS read-only 1875 STATUS current 1876 DESCRIPTION 1877 "If TRUE, individual senders are listed using 1878 Filter Specifications. If FALSE, all senders 1879 are implicitly selected. The Scope Object will 1880 contain a list of senders that need to receive 1881 this reservation request for the purpose of 1882 routing the RESV message." 1883 ::= { rsvpResvFwdEntry 24 } 1885 rsvpResvFwdRSVPHop OBJECT-TYPE 1886 SYNTAX TruthValue 1887 MAX-ACCESS read-only 1888 STATUS current 1889 DESCRIPTION 1890 "If TRUE, the node believes that the next IP 1891 hop is an RSVP hop. If FALSE, the node be- 1892 lieves that the next IP hop may not be an RSVP 1893 hop." 1894 ::= { rsvpResvFwdEntry 25 } 1896 rsvpResvFwdLastChange OBJECT-TYPE 1897 SYNTAX TimeStamp 1898 MAX-ACCESS read-only 1899 STATUS current 1900 DESCRIPTION 1901 "The time of the last change in this request; 1902 This is either the first time it was sent or 1903 the time of the most recent change in parame- 1904 ters." 1905 ::= { rsvpResvFwdEntry 26 } 1907 rsvpResvFwdPolicy OBJECT-TYPE 1908 SYNTAX OCTET STRING (SIZE(0..65536)) 1909 MAX-ACCESS read-only 1910 STATUS current 1911 DESCRIPTION 1912 "The contents of the policy object, displayed 1913 as an uninterpreted string of octets, including 1914 the object header. In the absence of such an 1915 object, this should be of zero length." 1916 ::= { rsvpResvFwdEntry 27 } 1918 rsvpResvFwdStatus OBJECT-TYPE 1919 SYNTAX RowStatus 1920 MAX-ACCESS read-write 1921 STATUS current 1922 DESCRIPTION 1923 "'active' for all active RESV messages. This 1924 object may be used to delete RESV information." 1925 ::= { rsvpResvFwdEntry 28 } 1927 rsvpResvFwdTTL OBJECT-TYPE 1928 SYNTAX INTEGER (0..255) 1929 MAX-ACCESS read-only 1930 STATUS current 1931 DESCRIPTION 1932 "The TTL value in the RSVP header that was last 1933 received." 1934 ::= { rsvpResvFwdEntry 29 } 1936 -- The RSVP Interface Attributes Database contains the 1937 -- RSVP-specific information for an interface. Information 1938 -- that is shared with other reservation procedures such 1939 -- as ST-II is in the Integrated Interface Attributes 1940 -- Database. 1942 rsvpIfTable OBJECT-TYPE 1943 SYNTAX SEQUENCE OF RsvpIfEntry 1944 MAX-ACCESS not-accessible 1945 STATUS current 1946 DESCRIPTION 1947 "The RSVP-specific attributes of the system's 1948 interfaces." 1949 ::= { rsvpObjects 6 } 1951 rsvpIfEntry OBJECT-TYPE 1952 SYNTAX RsvpIfEntry 1953 MAX-ACCESS not-accessible 1954 STATUS current 1955 DESCRIPTION 1956 "The RSVP-specific attributes of the a given 1957 interface." 1958 INDEX { ifIndex } 1959 ::= { rsvpIfTable 1 } 1961 RsvpIfEntry ::= 1962 SEQUENCE { 1963 rsvpIfUdpNbrs Gauge32, 1964 rsvpIfIpNbrs Gauge32, 1965 rsvpIfNbrs Gauge32, 1966 rsvpIfEnabled TruthValue, 1967 rsvpIfUdpRequired TruthValue, 1968 rsvpIfRefreshBlockadeMultiple INTEGER, 1969 rsvpIfRefreshMultiple INTEGER, 1970 rsvpIfTTL INTEGER, 1971 rsvpIfRefreshInterval TimeInterval, 1972 rsvpIfRouteDelay TimeInterval, 1973 rsvpIfStatus RowStatus 1974 } 1975 rsvpIfUdpNbrs OBJECT-TYPE 1976 SYNTAX Gauge32 1977 MAX-ACCESS read-only 1978 STATUS current 1979 DESCRIPTION 1980 "The number of neighbors perceived to be using 1981 only the RSVP UDP Encapsulation." 1982 ::= { rsvpIfEntry 1 } 1984 rsvpIfIpNbrs OBJECT-TYPE 1985 SYNTAX Gauge32 1986 MAX-ACCESS read-only 1987 STATUS current 1988 DESCRIPTION 1989 "The number of neighbors perceived to be using 1990 only the RSVP IP Encapsulation." 1991 ::= { rsvpIfEntry 2 } 1993 rsvpIfNbrs OBJECT-TYPE 1994 SYNTAX Gauge32 1995 MAX-ACCESS read-only 1996 STATUS current 1997 DESCRIPTION 1998 "The number of neighbors currently perceived; 1999 this will exceed rsvpIfIpNbrs + rsvpIfUdpNbrs 2000 by the number of neighbors using both encapsu- 2001 lations." 2002 ::= { rsvpIfEntry 3 } 2004 rsvpIfRefreshBlockadeMultiple OBJECT-TYPE 2005 SYNTAX INTEGER (1..65536) 2006 MAX-ACCESS read-create 2007 STATUS current 2008 DESCRIPTION 2009 "The value of the RSVP value 'Kb', Which is the 2010 minimum number of refresh intervals that 2011 blockade state will last once entered." 2012 DEFVAL { 4 } 2013 ::= { rsvpIfEntry 4 } 2015 rsvpIfRefreshMultiple OBJECT-TYPE 2016 SYNTAX INTEGER (1..65536) 2017 MAX-ACCESS read-create 2018 STATUS current 2019 DESCRIPTION 2020 "The value of the RSVP value 'K', which is the 2021 number of refresh intervals which must elapse 2022 (minimum) before a PATH or RESV message which 2023 is not being refreshed will be aged out." 2024 DEFVAL { 3 } 2025 ::= { rsvpIfEntry 5 } 2027 rsvpIfTTL OBJECT-TYPE 2028 SYNTAX INTEGER (0..255) 2029 MAX-ACCESS read-create 2030 STATUS current 2031 DESCRIPTION 2032 "The value of SEND_TTL used on this interface 2033 for messages this node originates. If set to 2034 zero, the node determines the TTL via other 2035 means." 2036 DEFVAL { 0 } -- which is to say, no override 2037 ::= { rsvpIfEntry 6 } 2039 rsvpIfRefreshInterval OBJECT-TYPE 2040 SYNTAX TimeInterval 2041 UNITS "hundredths of a second" 2042 MAX-ACCESS read-create 2043 STATUS current 2044 DESCRIPTION 2045 "The value of the RSVP value 'R', which is the 2046 minimum period between refresh transmissions of 2047 a given PATH or RESV message on an interface." 2048 DEFVAL { 3000 } -- 30 seconds 2049 ::= { rsvpIfEntry 7 } 2051 rsvpIfRouteDelay OBJECT-TYPE 2052 SYNTAX TimeInterval 2053 UNITS "hundredths of a second" 2054 MAX-ACCESS read-create 2055 STATUS current 2056 DESCRIPTION 2057 "The approximate period from the time a route 2058 is changed to the time a resulting message ap- 2059 pears on the interface." 2060 DEFVAL { 200 } -- 2 seconds 2061 ::= { rsvpIfEntry 8 } 2063 rsvpIfEnabled OBJECT-TYPE 2064 SYNTAX TruthValue 2065 MAX-ACCESS read-create 2066 STATUS current 2067 DESCRIPTION 2068 "If TRUE, RSVP is enabled on this Interface. 2069 If FALSE, RSVP is not enabled on this inter- 2070 face." 2071 ::= { rsvpIfEntry 9 } 2073 rsvpIfUdpRequired OBJECT-TYPE 2074 SYNTAX TruthValue 2075 MAX-ACCESS read-create 2076 STATUS current 2077 DESCRIPTION 2078 "If TRUE, manual configuration forces the use 2079 of UDP encapsulation on the interface. If 2080 FALSE, UDP encapsulation is only used if rsvpI- 2081 fUdpNbrs is not zero." 2083 ::= { rsvpIfEntry 10 } 2085 rsvpIfStatus OBJECT-TYPE 2086 SYNTAX RowStatus 2087 MAX-ACCESS read-create 2088 STATUS current 2089 DESCRIPTION 2090 "'active' on interfaces that are configured for 2091 RSVP." 2092 ::= { rsvpIfEntry 11 } 2094 -- The RSVP Neighbor Database lists the neighbors the RSVP 2095 -- process currently is receiving messages from. 2097 rsvpNbrTable OBJECT-TYPE 2098 SYNTAX SEQUENCE OF RsvpNbrEntry 2099 MAX-ACCESS not-accessible 2100 STATUS current 2101 DESCRIPTION 2102 "Information describing the Neighbors of an 2103 RSVP system." 2104 ::= { rsvpObjects 7 } 2106 rsvpNbrEntry OBJECT-TYPE 2107 SYNTAX RsvpNbrEntry 2108 MAX-ACCESS not-accessible 2109 STATUS current 2110 DESCRIPTION 2111 "Information describing a single RSVP Neigh- 2112 bor." 2113 INDEX { ifIndex, rsvpNbrAddress } 2114 ::= { rsvpNbrTable 1 } 2116 RsvpNbrEntry ::= 2117 SEQUENCE { 2118 rsvpNbrAddress OCTET STRING, 2119 rsvpNbrProtocol RsvpEncapsulation, 2120 rsvpNbrStatus RowStatus 2121 } 2123 rsvpNbrAddress OBJECT-TYPE 2124 SYNTAX OCTET STRING (SIZE(4..16)) 2125 MAX-ACCESS not-accessible 2126 STATUS current 2127 DESCRIPTION 2128 "The IP4 or IP6 Address used by this neighbor. 2129 This object may not be changed when the value 2130 of the RowStatus object is 'active'." 2131 ::= { rsvpNbrEntry 1 } 2133 rsvpNbrProtocol OBJECT-TYPE 2134 SYNTAX RsvpEncapsulation 2135 MAX-ACCESS read-create 2136 STATUS current 2137 DESCRIPTION 2138 "The encapsulation being used by this neigh- 2139 bor." 2140 ::= { rsvpNbrEntry 2 } 2142 rsvpNbrStatus OBJECT-TYPE 2143 SYNTAX RowStatus 2144 MAX-ACCESS read-create 2145 STATUS current 2146 DESCRIPTION 2147 "'active' for all neighbors. This object may 2148 be used to configure neighbors. In the pres- 2149 ence of configured neighbors, the implementa- 2150 tion may (but is not required to) limit the set 2151 of valid neighbors to those configured." 2152 ::= { rsvpNbrEntry 3 } 2154 -- 2155 -- Notifications used to signal events 2156 -- 2158 newFlow NOTIFICATION-TYPE 2159 OBJECTS { 2160 intSrvFlowStatus, rsvpSessionDestAddr, 2161 rsvpResvFwdStatus, rsvpResvStatus, rsvpSenderStatus 2162 } 2163 STATUS current 2164 DESCRIPTION 2165 "The newFlow trap indicates that the originat- 2166 ing system has installed a new flow in its 2167 classifier, or (when reservation authorization 2168 is in view) is prepared to install such a flow 2169 in the classifier and is requesting authoriza- 2170 tion. The objects included with the Notifica- 2171 tion may be used to read further information 2172 using the Integrated Services and RSVP MIBs. 2173 Authorization or non-authorization may be 2174 enacted by a write to the variable intSrvFlowS- 2175 tatus." 2176 ::= { rsvpNotifications 1 } 2178 lostFlow NOTIFICATION-TYPE 2179 OBJECTS { 2180 intSrvFlowStatus, rsvpSessionDestAddr, 2181 rsvpResvFwdStatus, rsvpResvStatus, rsvpSenderStatus 2182 } 2183 STATUS current 2184 DESCRIPTION 2185 "The lostFlow trap indicates that the originat- 2186 ing system has removed a flow from its classif- 2187 ier." 2188 ::= { rsvpNotifications 2 } 2190 -- conformance information 2192 rsvpGroups OBJECT IDENTIFIER ::= { rsvpConformance 1 } 2193 rsvpCompliances OBJECT IDENTIFIER ::= { rsvpConformance 2 } 2195 -- compliance statements 2196 rsvpCompliance MODULE-COMPLIANCE 2197 STATUS current 2198 DESCRIPTION 2199 "The compliance statement. Note that the im- 2200 plementation of this module requires implemen- 2201 tation of the Integrated Services MIB as well." 2202 MODULE -- this module 2203 MANDATORY-GROUPS { 2204 rsvpSessionGroup, rsvpSenderGroup, rsvpResvGroup, 2205 rsvpIfGroup, rsvpNbrGroup 2206 } 2208 GROUP rsvpResvFwdGroup 2209 DESCRIPTION 2210 "The Reservation Requests table is appropriate 2211 in implementations that store upstream reserva- 2212 tion messages, but not appropriate in implemen- 2213 tations which calculate them on each transmis- 2214 sion." 2216 GROUP rsvpNotificationGroup 2217 DESCRIPTION 2218 "The notifications in this module may be used to 2219 advise a network management station of changes in 2220 flow status, and are required when this use is in 2221 view." 2223 OBJECT rsvpSessionRequests 2224 MIN-ACCESS not-accessible 2225 DESCRIPTION 2226 "This object is optional." 2228 OBJECT rsvpSessionFlowId 2229 MIN-ACCESS not-accessible 2230 DESCRIPTION 2231 "This object is needed only in a system that imple- 2232 ments IPv6." 2234 OBJECT rsvpSenderType 2235 MIN-ACCESS read-only 2236 DESCRIPTION 2237 "read-create access is not required. This may be 2238 read-only." 2240 OBJECT rsvpSenderDestAddr 2241 MIN-ACCESS read-only 2242 DESCRIPTION 2243 "read-create access is not required. This may be 2244 read-only." 2246 OBJECT rsvpSenderAddr 2247 MIN-ACCESS read-only 2248 DESCRIPTION 2249 "read-create access is not required. This may be 2250 read-only." 2252 OBJECT rsvpSenderDestAddrLength 2253 MIN-ACCESS read-only 2254 DESCRIPTION 2255 "read-create access is not required. This may be 2256 read-only." 2258 OBJECT rsvpSenderAddrLength 2259 MIN-ACCESS read-only 2260 DESCRIPTION 2261 "read-create access is not required. This may be 2262 read-only." 2264 OBJECT rsvpSenderProtocol 2265 MIN-ACCESS read-only 2266 DESCRIPTION 2267 "read-create access is not required. This may be 2268 read-only." 2270 OBJECT rsvpSenderDestPort 2271 MIN-ACCESS read-only 2272 DESCRIPTION 2273 "read-create access is not required. This may be 2274 read-only." 2276 OBJECT rsvpSenderPort 2277 MIN-ACCESS read-only 2278 DESCRIPTION 2279 "read-create access is not required. This may be 2280 read-only." 2282 OBJECT rsvpSenderHopAddr 2283 MIN-ACCESS read-only 2284 DESCRIPTION 2285 "read-create access is not required. This may be 2286 read-only." 2288 OBJECT rsvpSenderHopLih 2289 MIN-ACCESS read-only 2290 DESCRIPTION 2291 "read-create access is not required. This may be 2292 read-only." 2294 OBJECT rsvpSenderInterface 2295 MIN-ACCESS read-only 2296 DESCRIPTION 2297 "read-create access is not required. This may be 2298 read-only." 2300 OBJECT rsvpSenderTSpecRate 2301 MIN-ACCESS read-only 2302 DESCRIPTION 2303 "read-create access is not required. This may be 2304 read-only." 2306 OBJECT rsvpSenderTSpecPeakRate 2307 MIN-ACCESS read-only 2308 DESCRIPTION 2309 "read-create access is not required. This may be 2310 read-only." 2312 OBJECT rsvpSenderTSpecBurst 2313 MIN-ACCESS read-only 2314 DESCRIPTION 2315 "read-create access is not required. This may be 2316 read-only." 2318 OBJECT rsvpSenderTSpecMinTU 2319 MIN-ACCESS read-only 2320 DESCRIPTION 2321 "read-create access is not required. This may be 2322 read-only." 2324 OBJECT rsvpSenderTSpecMaxTU 2325 MIN-ACCESS read-only 2326 DESCRIPTION 2327 "read-create access is not required. This may be 2328 read-only." 2330 OBJECT rsvpSenderInterval 2331 MIN-ACCESS read-only 2332 DESCRIPTION 2333 "read-create access is not required. This may be 2334 read-only." 2336 OBJECT rsvpSenderRSVPHop 2337 MIN-ACCESS read-only 2338 DESCRIPTION 2339 "read-create access is not required. This may be 2340 read-only." 2342 OBJECT rsvpSenderPolicy 2343 MIN-ACCESS read-only 2344 DESCRIPTION 2345 "read-create access is not required. This may be 2346 read-only." 2348 OBJECT rsvpSenderAdspecBreak 2349 MIN-ACCESS read-only 2350 DESCRIPTION 2351 "read-create access is not required. This may be 2352 read-only." 2354 OBJECT rsvpSenderAdspecHopCount 2355 MIN-ACCESS read-only 2356 DESCRIPTION 2357 "read-create access is not required. This may be 2358 read-only." 2360 OBJECT rsvpSenderAdspecPathBw 2361 MIN-ACCESS read-only 2362 DESCRIPTION 2363 "read-create access is not required. This may be 2364 read-only." 2366 OBJECT rsvpSenderAdspecMinLatency 2367 MIN-ACCESS read-only 2368 DESCRIPTION 2369 "read-create access is not required. This may be 2370 read-only." 2372 OBJECT rsvpSenderAdspecMtu 2373 MIN-ACCESS read-only 2374 DESCRIPTION 2375 "read-create access is not required. This may be 2376 read-only." 2378 OBJECT rsvpSenderAdspecGuaranteedSvc 2379 MIN-ACCESS not-accessible 2380 DESCRIPTION 2381 "This may be not-accessible if the system does not 2382 support Guaranteed Service." 2384 OBJECT rsvpSenderAdspecGuaranteedBreak 2385 MIN-ACCESS not-accessible 2386 DESCRIPTION 2387 "This may be not-accessible if the system does not 2388 support Guaranteed Service." 2390 OBJECT rsvpSenderAdspecGuaranteedCtot 2391 MIN-ACCESS not-accessible 2392 DESCRIPTION 2393 "This may be not-accessible if the system does not 2394 support Guaranteed Service." 2396 OBJECT rsvpSenderAdspecGuaranteedDtot 2397 MIN-ACCESS not-accessible 2398 DESCRIPTION 2399 "This may be not-accessible if the system does not 2400 support Guaranteed Service." 2402 OBJECT rsvpSenderAdspecGuaranteedCsum 2403 MIN-ACCESS not-accessible 2404 DESCRIPTION 2405 "This may be not-accessible if the system does not 2406 support Guaranteed Service." 2408 OBJECT rsvpSenderAdspecGuaranteedDsum 2409 MIN-ACCESS read-only 2410 DESCRIPTION 2411 "This may be not-accessible if the system does not 2412 support Guaranteed Service." 2414 OBJECT rsvpSenderAdspecGuaranteedHopCount 2415 MIN-ACCESS not-accessible 2416 DESCRIPTION 2417 "This may be not-accessible if the system does not 2418 support Guaranteed Service." 2420 OBJECT rsvpSenderAdspecGuaranteedPathBw 2421 MIN-ACCESS not-accessible 2422 DESCRIPTION 2423 "This may be not-accessible if the system does not 2424 support Guaranteed Service." 2426 OBJECT rsvpSenderAdspecGuaranteedMinLatency 2427 MIN-ACCESS not-accessible 2428 DESCRIPTION 2429 "This may be not-accessible if the system does not 2430 support Guaranteed Service." 2432 OBJECT rsvpSenderAdspecGuaranteedMtu 2433 MIN-ACCESS not-accessible 2434 DESCRIPTION 2435 "This may be not-accessible if the system does not 2436 support Guaranteed Service." 2438 OBJECT rsvpSenderAdspecCtrlLoadSvc 2439 MIN-ACCESS not-accessible 2440 DESCRIPTION 2441 "This may be not-accessible if the system does not 2442 support Controlled Load." 2444 OBJECT rsvpSenderAdspecCtrlLoadBreak 2445 MIN-ACCESS not-accessible 2446 DESCRIPTION 2447 "This may be not-accessible if the system does not 2448 support Controlled Load." 2450 OBJECT rsvpSenderAdspecCtrlLoadHopCount 2451 MIN-ACCESS not-accessible 2452 DESCRIPTION 2453 "This may be not-accessible if the system does not 2454 support Controlled Load." 2456 OBJECT rsvpSenderAdspecCtrlLoadPathBw 2457 MIN-ACCESS not-accessible 2458 DESCRIPTION 2459 "This may be not-accessible if the system does not 2460 support Controlled Load." 2462 OBJECT rsvpSenderAdspecCtrlLoadMinLatency 2463 MIN-ACCESS not-accessible 2464 DESCRIPTION 2465 "This may be not-accessible if the system does not 2466 support Controlled Load." 2468 OBJECT rsvpSenderAdspecCtrlLoadMtu 2469 MIN-ACCESS not-accessible 2470 DESCRIPTION 2471 "This may be not-accessible if the system does not 2472 support Controlled Load." 2474 OBJECT rsvpSenderStatus 2475 MIN-ACCESS read-only 2476 DESCRIPTION 2477 "read-create access is not required. This may be 2478 read-only." 2480 OBJECT rsvpResvType 2481 MIN-ACCESS read-only 2482 DESCRIPTION 2483 "read-create access is not required. This may be 2484 read-only." 2486 OBJECT rsvpResvDestAddr 2487 MIN-ACCESS read-only 2488 DESCRIPTION 2489 "read-create access is not required. This may be 2490 read-only." 2492 OBJECT rsvpResvSenderAddr 2493 MIN-ACCESS read-only 2494 DESCRIPTION 2495 "read-create access is not required. This may be 2496 read-only." 2498 OBJECT rsvpResvDestAddrLength 2499 MIN-ACCESS read-only 2500 DESCRIPTION 2501 "read-create access is not required. This may be 2502 read-only." 2504 OBJECT rsvpResvSenderAddrLength 2505 MIN-ACCESS read-only 2506 DESCRIPTION 2507 "read-create access is not required. This may be 2508 read-only." 2510 OBJECT rsvpResvProtocol 2511 MIN-ACCESS read-only 2512 DESCRIPTION 2513 "read-create access is not required. This may be 2514 read-only." 2516 OBJECT rsvpResvDestPort 2517 MIN-ACCESS read-only 2518 DESCRIPTION 2519 "read-create access is not required. This may be 2520 read-only." 2522 OBJECT rsvpResvPort 2523 MIN-ACCESS read-only 2524 DESCRIPTION 2525 "read-create access is not required. This may be 2526 read-only." 2528 OBJECT rsvpResvHopAddr 2529 MIN-ACCESS read-only 2530 DESCRIPTION 2531 "read-create access is not required. This may be 2532 read-only." 2534 OBJECT rsvpResvHopLih 2535 MIN-ACCESS read-only 2536 DESCRIPTION 2537 "read-create access is not required. This may be 2538 read-only." 2540 OBJECT rsvpResvInterface 2541 MIN-ACCESS read-only 2542 DESCRIPTION 2543 "read-create access is not required. This may be 2544 read-only." 2546 OBJECT rsvpResvService 2547 MIN-ACCESS read-only 2548 DESCRIPTION 2549 "read-create access is not required. This may be 2550 read-only." 2552 OBJECT rsvpResvTSpecRate 2553 MIN-ACCESS read-only 2554 DESCRIPTION 2555 "read-create access is not required. This may be 2556 read-only." 2558 OBJECT rsvpResvTSpecPeakRate 2559 MIN-ACCESS read-only 2560 DESCRIPTION 2561 "read-create access is not required. This may be 2562 read-only." 2564 OBJECT rsvpResvTSpecBurst 2565 MIN-ACCESS read-only 2566 DESCRIPTION 2567 "read-create access is not required. This may be 2568 read-only." 2570 OBJECT rsvpResvTSpecMinTU 2571 MIN-ACCESS read-only 2572 DESCRIPTION 2573 "read-create access is not required. This may be 2574 read-only." 2576 OBJECT rsvpResvTSpecMaxTU 2577 MIN-ACCESS read-only 2578 DESCRIPTION 2579 "read-create access is not required. This may be 2580 read-only." 2582 OBJECT rsvpResvRSpecRate 2583 MIN-ACCESS read-only 2584 DESCRIPTION 2585 "read-create access is not required. This may be 2586 read-only." 2588 OBJECT rsvpResvRSpecSlack 2589 MIN-ACCESS read-only 2590 DESCRIPTION 2591 "read-create access is not required. This may be 2592 read-only." 2594 OBJECT rsvpResvInterval 2595 MIN-ACCESS read-only 2596 DESCRIPTION 2597 "read-create access is not required. This may be 2598 read-only." 2600 OBJECT rsvpResvScope 2601 MIN-ACCESS read-only 2602 DESCRIPTION 2603 "read-create access is not required. This may be 2604 read-only." 2606 OBJECT rsvpResvShared 2607 MIN-ACCESS read-only 2608 DESCRIPTION 2609 "read-create access is not required. This may be 2610 read-only." 2612 OBJECT rsvpResvExplicit 2613 MIN-ACCESS read-only 2614 DESCRIPTION 2615 "read-create access is not required. This may be 2616 read-only." 2618 OBJECT rsvpResvRSVPHop 2619 MIN-ACCESS read-only 2620 DESCRIPTION 2621 "read-create access is not required. This may be 2622 read-only." 2624 OBJECT rsvpResvPolicy 2625 MIN-ACCESS read-only 2626 DESCRIPTION 2627 "read-create access is not required. This may be 2628 read-only." 2630 OBJECT rsvpResvStatus 2631 MIN-ACCESS read-only 2632 DESCRIPTION 2633 "read-create access is not required. This may be 2634 read-only." 2636 OBJECT rsvpResvFwdStatus 2637 MIN-ACCESS read-only 2638 DESCRIPTION 2639 "read-create access is not required. This may be 2640 read-only." 2642 ::= { rsvpCompliances 1 } 2643 rsvpSessionGroup OBJECT-GROUP 2644 OBJECTS { 2645 rsvpSessionType, rsvpSessionDestAddr, 2646 rsvpSessionDestAddrLength, rsvpSessionProtocol, 2647 rsvpSessionPort, rsvpSessionSenders, rsvpSessionReceivers, 2648 rsvpSessionRequests, rsvpSessionFlowId 2649 } 2650 STATUS current 2651 DESCRIPTION 2652 "These objects are required for RSVP Systems." 2653 ::= { rsvpGroups 1 } 2655 rsvpSenderGroup OBJECT-GROUP 2656 OBJECTS { 2657 rsvpSenderType, rsvpSenderDestAddr, rsvpSenderAddr, 2658 rsvpSenderDestAddrLength, rsvpSenderAddrLength, 2659 rsvpSenderProtocol, rsvpSenderDestPort, rsvpSenderPort, 2660 rsvpSenderHopAddr, rsvpSenderHopLih, rsvpSenderInterface, 2661 rsvpSenderTSpecRate, rsvpSenderTSpecPeakRate, 2662 rsvpSenderTSpecBurst, rsvpSenderTSpecMinTU, 2663 rsvpSenderTSpecMaxTU, rsvpSenderInterval, rsvpSenderLastChange, 2664 rsvpSenderStatus, rsvpSenderRSVPHop, rsvpSenderPolicy, 2665 rsvpSenderAdspecBreak, rsvpSenderAdspecHopCount, 2666 rsvpSenderAdspecPathBw, rsvpSenderAdspecMinLatency, 2667 rsvpSenderAdspecMtu, rsvpSenderAdspecGuaranteedSvc, 2668 rsvpSenderAdspecGuaranteedBreak, 2669 rsvpSenderAdspecGuaranteedCtot, rsvpSenderAdspecGuaranteedDtot, 2670 rsvpSenderAdspecGuaranteedCsum, rsvpSenderAdspecGuaranteedDsum, 2671 rsvpSenderAdspecGuaranteedHopCount, 2672 rsvpSenderAdspecGuaranteedPathBw, 2673 rsvpSenderAdspecGuaranteedMinLatency, 2674 rsvpSenderAdspecGuaranteedMtu, rsvpSenderAdspecCtrlLoadSvc, 2675 rsvpSenderAdspecCtrlLoadBreak, 2676 rsvpSenderAdspecCtrlLoadHopCount, 2677 rsvpSenderAdspecCtrlLoadPathBw, 2678 rsvpSenderAdspecCtrlLoadMinLatency, 2679 rsvpSenderAdspecCtrlLoadMtu, rsvpSenderNewIndex 2680 } 2681 STATUS current 2682 DESCRIPTION 2683 "These objects are required for RSVP Systems." 2684 ::= { rsvpGroups 2 } 2686 rsvpResvGroup OBJECT-GROUP 2687 OBJECTS { 2688 rsvpResvType, rsvpResvDestAddr, rsvpResvSenderAddr, 2689 rsvpResvDestAddrLength, rsvpResvSenderAddrLength, 2690 rsvpResvProtocol, rsvpResvDestPort, rsvpResvPort, 2691 rsvpResvHopAddr, rsvpResvHopLih, rsvpResvInterface, 2692 rsvpResvService, rsvpResvTSpecRate, rsvpResvTSpecBurst, 2693 rsvpResvTSpecPeakRate, rsvpResvTSpecMinTU, rsvpResvTSpecMaxTU, 2694 rsvpResvRSpecRate, rsvpResvRSpecSlack, rsvpResvInterval, 2695 rsvpResvScope, rsvpResvShared, rsvpResvExplicit, 2696 rsvpResvRSVPHop, rsvpResvLastChange, rsvpResvPolicy, 2697 rsvpResvStatus, rsvpResvNewIndex 2698 } 2699 STATUS current 2700 DESCRIPTION 2701 "These objects are required for RSVP Systems." 2702 ::= { rsvpGroups 3 } 2704 rsvpResvFwdGroup OBJECT-GROUP 2705 OBJECTS { 2706 rsvpResvFwdType, rsvpResvFwdDestAddr, rsvpResvFwdSenderAddr, 2707 rsvpResvFwdDestAddrLength, rsvpResvFwdSenderAddrLength, 2708 rsvpResvFwdProtocol, rsvpResvFwdDestPort, rsvpResvFwdPort, 2709 rsvpResvFwdHopAddr, rsvpResvFwdHopLih, rsvpResvFwdInterface, 2710 rsvpResvFwdNewIndex, rsvpResvFwdService, 2711 rsvpResvFwdTSpecPeakRate, rsvpResvFwdTSpecMinTU, 2712 rsvpResvFwdTSpecMaxTU, rsvpResvFwdTSpecRate, 2713 rsvpResvFwdTSpecBurst, rsvpResvFwdRSpecRate, 2714 rsvpResvFwdRSpecSlack, rsvpResvFwdInterval, rsvpResvFwdScope, 2715 rsvpResvFwdShared, rsvpResvFwdExplicit, rsvpResvFwdRSVPHop, 2716 rsvpResvFwdLastChange, rsvpResvFwdPolicy, rsvpResvFwdStatus 2717 } 2718 STATUS current 2719 DESCRIPTION 2720 "These objects are optional, used for some RSVP 2721 Systems." 2722 ::= { rsvpGroups 4 } 2724 rsvpIfGroup OBJECT-GROUP 2725 OBJECTS { 2726 rsvpIfUdpNbrs, rsvpIfIpNbrs, rsvpIfNbrs, rsvpIfEnabled, 2727 rsvpIfUdpRequired, rsvpIfRefreshBlockadeMultiple, 2728 rsvpIfRefreshMultiple, rsvpIfRefreshInterval, rsvpIfTTL, 2729 rsvpIfRouteDelay, rsvpIfStatus 2730 } 2731 STATUS current 2732 DESCRIPTION 2733 "These objects are required for RSVP Systems." 2734 ::= { rsvpGroups 6 } 2736 rsvpNbrGroup OBJECT-GROUP 2737 OBJECTS { 2738 rsvpNbrProtocol, rsvpNbrStatus 2739 } 2740 STATUS current 2741 DESCRIPTION 2742 "These objects are required for RSVP Systems." 2743 ::= { rsvpGroups 7 } 2745 rsvpNotificationGroup NOTIFICATION-GROUP 2746 NOTIFICATIONS { newFlow, lostFlow } 2747 STATUS current 2748 DESCRIPTION 2749 "This notification is required for Systems sup- 2750 porting the RSVP Policy Module using an SNMP 2751 interface to the Policy Manager." 2752 ::= { rsvpGroups 8 } 2754 END 2755 6. Security Issues 2757 Security issues for this MIB are entirely covered by the SNMP 2758 Security Architecture, and have not been expanded within the 2759 contents of this MIB. RSVP has its own set of security issues, 2760 which are outside the scope of this MIB. 2762 7. Authors' Addresses 2764 Fred Baker 2765 Postal: Cisco Systems 2766 519 Lado Drive 2767 Santa Barbara, California 93111 2768 Tel: +1 805 681 0115 2769 E-Mail: fred@cisco.com 2771 John Krawczyk 2772 Postal: ArrowPoint Communications 2773 235 Littleton Road 2774 Westford, Massachusetts 01886 2775 Tel: +1 508 692 5875 2776 E-Mail: jjk@tiac.net" 2778 8. Acknowledgements 2780 This document was produced by the RSVP Working Group. 2782 9. References 2784 [1] M.T. Rose (editor), Management Information Base for 2785 Network Management of TCP/IP-based internets, Internet 2786 Working Group Request for Comments 1213. Network 2787 Information Center, SRI International, Menlo Park, 2788 California, (May, 1990). 2790 [2] Information processing systems - Open Systems 2791 Interconnection - Specification of Abstract Syntax 2792 Notation One (ASN.1), International Organization for 2793 Standardization. International Standard 8824, (December, 2794 1987). 2796 [3] Information processing systems - Open Systems 2797 Interconnection - Specification of Basic Encoding Rules 2798 for Abstract Notation One (ASN.1), International 2799 Organization for Standardization. International Standard 2800 8825, (December, 1987). 2802 Table of Contents 2804 1 Status of this Memo ................................... 1 2805 2 Abstract .............................................. 2 2806 3 The SNMPv2 Network Management Framework ............... 3 2807 3.1 Object Definitions .................................. 3 2808 4 Overview .............................................. 3 2809 4.1 Textual Conventions ................................. 3 2810 4.2 Structure of MIB .................................... 4 2811 4.3 Semantics of Writing the Path and Reservation 2812 State Databases .................................... 4 2813 4.4 Intended use of Flow Notifications .................. 5 2814 4.4.1 The lostFlow Notification ......................... 5 2815 4.4.2 The newFlow Notification .......................... 5 2816 5 Definitions ........................................... 6 2817 5.1 RSVP Session Statistics Database .................... 7 2818 5.1 RSVP Session Sender Database ........................ 11 2819 5.2 RSVP Reservations Requested Database ................ 31 2820 5.3 RSVP Reservation Requests Database .................. 43 2821 5.4 RSVP Interface Attributes Database .................. 55 2822 5.5 RSVP Neighbor Database .............................. 60 2823 5.4 Notifications ....................................... 62 2824 6 Security Issues ....................................... 78 2825 7 Authors' Addresses .................................... 78 2826 8 Acknowledgements ...................................... 78 2827 9 References ............................................ 79