idnits 2.17.1 draft-ietf-rsvp-v2-mib-00.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-23) 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 84 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 382 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 10 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 233 has weird spacing: '...ds that are ...' == Line 235 has weird spacing: '...d Path or r...' == Line 249 has weird spacing: '... given sys-...' == Line 281 has weird spacing: '...ndexing purpo...' == Line 290 has weird spacing: '...6 with flow...' == (377 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 (July 1997) is 9779 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 2861 looks like a reference -- Missing reference section? '2' on line 2867 looks like a reference -- Missing reference section? '3' on line 2873 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 July 1997 4 RSVP Management Information Base 5 draft-ietf-rsvp-v2-mib-00.txt 7 Tue Oct 7 12:01:03 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 Arun Sastry 27 Cisco Systems 28 210 W. Tasman Drive 29 San Jose, California 95134 31 arun@cisco.com 33 1. Status of this Memo 35 This document is an Internet Draft. Internet Drafts are 36 working documents of the Internet Engineering Task Force 37 (IETF), its Areas, and its Working Groups. Note that other 38 groups may also distribute working documents as Internet 39 Drafts. 41 Internet Drafts are draft documents valid for a maximum of six 42 months. Internet Drafts may be updated, replaced, or obsoleted 43 by other documents at any time. It is not appropriate to use 44 Internet Drafts as reference material or to cite them other 45 than as a "working draft" or "work in progress." 47 Please check the I-D abstract listing contained in each 48 Internet Draft directory to learn the current status of this 49 or any other Internet Draft. 51 2. Abstract 53 This memo defines a portion of the Management Information Base 54 (MIB) for use with network management protocols in TCP/IP- 55 based internets. In particular, it defines objects for 56 managing the Resource Reservation Protocol (RSVP) within the 57 interface attributes defined in the Integrated Services Model. 58 Thus, the Integrated Services MIB is directly relevant to and 59 cross-referenced by this MIB. Comments should be made to the 60 RSVP Working Group, rsvp@isi.edu. 62 This memo does not, in its draft form, specify a standard for 63 the Internet community. 65 3. The SNMPv2 Network Management Framework 67 The SNMPv2 Network Management Framework consists of four major 68 components. They are: 70 o RFC 1441 which defines the SMI, the mechanisms used for 71 describing and naming objects for the purpose of 72 management. 74 o RFC 1213 defines MIB-II, the core set of managed objects 75 for the Internet suite of protocols. 77 o RFC 1445 which defines the administrative and other 78 architectural aspects of the framework. 80 o RFC 1448 which defines the protocol used for network 81 access to managed objects. 83 The Framework permits new objects to be defined for the 84 purpose of experimentation and evaluation. 86 3.1. Object Definitions 88 Managed objects are accessed via a virtual information store, 89 termed the Management Information Base or MIB. Objects in the 90 MIB are defined using the subset of Abstract Syntax Notation 91 One (ASN.1) defined in the SMI. In particular, each object 92 type is named by an OBJECT IDENTIFIER, an administratively 93 assigned name. The object type together with an object 94 instance serves to uniquely identify a specific instantiation 95 of the object. For human convenience, we often use a textual 96 string, termed the descriptor, to refer to the object type. 98 4. Overview 100 4.1. Textual Conventions 102 Several new data types are introduced as a textual convention 103 in this MIB document. These textual conventions enhance the 104 readability of the specification and can ease comparison with 105 other specifications if appropriate. It should be noted that 106 the introduction of the these textual conventions has no 107 effect on either the syntax nor the semantics of any managed 108 objects. The use of these is merely an artifact of the 109 explanatory method used. Objects defined in terms of one of 110 these methods are always encoded by means of the rules that 111 define the primitive type. Hence, no changes to the SMI or 112 the SNMP are necessary to accommodate these textual 113 conventions which are adopted merely for the convenience of 114 readers and writers in pursuit of the elusive goal of clear, 115 concise, and unambiguous MIB documents. 117 4.2. Structure of MIB 119 The MIB is composed of the following sections: 120 General Objects 121 Session Statistics Table 122 Session Sender Table 123 Reservation Requests Received Table 124 Reservation Requests Forwarded Table 125 RSVP Interface Attributes Table 126 RSVP Neighbor Table 128 As a general rule, it is difficult in SNMP to describe 129 arbitrarily long of complex messages; this MIB therefore seeks 130 to describe the Path State Database and the Reservation State 131 Database as though each flow and filter description received 132 in an aggregate message had been received in a separate 133 reservation message. 135 Thus, if a RESV message is received for session 136 224.1.2.3+UDP+4455 with two filter/flow spec groups describing 137 a sender 1.2.3.4 and another sender 1.2.7.8, these two will 138 show in the MIB as two separate rows: one for 139 224.1.2.3+UDP+4455 from 1.2.3.4 and the other for 140 224.1.2.3+UDP+4455 from 1.2.7.8. 142 4.3. Semantics of Writing the Path and Reservation State 143 Databases 145 The path and reservation state tables are writeable. Writing 146 into the Path and Reservation State databases allows one to 147 perform RSVP reservations without authenticating through RSVP 148 mechanisms, but rather through SNMP mechanisms. State created 149 in this way by SNMP does not time out and cannot be deleted by 150 receiving an RSVP teardown message; it can only be deleted by 151 SNMP. Deletion is accomplished by writing 'destroy' to the 152 associated Row Status object, and this will initiate a 153 teardown message as if the state had timed out. 155 4.4. Intended use of Flow Notifications 157 4.4.1. The lostFlow Notification 159 The Lost Flow notification is an asychronous event that 160 signifies that a flow is no longer being observed. 162 4.4.2. The newFlow Notification 164 The newFlow Notification defined in this MIB can be used to 165 advise a network management system of the state of a flow. 167 5. Definitions 169 RSVP-MIB DEFINITIONS ::= BEGIN 171 IMPORTS 172 MODULE-IDENTITY, OBJECT-TYPE, Gauge32, 173 NOTIFICATION-TYPE, Integer32, mib-2 174 FROM SNMPv2-SMI 175 TEXTUAL-CONVENTION, TruthValue, RowStatus, 176 TimeStamp, TestAndIncr, TimeInterval 177 FROM SNMPv2-TC 178 MODULE-COMPLIANCE, OBJECT-GROUP, 179 NOTIFICATION-GROUP FROM SNMPv2-CONF 180 Port, SessionNumber, SessionType, 181 Protocol, QosService, intSrvFlowStatus, 182 MessageSize, BitRate, BurstSize FROM INTEGRATED-SERVICES-MIB 183 ifIndex, InterfaceIndex FROM IF-MIB; 185 rsvp MODULE-IDENTITY 186 LAST-UPDATED "9710071901Z" -- Tue Oct 7 12:01:03 PDT 1997 187 ORGANIZATION "IETF RSVP Working Group" 188 CONTACT-INFO 189 " Fred Baker 190 Postal: Cisco Systems 191 519 Lado Drive 192 Santa Barbara, California 93111 193 Tel: +1 805 681 0115 194 E-Mail: fred@cisco.com 196 John Krawczyk 197 Postal: ArrowPoint Communications 198 235 Littleton Road 199 Westford, Massachusetts 01886 200 Tel: +1 508 692 5875 201 E-Mail: jjk@tiac.net 203 Arun Sastry 204 Postal: Cisco Systems 205 210 W. Tasman Drive 206 San Jose, California 95134 207 Tel: +1 408 526 7685 208 E-Mail: arun@cisco.com" 209 DESCRIPTION 210 "The MIB module to describe the RSVP Protocol" 211 ::= { mib-2 51 } 213 rsvpObjects OBJECT IDENTIFIER ::= { rsvp 1 } -- tables 214 rsvpGenObjects OBJECT IDENTIFIER ::= { rsvp 2 } -- global objects 215 rsvpNotificationsPrefix OBJECT IDENTIFIER ::= { rsvp 3 } -- traps 216 rsvpConformance OBJECT IDENTIFIER ::= { rsvp 4 } -- conformance 218 RsvpEncapsulation ::= TEXTUAL-CONVENTION 219 STATUS current 220 DESCRIPTION 221 "This indicates the encapsulation that an RSVP 222 Neighbor is perceived to be using." 223 SYNTAX INTEGER { 224 ip (1), -- IP Protocol 46 225 udp (2), -- UDP Encapsulation 226 both (3) -- neighbor is using both encapsulations 227 } 229 RefreshInterval ::= TEXTUAL-CONVENTION 230 DISPLAY-HINT "d" 231 STATUS current 232 DESCRIPTION 233 "The number of milliseconds that are expected 234 to elapse between refreshes of path or reserva- 235 tion state. Unrefreshed Path or reservation 236 state is removed after a small multiple of this 237 period." 238 SYNTAX INTEGER (0..'7FFFFFFF'h) 240 -- The RSVP Session Statistics Database displays statistics 241 -- relating to the number of senders and receivers in each 242 -- session. 244 rsvpSessionTable OBJECT-TYPE 245 SYNTAX SEQUENCE OF RsvpSessionEntry 246 MAX-ACCESS not-accessible 247 STATUS current 248 DESCRIPTION 249 "A table of all sessions seen by a given sys- 250 tem." 251 ::= { rsvpObjects 1 } 253 rsvpSessionEntry OBJECT-TYPE 254 SYNTAX RsvpSessionEntry 255 MAX-ACCESS not-accessible 256 STATUS current 257 DESCRIPTION 258 "A single session seen by a given system." 259 INDEX { rsvpSessionNumber } 260 ::= { rsvpSessionTable 1 } 262 RsvpSessionEntry ::= 263 SEQUENCE { 264 rsvpSessionNumber SessionNumber, 265 rsvpSessionType SessionType, 266 rsvpSessionDestAddr OCTET STRING, 267 rsvpSessionDestAddrLength INTEGER, 268 rsvpSessionProtocol Protocol, 269 rsvpSessionPort Port, 270 rsvpSessionSenders Gauge32, 271 rsvpSessionReceivers Gauge32, 272 rsvpSessionRequests Gauge32 273 } 275 rsvpSessionNumber OBJECT-TYPE 276 SYNTAX SessionNumber 277 MAX-ACCESS not-accessible 278 STATUS current 279 DESCRIPTION 280 "The number of this session. This is for SNMP 281 Indexing purposes only and has no relation to 282 any protocol value." 283 ::= { rsvpSessionEntry 1 } 285 rsvpSessionType OBJECT-TYPE 286 SYNTAX SessionType 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The type of session (IP4, IP6, IP6 with flow 291 information, etc)." 292 ::= { rsvpSessionEntry 2 } 294 rsvpSessionDestAddr OBJECT-TYPE 295 SYNTAX OCTET STRING (SIZE(4..16)) 296 MAX-ACCESS read-only 297 STATUS current 298 DESCRIPTION 299 "The destination address used by all senders in 300 this session. This object may not be changed 301 when the value of the RowStatus object is 'ac- 302 tive'." 303 ::= { rsvpSessionEntry 3 } 305 rsvpSessionDestAddrLength OBJECT-TYPE 306 SYNTAX INTEGER(0..128) 307 MAX-ACCESS read-only 308 STATUS current 309 DESCRIPTION 310 "The CIDR prefix length of the session address, 311 which is 32 for IP4 host and multicast ad- 312 dresses, and 128 for IP6 addresses. This ob- 313 ject may not be changed when the value of the 314 RowStatus object is 'active'." 315 ::= { rsvpSessionEntry 4 } 317 rsvpSessionProtocol OBJECT-TYPE 318 SYNTAX Protocol 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 "The IP Protocol used by this session. This 323 object may not be changed when the value of the 324 RowStatus object is 'active'." 325 ::= { rsvpSessionEntry 5 } 327 rsvpSessionPort OBJECT-TYPE 328 SYNTAX Port 329 MAX-ACCESS read-only 330 STATUS current 331 DESCRIPTION 332 "The UDP or TCP port number used as a destina- 333 tion port for all senders in this session. If 334 the IP protocol in use, specified by rsvpSen- 335 derProtocol, is 50 (ESP) or 51 (AH), this 336 represents a virtual destination port number. 337 A value of zero indicates that the IP protocol 338 in use does not have ports. This object may 339 not be changed when the value of the RowStatus 340 object is 'active'." 341 ::= { rsvpSessionEntry 6 } 343 rsvpSessionSenders OBJECT-TYPE 344 SYNTAX Gauge32 345 MAX-ACCESS read-only 346 STATUS current 347 DESCRIPTION 348 "The number of distinct senders currently known 349 to be part of this session." 350 ::= { rsvpSessionEntry 7 } 352 rsvpSessionReceivers OBJECT-TYPE 353 SYNTAX Gauge32 354 MAX-ACCESS read-only 355 STATUS current 356 DESCRIPTION 357 "The number of reservations being requested of 358 this system for this session." 359 ::= { rsvpSessionEntry 8 } 361 rsvpSessionRequests OBJECT-TYPE 362 SYNTAX Gauge32 363 MAX-ACCESS read-only 364 STATUS current 365 DESCRIPTION 366 "The number of reservation requests this system 367 is sending upstream for this session." 368 ::= { rsvpSessionEntry 9 } 370 rsvpBadPackets OBJECT-TYPE 371 SYNTAX Gauge32 372 MAX-ACCESS read-only 373 STATUS current 374 DESCRIPTION 375 "This object keeps a count of the number of bad 376 RSVP packets received." 377 ::= { rsvpGenObjects 1 } 379 -- The RSVP Session Sender Database contains the information 380 -- displayed by senders regarding their potential contribution 381 -- to session data content. It is in essence a list of the 382 -- valid PATH messages that the RSVP Router or Host is receiving. 384 rsvpSenderNewIndex OBJECT-TYPE 385 SYNTAX TestAndIncr 386 MAX-ACCESS read-write 387 STATUS current 388 DESCRIPTION 389 "This object is used to assign values to 390 rsvpSenderNumber as described in 'Textual Con- 391 ventions for SNMPv2'. The network manager 392 reads the object, and then writes the value 393 back in the SET that creates a new instance of 394 rsvpSenderEntry. If the SET fails with the 395 code 'inconsistentValue', then the process must 396 be repeated; If the SET succeeds, then the ob- 397 ject is incremented, and the new instance is 398 created according to the manager's directions." 399 ::= { rsvpGenObjects 2 } 401 rsvpSenderTable OBJECT-TYPE 402 SYNTAX SEQUENCE OF RsvpSenderEntry 403 MAX-ACCESS not-accessible 404 STATUS current 405 DESCRIPTION 406 "Information describing the state information 407 displayed by senders in PATH messages." 408 ::= { rsvpObjects 2 } 410 rsvpSenderEntry OBJECT-TYPE 411 SYNTAX RsvpSenderEntry 412 MAX-ACCESS not-accessible 413 STATUS current 414 DESCRIPTION 415 "Information describing the state information 416 displayed by a single sender's PATH message." 417 INDEX { rsvpSessionNumber, rsvpSenderNumber } 418 ::= { rsvpSenderTable 1 } 420 RsvpSenderEntry ::= 421 SEQUENCE { 422 rsvpSenderNumber SessionNumber, 423 rsvpSenderType SessionType, 424 rsvpSenderDestAddr OCTET STRING, 425 rsvpSenderAddr OCTET STRING, 426 rsvpSenderDestAddrLength INTEGER, 427 rsvpSenderAddrLength INTEGER, 428 rsvpSenderProtocol Protocol, 429 rsvpSenderDestPort Port, 430 rsvpSenderPort Port, 431 rsvpSenderFlowId INTEGER, 432 rsvpSenderHopAddr OCTET STRING, 433 rsvpSenderHopLih Integer32, 434 rsvpSenderInterface InterfaceIndex, 435 rsvpSenderTSpecRate BitRate, 436 rsvpSenderTSpecPeakRate BitRate, 437 rsvpSenderTSpecBurst BurstSize, 438 rsvpSenderTSpecMinTU MessageSize, 439 rsvpSenderTSpecMaxTU MessageSize, 440 rsvpSenderInterval RefreshInterval, 441 rsvpSenderRSVPHop TruthValue, 442 rsvpSenderLastChange TimeStamp, 443 rsvpSenderPolicy OCTET STRING, 444 rsvpSenderAdspecBreak TruthValue, 445 rsvpSenderAdspecHopCount INTEGER, 446 rsvpSenderAdspecPathBw BitRate, 447 rsvpSenderAdspecMinLatency Integer32, 448 rsvpSenderAdspecMtu INTEGER, 449 rsvpSenderAdspecGuaranteedSvc TruthValue, 450 rsvpSenderAdspecGuaranteedBreak TruthValue, 451 rsvpSenderAdspecGuaranteedCtot Integer32, 452 rsvpSenderAdspecGuaranteedDtot Integer32, 453 rsvpSenderAdspecGuaranteedCsum Integer32, 454 rsvpSenderAdspecGuaranteedDsum Integer32, 455 rsvpSenderAdspecGuaranteedHopCount INTEGER, 456 rsvpSenderAdspecGuaranteedPathBw BitRate, 457 rsvpSenderAdspecGuaranteedMinLatency Integer32, 458 rsvpSenderAdspecGuaranteedMtu INTEGER, 459 rsvpSenderAdspecCtrlLoadSvc TruthValue, 460 rsvpSenderAdspecCtrlLoadBreak TruthValue, 461 rsvpSenderAdspecCtrlLoadHopCount INTEGER, 462 rsvpSenderAdspecCtrlLoadPathBw BitRate, 463 rsvpSenderAdspecCtrlLoadMinLatency Integer32, 464 rsvpSenderAdspecCtrlLoadMtu INTEGER, 465 rsvpSenderStatus RowStatus, 466 rsvpSenderTTL INTEGER 467 } 469 rsvpSenderNumber OBJECT-TYPE 470 SYNTAX SessionNumber 471 MAX-ACCESS not-accessible 472 STATUS current 473 DESCRIPTION 474 "The number of this sender. This is for SNMP 475 Indexing purposes only and has no relation to 476 any protocol value." 477 ::= { rsvpSenderEntry 1 } 479 rsvpSenderType OBJECT-TYPE 480 SYNTAX SessionType 481 MAX-ACCESS read-create 482 STATUS current 483 DESCRIPTION 484 "The type of session (IP4, IP6, IP6 with flow 485 information, etc)." 486 ::= { rsvpSenderEntry 2 } 488 rsvpSenderDestAddr OBJECT-TYPE 489 SYNTAX OCTET STRING (SIZE(4..16)) 490 MAX-ACCESS read-create 491 STATUS current 492 DESCRIPTION 493 "The destination address used by all senders in 494 this session. This object may not be changed 495 when the value of the RowStatus object is 'ac- 496 tive'." 497 ::= { rsvpSenderEntry 3 } 499 rsvpSenderAddr OBJECT-TYPE 500 SYNTAX OCTET STRING (SIZE(4..16)) 501 MAX-ACCESS read-create 502 STATUS current 503 DESCRIPTION 504 "The source address used by this sender in this 505 session. This object may not be changed when 506 the value of the RowStatus object is 'active'." 507 ::= { rsvpSenderEntry 4 } 509 rsvpSenderDestAddrLength OBJECT-TYPE 510 SYNTAX INTEGER(0..128) 511 MAX-ACCESS read-create 512 STATUS current 513 DESCRIPTION 514 "The length of the destination address in bits. 515 This is the CIDR Prefix Length, which for IP4 516 hosts and multicast addresses is 32 bits. This 517 object may not be changed when the value of the 518 RowStatus object is 'active'." 519 ::= { rsvpSenderEntry 5 } 521 rsvpSenderAddrLength OBJECT-TYPE 522 SYNTAX INTEGER(0..128) 523 MAX-ACCESS read-create 524 STATUS current 525 DESCRIPTION 526 "The length of the sender's address in bits. 527 This is the CIDR Prefix Length, which for IP4 528 hosts and multicast addresses is 32 bits. This 529 object may not be changed when the value of the 530 RowStatus object is 'active'." 531 ::= { rsvpSenderEntry 6 } 533 rsvpSenderProtocol OBJECT-TYPE 534 SYNTAX Protocol 535 MAX-ACCESS read-create 536 STATUS current 537 DESCRIPTION 538 "The IP Protocol used by this session. This 539 object may not be changed when the value of the 540 RowStatus object is 'active'." 541 ::= { rsvpSenderEntry 7 } 543 rsvpSenderDestPort OBJECT-TYPE 544 SYNTAX Port 545 MAX-ACCESS read-create 546 STATUS current 547 DESCRIPTION 548 "The UDP or TCP port number used as a destina- 549 tion port for all senders in this session. If 550 the IP protocol in use, specified by rsvpSen- 551 derProtocol, is 50 (ESP) or 51 (AH), this 552 represents a virtual destination port number. 553 A value of zero indicates that the IP protocol 554 in use does not have ports. This object may 555 not be changed when the value of the RowStatus 556 object is 'active'." 557 ::= { rsvpSenderEntry 8 } 559 rsvpSenderPort OBJECT-TYPE 560 SYNTAX Port 561 MAX-ACCESS read-create 562 STATUS current 563 DESCRIPTION 564 "The UDP or TCP port number used as a source 565 port for this sender in this session. If the 566 IP protocol in use, specified by rsvpSenderPro- 567 tocol is 50 (ESP) or 51 (AH), this represents a 568 generalized port identifier (GPI). A value of 569 zero indicates that the IP protocol in use does 570 not have ports. This object may not be changed 571 when the value of the RowStatus object is 'ac- 572 tive'." 573 ::= { rsvpSenderEntry 9 } 575 rsvpSenderFlowId OBJECT-TYPE 576 SYNTAX INTEGER (0..16777215) 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "The flow ID that this sender is using, if 581 this is an IPv6 session." 582 ::= { rsvpSenderEntry 10 } 584 rsvpSenderHopAddr OBJECT-TYPE 585 SYNTAX OCTET STRING (SIZE(4..16)) 586 MAX-ACCESS read-create 587 STATUS current 588 DESCRIPTION 589 "The address used by the previous RSVP hop 590 (which may be the original sender)." 591 ::= { rsvpSenderEntry 11 } 593 rsvpSenderHopLih OBJECT-TYPE 594 SYNTAX Integer32 595 MAX-ACCESS read-create 596 STATUS current 597 DESCRIPTION 598 "The Logical Interface Handle used by the pre- 599 vious RSVP hop (which may be the original 600 sender)." 601 ::= { rsvpSenderEntry 12 } 603 rsvpSenderInterface OBJECT-TYPE 604 SYNTAX InterfaceIndex 605 MAX-ACCESS read-create 606 STATUS current 607 DESCRIPTION 608 "The ifIndex value of the interface on which 609 this PATH message was most recently received." 610 ::= { rsvpSenderEntry 13 } 612 rsvpSenderTSpecRate OBJECT-TYPE 613 SYNTAX BitRate 614 UNITS "bits per second" 615 MAX-ACCESS read-create 616 STATUS current 617 DESCRIPTION 618 "The Average Bit Rate of the sender's data 619 stream. Within a transmission burst, the ar- 620 rival rate may be as fast as rsvpSenderTSpec- 621 PeakRate (if supported by the service model); 622 however, averaged across two or more burst in- 623 tervals, the rate should not exceed rsvpSen- 624 derTSpecRate. 626 Note that this is a prediction, often based on 627 the general capability of a type of codec or 628 particular encoding; the measured average rate 629 may be significantly lower." 630 ::= { rsvpSenderEntry 14 } 632 rsvpSenderTSpecPeakRate OBJECT-TYPE 633 SYNTAX BitRate 634 UNITS "bits per second" 635 MAX-ACCESS read-create 636 STATUS current 637 DESCRIPTION 638 "The Peak Bit Rate of the sender's data stream. 639 Traffic arrival is not expected to exceed this 640 rate at any time, apart from the effects of 641 jitter in the network. If not specified in the 642 TSpec, this returns zero or noSuchValue." 643 ::= { rsvpSenderEntry 15 } 645 rsvpSenderTSpecBurst OBJECT-TYPE 646 SYNTAX BurstSize 647 UNITS "bytes" 648 MAX-ACCESS read-create 649 STATUS current 650 DESCRIPTION 651 "The size of the largest burst expected from 652 the sender at a time." 653 ::= { rsvpSenderEntry 16 } 655 rsvpSenderTSpecMinTU OBJECT-TYPE 656 SYNTAX MessageSize 657 MAX-ACCESS read-create 658 STATUS current 659 DESCRIPTION 660 "The minimum message size for this flow. The 661 policing algorithm will treat smaller messages 662 as though they are this size." 663 ::= { rsvpSenderEntry 17 } 665 rsvpSenderTSpecMaxTU OBJECT-TYPE 666 SYNTAX MessageSize 667 MAX-ACCESS read-create 668 STATUS current 669 DESCRIPTION 670 "The maximum message size for this flow. The 671 admission algorithm will reject TSpecs whose 672 Maximum Transmission Unit, plus the interface 673 headers, exceed the interface MTU." 674 ::= { rsvpSenderEntry 18 } 676 rsvpSenderInterval OBJECT-TYPE 677 SYNTAX RefreshInterval 678 MAX-ACCESS read-create 679 STATUS current 680 DESCRIPTION 681 "The interval between refresh messages as ad- 682 vertised by the Previous Hop." 683 ::= { rsvpSenderEntry 19 } 685 rsvpSenderRSVPHop OBJECT-TYPE 686 SYNTAX TruthValue 687 MAX-ACCESS read-create 688 STATUS current 689 DESCRIPTION 690 "If TRUE, the node believes that the previous 691 IP hop is an RSVP hop. If FALSE, the node be- 692 lieves that the previous IP hop may not be an 693 RSVP hop." 694 ::= { rsvpSenderEntry 20 } 696 rsvpSenderLastChange OBJECT-TYPE 697 SYNTAX TimeStamp 698 MAX-ACCESS read-only 699 STATUS current 700 DESCRIPTION 701 "The time of the last change in this PATH mes- 702 sage; This is either the first time it was re- 703 ceived or the time of the most recent change in 704 parameters." 705 ::= { rsvpSenderEntry 21 } 707 rsvpSenderPolicy OBJECT-TYPE 708 SYNTAX OCTET STRING (SIZE(4..65536)) 709 MAX-ACCESS read-create 710 STATUS current 711 DESCRIPTION 712 "The contents of the policy object, displayed 713 as an uninterpreted string of octets, including 714 the object header. In the absence of such an 715 object, this should be of zero length." 716 ::= { rsvpSenderEntry 22 } 718 rsvpSenderAdspecBreak OBJECT-TYPE 719 SYNTAX TruthValue 720 MAX-ACCESS read-create 721 STATUS current 722 DESCRIPTION 723 "The global break bit general characterization 724 parameter from the ADSPEC. If TRUE, at least 725 one non-IS hop was detected in the path. If 726 FALSE, no non-IS hops were detected." 727 ::= { rsvpSenderEntry 23 } 729 rsvpSenderAdspecHopCount OBJECT-TYPE 730 SYNTAX INTEGER (0..65535) 731 MAX-ACCESS read-create 732 STATUS current 733 DESCRIPTION 734 "The hop count general characterization parame- 735 ter from the ADSPEC. A return of zero or 736 noSuchValue indicates one of the following con- 737 ditions: 739 the invalid bit was set 740 the parameter was not present" 741 ::= { rsvpSenderEntry 24 } 743 rsvpSenderAdspecPathBw OBJECT-TYPE 744 SYNTAX BitRate 745 UNITS "bits per second" 746 MAX-ACCESS read-create 747 STATUS current 748 DESCRIPTION 749 "The path bandwidth estimate general character- 750 ization 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 rsvpSenderAdspecMinLatency OBJECT-TYPE 759 SYNTAX Integer32 760 UNITS "microseconds" 761 MAX-ACCESS read-create 762 STATUS current 763 DESCRIPTION 764 "The minimum path latency general characteriza- 765 tion parameter from the ADSPEC. A return of 766 zero or noSuchValue indicates one of the fol- 767 lowing conditions: 769 the invalid bit was set 770 the parameter was not present" 771 ::= { rsvpSenderEntry 26 } 773 rsvpSenderAdspecMtu OBJECT-TYPE 774 SYNTAX INTEGER (0..65535) 775 UNITS "bytes" 776 MAX-ACCESS read-create 777 STATUS current 778 DESCRIPTION 779 "The composed Maximum Transmission Unit general 780 characterization parameter from the ADSPEC. A 781 return of zero or noSuchValue indicates one of 782 the following conditions: 784 the invalid bit was set 785 the parameter was not present" 786 ::= { rsvpSenderEntry 27 } 788 rsvpSenderAdspecGuaranteedSvc OBJECT-TYPE 789 SYNTAX TruthValue 790 MAX-ACCESS read-create 791 STATUS current 792 DESCRIPTION 793 "If TRUE, the ADSPEC contains a Guaranteed Ser- 794 vice fragment. If FALSE, the ADSPEC does not 795 contain a Guaranteed Service fragment." 796 ::= { rsvpSenderEntry 28 } 798 rsvpSenderAdspecGuaranteedBreak OBJECT-TYPE 799 SYNTAX TruthValue 800 MAX-ACCESS read-create 801 STATUS current 802 DESCRIPTION 803 "If TRUE, the Guaranteed Service fragment has 804 its 'break' bit set, indicating that one or 805 more nodes along the path do not support the 806 guaranteed service. If FALSE, and rsvpSen- 807 derAdspecGuaranteedSvc is TRUE, the 'break' bit 808 is not set. 810 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 811 returns FALSE or noSuchValue." 812 ::= { rsvpSenderEntry 29 } 814 rsvpSenderAdspecGuaranteedCtot OBJECT-TYPE 815 SYNTAX Integer32 816 UNITS "bytes" 817 MAX-ACCESS read-create 818 STATUS current 819 DESCRIPTION 821 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 822 is the end-to-end composed value for the 823 guaranteed service 'C' parameter. A return of 824 zero or noSuchValue indicates one of the fol- 825 lowing conditions: 827 the invalid bit was set 828 the parameter was not present 830 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 831 returns zero or noSuchValue." 832 ::= { rsvpSenderEntry 30 } 834 rsvpSenderAdspecGuaranteedDtot OBJECT-TYPE 835 SYNTAX Integer32 836 UNITS "microseconds" 837 MAX-ACCESS read-create 838 STATUS current 839 DESCRIPTION 840 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 841 is the end-to-end composed value for the 842 guaranteed service 'D' parameter. A return of 843 zero or noSuchValue indicates one of the fol- 844 lowing conditions: 846 the invalid bit was set 847 the parameter was not present 849 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 850 returns zero or noSuchValue." 851 ::= { rsvpSenderEntry 31 } 853 rsvpSenderAdspecGuaranteedCsum OBJECT-TYPE 854 SYNTAX Integer32 855 UNITS "bytes" 856 MAX-ACCESS read-create 857 STATUS current 858 DESCRIPTION 859 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 860 is the composed value for the guaranteed ser- 861 vice 'C' parameter since the last reshaping 862 point. A return of zero or noSuchValue indi- 863 cates one of the following conditions: 865 the invalid bit was set 866 the parameter was not present 868 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 869 returns zero or noSuchValue." 870 ::= { rsvpSenderEntry 32 } 872 rsvpSenderAdspecGuaranteedDsum OBJECT-TYPE 873 SYNTAX Integer32 874 UNITS "microseconds" 875 MAX-ACCESS read-create 876 STATUS current 877 DESCRIPTION 878 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 879 is the composed value for the guaranteed ser- 880 vice 'D' parameter since the last reshaping 881 point. A return of zero or noSuchValue indi- 882 cates one of the following conditions: 884 the invalid bit was set 885 the parameter was not present 887 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 888 returns zero or noSuchValue." 889 ::= { rsvpSenderEntry 33 } 891 rsvpSenderAdspecGuaranteedHopCount OBJECT-TYPE 892 SYNTAX INTEGER (0..65535) 893 MAX-ACCESS read-create 894 STATUS current 895 DESCRIPTION 897 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 898 is the service-specific override of the hop 899 count general characterization parameter from 900 the ADSPEC. A return of zero or noSuchValue 901 indicates one of the following conditions: 903 the invalid bit was set 904 the parameter was not present 906 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 907 returns zero or noSuchValue." 908 ::= { rsvpSenderEntry 34 } 910 rsvpSenderAdspecGuaranteedPathBw OBJECT-TYPE 911 SYNTAX BitRate 912 UNITS "bits per second" 913 MAX-ACCESS read-create 914 STATUS current 915 DESCRIPTION 916 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 917 is the service-specific override of the path 918 bandwidth estimate general characterization 919 parameter from the ADSPEC. A return of zero or 920 noSuchValue indicates one of the following con- 921 ditions: 923 the invalid bit was set 924 the parameter was not present 926 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 927 returns zero or noSuchValue." 928 ::= { rsvpSenderEntry 35 } 930 rsvpSenderAdspecGuaranteedMinLatency OBJECT-TYPE 931 SYNTAX Integer32 932 UNITS "microseconds" 933 MAX-ACCESS read-create 934 STATUS current 935 DESCRIPTION 936 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 937 is the service-specific override of the minimum 938 path latency general characterization parameter 939 from the ADSPEC. A return of zero or noSuch- 940 Value indicates one of the following condi- 941 tions: 943 the invalid bit was set 944 the parameter was not present 946 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 947 returns zero or noSuchValue." 948 ::= { rsvpSenderEntry 36 } 950 rsvpSenderAdspecGuaranteedMtu OBJECT-TYPE 951 SYNTAX INTEGER (0..65535) 952 UNITS "bytes" 953 MAX-ACCESS read-create 954 STATUS current 955 DESCRIPTION 956 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 957 is the service-specific override of the com- 958 posed Maximum Transmission Unit general charac- 959 terization parameter from the ADSPEC. A return 960 of zero or noSuchValue indicates one of the 961 following conditions: 963 the invalid bit was set 964 the parameter was not present 966 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 967 returns zero or noSuchValue." 968 ::= { rsvpSenderEntry 37 } 970 rsvpSenderAdspecCtrlLoadSvc OBJECT-TYPE 971 SYNTAX TruthValue 972 MAX-ACCESS read-create 973 STATUS current 974 DESCRIPTION 975 "If TRUE, the ADSPEC contains a Controlled Load 976 Service fragment. If FALSE, the ADSPEC does 977 not contain a Controlled Load Service frag- 978 ment." 979 ::= { rsvpSenderEntry 38 } 981 rsvpSenderAdspecCtrlLoadBreak OBJECT-TYPE 982 SYNTAX TruthValue 983 MAX-ACCESS read-create 984 STATUS current 985 DESCRIPTION 986 "If TRUE, the Controlled Load Service fragment 987 has its 'break' bit set, indicating that one or 988 more nodes along the path do not support the 989 controlled load service. If FALSE, and 990 rsvpSenderAdspecCtrlLoadSvc is TRUE, the 991 'break' bit is not set. 993 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 994 returns FALSE or noSuchValue." 995 ::= { rsvpSenderEntry 39 } 997 rsvpSenderAdspecCtrlLoadHopCount OBJECT-TYPE 998 SYNTAX INTEGER (0..65535) 999 MAX-ACCESS read-create 1000 STATUS current 1001 DESCRIPTION 1003 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1004 is the service-specific override of the hop 1005 count general characterization parameter from 1006 the ADSPEC. A return of zero or noSuchValue 1007 indicates one of the following conditions: 1009 the invalid bit was set 1010 the parameter was not present 1012 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1013 returns zero or noSuchValue." 1014 ::= { rsvpSenderEntry 40 } 1016 rsvpSenderAdspecCtrlLoadPathBw OBJECT-TYPE 1017 SYNTAX BitRate 1018 UNITS "bits per second" 1019 MAX-ACCESS read-create 1020 STATUS current 1021 DESCRIPTION 1022 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1023 is the service-specific override of the path 1024 bandwidth estimate general characterization 1025 parameter from the ADSPEC. A return of zero or 1026 noSuchValue indicates one of the following con- 1027 ditions: 1029 the invalid bit was set 1030 the parameter was not present 1032 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1033 returns zero or noSuchValue." 1034 ::= { rsvpSenderEntry 41 } 1036 rsvpSenderAdspecCtrlLoadMinLatency OBJECT-TYPE 1037 SYNTAX Integer32 1038 UNITS "microseconds" 1039 MAX-ACCESS read-create 1040 STATUS current 1041 DESCRIPTION 1042 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1043 is the service-specific override of the minimum 1044 path latency general characterization parameter 1045 from the ADSPEC. A return of zero or noSuch- 1046 Value indicates one of the following condi- 1047 tions: 1049 the invalid bit was set 1050 the parameter was not present 1052 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1053 returns zero or noSuchValue." 1054 ::= { rsvpSenderEntry 42 } 1056 rsvpSenderAdspecCtrlLoadMtu OBJECT-TYPE 1057 SYNTAX INTEGER (0..65535) 1058 UNITS "bytes" 1059 MAX-ACCESS read-create 1060 STATUS current 1061 DESCRIPTION 1062 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1063 is the service-specific override of the com- 1064 posed Maximum Transmission Unit general charac- 1065 terization parameter from the ADSPEC. A return 1066 of zero or noSuchValue indicates one of the 1067 following conditions: 1069 the invalid bit was set 1070 the parameter was not present 1072 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1073 returns zero or noSuchValue." 1074 ::= { rsvpSenderEntry 43 } 1076 rsvpSenderStatus OBJECT-TYPE 1077 SYNTAX RowStatus 1078 MAX-ACCESS read-create 1079 STATUS current 1080 DESCRIPTION 1081 "'active' for all active PATH messages. This 1082 object may be used to install static PATH in- 1083 formation or delete PATH information." 1084 ::= { rsvpSenderEntry 44 } 1086 rsvpSenderTTL OBJECT-TYPE 1087 SYNTAX INTEGER (0..255) 1088 MAX-ACCESS read-only 1089 STATUS current 1090 DESCRIPTION 1091 "The TTL value in the RSVP header that was last 1092 received." 1093 ::= { rsvpSenderEntry 45 } 1095 rsvpSenderOutInterfaceTable OBJECT-TYPE 1096 SYNTAX SEQUENCE OF RsvpSenderOutInterfaceEntry 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "List of outgoing interfaces that PATH messages 1101 use. The ifIndex is the ifIndex value of the 1102 egress interface." 1103 ::= { rsvpObjects 3 } 1105 rsvpSenderOutInterfaceEntry OBJECT-TYPE 1106 SYNTAX RsvpSenderOutInterfaceEntry 1107 MAX-ACCESS not-accessible 1108 STATUS current 1109 DESCRIPTION 1110 "List of outgoing interfaces that a particular 1111 PATH message has." 1112 INDEX { rsvpSessionNumber, rsvpSenderNumber, ifIndex } 1113 ::= { rsvpSenderOutInterfaceTable 1 } 1115 RsvpSenderOutInterfaceEntry ::= 1116 SEQUENCE { 1117 rsvpSenderOutInterfaceStatus RowStatus 1118 } 1120 rsvpSenderOutInterfaceStatus OBJECT-TYPE 1121 SYNTAX RowStatus 1122 MAX-ACCESS read-only 1123 STATUS current 1124 DESCRIPTION 1125 "'active' for all active PATH messages." 1126 ::= { rsvpSenderOutInterfaceEntry 1 } 1128 -- The RSVP Reservation Requests Received Table contains the 1129 -- information displayed by receivers regarding their needs with 1130 -- respect to sessions and senders. It is in essence a list of the 1131 -- valid RESV messages that the RSVP Router or Host is receiving. 1133 rsvpResvNewIndex OBJECT-TYPE 1134 SYNTAX TestAndIncr 1135 MAX-ACCESS read-write 1136 STATUS current 1137 DESCRIPTION 1138 "This object is used to assign values to 1139 rsvpResvNumber as described in 'Textual Conven- 1140 tions for SNMPv2'. The network manager reads 1141 the object, and then writes the value back in 1142 the SET that creates a new instance of 1143 rsvpResvEntry. If the SET fails with the code 1144 'inconsistentValue', then the process must be 1145 repeated; If the SET succeeds, then the object 1146 is incremented, and the new instance is created 1147 according to the manager's directions." 1148 ::= { rsvpGenObjects 3 } 1150 rsvpResvTable OBJECT-TYPE 1151 SYNTAX SEQUENCE OF RsvpResvEntry 1152 MAX-ACCESS not-accessible 1153 STATUS current 1154 DESCRIPTION 1155 "Information describing the state information 1156 displayed by receivers in RESV messages." 1157 ::= { rsvpObjects 4 } 1159 rsvpResvEntry OBJECT-TYPE 1160 SYNTAX RsvpResvEntry 1161 MAX-ACCESS not-accessible 1162 STATUS current 1163 DESCRIPTION 1164 "Information describing the state information 1165 displayed by a single receiver's RESV message 1166 concerning a single sender." 1167 INDEX { rsvpSessionNumber, rsvpResvNumber } 1168 ::= { rsvpResvTable 1 } 1170 RsvpResvEntry ::= 1171 SEQUENCE { 1172 rsvpResvNumber SessionNumber, 1173 rsvpResvType SessionType, 1174 rsvpResvDestAddr OCTET STRING, 1175 rsvpResvSenderAddr OCTET STRING, 1176 rsvpResvDestAddrLength INTEGER, 1177 rsvpResvSenderAddrLength INTEGER, 1178 rsvpResvProtocol Protocol, 1179 rsvpResvDestPort Port, 1180 rsvpResvPort Port, 1181 rsvpResvHopAddr OCTET STRING, 1182 rsvpResvHopLih Integer32, 1183 rsvpResvInterface InterfaceIndex, 1184 rsvpResvService QosService, 1185 rsvpResvTSpecRate BitRate, 1186 rsvpResvTSpecPeakRate BitRate, 1187 rsvpResvTSpecBurst BurstSize, 1188 rsvpResvTSpecMinTU MessageSize, 1189 rsvpResvTSpecMaxTU MessageSize, 1190 rsvpResvRSpecRate BitRate, 1191 rsvpResvRSpecSlack Integer32, 1192 rsvpResvInterval RefreshInterval, 1193 rsvpResvScope OCTET STRING, 1194 rsvpResvShared TruthValue, 1195 rsvpResvExplicit TruthValue, 1196 rsvpResvRSVPHop TruthValue, 1197 rsvpResvLastChange TimeStamp, 1198 rsvpResvPolicy OCTET STRING, 1199 rsvpResvStatus RowStatus, 1200 rsvpResvTTL INTEGER, 1201 rsvpResvFlowId INTEGER 1202 } 1204 rsvpResvNumber OBJECT-TYPE 1205 SYNTAX SessionNumber 1206 MAX-ACCESS not-accessible 1207 STATUS current 1208 DESCRIPTION 1209 "The number of this reservation request. This 1210 is for SNMP Indexing purposes only and has no 1211 relation to any protocol value." 1212 ::= { rsvpResvEntry 1 } 1214 rsvpResvType OBJECT-TYPE 1215 SYNTAX SessionType 1216 MAX-ACCESS read-create 1217 STATUS current 1218 DESCRIPTION 1219 "The type of session (IP4, IP6, IP6 with flow 1220 information, etc)." 1221 ::= { rsvpResvEntry 2 } 1223 rsvpResvDestAddr OBJECT-TYPE 1224 SYNTAX OCTET STRING (SIZE(4..16)) 1225 MAX-ACCESS read-create 1226 STATUS current 1227 DESCRIPTION 1228 "The destination address used by all senders in 1229 this session. This object may not be changed 1230 when the value of the RowStatus object is 'ac- 1231 tive'." 1232 ::= { rsvpResvEntry 3 } 1234 rsvpResvSenderAddr OBJECT-TYPE 1235 SYNTAX OCTET STRING (SIZE(4..16)) 1236 MAX-ACCESS read-create 1237 STATUS current 1238 DESCRIPTION 1239 "The source address of the sender selected by 1240 this reservation. The value of all zeroes in- 1241 dicates 'all senders'. This object may not be 1242 changed when the value of the RowStatus object 1243 is 'active'." 1244 ::= { rsvpResvEntry 4 } 1246 rsvpResvDestAddrLength OBJECT-TYPE 1247 SYNTAX INTEGER(0..128) 1248 MAX-ACCESS read-create 1249 STATUS current 1250 DESCRIPTION 1251 "The length of the destination address in bits. 1252 This is the CIDR Prefix Length, which for IP4 1253 hosts and multicast addresses is 32 bits. This 1254 object may not be changed when the value of the 1255 RowStatus object is 'active'." 1256 ::= { rsvpResvEntry 5 } 1258 rsvpResvSenderAddrLength OBJECT-TYPE 1259 SYNTAX INTEGER(0..128) 1260 MAX-ACCESS read-create 1261 STATUS current 1262 DESCRIPTION 1263 "The length of the sender's address in bits. 1264 This is the CIDR Prefix Length, which for IP4 1265 hosts and multicast addresses is 32 bits. This 1266 object may not be changed when the value of the 1267 RowStatus object is 'active'." 1268 ::= { rsvpResvEntry 6 } 1270 rsvpResvProtocol OBJECT-TYPE 1271 SYNTAX Protocol 1272 MAX-ACCESS read-create 1273 STATUS current 1274 DESCRIPTION 1275 "The IP Protocol used by this session. This 1276 object may not be changed when the value of the 1277 RowStatus object is 'active'." 1278 ::= { rsvpResvEntry 7 } 1280 rsvpResvDestPort 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 destina- 1286 tion port for all senders in this session. If 1287 the IP protocol in use, specified by 1288 rsvpResvProtocol, is 50 (ESP) or 51 (AH), this 1289 represents a virtual destination port number. 1290 A value of zero indicates that the IP protocol 1291 in use does not have ports. This object may 1292 not be changed when the value of the RowStatus 1293 object is 'active'." 1294 ::= { rsvpResvEntry 8 } 1296 rsvpResvPort OBJECT-TYPE 1297 SYNTAX Port 1298 MAX-ACCESS read-create 1299 STATUS current 1300 DESCRIPTION 1301 "The UDP or TCP port number used as a source 1302 port for this sender in this session. If the 1303 IP protocol in use, specified by rsvpResvProto- 1304 col is 50 (ESP) or 51 (AH), this represents a 1305 generalized port identifier (GPI). A value of 1306 zero indicates that the IP protocol in use does 1307 not have ports. This object may not be changed 1308 when the value of the RowStatus object is 'ac- 1309 tive'." 1310 ::= { rsvpResvEntry 9 } 1312 rsvpResvHopAddr OBJECT-TYPE 1313 SYNTAX OCTET STRING (SIZE(4..16)) 1314 MAX-ACCESS read-create 1315 STATUS current 1316 DESCRIPTION 1317 "The address used by the next RSVP hop (which 1318 may be the ultimate receiver)." 1319 ::= { rsvpResvEntry 10 } 1321 rsvpResvHopLih OBJECT-TYPE 1322 SYNTAX Integer32 1323 MAX-ACCESS read-create 1324 STATUS current 1325 DESCRIPTION 1326 "The Logical Interface Handle received from the 1327 previous RSVP hop (which may be the ultimate 1328 receiver)." 1329 ::= { rsvpResvEntry 11 } 1331 rsvpResvInterface OBJECT-TYPE 1332 SYNTAX InterfaceIndex 1333 MAX-ACCESS read-create 1334 STATUS current 1335 DESCRIPTION 1336 "The ifIndex value of the interface on which 1337 this RESV message was most recently received." 1338 ::= { rsvpResvEntry 12 } 1340 rsvpResvService OBJECT-TYPE 1341 SYNTAX QosService 1342 MAX-ACCESS read-create 1343 STATUS current 1344 DESCRIPTION 1345 "The QoS Service classification requested by 1346 the receiver." 1347 ::= { rsvpResvEntry 13 } 1349 rsvpResvTSpecRate OBJECT-TYPE 1350 SYNTAX BitRate 1351 UNITS "bits per second" 1352 MAX-ACCESS read-create 1353 STATUS current 1354 DESCRIPTION 1355 "The Average Bit Rate of the sender's data 1356 stream. Within a transmission burst, the ar- 1357 rival rate may be as fast as rsvpResvTSpec- 1358 PeakRate (if supported by the service model); 1359 however, averaged across two or more burst in- 1360 tervals, the rate should not exceed 1361 rsvpResvTSpecRate. 1363 Note that this is a prediction, often based on 1364 the general capability of a type of codec or 1365 particular encoding; the measured average rate 1366 may be significantly lower." 1367 ::= { rsvpResvEntry 14 } 1369 rsvpResvTSpecPeakRate OBJECT-TYPE 1370 SYNTAX BitRate 1371 UNITS "bits per second" 1372 MAX-ACCESS read-create 1373 STATUS current 1374 DESCRIPTION 1375 "The Peak Bit Rate of the sender's data stream. 1376 Traffic arrival is not expected to exceed this 1377 rate at any time, apart from the effects of 1378 jitter in the network. If not specified in the 1379 TSpec, this returns zero or noSuchValue." 1380 ::= { rsvpResvEntry 15 } 1382 rsvpResvTSpecBurst OBJECT-TYPE 1383 SYNTAX BurstSize 1384 UNITS "bytes" 1385 MAX-ACCESS read-create 1386 STATUS current 1387 DESCRIPTION 1388 "The size of the largest burst expected from 1389 the sender at a time. 1391 If this is less than the sender's advertised 1392 burst size, the receiver is asking the network 1393 to provide flow pacing beyond what would be 1394 provided under normal circumstances. Such pac- 1395 ing is at the network's option." 1396 ::= { rsvpResvEntry 16 } 1398 rsvpResvTSpecMinTU OBJECT-TYPE 1399 SYNTAX MessageSize 1400 MAX-ACCESS read-create 1401 STATUS current 1402 DESCRIPTION 1403 "The minimum message size for this flow. The 1404 policing algorithm will treat smaller messages 1405 as though they are this size." 1406 ::= { rsvpResvEntry 17 } 1408 rsvpResvTSpecMaxTU OBJECT-TYPE 1409 SYNTAX MessageSize 1410 MAX-ACCESS read-create 1411 STATUS current 1412 DESCRIPTION 1413 "The maximum message size for this flow. The 1414 admission algorithm will reject TSpecs whose 1415 Maximum Transmission Unit, plus the interface 1416 headers, exceed the interface MTU." 1417 ::= { rsvpResvEntry 18 } 1419 rsvpResvRSpecRate OBJECT-TYPE 1420 SYNTAX BitRate 1421 UNITS "bits per second" 1422 MAX-ACCESS read-create 1423 STATUS current 1424 DESCRIPTION 1425 "If the requested service is Guaranteed, as 1426 specified by rsvpResvService, this is the 1427 clearing rate that is being requested. Other- 1428 wise, it is zero, or the agent may return 1429 noSuchValue." 1430 ::= { rsvpResvEntry 19 } 1432 rsvpResvRSpecSlack OBJECT-TYPE 1433 SYNTAX Integer32 1434 UNITS "microseconds" 1435 MAX-ACCESS read-create 1436 STATUS current 1437 DESCRIPTION 1438 "If the requested service is Guaranteed, as 1439 specified by rsvpResvService, this is the delay 1440 slack. Otherwise, it is zero, or the agent may 1441 return noSuchValue." 1442 ::= { rsvpResvEntry 20 } 1444 rsvpResvInterval OBJECT-TYPE 1445 SYNTAX RefreshInterval 1446 MAX-ACCESS read-create 1447 STATUS current 1448 DESCRIPTION 1449 "The interval between refresh messages as ad- 1450 vertised by the Next Hop." 1451 ::= { rsvpResvEntry 21 } 1453 rsvpResvScope OBJECT-TYPE 1454 SYNTAX OCTET STRING (SIZE(0..65536)) 1455 MAX-ACCESS read-create 1456 STATUS current 1457 DESCRIPTION 1459 "The contents of the scope object, displayed as 1460 an uninterpreted string of octets, including 1461 the object header. In the absence of such an 1462 object, this should be of zero length. 1464 If the length is non-zero, this contains a 1465 series of IP4 or IP6 addresses." 1466 ::= { rsvpResvEntry 22 } 1468 rsvpResvShared OBJECT-TYPE 1469 SYNTAX TruthValue 1470 MAX-ACCESS read-create 1471 STATUS current 1472 DESCRIPTION 1473 "If TRUE, a reservation shared among senders is 1474 requested. If FALSE, a reservation specific to 1475 this sender is requested." 1476 ::= { rsvpResvEntry 23 } 1478 rsvpResvExplicit OBJECT-TYPE 1479 SYNTAX TruthValue 1480 MAX-ACCESS read-create 1481 STATUS current 1482 DESCRIPTION 1483 "If TRUE, individual senders are listed using 1484 Filter Specifications. If FALSE, all senders 1485 are implicitly selected. The Scope Object will 1486 contain a list of senders that need to receive 1487 this reservation request for the purpose of 1488 routing the RESV message." 1489 ::= { rsvpResvEntry 24 } 1491 rsvpResvRSVPHop OBJECT-TYPE 1492 SYNTAX TruthValue 1493 MAX-ACCESS read-create 1494 STATUS current 1495 DESCRIPTION 1496 "If TRUE, the node believes that the previous 1497 IP hop is an RSVP hop. If FALSE, the node be- 1498 lieves that the previous IP hop may not be an 1499 RSVP hop." 1500 ::= { rsvpResvEntry 25 } 1502 rsvpResvLastChange OBJECT-TYPE 1503 SYNTAX TimeStamp 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "The time of the last change in this reserva- 1508 tion request; This is either the first time it 1509 was received or the time of the most recent 1510 change in parameters." 1511 ::= { rsvpResvEntry 26 } 1513 rsvpResvPolicy OBJECT-TYPE 1514 SYNTAX OCTET STRING (SIZE(0..65536)) 1515 MAX-ACCESS read-create 1516 STATUS current 1517 DESCRIPTION 1518 "The contents of the policy object, displayed 1519 as an uninterpreted string of octets, including 1520 the object header. In the absence of such an 1521 object, this should be of zero length." 1522 ::= { rsvpResvEntry 27 } 1524 rsvpResvStatus OBJECT-TYPE 1525 SYNTAX RowStatus 1526 MAX-ACCESS read-create 1527 STATUS current 1528 DESCRIPTION 1529 "'active' for all active RESV messages. This 1530 object may be used to install static RESV in- 1531 formation or delete RESV information." 1532 ::= { rsvpResvEntry 28 } 1534 rsvpResvTTL OBJECT-TYPE 1535 SYNTAX INTEGER (0..255) 1536 MAX-ACCESS read-only 1537 STATUS current 1538 DESCRIPTION 1539 "The TTL value in the RSVP header that was last 1540 received." 1541 ::= { rsvpResvEntry 29 } 1543 rsvpResvFlowId OBJECT-TYPE 1544 SYNTAX INTEGER (0..16777215) 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "The flow ID that this receiver is using, if 1549 this is an IPv6 session." 1550 ::= { rsvpResvEntry 30 } 1552 -- The RSVP Reservation Requests Forwarded Table contains the 1553 -- information displayed by receivers regarding their needs with 1554 -- respect to sessions and senders. It is in essence a list of the 1555 -- valid RESV messages that the RSVP Router or Host is sending 1556 -- to its upstream neighbors. 1558 rsvpResvFwdNewIndex OBJECT-TYPE 1559 SYNTAX TestAndIncr 1560 MAX-ACCESS read-write 1561 STATUS current 1562 DESCRIPTION 1563 "This object is used to assign values to 1564 rsvpResvFwdNumber as described in 'Textual Con- 1565 ventions for SNMPv2'. The network manager 1566 reads the object, and then writes the value 1567 back in the SET that creates a new instance of 1568 rsvpResvFwdEntry. If the SET fails with the 1569 code 'inconsistentValue', then the process must 1570 be repeated; If the SET succeeds, then the ob- 1571 ject is incremented, and the new instance is 1572 created according to the manager's directions." 1573 ::= { rsvpGenObjects 4 } 1575 rsvpResvFwdTable OBJECT-TYPE 1576 SYNTAX SEQUENCE OF RsvpResvFwdEntry 1577 MAX-ACCESS not-accessible 1578 STATUS current 1579 DESCRIPTION 1580 "Information describing the state information 1581 displayed upstream in RESV messages." 1582 ::= { rsvpObjects 5 } 1584 rsvpResvFwdEntry OBJECT-TYPE 1585 SYNTAX RsvpResvFwdEntry 1586 MAX-ACCESS not-accessible 1587 STATUS current 1588 DESCRIPTION 1589 "Information describing the state information 1590 displayed upstream in an RESV message concern- 1591 ing a single sender." 1592 INDEX { rsvpSessionNumber, rsvpResvFwdNumber } 1593 ::= { rsvpResvFwdTable 1 } 1595 RsvpResvFwdEntry ::= 1596 SEQUENCE { 1597 rsvpResvFwdNumber SessionNumber, 1598 rsvpResvFwdType SessionType, 1599 rsvpResvFwdDestAddr OCTET STRING, 1600 rsvpResvFwdSenderAddr OCTET STRING, 1601 rsvpResvFwdDestAddrLength INTEGER, 1602 rsvpResvFwdSenderAddrLength INTEGER, 1603 rsvpResvFwdProtocol Protocol, 1604 rsvpResvFwdDestPort Port, 1605 rsvpResvFwdPort Port, 1606 rsvpResvFwdHopAddr OCTET STRING, 1607 rsvpResvFwdHopLih Integer32, 1608 rsvpResvFwdInterface InterfaceIndex, 1609 rsvpResvFwdService QosService, 1610 rsvpResvFwdTSpecRate BitRate, 1611 rsvpResvFwdTSpecPeakRate BitRate, 1612 rsvpResvFwdTSpecBurst BurstSize, 1613 rsvpResvFwdTSpecMinTU MessageSize, 1614 rsvpResvFwdTSpecMaxTU MessageSize, 1615 rsvpResvFwdRSpecRate BitRate, 1616 rsvpResvFwdRSpecSlack Integer32, 1617 rsvpResvFwdInterval RefreshInterval, 1618 rsvpResvFwdScope OCTET STRING, 1619 rsvpResvFwdShared TruthValue, 1620 rsvpResvFwdExplicit TruthValue, 1621 rsvpResvFwdRSVPHop TruthValue, 1622 rsvpResvFwdLastChange TimeStamp, 1623 rsvpResvFwdPolicy OCTET STRING, 1624 rsvpResvFwdStatus RowStatus, 1625 rsvpResvFwdTTL INTEGER, 1626 rsvpResvFwdFlowId INTEGER 1627 } 1629 rsvpResvFwdNumber OBJECT-TYPE 1630 SYNTAX SessionNumber 1631 MAX-ACCESS not-accessible 1632 STATUS current 1633 DESCRIPTION 1634 "The number of this reservation request. This 1635 is for SNMP Indexing purposes only and has no 1636 relation to any protocol value." 1637 ::= { rsvpResvFwdEntry 1 } 1639 rsvpResvFwdType OBJECT-TYPE 1640 SYNTAX SessionType 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "The type of session (IP4, IP6, IP6 with flow 1645 information, etc)." 1646 ::= { rsvpResvFwdEntry 2 } 1648 rsvpResvFwdDestAddr OBJECT-TYPE 1649 SYNTAX OCTET STRING (SIZE(4..16)) 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 "The destination address used by all senders in 1654 this session. This object may not be changed 1655 when the value of the RowStatus object is 'ac- 1656 tive'." 1657 ::= { rsvpResvFwdEntry 3 } 1659 rsvpResvFwdSenderAddr OBJECT-TYPE 1660 SYNTAX OCTET STRING (SIZE(4..16)) 1661 MAX-ACCESS read-only 1662 STATUS current 1663 DESCRIPTION 1664 "The source address of the sender selected by 1665 this reservation. The value of all zeroes in- 1666 dicates 'all senders'. This object may not be 1667 changed when the value of the RowStatus object 1668 is 'active'." 1669 ::= { rsvpResvFwdEntry 4 } 1671 rsvpResvFwdDestAddrLength OBJECT-TYPE 1672 SYNTAX INTEGER(0..128) 1673 MAX-ACCESS read-only 1674 STATUS current 1675 DESCRIPTION 1676 "The length of the destination address in bits. 1677 This is the CIDR Prefix Length, which for IP4 1678 hosts and multicast addresses is 32 bits. This 1679 object may not be changed when the value of the 1680 RowStatus object is 'active'." 1681 ::= { rsvpResvFwdEntry 5 } 1683 rsvpResvFwdSenderAddrLength OBJECT-TYPE 1684 SYNTAX INTEGER(0..128) 1685 MAX-ACCESS read-only 1686 STATUS current 1687 DESCRIPTION 1688 "The length of the sender's address in bits. 1689 This is the CIDR Prefix Length, which for IP4 1690 hosts and multicast addresses is 32 bits. This 1691 object may not be changed when the value of the 1692 RowStatus object is 'active'." 1693 ::= { rsvpResvFwdEntry 6 } 1695 rsvpResvFwdProtocol OBJECT-TYPE 1696 SYNTAX Protocol 1697 MAX-ACCESS read-only 1698 STATUS current 1699 DESCRIPTION 1700 "The IP Protocol used by a session. for secure 1701 sessions, this indicates IP Security. This ob- 1702 ject may not be changed when the value of the 1703 RowStatus object is 'active'." 1704 ::= { rsvpResvFwdEntry 7 } 1706 rsvpResvFwdDestPort OBJECT-TYPE 1707 SYNTAX Port 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "The UDP or TCP port number used as a destina- 1712 tion port for all senders in this session. If 1713 the IP protocol in use, specified by 1714 rsvpResvFwdProtocol, is 50 (ESP) or 51 (AH), 1715 this represents a virtual destination port 1716 number. A value of zero indicates that the IP 1717 protocol in use does not have ports. This ob- 1718 ject may not be changed when the value of the 1719 RowStatus object is 'active'." 1720 ::= { rsvpResvFwdEntry 8 } 1722 rsvpResvFwdPort OBJECT-TYPE 1723 SYNTAX Port 1724 MAX-ACCESS read-only 1725 STATUS current 1726 DESCRIPTION 1727 "The UDP or TCP port number used as a source 1728 port for this sender in this session. If the 1729 IP protocol in use, specified by 1730 rsvpResvFwdProtocol is 50 (ESP) or 51 (AH), 1731 this represents a generalized port identifier 1732 (GPI). A value of zero indicates that the IP 1733 protocol in use does not have ports. This ob- 1734 ject may not be changed when the value of the 1735 RowStatus object is 'active'." 1736 ::= { rsvpResvFwdEntry 9 } 1738 rsvpResvFwdHopAddr OBJECT-TYPE 1739 SYNTAX OCTET STRING (SIZE(4..16)) 1740 MAX-ACCESS read-only 1741 STATUS current 1742 DESCRIPTION 1743 "The address of the (previous) RSVP that will 1744 receive this message." 1745 ::= { rsvpResvFwdEntry 10 } 1747 rsvpResvFwdHopLih OBJECT-TYPE 1748 SYNTAX Integer32 1749 MAX-ACCESS read-only 1750 STATUS current 1751 DESCRIPTION 1752 "The Logical Interface Handle sent to the (pre- 1753 vious) RSVP that will receive this message." 1754 ::= { rsvpResvFwdEntry 11 } 1756 rsvpResvFwdInterface OBJECT-TYPE 1757 SYNTAX InterfaceIndex 1758 MAX-ACCESS read-only 1759 STATUS current 1760 DESCRIPTION 1761 "The ifIndex value of the interface on which 1762 this RESV message was most recently sent." 1763 ::= { rsvpResvFwdEntry 12 } 1765 rsvpResvFwdService OBJECT-TYPE 1766 SYNTAX QosService 1767 MAX-ACCESS read-only 1768 STATUS current 1769 DESCRIPTION 1770 "The QoS Service classification requested." 1771 ::= { rsvpResvFwdEntry 13 } 1773 rsvpResvFwdTSpecRate OBJECT-TYPE 1774 SYNTAX BitRate 1775 UNITS "bits per second" 1776 MAX-ACCESS read-only 1777 STATUS current 1778 DESCRIPTION 1779 "The Average Bit Rate of the sender's data 1780 stream. Within a transmission burst, the ar- 1781 rival rate may be as fast as rsvpResvFwdTSpec- 1782 PeakRate (if supported by the service model); 1783 however, averaged across two or more burst in- 1784 tervals, the rate should not exceed 1785 rsvpResvFwdTSpecRate. 1787 Note that this is a prediction, often based on 1788 the general capability of a type of codec or 1789 particular encoding; the measured average rate 1790 may be significantly lower." 1791 ::= { rsvpResvFwdEntry 14 } 1793 rsvpResvFwdTSpecPeakRate OBJECT-TYPE 1794 SYNTAX BitRate 1795 UNITS "bits per second" 1796 MAX-ACCESS read-only 1797 STATUS current 1798 DESCRIPTION 1799 "The Peak Bit Rate of the sender's data stream 1800 Traffic arrival is not expected to exceed this 1801 rate at any time, apart from the effects of 1802 jitter in the network. If not specified in the 1803 TSpec, this returns zero or noSuchValue." 1804 ::= { rsvpResvFwdEntry 15 } 1806 rsvpResvFwdTSpecBurst OBJECT-TYPE 1807 SYNTAX BurstSize 1808 UNITS "bytes" 1809 MAX-ACCESS read-only 1810 STATUS current 1811 DESCRIPTION 1812 "The size of the largest burst expected from 1813 the sender at a time. 1815 If this is less than the sender's advertised 1816 burst size, the receiver is asking the network 1817 to provide flow pacing beyond what would be 1818 provided under normal circumstances. Such pac- 1819 ing is at the network's option." 1820 ::= { rsvpResvFwdEntry 16 } 1822 rsvpResvFwdTSpecMinTU OBJECT-TYPE 1823 SYNTAX MessageSize 1824 MAX-ACCESS read-only 1825 STATUS current 1826 DESCRIPTION 1827 "The minimum message size for this flow. The 1828 policing algorithm will treat smaller messages 1829 as though they are this size." 1830 ::= { rsvpResvFwdEntry 17 } 1832 rsvpResvFwdTSpecMaxTU OBJECT-TYPE 1833 SYNTAX MessageSize 1834 MAX-ACCESS read-only 1835 STATUS current 1836 DESCRIPTION 1837 "The maximum message size for this flow. The 1838 admission algorithm will reject TSpecs whose 1839 Maximum Transmission Unit, plus the interface 1840 headers, exceed the interface MTU." 1841 ::= { rsvpResvFwdEntry 18 } 1843 rsvpResvFwdRSpecRate OBJECT-TYPE 1844 SYNTAX BitRate 1845 UNITS "bytes per second" 1846 MAX-ACCESS read-only 1847 STATUS current 1848 DESCRIPTION 1849 "If the requested service is Guaranteed, as 1850 specified by rsvpResvService, this is the 1851 clearing rate that is being requested. Other- 1852 wise, it is zero, or the agent may return 1853 noSuchValue." 1854 ::= { rsvpResvFwdEntry 19 } 1856 rsvpResvFwdRSpecSlack OBJECT-TYPE 1857 SYNTAX Integer32 1858 UNITS "microseconds" 1859 MAX-ACCESS read-only 1860 STATUS current 1861 DESCRIPTION 1862 "If the requested service is Guaranteed, as 1863 specified by rsvpResvService, this is the delay 1864 slack. Otherwise, it is zero, or the agent may 1865 return noSuchValue." 1866 ::= { rsvpResvFwdEntry 20 } 1868 rsvpResvFwdInterval OBJECT-TYPE 1869 SYNTAX RefreshInterval 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "The interval between refresh messages adver- 1874 tised to the Previous Hop." 1875 ::= { rsvpResvFwdEntry 21 } 1877 rsvpResvFwdScope OBJECT-TYPE 1878 SYNTAX OCTET STRING (SIZE(0..65536)) 1879 MAX-ACCESS read-only 1880 STATUS current 1881 DESCRIPTION 1882 "The contents of the scope object, displayed as 1883 an uninterpreted string of octets, including 1884 the object header. In the absence of such an 1885 object, this should be of zero length." 1886 ::= { rsvpResvFwdEntry 22 } 1888 rsvpResvFwdShared OBJECT-TYPE 1889 SYNTAX TruthValue 1890 MAX-ACCESS read-only 1891 STATUS current 1892 DESCRIPTION 1893 "If TRUE, a reservation shared among senders is 1894 requested. If FALSE, a reservation specific to 1895 this sender is requested." 1896 ::= { rsvpResvFwdEntry 23 } 1898 rsvpResvFwdExplicit OBJECT-TYPE 1899 SYNTAX TruthValue 1900 MAX-ACCESS read-only 1901 STATUS current 1902 DESCRIPTION 1903 "If TRUE, individual senders are listed using 1904 Filter Specifications. If FALSE, all senders 1905 are implicitly selected. The Scope Object will 1906 contain a list of senders that need to receive 1907 this reservation request for the purpose of 1908 routing the RESV message." 1909 ::= { rsvpResvFwdEntry 24 } 1911 rsvpResvFwdRSVPHop OBJECT-TYPE 1912 SYNTAX TruthValue 1913 MAX-ACCESS read-only 1914 STATUS current 1915 DESCRIPTION 1916 "If TRUE, the node believes that the next IP 1917 hop is an RSVP hop. If FALSE, the node be- 1918 lieves that the next IP hop may not be an RSVP 1919 hop." 1920 ::= { rsvpResvFwdEntry 25 } 1922 rsvpResvFwdLastChange OBJECT-TYPE 1923 SYNTAX TimeStamp 1924 MAX-ACCESS read-only 1925 STATUS current 1926 DESCRIPTION 1927 "The time of the last change in this request; 1928 This is either the first time it was sent or 1929 the time of the most recent change in parame- 1930 ters." 1931 ::= { rsvpResvFwdEntry 26 } 1933 rsvpResvFwdPolicy OBJECT-TYPE 1934 SYNTAX OCTET STRING (SIZE(0..65536)) 1935 MAX-ACCESS read-only 1936 STATUS current 1937 DESCRIPTION 1938 "The contents of the policy object, displayed 1939 as an uninterpreted string of octets, including 1940 the object header. In the absence of such an 1941 object, this should be of zero length." 1942 ::= { rsvpResvFwdEntry 27 } 1944 rsvpResvFwdStatus OBJECT-TYPE 1945 SYNTAX RowStatus 1946 MAX-ACCESS read-write 1947 STATUS current 1948 DESCRIPTION 1949 "'active' for all active RESV messages. This 1950 object may be used to delete RESV information." 1951 ::= { rsvpResvFwdEntry 28 } 1953 rsvpResvFwdTTL OBJECT-TYPE 1954 SYNTAX INTEGER (0..255) 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 "The TTL value in the RSVP header that was last 1959 received." 1960 ::= { rsvpResvFwdEntry 29 } 1962 rsvpResvFwdFlowId OBJECT-TYPE 1963 SYNTAX INTEGER (0..16777215) 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "The flow ID that this receiver is using, if 1968 this is an IPv6 session." 1969 ::= { rsvpResvFwdEntry 30 } 1971 -- The RSVP Interface Attributes Database contains the 1972 -- RSVP-specific information for an interface. Information 1973 -- that is shared with other reservation procedures such 1974 -- as ST-II is in the Integrated Interface Attributes 1975 -- Database. 1977 rsvpIfTable OBJECT-TYPE 1978 SYNTAX SEQUENCE OF RsvpIfEntry 1979 MAX-ACCESS not-accessible 1980 STATUS current 1981 DESCRIPTION 1982 "The RSVP-specific attributes of the system's 1983 interfaces." 1984 ::= { rsvpObjects 6 } 1986 rsvpIfEntry OBJECT-TYPE 1987 SYNTAX RsvpIfEntry 1988 MAX-ACCESS not-accessible 1989 STATUS current 1990 DESCRIPTION 1991 "The RSVP-specific attributes of the a given 1992 interface." 1993 INDEX { ifIndex } 1994 ::= { rsvpIfTable 1 } 1996 RsvpIfEntry ::= 1997 SEQUENCE { 1998 rsvpIfUdpNbrs Gauge32, 1999 rsvpIfIpNbrs Gauge32, 2000 rsvpIfNbrs Gauge32, 2001 rsvpIfEnabled TruthValue, 2002 rsvpIfUdpRequired TruthValue, 2003 rsvpIfRefreshBlockadeMultiple INTEGER, 2004 rsvpIfRefreshMultiple INTEGER, 2005 rsvpIfTTL INTEGER, 2006 rsvpIfRefreshInterval TimeInterval, 2007 rsvpIfRouteDelay TimeInterval, 2008 rsvpIfStatus RowStatus 2009 } 2010 rsvpIfUdpNbrs OBJECT-TYPE 2011 SYNTAX Gauge32 2012 MAX-ACCESS read-only 2013 STATUS current 2014 DESCRIPTION 2015 "The number of neighbors perceived to be using 2016 only the RSVP UDP Encapsulation." 2017 ::= { rsvpIfEntry 1 } 2019 rsvpIfIpNbrs OBJECT-TYPE 2020 SYNTAX Gauge32 2021 MAX-ACCESS read-only 2022 STATUS current 2023 DESCRIPTION 2024 "The number of neighbors perceived to be using 2025 only the RSVP IP Encapsulation." 2026 ::= { rsvpIfEntry 2 } 2028 rsvpIfNbrs OBJECT-TYPE 2029 SYNTAX Gauge32 2030 MAX-ACCESS read-only 2031 STATUS current 2032 DESCRIPTION 2033 "The number of neighbors currently perceived; 2034 this will exceed rsvpIfIpNbrs + rsvpIfUdpNbrs 2035 by the number of neighbors using both encapsu- 2036 lations." 2037 ::= { rsvpIfEntry 3 } 2039 rsvpIfRefreshBlockadeMultiple OBJECT-TYPE 2040 SYNTAX INTEGER (1..65536) 2041 MAX-ACCESS read-create 2042 STATUS current 2043 DESCRIPTION 2044 "The value of the RSVP value 'Kb', Which is the 2045 minimum number of refresh intervals that 2046 blockade state will last once entered." 2047 DEFVAL { 4 } 2048 ::= { rsvpIfEntry 4 } 2050 rsvpIfRefreshMultiple OBJECT-TYPE 2051 SYNTAX INTEGER (1..65536) 2052 MAX-ACCESS read-create 2053 STATUS current 2054 DESCRIPTION 2055 "The value of the RSVP value 'K', which is the 2056 number of refresh intervals which must elapse 2057 (minimum) before a PATH or RESV message which 2058 is not being refreshed will be aged out." 2059 DEFVAL { 3 } 2060 ::= { rsvpIfEntry 5 } 2062 rsvpIfTTL OBJECT-TYPE 2063 SYNTAX INTEGER (0..255) 2064 MAX-ACCESS read-create 2065 STATUS current 2066 DESCRIPTION 2067 "The value of SEND_TTL used on this interface 2068 for messages this node originates. If set to 2069 zero, the node determines the TTL via other 2070 means." 2071 DEFVAL { 0 } -- which is to say, no override 2072 ::= { rsvpIfEntry 6 } 2074 rsvpIfRefreshInterval OBJECT-TYPE 2075 SYNTAX TimeInterval 2076 UNITS "milliseconds" 2077 MAX-ACCESS read-create 2078 STATUS current 2079 DESCRIPTION 2080 "The value of the RSVP value 'R', which is the 2081 minimum period between refresh transmissions of 2082 a given PATH or RESV message on an interface." 2083 DEFVAL { 3000 } -- 30 seconds 2084 ::= { rsvpIfEntry 7 } 2086 rsvpIfRouteDelay OBJECT-TYPE 2087 SYNTAX TimeInterval 2088 UNITS "hundredths of a second" 2089 MAX-ACCESS read-create 2090 STATUS current 2091 DESCRIPTION 2092 "The approximate period from the time a route 2093 is changed to the time a resulting message ap- 2094 pears on the interface." 2095 DEFVAL { 200 } -- 2 seconds 2096 ::= { rsvpIfEntry 8 } 2098 rsvpIfEnabled OBJECT-TYPE 2099 SYNTAX TruthValue 2100 MAX-ACCESS read-create 2101 STATUS current 2102 DESCRIPTION 2103 "If TRUE, RSVP is enabled on this Interface. 2104 If FALSE, RSVP is not enabled on this inter- 2105 face." 2106 ::= { rsvpIfEntry 9 } 2108 rsvpIfUdpRequired OBJECT-TYPE 2109 SYNTAX TruthValue 2110 MAX-ACCESS read-create 2111 STATUS current 2112 DESCRIPTION 2113 "If TRUE, manual configuration forces the use 2114 of UDP encapsulation on the interface. If 2115 FALSE, UDP encapsulation is only used if rsvpI- 2116 fUdpNbrs is not zero." 2118 ::= { rsvpIfEntry 10 } 2120 rsvpIfStatus OBJECT-TYPE 2121 SYNTAX RowStatus 2122 MAX-ACCESS read-create 2123 STATUS current 2124 DESCRIPTION 2125 "'active' on interfaces that are configured for 2126 RSVP." 2127 ::= { rsvpIfEntry 11 } 2129 -- The RSVP Neighbor Database lists the neighbors the RSVP 2130 -- process currently is receiving messages from. 2132 rsvpNbrTable OBJECT-TYPE 2133 SYNTAX SEQUENCE OF RsvpNbrEntry 2134 MAX-ACCESS not-accessible 2135 STATUS current 2136 DESCRIPTION 2137 "Information describing the Neighbors of an 2138 RSVP system." 2139 ::= { rsvpObjects 7 } 2141 rsvpNbrEntry OBJECT-TYPE 2142 SYNTAX RsvpNbrEntry 2143 MAX-ACCESS not-accessible 2144 STATUS current 2145 DESCRIPTION 2146 "Information describing a single RSVP Neigh- 2147 bor." 2148 INDEX { ifIndex, rsvpNbrAddress } 2149 ::= { rsvpNbrTable 1 } 2151 RsvpNbrEntry ::= 2152 SEQUENCE { 2153 rsvpNbrAddress OCTET STRING, 2154 rsvpNbrProtocol RsvpEncapsulation, 2155 rsvpNbrStatus RowStatus 2156 } 2158 rsvpNbrAddress OBJECT-TYPE 2159 SYNTAX OCTET STRING (SIZE(4..16)) 2160 MAX-ACCESS not-accessible 2161 STATUS current 2162 DESCRIPTION 2163 "The IP4 or IP6 Address used by this neighbor. 2164 This object may not be changed when the value 2165 of the RowStatus object is 'active'." 2166 ::= { rsvpNbrEntry 1 } 2168 rsvpNbrProtocol OBJECT-TYPE 2169 SYNTAX RsvpEncapsulation 2170 MAX-ACCESS read-create 2171 STATUS current 2172 DESCRIPTION 2173 "The encapsulation being used by this neigh- 2174 bor." 2175 ::= { rsvpNbrEntry 2 } 2177 rsvpNbrStatus OBJECT-TYPE 2178 SYNTAX RowStatus 2179 MAX-ACCESS read-create 2180 STATUS current 2181 DESCRIPTION 2182 "'active' for all neighbors. This object may 2183 be used to configure neighbors. In the pres- 2184 ence of configured neighbors, the implementa- 2185 tion may (but is not required to) limit the set 2186 of valid neighbors to those configured." 2187 ::= { rsvpNbrEntry 3 } 2189 -- 2190 -- Notifications used to signal events 2191 -- 2193 rsvpNotifications OBJECT IDENTIFIER ::= { rsvpNotificationsPrefix 0 } 2195 newFlow NOTIFICATION-TYPE 2196 OBJECTS { 2197 intSrvFlowStatus, rsvpSessionDestAddr, 2198 rsvpResvFwdStatus, rsvpResvStatus, rsvpSenderStatus 2199 } 2200 STATUS current 2201 DESCRIPTION 2202 "The newFlow trap indicates that the originat- 2203 ing system has installed a new flow in its 2204 classifier, or (when reservation authorization 2205 is in view) is prepared to install such a flow 2206 in the classifier and is requesting authoriza- 2207 tion. The objects included with the Notifica- 2208 tion may be used to read further information 2209 using the Integrated Services and RSVP MIBs. 2210 Authorization or non-authorization may be 2211 enacted by a write to the variable intSrvFlowS- 2212 tatus." 2213 ::= { rsvpNotifications 1 } 2215 lostFlow NOTIFICATION-TYPE 2216 OBJECTS { 2217 intSrvFlowStatus, rsvpSessionDestAddr, 2218 rsvpResvFwdStatus, rsvpResvStatus, rsvpSenderStatus 2219 } 2220 STATUS current 2221 DESCRIPTION 2222 "The lostFlow trap indicates that the originat- 2223 ing system has removed a flow from its classif- 2224 ier." 2225 ::= { rsvpNotifications 2 } 2227 -- conformance information 2229 rsvpGroups OBJECT IDENTIFIER ::= { rsvpConformance 1 } 2230 rsvpCompliances OBJECT IDENTIFIER ::= { rsvpConformance 2 } 2232 -- compliance statements 2233 rsvpCompliance MODULE-COMPLIANCE 2234 STATUS current 2235 DESCRIPTION 2236 "The compliance statement. Note that the im- 2237 plementation of this module requires implemen- 2238 tation of the Integrated Services MIB as well." 2239 MODULE -- this module 2240 MANDATORY-GROUPS { 2241 rsvpSessionGroup, rsvpSenderGroup, rsvpResvGroup, 2242 rsvpIfGroup, rsvpNbrGroup, 2243 rsvpGenObjectsGroup, rsvpSenderOutInterfaceGroup 2244 } 2246 GROUP rsvpResvFwdGroup 2247 DESCRIPTION 2248 "The Reservation Requests table is appropriate 2249 in implementations that store upstream reserva- 2250 tion messages, but not appropriate in implemen- 2251 tations which calculate them on each transmis- 2252 sion." 2254 GROUP rsvpNotificationGroup 2255 DESCRIPTION 2256 "The notifications in this module may be used to 2257 advise a network management station of changes in 2258 flow status, and are required when this use is in 2259 view." 2261 OBJECT rsvpSessionRequests 2262 MIN-ACCESS not-accessible 2263 DESCRIPTION 2264 "This object is optional." 2266 OBJECT rsvpSenderType 2267 MIN-ACCESS read-only 2268 DESCRIPTION 2269 "read-create access is not required. This may be 2270 read-only." 2272 OBJECT rsvpSenderDestAddr 2273 MIN-ACCESS read-only 2274 DESCRIPTION 2275 "read-create access is not required. This may be 2276 read-only." 2278 OBJECT rsvpSenderAddr 2279 MIN-ACCESS read-only 2280 DESCRIPTION 2281 "read-create access is not required. This may be 2282 read-only." 2284 OBJECT rsvpSenderDestAddrLength 2285 MIN-ACCESS read-only 2286 DESCRIPTION 2287 "read-create access is not required. This may be 2288 read-only." 2290 OBJECT rsvpSenderAddrLength 2291 MIN-ACCESS read-only 2292 DESCRIPTION 2293 "read-create access is not required. This may be 2294 read-only." 2296 OBJECT rsvpSenderProtocol 2297 MIN-ACCESS read-only 2298 DESCRIPTION 2299 "read-create access is not required. This may be 2300 read-only." 2302 OBJECT rsvpSenderDestPort 2303 MIN-ACCESS read-only 2304 DESCRIPTION 2305 "read-create access is not required. This may be 2306 read-only." 2308 OBJECT rsvpSenderPort 2309 MIN-ACCESS read-only 2310 DESCRIPTION 2311 "read-create access is not required. This may be 2312 read-only." 2314 OBJECT rsvpSenderHopAddr 2315 MIN-ACCESS read-only 2316 DESCRIPTION 2317 "read-create access is not required. This may be 2318 read-only." 2320 OBJECT rsvpSenderHopLih 2321 MIN-ACCESS read-only 2322 DESCRIPTION 2323 "read-create access is not required. This may be 2324 read-only." 2326 OBJECT rsvpSenderInterface 2327 MIN-ACCESS read-only 2328 DESCRIPTION 2329 "read-create access is not required. This may be 2330 read-only." 2332 OBJECT rsvpSenderTSpecRate 2333 MIN-ACCESS read-only 2334 DESCRIPTION 2335 "read-create access is not required. This may be 2336 read-only." 2338 OBJECT rsvpSenderTSpecPeakRate 2339 MIN-ACCESS read-only 2340 DESCRIPTION 2341 "read-create access is not required. This may be 2342 read-only." 2344 OBJECT rsvpSenderTSpecBurst 2345 MIN-ACCESS read-only 2346 DESCRIPTION 2347 "read-create access is not required. This may be 2348 read-only." 2350 OBJECT rsvpSenderTSpecMinTU 2351 MIN-ACCESS read-only 2352 DESCRIPTION 2353 "read-create access is not required. This may be 2354 read-only." 2356 OBJECT rsvpSenderTSpecMaxTU 2357 MIN-ACCESS read-only 2358 DESCRIPTION 2359 "read-create access is not required. This may be 2360 read-only." 2362 OBJECT rsvpSenderInterval 2363 MIN-ACCESS read-only 2364 DESCRIPTION 2365 "read-create access is not required. This may be 2366 read-only." 2368 OBJECT rsvpSenderRSVPHop 2369 MIN-ACCESS read-only 2370 DESCRIPTION 2371 "read-create access is not required. This may be 2372 read-only." 2374 OBJECT rsvpSenderPolicy 2375 MIN-ACCESS read-only 2376 DESCRIPTION 2377 "read-create access is not required. This may be 2378 read-only." 2380 OBJECT rsvpSenderAdspecBreak 2381 MIN-ACCESS read-only 2382 DESCRIPTION 2383 "read-create access is not required. This may be 2384 read-only." 2386 OBJECT rsvpSenderAdspecHopCount 2387 MIN-ACCESS read-only 2388 DESCRIPTION 2389 "read-create access is not required. This may be 2390 read-only." 2392 OBJECT rsvpSenderAdspecPathBw 2393 MIN-ACCESS read-only 2394 DESCRIPTION 2395 "read-create access is not required. This may be 2396 read-only." 2398 OBJECT rsvpSenderAdspecMinLatency 2399 MIN-ACCESS read-only 2400 DESCRIPTION 2401 "read-create access is not required. This may be 2402 read-only." 2404 OBJECT rsvpSenderAdspecMtu 2405 MIN-ACCESS read-only 2406 DESCRIPTION 2407 "read-create access is not required. This may be 2408 read-only." 2410 OBJECT rsvpSenderAdspecGuaranteedSvc 2411 MIN-ACCESS not-accessible 2412 DESCRIPTION 2413 "This may be not-accessible if the system does not 2414 support Guaranteed Service." 2416 OBJECT rsvpSenderAdspecGuaranteedBreak 2417 MIN-ACCESS not-accessible 2418 DESCRIPTION 2419 "This may be not-accessible if the system does not 2420 support Guaranteed Service." 2422 OBJECT rsvpSenderAdspecGuaranteedCtot 2423 MIN-ACCESS not-accessible 2424 DESCRIPTION 2425 "This may be not-accessible if the system does not 2426 support Guaranteed Service." 2428 OBJECT rsvpSenderAdspecGuaranteedDtot 2429 MIN-ACCESS not-accessible 2430 DESCRIPTION 2431 "This may be not-accessible if the system does not 2432 support Guaranteed Service." 2434 OBJECT rsvpSenderAdspecGuaranteedCsum 2435 MIN-ACCESS not-accessible 2436 DESCRIPTION 2437 "This may be not-accessible if the system does not 2438 support Guaranteed Service." 2440 OBJECT rsvpSenderAdspecGuaranteedDsum 2441 MIN-ACCESS read-only 2442 DESCRIPTION 2443 "This may be not-accessible if the system does not 2444 support Guaranteed Service." 2446 OBJECT rsvpSenderAdspecGuaranteedHopCount 2447 MIN-ACCESS not-accessible 2448 DESCRIPTION 2449 "This may be not-accessible if the system does not 2450 support Guaranteed Service." 2452 OBJECT rsvpSenderAdspecGuaranteedPathBw 2453 MIN-ACCESS not-accessible 2454 DESCRIPTION 2455 "This may be not-accessible if the system does not 2456 support Guaranteed Service." 2458 OBJECT rsvpSenderAdspecGuaranteedMinLatency 2459 MIN-ACCESS not-accessible 2460 DESCRIPTION 2461 "This may be not-accessible if the system does not 2462 support Guaranteed Service." 2464 OBJECT rsvpSenderAdspecGuaranteedMtu 2465 MIN-ACCESS not-accessible 2466 DESCRIPTION 2467 "This may be not-accessible if the system does not 2468 support Guaranteed Service." 2470 OBJECT rsvpSenderAdspecCtrlLoadSvc 2471 MIN-ACCESS not-accessible 2472 DESCRIPTION 2473 "This may be not-accessible if the system does not 2474 support Controlled Load." 2476 OBJECT rsvpSenderAdspecCtrlLoadBreak 2477 MIN-ACCESS not-accessible 2478 DESCRIPTION 2479 "This may be not-accessible if the system does not 2480 support Controlled Load." 2482 OBJECT rsvpSenderAdspecCtrlLoadHopCount 2483 MIN-ACCESS not-accessible 2484 DESCRIPTION 2485 "This may be not-accessible if the system does not 2486 support Controlled Load." 2488 OBJECT rsvpSenderAdspecCtrlLoadPathBw 2489 MIN-ACCESS not-accessible 2490 DESCRIPTION 2491 "This may be not-accessible if the system does not 2492 support Controlled Load." 2494 OBJECT rsvpSenderAdspecCtrlLoadMinLatency 2495 MIN-ACCESS not-accessible 2496 DESCRIPTION 2497 "This may be not-accessible if the system does not 2498 support Controlled Load." 2500 OBJECT rsvpSenderAdspecCtrlLoadMtu 2501 MIN-ACCESS not-accessible 2502 DESCRIPTION 2503 "This may be not-accessible if the system does not 2504 support Controlled Load." 2506 OBJECT rsvpSenderStatus 2507 MIN-ACCESS read-only 2508 DESCRIPTION 2509 "read-create access is not required. This may be 2510 read-only." 2512 OBJECT rsvpSenderFlowId 2513 MIN-ACCESS not-accessible 2514 DESCRIPTION 2515 "This object is needed only in a system that imple- 2516 ments IPv6." 2518 OBJECT rsvpResvType 2519 MIN-ACCESS read-only 2520 DESCRIPTION 2521 "read-create access is not required. This may be 2522 read-only." 2524 OBJECT rsvpResvDestAddr 2525 MIN-ACCESS read-only 2526 DESCRIPTION 2527 "read-create access is not required. This may be 2528 read-only." 2530 OBJECT rsvpResvSenderAddr 2531 MIN-ACCESS read-only 2532 DESCRIPTION 2533 "read-create access is not required. This may be 2534 read-only." 2536 OBJECT rsvpResvDestAddrLength 2537 MIN-ACCESS read-only 2538 DESCRIPTION 2539 "read-create access is not required. This may be 2540 read-only." 2542 OBJECT rsvpResvSenderAddrLength 2543 MIN-ACCESS read-only 2544 DESCRIPTION 2545 "read-create access is not required. This may be 2546 read-only." 2548 OBJECT rsvpResvProtocol 2549 MIN-ACCESS read-only 2550 DESCRIPTION 2551 "read-create access is not required. This may be 2552 read-only." 2554 OBJECT rsvpResvDestPort 2555 MIN-ACCESS read-only 2556 DESCRIPTION 2557 "read-create access is not required. This may be 2558 read-only." 2560 OBJECT rsvpResvPort 2561 MIN-ACCESS read-only 2562 DESCRIPTION 2563 "read-create access is not required. This may be 2564 read-only." 2566 OBJECT rsvpResvHopAddr 2567 MIN-ACCESS read-only 2568 DESCRIPTION 2569 "read-create access is not required. This may be 2570 read-only." 2572 OBJECT rsvpResvHopLih 2573 MIN-ACCESS read-only 2574 DESCRIPTION 2575 "read-create access is not required. This may be 2576 read-only." 2578 OBJECT rsvpResvInterface 2579 MIN-ACCESS read-only 2580 DESCRIPTION 2581 "read-create access is not required. This may be 2582 read-only." 2584 OBJECT rsvpResvService 2585 MIN-ACCESS read-only 2586 DESCRIPTION 2587 "read-create access is not required. This may be 2588 read-only." 2590 OBJECT rsvpResvTSpecRate 2591 MIN-ACCESS read-only 2592 DESCRIPTION 2593 "read-create access is not required. This may be 2594 read-only." 2596 OBJECT rsvpResvTSpecPeakRate 2597 MIN-ACCESS read-only 2598 DESCRIPTION 2599 "read-create access is not required. This may be 2600 read-only." 2602 OBJECT rsvpResvTSpecBurst 2603 MIN-ACCESS read-only 2604 DESCRIPTION 2605 "read-create access is not required. This may be 2606 read-only." 2608 OBJECT rsvpResvTSpecMinTU 2609 MIN-ACCESS read-only 2610 DESCRIPTION 2611 "read-create access is not required. This may be 2612 read-only." 2614 OBJECT rsvpResvTSpecMaxTU 2615 MIN-ACCESS read-only 2616 DESCRIPTION 2617 "read-create access is not required. This may be 2618 read-only." 2620 OBJECT rsvpResvRSpecRate 2621 MIN-ACCESS read-only 2622 DESCRIPTION 2623 "read-create access is not required. This may be 2624 read-only." 2626 OBJECT rsvpResvRSpecSlack 2627 MIN-ACCESS read-only 2628 DESCRIPTION 2629 "read-create access is not required. This may be 2630 read-only." 2632 OBJECT rsvpResvInterval 2633 MIN-ACCESS read-only 2634 DESCRIPTION 2635 "read-create access is not required. This may be 2636 read-only." 2638 OBJECT rsvpResvScope 2639 MIN-ACCESS read-only 2640 DESCRIPTION 2641 "read-create access is not required. This may be 2642 read-only." 2644 OBJECT rsvpResvShared 2645 MIN-ACCESS read-only 2646 DESCRIPTION 2647 "read-create access is not required. This may be 2648 read-only." 2650 OBJECT rsvpResvExplicit 2651 MIN-ACCESS read-only 2652 DESCRIPTION 2653 "read-create access is not required. This may be 2654 read-only." 2656 OBJECT rsvpResvRSVPHop 2657 MIN-ACCESS read-only 2658 DESCRIPTION 2659 "read-create access is not required. This may be 2660 read-only." 2662 OBJECT rsvpResvPolicy 2663 MIN-ACCESS read-only 2664 DESCRIPTION 2665 "read-create access is not required. This may be 2666 read-only." 2668 OBJECT rsvpResvStatus 2669 MIN-ACCESS read-only 2670 DESCRIPTION 2671 "read-create access is not required. This may be 2672 read-only." 2673 OBJECT rsvpResvFlowId 2674 MIN-ACCESS not-accessible 2675 DESCRIPTION 2676 "This object is needed only in a system that imple- 2677 ments IPv6." 2679 OBJECT rsvpResvFwdStatus 2680 MIN-ACCESS read-only 2681 DESCRIPTION 2682 "read-create access is not required. This may be 2683 read-only." 2684 OBJECT rsvpResvFwdFlowId 2685 MIN-ACCESS not-accessible 2686 DESCRIPTION 2687 "This object is needed only in a system that imple- 2688 ments IPv6." 2690 ::= { rsvpCompliances 1 } 2692 rsvpSessionGroup OBJECT-GROUP 2693 OBJECTS { 2694 rsvpSessionType, rsvpSessionDestAddr, 2695 rsvpSessionDestAddrLength, rsvpSessionProtocol, 2696 rsvpSessionPort, rsvpSessionSenders, rsvpSessionReceivers, 2697 rsvpSessionRequests 2698 } 2699 STATUS current 2700 DESCRIPTION 2701 "These objects are required for RSVP Systems." 2702 ::= { rsvpGroups 1 } 2704 rsvpSenderGroup OBJECT-GROUP 2705 OBJECTS { 2706 rsvpSenderType, rsvpSenderDestAddr, rsvpSenderAddr, 2707 rsvpSenderDestAddrLength, rsvpSenderAddrLength, 2708 rsvpSenderProtocol, rsvpSenderDestPort, rsvpSenderPort, 2709 rsvpSenderFlowId, rsvpSenderTTL, 2710 rsvpSenderHopAddr, rsvpSenderHopLih, rsvpSenderInterface, 2711 rsvpSenderTSpecRate, rsvpSenderTSpecPeakRate, 2712 rsvpSenderTSpecBurst, rsvpSenderTSpecMinTU, 2713 rsvpSenderTSpecMaxTU, rsvpSenderInterval, rsvpSenderLastChange, 2714 rsvpSenderStatus, rsvpSenderRSVPHop, rsvpSenderPolicy, 2715 rsvpSenderAdspecBreak, rsvpSenderAdspecHopCount, 2716 rsvpSenderAdspecPathBw, rsvpSenderAdspecMinLatency, 2717 rsvpSenderAdspecMtu, rsvpSenderAdspecGuaranteedSvc, 2718 rsvpSenderAdspecGuaranteedBreak, 2719 rsvpSenderAdspecGuaranteedCtot, rsvpSenderAdspecGuaranteedDtot, 2720 rsvpSenderAdspecGuaranteedCsum, rsvpSenderAdspecGuaranteedDsum, 2721 rsvpSenderAdspecGuaranteedHopCount, 2722 rsvpSenderAdspecGuaranteedPathBw, 2723 rsvpSenderAdspecGuaranteedMinLatency, 2724 rsvpSenderAdspecGuaranteedMtu, rsvpSenderAdspecCtrlLoadSvc, 2725 rsvpSenderAdspecCtrlLoadBreak, 2726 rsvpSenderAdspecCtrlLoadHopCount, 2727 rsvpSenderAdspecCtrlLoadPathBw, 2728 rsvpSenderAdspecCtrlLoadMinLatency, 2729 rsvpSenderAdspecCtrlLoadMtu, rsvpSenderNewIndex 2730 } 2731 STATUS current 2732 DESCRIPTION 2733 "These objects are required for RSVP Systems." 2734 ::= { rsvpGroups 2 } 2736 rsvpResvGroup OBJECT-GROUP 2737 OBJECTS { 2738 rsvpResvType, rsvpResvDestAddr, rsvpResvSenderAddr, 2739 rsvpResvDestAddrLength, rsvpResvSenderAddrLength, 2740 rsvpResvProtocol, rsvpResvDestPort, rsvpResvPort, 2741 rsvpResvHopAddr, rsvpResvHopLih, rsvpResvInterface, 2742 rsvpResvService, rsvpResvTSpecRate, rsvpResvTSpecBurst, 2743 rsvpResvTSpecPeakRate, rsvpResvTSpecMinTU, rsvpResvTSpecMaxTU, 2744 rsvpResvRSpecRate, rsvpResvRSpecSlack, rsvpResvInterval, 2745 rsvpResvScope, rsvpResvShared, rsvpResvExplicit, 2746 rsvpResvRSVPHop, rsvpResvLastChange, rsvpResvPolicy, 2747 rsvpResvStatus, rsvpResvNewIndex, rsvpResvTTL, rsvpResvFlowId 2748 } 2749 STATUS current 2750 DESCRIPTION 2751 "These objects are required for RSVP Systems." 2752 ::= { rsvpGroups 3 } 2754 rsvpResvFwdGroup OBJECT-GROUP 2755 OBJECTS { 2756 rsvpResvFwdType, rsvpResvFwdDestAddr, rsvpResvFwdSenderAddr, 2757 rsvpResvFwdDestAddrLength, rsvpResvFwdSenderAddrLength, 2758 rsvpResvFwdProtocol, rsvpResvFwdDestPort, rsvpResvFwdPort, 2759 rsvpResvFwdHopAddr, rsvpResvFwdHopLih, rsvpResvFwdInterface, 2760 rsvpResvFwdNewIndex, rsvpResvFwdService, 2761 rsvpResvFwdTSpecPeakRate, rsvpResvFwdTSpecMinTU, 2762 rsvpResvFwdTSpecMaxTU, rsvpResvFwdTSpecRate, 2763 rsvpResvFwdTSpecBurst, rsvpResvFwdRSpecRate, 2764 rsvpResvFwdRSpecSlack, rsvpResvFwdInterval, rsvpResvFwdScope, 2765 rsvpResvFwdShared, rsvpResvFwdExplicit, rsvpResvFwdRSVPHop, 2766 rsvpResvFwdLastChange, rsvpResvFwdPolicy, rsvpResvFwdStatus, 2767 rsvpResvFwdTTL, rsvpResvFwdFlowId 2768 } 2769 STATUS current 2770 DESCRIPTION 2771 "These objects are optional, used for some RSVP 2772 Systems." 2773 ::= { rsvpGroups 4 } 2775 rsvpIfGroup OBJECT-GROUP 2776 OBJECTS { 2777 rsvpIfUdpNbrs, rsvpIfIpNbrs, rsvpIfNbrs, rsvpIfEnabled, 2778 rsvpIfUdpRequired, rsvpIfRefreshBlockadeMultiple, 2779 rsvpIfRefreshMultiple, rsvpIfRefreshInterval, rsvpIfTTL, 2780 rsvpIfRouteDelay, rsvpIfStatus 2781 } 2782 STATUS current 2783 DESCRIPTION 2784 "These objects are required for RSVP Systems." 2785 ::= { rsvpGroups 5 } 2787 rsvpNbrGroup OBJECT-GROUP 2788 OBJECTS { 2789 rsvpNbrProtocol, rsvpNbrStatus 2790 } 2791 STATUS current 2792 DESCRIPTION 2793 "These objects are required for RSVP Systems." 2794 ::= { rsvpGroups 6 } 2796 rsvpGenObjectsGroup OBJECT-GROUP 2797 OBJECTS { 2798 rsvpBadPackets 2799 } 2800 STATUS current 2801 DESCRIPTION 2802 "This objects are required for RSVP Systems." 2803 ::= { rsvpGroups 7 } 2805 rsvpSenderOutInterfaceGroup OBJECT-GROUP 2806 OBJECTS { 2807 rsvpSenderOutInterfaceStatus 2808 } 2809 STATUS current 2810 DESCRIPTION 2811 "These objects are required for RSVP Systems." 2812 ::= { rsvpGroups 8 } 2814 rsvpNotificationGroup NOTIFICATION-GROUP 2815 NOTIFICATIONS { newFlow, lostFlow } 2816 STATUS current 2817 DESCRIPTION 2818 "This notification is required for Systems sup- 2819 porting the RSVP Policy Module using an SNMP 2820 interface to the Policy Manager." 2821 ::= { rsvpGroups 9 } 2823 END 2824 6. Security Issues 2826 The use of an SNMP SET results in an RSVP or Integrated 2827 Services reservation under rules that are different compared 2828 to if the reservation was negotiated using RSVP. However, no 2829 other security considerations exist other than those imposed 2830 by SNMP itself. 2832 7. Authors' Addresses 2834 Fred Baker 2835 Postal: Cisco Systems 2836 519 Lado Drive 2837 Santa Barbara, California 93111 2838 Tel: +1 805 681 0115 2839 E-Mail: fred@cisco.com 2841 John Krawczyk 2842 Postal: ArrowPoint Communications 2843 235 Littleton Road 2844 Westford, Massachusetts 01886 2845 Tel: +1 508 692 5875 2846 E-Mail: jjk@tiac.net" 2848 Arun Sastry 2849 Postal: Cisco Systems 2850 210 W. Tasman Drive 2851 San Jose, California 95134 2852 Tel: +1 408 526 7685 2853 E-Mail: arun@cisco.com 2855 8. Acknowledgements 2857 This document was produced by the RSVP Working Group. 2859 9. References 2861 [1] M.T. Rose (editor), Management Information Base for 2862 Network Management of TCP/IP-based internets, Internet 2863 Working Group Request for Comments 1213. Network 2864 Information Center, SRI International, Menlo Park, 2865 California, (May, 1990). 2867 [2] Information processing systems - Open Systems 2868 Interconnection - Specification of Abstract Syntax 2869 Notation One (ASN.1), International Organization for 2870 Standardization. International Standard 8824, (December, 2871 1987). 2873 [3] Information processing systems - Open Systems 2874 Interconnection - Specification of Basic Encoding Rules 2875 for Abstract Notation One (ASN.1), International 2876 Organization for Standardization. International Standard 2877 8825, (December, 1987). 2879 Table of Contents 2881 1 Status of this Memo ................................... 1 2882 2 Abstract .............................................. 2 2883 3 The SNMPv2 Network Management Framework ............... 3 2884 3.1 Object Definitions .................................. 3 2885 4 Overview .............................................. 3 2886 4.1 Textual Conventions ................................. 3 2887 4.2 Structure of MIB .................................... 4 2888 4.3 Semantics of Writing the Path and Reservation 2889 State Databases .................................... 4 2890 4.4 Intended use of Flow Notifications .................. 5 2891 4.4.1 The lostFlow Notification ......................... 5 2892 4.4.2 The newFlow Notification .......................... 5 2893 5 Definitions ........................................... 6 2894 5.1 RSVP Session Statistics Database .................... 8 2895 5.1 RSVP Session Sender Database ........................ 12 2896 5.2 RSVP Reservations Requested Database ................ 32 2897 5.3 RSVP Reservation Requests Database .................. 44 2898 5.4 RSVP Interface Attributes Database .................. 57 2899 5.5 RSVP Neighbor Database .............................. 62 2900 5.4 Notifications ....................................... 64 2901 6 Security Issues ....................................... 82 2902 7 Authors' Addresses .................................... 82 2903 8 Acknowledgements ...................................... 82 2904 9 References ............................................ 83