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