idnits 2.17.1 draft-ietf-rsvp-mib-05.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 79 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 375 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 6 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 279 has weird spacing: '...ds that are ...' == Line 281 has weird spacing: '...d Path or r...' == Line 295 has weird spacing: '...ns seen by a...' == Line 328 has weird spacing: '...ndexing purpo...' == Line 337 has weird spacing: '...6 with flow...' == (370 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 (January 1997) is 9960 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) == Unused Reference: '1' is defined on line 2750, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 2756, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 2762, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' Summary: 12 errors (**), 0 flaws (~~), 11 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft RSVP MIB January 1997 4 RSVP Management Information Base 5 draft-ietf-rsvp-mib-05.txt 7 Thu Jan 30 19:54:54 PST 1997 9 Fred Baker 11 Cisco Systems 12 519 Lado Drive 13 Santa Barbara, California 93111 15 fred@cisco.com 17 John Krawczyk 19 Bay Networks, Inc 20 2 Federal Street 21 Billerica, Massachusetts 01821 23 jj@BayNetworks.com 25 1. Status of this Memo 27 This document is an Internet Draft. Internet Drafts are 28 working documents of the Internet Engineering Task Force 29 (IETF), its Areas, and its Working Groups. Note that other 30 groups may also distribute working documents as Internet 31 Drafts. 33 Internet Drafts are draft documents valid for a maximum of six 34 months. Internet Drafts may be updated, replaced, or obsoleted 35 by other documents at any time. It is not appropriate to use 36 Internet Drafts as reference material or to cite them other 37 than as a "working draft" or "work in progress." 39 Please check the I-D abstract listing contained in each 40 Internet Draft directory to learn the current status of this 41 or any other Internet Draft. 43 2. Abstract 45 This memo defines a portion of the Management Information Base 46 (MIB) for use with network management protocols in TCP/IP- 47 based internets. In particular, it defines objects for 48 managing the Resource Reservation Protocol (RSVP) within the 49 interface attributes defined in the Integrated Services Model. 50 Thus, the Integrated Services MIB is directly relevant to and 51 cross-referenced by this MIB. Comments should be made to the 52 RSVP Working Group, rsvp@isi.edu. 54 This memo does not, in its draft form, specify a standard for 55 the Internet community. 57 3. The SNMPv2 Network Management Framework 59 The SNMPv2 Network Management Framework consists of four major 60 components. They are: 62 o RFC 1441 which defines the SMI, the mechanisms used for 63 describing and naming objects for the purpose of 64 management. 66 o RFC 1213 defines MIB-II, the core set of managed objects 67 for the Internet suite of protocols. 69 o RFC 1445 which defines the administrative and other 70 architectural aspects of the framework. 72 o RFC 1448 which defines the protocol used for network 73 access to managed objects. 75 The Framework permits new objects to be defined for the 76 purpose of experimentation and evaluation. 78 3.1. Object Definitions 80 Managed objects are accessed via a virtual information store, 81 termed the Management Information Base or MIB. Objects in the 82 MIB are defined using the subset of Abstract Syntax Notation 83 One (ASN.1) defined in the SMI. In particular, each object 84 type is named by an OBJECT IDENTIFIER, an administratively 85 assigned name. The object type together with an object 86 instance serves to uniquely identify a specific instantiation 87 of the object. For human convenience, we often use a textual 88 string, termed the descriptor, to refer to the object type. 90 4. Overview 92 4.1. Textual Conventions 94 Several new data types are introduced as a textual convention 95 in this MIB document. These textual conventions enhance the 96 readability of the specification and can ease comparison with 97 other specifications if appropriate. It should be noted that 98 the introduction of the these textual conventions has no 99 effect on either the syntax nor the semantics of any managed 100 objects. The use of these is merely an artifact of the 101 explanatory method used. Objects defined in terms of one of 102 these methods are always encoded by means of the rules that 103 define the primitive type. Hence, no changes to the SMI or 104 the SNMP are necessary to accommodate these textual 105 conventions which are adopted merely for the convenience of 106 readers and writers in pursuit of the elusive goal of clear, 107 concise, and unambiguous MIB documents. 109 4.2. Structure of MIB 111 The MIB is composed of the following sections: 112 General Objects 113 Session Statistics Table 114 Session Sender Table 115 Reservation Requests Received Table 116 Reservation Requests Forwarded Table 117 RSVP Interface Attributes Table 118 RSVP Neighbor Table 120 As a general rule, it is difficult in SNMP to describe 121 arbitrarily long of complex messages; this MIB therefore seeks 122 to describe the Path State Database and the Reservation State 123 Database as though each flow and filter description received 124 in an aggregate message had been received in a separate 125 reservation message. 127 Thus, if a RESV message is received for session 128 224.1.2.3+UDP+4455 with two filter/flow spec groups describing 129 a sender 1.2.3.4 and another sender 1.2.7.8, these two will 130 show in the MIB as two separate rows: one for 131 224.1.2.3+UDP+4455 from 1.2.3.4 and the other for 132 224.1.2.3+UDP+4455 from 1.2.7.8. 134 4.3. Semantics of Writing the Path and Reservation State 135 Databases 137 The fact that the Session Sender and Reservation Requests 138 Tables are writable was of some discussion in the working 139 group as this was developed. It would be good to give an 140 overview of what is expected in implementations that make 141 these tables writable. 143 The objective of writing these tables is to instruct the RSVP 144 Process to act as if it were receiving these messages at a 145 sufficient rate that the protocol would not time them out. 146 "Sufficient" is left somewhat to the implementation; the Time 147 Values object could specify a one hour or one day refresh 148 period, and "receive" the message on that interval, or do so 149 once a millisecond. The point is not the rate of pseudo- 150 reception, but what happens as a result of it. 152 This facility enables network managers to install flexible 153 reservation paths for applications which do not (or do not 154 yet) support RSVP, and to implement corporate policies which 155 preclude end station implementation of RSVP. It presents a 156 simple way to build a proxy RSVP server without some of its 157 issues. 159 The semantics of pseudo-receiving an RSVP message are the same 160 as actually receiving one, including the emission of a 161 teardown when such a message when network management removes 162 the specification by writing 'destroy' to the associated Row 163 Status object. 165 4.4. Intended use of Flow Notifications 167 4.4.1. The lostFlow Notification 169 The Lost Flow notification is an asychronous event that 170 signifies that a flow is no longer being observed. 172 4.4.2. The newFlow Notification 174 The newFlow Notification defined in this MIB is intended to 175 assist in the implementation of a Policy Management Process 176 external to the RSVP system, if and when such an approach is 177 deemed appropriate. We do recommend that the Inform Request be 178 used for this purpose, however. 180 The objective here is to have an external policy management 181 process interpret the RSVP Policy Object, apply the policy, 182 and determine whether the reservation should be accepted. 183 Sample policies include timed reservation (which is a 184 reservation which if otherwise acceptable is installed if the 185 wall clock reads between certain times and not installed 186 otherwise) or prioritized reservation (which may imply sifting 187 through installed reservations, tearing down lower priority 188 reservations, and then accepting this one). In either case, 189 they likely mean some amount of inspection of the RSVP MIB to 190 determine what's valid. 192 The architecture, in the case of an external management 193 process, mandate this kind of an approach: 195 Reservation ---> Router 196 Router detects Policy object 197 Router installs equivalent of RESV entry, 198 leaving RowStatus in the 'notInService' state. 200 ----------> Trigger Network Management 201 <---------- Ack System 203 <----Get/GetBulk as needed 204 <----Set as needed 206 <----Set RowStatus either 'active' or `destroy' 208 <------ -----> 209 Resulting Upline Reservation or Teardown 211 This may be accomplished entirely with SNMPV2, if the 212 "trigger/ack" is an Inform Request and Response. If the NMS is 213 required to poll the router to determine if there is new 214 pending state, either there is an unacceptably high poll rate 215 (on the order of several times a second on each router in the 216 net), or human factors relating to installation of 217 reservations will significantly impact market acceptability of 218 RSVP products. An unacknowledged trap should not be used as a 219 trigger, as it can be lost. 221 5. Definitions 223 RSVP-MIB DEFINITIONS ::= BEGIN 225 IMPORTS 226 MODULE-IDENTITY, OBJECT-TYPE, Gauge32, 227 NOTIFICATION-TYPE, Integer32, experimental 228 FROM SNMPv2-SMI 229 TEXTUAL-CONVENTION, TruthValue, RowStatus, 230 TimeStamp, TestAndIncr, TimeInterval 231 FROM SNMPv2-TC 232 MODULE-COMPLIANCE, OBJECT-GROUP, 233 NOTIFICATION-GROUP FROM SNMPv2-CONF 234 Port, SessionNumber, SessionType, 235 Protocol, QosService, intSrvFlowStatus, 236 MessageSize, BitRate, BurstSize FROM INTEGRATED-SERVICES-MIB 237 ifIndex, InterfaceIndex FROM IF-MIB; 239 rsvp MODULE-IDENTITY 240 LAST-UPDATED "9701301954Z" -- Thu Jan 30 19:54:54 PST 1997 241 ORGANIZATION "IETF RSVP Working Group" 242 CONTACT-INFO 243 " Fred Baker 244 Postal: Cisco Systems 245 519 Lado Drive 246 Santa Barbara, California 93111 247 Tel: +1 805 681 0115 248 E-Mail: fred@cisco.com 250 John Krawczyk 251 Postal: Bay Networks, Inc 252 2 Federal Street 253 Billerica, Massachusetts 01821 254 Tel: +1 508 916 3811 255 E-Mail: jj@BayNetworks.com" 256 DESCRIPTION 257 "The MIB module to describe the RSVP Protocol" 258 ::= { experimental 71 } 260 rsvpObjects OBJECT IDENTIFIER ::= { rsvp 1 } -- tables 261 rsvpGenObjects OBJECT IDENTIFIER ::= { rsvp 2 } -- global objects 262 rsvpNotifications OBJECT IDENTIFIER ::= { rsvp 3 } -- traps 263 rsvpConformance OBJECT IDENTIFIER ::= { rsvp 4 } -- conformance 264 RsvpEncapsulation ::= TEXTUAL-CONVENTION 265 STATUS current 266 DESCRIPTION 267 "This indicates the encapsulation that an RSVP 268 Neighbor is perceived to be using." 269 SYNTAX INTEGER { 270 ip (1), -- IP Protocol 46 271 udp (2), -- UDP Encapsulation 272 both (3) -- neighbor is using both encapsulations 273 } 275 RefreshInterval ::= TEXTUAL-CONVENTION 276 DISPLAY-HINT "d" 277 STATUS current 278 DESCRIPTION 279 "The number of milliseconds that are expected 280 to elapse between refreshes of path or reserva- 281 tion state. Unrefreshed Path or reservation 282 state is removed after a small multiple of this 283 period." 284 SYNTAX INTEGER (0..'7FFFFFFF'h) 286 -- The RSVP Session Statistics Database displays statistics 287 -- relating to the number of senders and receivers in each 288 -- session. 290 rsvpSessionTable OBJECT-TYPE 291 SYNTAX SEQUENCE OF RsvpSessionEntry 292 MAX-ACCESS not-accessible 293 STATUS current 294 DESCRIPTION 295 "Statistics concerning the sessions seen by a 296 given system." 297 ::= { rsvpObjects 1 } 299 rsvpSessionEntry OBJECT-TYPE 300 SYNTAX RsvpSessionEntry 301 MAX-ACCESS not-accessible 302 STATUS current 303 DESCRIPTION 304 "Statistics concerning a single RSVP session 305 seen by a given system." 306 INDEX { rsvpSessionNumber } 307 ::= { rsvpSessionTable 1 } 309 RsvpSessionEntry ::= 310 SEQUENCE { 311 rsvpSessionNumber SessionNumber, 312 rsvpSessionType SessionType, 313 rsvpSessionDestAddr OCTET STRING, 314 rsvpSessionDestAddrLength INTEGER, 315 rsvpSessionProtocol Protocol, 316 rsvpSessionPort Port, 317 rsvpSessionSenders Gauge32, 318 rsvpSessionReceivers Gauge32, 319 rsvpSessionRequests Gauge32 320 } 322 rsvpSessionNumber OBJECT-TYPE 323 SYNTAX SessionNumber 324 MAX-ACCESS not-accessible 325 STATUS current 326 DESCRIPTION 327 "The number of this session. This is for SNMP 328 Indexing purposes only and has no relation to 329 any protocol value." 330 ::= { rsvpSessionEntry 1 } 332 rsvpSessionType OBJECT-TYPE 333 SYNTAX SessionType 334 MAX-ACCESS read-only 335 STATUS current 336 DESCRIPTION 337 "The type of session (IP4, IP6, IP6 with flow 338 information, etc)." 339 ::= { rsvpSessionEntry 2 } 341 rsvpSessionDestAddr OBJECT-TYPE 342 SYNTAX OCTET STRING (SIZE(4..16)) 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The destination address used by all senders in 347 this session. This object may not be changed 348 when the value of the RowStatus object is 'ac- 349 tive'." 350 ::= { rsvpSessionEntry 3 } 352 rsvpSessionDestAddrLength OBJECT-TYPE 353 SYNTAX INTEGER(0..128) 354 MAX-ACCESS read-only 355 STATUS current 356 DESCRIPTION 357 "The CIDR prefix length of the session address, 358 which is 32 for IP4 host and multicast ad- 359 dresses. This object may not be changed when 360 the value of the RowStatus object is 'active'." 361 ::= { rsvpSessionEntry 4 } 363 rsvpSessionProtocol OBJECT-TYPE 364 SYNTAX Protocol 365 MAX-ACCESS read-only 366 STATUS current 367 DESCRIPTION 368 "The IP Protocol used by this session. This 369 object may not be changed when the value of the 370 RowStatus object is 'active'." 371 ::= { rsvpSessionEntry 5 } 373 rsvpSessionPort OBJECT-TYPE 374 SYNTAX Port 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The UDP or TCP port number used as a destina- 379 tion port for all senders in this session. If 380 the IP protocol in use, specified by rsvpSen- 381 derProtocol, is 50 (ESP) or 51 (AH), this 382 represents a virtual destination port number. 383 A value of zero indicates that the IP protocol 384 in use does not have ports. This object may 385 not be changed when the value of the RowStatus 386 object is 'active'." 387 ::= { rsvpSessionEntry 6 } 389 rsvpSessionSenders OBJECT-TYPE 390 SYNTAX Gauge32 391 MAX-ACCESS read-only 392 STATUS current 393 DESCRIPTION 394 "The number of senders currently known to be 395 part of this session." 396 ::= { rsvpSessionEntry 7 } 398 rsvpSessionReceivers OBJECT-TYPE 399 SYNTAX Gauge32 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "The number of reservations being requested of 404 this system for this session." 405 ::= { rsvpSessionEntry 8 } 407 rsvpSessionRequests OBJECT-TYPE 408 SYNTAX Gauge32 409 MAX-ACCESS read-only 410 STATUS current 411 DESCRIPTION 412 "The number of reservation requests this system 413 is sending upstream for this session." 414 ::= { rsvpSessionEntry 9 } 416 -- The RSVP Session Sender Database contains the information 417 -- displayed by senders regarding their potential contribution 418 -- to session data content. It is in essence a list of the 419 -- valid PATH messages that the RSVP Router or Host is receiving. 421 rsvpSenderNewIndex OBJECT-TYPE 422 SYNTAX TestAndIncr 423 MAX-ACCESS read-write 424 STATUS current 425 DESCRIPTION 426 "This object is used to assign values to 427 rsvpSenderNumber as described in 'Textual Con- 428 ventions for SNMPv2'. The network manager 429 reads the object, and then writes the value 430 back in the SET that creates a new instance of 431 rsvpSenderEntry. If the SET fails with the 432 code 'inconsistentValue', then the process must 433 be repeated; If the SET succeeds, then the ob- 434 ject is incremented, and the new instance is 435 created according to the manager's directions." 436 ::= { rsvpGenObjects 2 } 438 rsvpSenderTable OBJECT-TYPE 439 SYNTAX SEQUENCE OF RsvpSenderEntry 440 MAX-ACCESS not-accessible 441 STATUS current 442 DESCRIPTION 443 "Information describing the state information 444 displayed by senders in PATH messages." 445 ::= { rsvpObjects 2 } 447 rsvpSenderEntry OBJECT-TYPE 448 SYNTAX RsvpSenderEntry 449 MAX-ACCESS not-accessible 450 STATUS current 451 DESCRIPTION 452 "Information describing the state information 453 displayed by a single sender's PATH message." 454 INDEX { rsvpSessionNumber, rsvpSenderNumber } 455 ::= { rsvpSenderTable 1 } 457 RsvpSenderEntry ::= 458 SEQUENCE { 459 rsvpSenderNumber SessionNumber, 460 rsvpSenderType SessionType, 461 rsvpSenderDestAddr OCTET STRING, 462 rsvpSenderAddr OCTET STRING, 463 rsvpSenderDestAddrLength INTEGER, 464 rsvpSenderAddrLength INTEGER, 465 rsvpSenderProtocol Protocol, 466 rsvpSenderDestPort Port, 467 rsvpSenderPort Port, 468 rsvpSenderHopAddr OCTET STRING, 469 rsvpSenderHopLih Integer32, 470 rsvpSenderInterface InterfaceIndex, 471 rsvpSenderTSpecRate BitRate, 472 rsvpSenderTSpecPeakRate BitRate, 473 rsvpSenderTSpecBurst BurstSize, 474 rsvpSenderTSpecMinTU MessageSize, 475 rsvpSenderTSpecMaxTU MessageSize, 476 rsvpSenderInterval RefreshInterval, 477 rsvpSenderRSVPHop TruthValue, 478 rsvpSenderLastChange TimeStamp, 479 rsvpSenderPolicy OCTET STRING, 480 rsvpSenderAdspecBreak TruthValue, 481 rsvpSenderAdspecHopCount INTEGER, 482 rsvpSenderAdspecPathBw BitRate, 483 rsvpSenderAdspecMinLatency Integer32, 484 rsvpSenderAdspecMtu INTEGER, 485 rsvpSenderAdspecGuaranteedSvc TruthValue, 486 rsvpSenderAdspecGuaranteedBreak TruthValue, 487 rsvpSenderAdspecGuaranteedCtot Integer32, 488 rsvpSenderAdspecGuaranteedDtot Integer32, 489 rsvpSenderAdspecGuaranteedCsum Integer32, 490 rsvpSenderAdspecGuaranteedDsum Integer32, 491 rsvpSenderAdspecGuaranteedHopCount INTEGER, 492 rsvpSenderAdspecGuaranteedPathBw BitRate, 493 rsvpSenderAdspecGuaranteedMinLatency Integer32, 494 rsvpSenderAdspecGuaranteedMtu INTEGER, 495 rsvpSenderAdspecCtrlLoadSvc TruthValue, 496 rsvpSenderAdspecCtrlLoadBreak TruthValue, 497 rsvpSenderAdspecCtrlLoadHopCount INTEGER, 498 rsvpSenderAdspecCtrlLoadPathBw BitRate, 499 rsvpSenderAdspecCtrlLoadMinLatency Integer32, 500 rsvpSenderAdspecCtrlLoadMtu INTEGER, 501 rsvpSenderStatus RowStatus 502 } 503 rsvpSenderNumber OBJECT-TYPE 504 SYNTAX SessionNumber 505 MAX-ACCESS not-accessible 506 STATUS current 507 DESCRIPTION 508 "The number of this sender. This is for SNMP 509 Indexing purposes only and has no relation to 510 any protocol vaalue." 511 ::= { rsvpSenderEntry 1 } 513 rsvpSenderType OBJECT-TYPE 514 SYNTAX SessionType 515 MAX-ACCESS read-create 516 STATUS current 517 DESCRIPTION 518 "The type of session (IP4, IP6, IP6 with flow 519 information, etc)." 520 ::= { rsvpSenderEntry 2 } 522 rsvpSenderDestAddr OBJECT-TYPE 523 SYNTAX OCTET STRING (SIZE(4..16)) 524 MAX-ACCESS read-create 525 STATUS current 526 DESCRIPTION 527 "The destination address used by all senders in 528 this session. This object may not be changed 529 when the value of the RowStatus object is 'ac- 530 tive'." 531 ::= { rsvpSenderEntry 3 } 533 rsvpSenderAddr OBJECT-TYPE 534 SYNTAX OCTET STRING (SIZE(4..16)) 535 MAX-ACCESS read-create 536 STATUS current 537 DESCRIPTION 538 "The source address used by this sender in this 539 session. This object may not be changed when 540 the value of the RowStatus object is 'active'." 541 ::= { rsvpSenderEntry 4 } 543 rsvpSenderDestAddrLength OBJECT-TYPE 544 SYNTAX INTEGER(0..128) 545 MAX-ACCESS read-create 546 STATUS current 547 DESCRIPTION 548 "The length of the destination address in bits. 549 This is the CIDR Prefix Length, which for IP4 550 hosts and multicast addresses is 32 bits. This 551 object may not be changed when the value of the 552 RowStatus object is 'active'." 553 ::= { rsvpSenderEntry 5 } 555 rsvpSenderAddrLength OBJECT-TYPE 556 SYNTAX INTEGER(0..128) 557 MAX-ACCESS read-create 558 STATUS current 559 DESCRIPTION 560 "The length of the sender's address in bits. 561 This is the CIDR Prefix Length, which for IP4 562 hosts and multicast addresses is 32 bits. This 563 object may not be changed when the value of the 564 RowStatus object is 'active'." 565 ::= { rsvpSenderEntry 6 } 567 rsvpSenderProtocol OBJECT-TYPE 568 SYNTAX Protocol 569 MAX-ACCESS read-create 570 STATUS current 571 DESCRIPTION 572 "The IP Protocol used by this session. This 573 object may not be changed when the value of the 574 RowStatus object is 'active'." 575 ::= { rsvpSenderEntry 7 } 577 rsvpSenderDestPort OBJECT-TYPE 578 SYNTAX Port 579 MAX-ACCESS read-create 580 STATUS current 581 DESCRIPTION 582 "The UDP or TCP port number used as a destina- 583 tion port for all senders in this session. If 584 the IP protocol in use, specified by rsvpSen- 585 derProtocol, is 50 (ESP) or 51 (AH), this 586 represents a virtual destination port number. 587 A value of zero indicates that the IP protocol 588 in use does not have ports. This object may 589 not be changed when the value of the RowStatus 590 object is 'active'." 591 ::= { rsvpSenderEntry 8 } 593 rsvpSenderPort OBJECT-TYPE 594 SYNTAX Port 595 MAX-ACCESS read-create 596 STATUS current 597 DESCRIPTION 598 "The UDP or TCP port number used as a source 599 port for this sender in this session. If the 600 IP protocol in use, specified by rsvpSenderPro- 601 tocol is 50 (ESP) or 51 (AH), this represents a 602 generalized port identifier (GPI). A value of 603 zero indicates that the IP protocol in use does 604 not have ports. This object may not be changed 605 when the value of the RowStatus object is 'ac- 606 tive'." 607 ::= { rsvpSenderEntry 9 } 609 rsvpSenderHopAddr OBJECT-TYPE 610 SYNTAX OCTET STRING (SIZE(4..16)) 611 MAX-ACCESS read-create 612 STATUS current 613 DESCRIPTION 614 "The address used by the previous RSVP hop 615 (which may be the original sender)." 616 ::= { rsvpSenderEntry 10 } 618 rsvpSenderHopLih OBJECT-TYPE 619 SYNTAX Integer32 620 MAX-ACCESS read-create 621 STATUS current 622 DESCRIPTION 623 "The Logical Interface Handle used by the pre- 624 vious RSVP hop (which may be the original 625 sender)." 626 ::= { rsvpSenderEntry 11 } 628 rsvpSenderInterface OBJECT-TYPE 629 SYNTAX InterfaceIndex 630 MAX-ACCESS read-create 631 STATUS current 632 DESCRIPTION 633 "The ifIndex value of the interface on which 634 this PATH message was most recently received." 635 ::= { rsvpSenderEntry 12 } 637 rsvpSenderTSpecRate OBJECT-TYPE 638 SYNTAX BitRate 639 UNITS "bits per second" 640 MAX-ACCESS read-create 641 STATUS current 642 DESCRIPTION 643 "The Average Bit Rate of the sender's data 644 stream. Within a transmission burst, the ar- 645 rival rate may be as fast as rsvpSenderTSpec- 646 PeakRate (if supported by the service model); 647 however, averaged across two or more burst in- 648 tervals, the rate should not exceed rsvpSen- 649 derTSpecRate. 651 Note that this is a prediction, often based on 652 the general capability of a type of codec or 653 particular encoding; the measured average rate 654 may be significantly lower." 655 ::= { rsvpSenderEntry 13 } 657 rsvpSenderTSpecPeakRate OBJECT-TYPE 658 SYNTAX BitRate 659 UNITS "bits per second" 660 MAX-ACCESS read-create 661 STATUS current 662 DESCRIPTION 663 "The Peak Bit Rate of the sender's data stream. 664 Traffic arrival is not expected to exceed this 665 rate at any time, apart from the effects of 666 jitter in the network. If not specified in the 667 TSpec, this returns zero or noSuchValue." 668 ::= { rsvpSenderEntry 14 } 670 rsvpSenderTSpecBurst OBJECT-TYPE 671 SYNTAX BurstSize 672 UNITS "bytes" 673 MAX-ACCESS read-create 674 STATUS current 675 DESCRIPTION 676 "The size of the largest burst expected from 677 the sender at a time." 678 ::= { rsvpSenderEntry 15 } 680 rsvpSenderTSpecMinTU OBJECT-TYPE 681 SYNTAX MessageSize 682 MAX-ACCESS read-create 683 STATUS current 684 DESCRIPTION 685 "The minimum message size for this flow. The 686 policing algorithm will treat smaller messages 687 as though they are this size." 688 ::= { rsvpSenderEntry 16 } 690 rsvpSenderTSpecMaxTU OBJECT-TYPE 691 SYNTAX MessageSize 692 MAX-ACCESS read-create 693 STATUS current 694 DESCRIPTION 695 "The maximum message size for this flow. The 696 admission algorithm will reject TSpecs whose 697 Maximum Transmission Unit, plus the interface 698 headers, exceed the interface MTU." 699 ::= { rsvpSenderEntry 17 } 701 rsvpSenderInterval OBJECT-TYPE 702 SYNTAX RefreshInterval 703 MAX-ACCESS read-create 704 STATUS current 705 DESCRIPTION 706 "The interval between refresh messages as ad- 707 vertised by the Previous Hop." 708 ::= { rsvpSenderEntry 18 } 710 rsvpSenderRSVPHop OBJECT-TYPE 711 SYNTAX TruthValue 712 MAX-ACCESS read-create 713 STATUS current 714 DESCRIPTION 715 "If TRUE, the node believes that the previous 716 IP hop is an RSVP hop. If FALSE, the node be- 717 lieves that the previous IP hop may not be an 718 RSVP hop." 719 ::= { rsvpSenderEntry 19 } 721 rsvpSenderLastChange OBJECT-TYPE 722 SYNTAX TimeStamp 723 MAX-ACCESS read-only 724 STATUS current 725 DESCRIPTION 726 "The time of the last change in this PATH mes- 727 sage; This is either the first time it was re- 728 ceived or the time of the most recent change in 729 parameters." 730 ::= { rsvpSenderEntry 20 } 732 rsvpSenderPolicy OBJECT-TYPE 733 SYNTAX OCTET STRING (SIZE(4..65536)) 734 MAX-ACCESS read-create 735 STATUS current 736 DESCRIPTION 737 "The contents of the policy object, displayed 738 as an uninterpreted string of octets, including 739 the object header. In the absence of such an 740 object, this should be of zero length." 741 ::= { rsvpSenderEntry 21 } 743 rsvpSenderAdspecBreak OBJECT-TYPE 744 SYNTAX TruthValue 745 MAX-ACCESS read-create 746 STATUS current 747 DESCRIPTION 748 "The global break bit general characterization 749 parameter from the ADSPEC. If TRUE, at least 750 one non-IS hop was detected in the path. If 751 FALSE, no non-IS hops were detected." 752 ::= { rsvpSenderEntry 22 } 754 rsvpSenderAdspecHopCount OBJECT-TYPE 755 SYNTAX INTEGER (0..65535) 756 MAX-ACCESS read-create 757 STATUS current 758 DESCRIPTION 759 "The hop count general characterization parame- 760 ter from the ADSPEC. A return of zero or 761 noSuchValue indicates one of the following con- 762 ditions: 764 the invalid bit was set 765 the parameter was not present" 766 ::= { rsvpSenderEntry 23 } 768 rsvpSenderAdspecPathBw OBJECT-TYPE 769 SYNTAX BitRate 770 UNITS "bits per second" 771 MAX-ACCESS read-create 772 STATUS current 773 DESCRIPTION 774 "The path bandwidth estimate general character- 775 ization parameter from the ADSPEC. A return of 776 zero or noSuchValue indicates one of the fol- 777 lowing conditions: 779 the invalid bit was set 780 the parameter was not present" 781 ::= { rsvpSenderEntry 24 } 783 rsvpSenderAdspecMinLatency OBJECT-TYPE 784 SYNTAX Integer32 785 UNITS "microseconds" 786 MAX-ACCESS read-create 787 STATUS current 788 DESCRIPTION 789 "The minimum path latency general characteriza- 790 tion parameter from the ADSPEC. A return of 791 zero or noSuchValue indicates one of the fol- 792 lowing conditions: 794 the invalid bit was set 795 the parameter was not present" 796 ::= { rsvpSenderEntry 25 } 798 rsvpSenderAdspecMtu OBJECT-TYPE 799 SYNTAX INTEGER (0..65535) 800 UNITS "bytes" 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 804 "The composed Maximum Transmission Unit general 805 characterization parameter from the ADSPEC. A 806 return of zero or noSuchValue indicates one of 807 the following conditions: 809 the invalid bit was set 810 the parameter was not present" 811 ::= { rsvpSenderEntry 26 } 813 rsvpSenderAdspecGuaranteedSvc OBJECT-TYPE 814 SYNTAX TruthValue 815 MAX-ACCESS read-create 816 STATUS current 817 DESCRIPTION 818 "If TRUE, the ADSPEC contains a Guaranteed Ser- 819 vice fragment. If FALSE, the ADSPEC does not 820 contain a Guaranteed Service fragment." 821 ::= { rsvpSenderEntry 27 } 823 rsvpSenderAdspecGuaranteedBreak OBJECT-TYPE 824 SYNTAX TruthValue 825 MAX-ACCESS read-create 826 STATUS current 827 DESCRIPTION 828 "If TRUE, the Guaranteed Service fragment has 829 its 'break' bit set, indicating that one or 830 more nodes along the path do not support the 831 guaranteed service. If FALSE, and rsvpSen- 832 derAdspecGuaranteedSvc is TRUE, the 'break' bit 833 is not set. 835 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 836 returns FALSE or noSuchValue." 837 ::= { rsvpSenderEntry 28 } 839 rsvpSenderAdspecGuaranteedCtot OBJECT-TYPE 840 SYNTAX Integer32 841 UNITS "bytes" 842 MAX-ACCESS read-create 843 STATUS current 844 DESCRIPTION 846 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 847 is the end-to-end composed value for the 848 guaranteed service 'C' parameter. A return of 849 zero or noSuchValue indicates one of the fol- 850 lowing conditions: 852 the invalid bit was set 853 the parameter was not present 855 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 856 returns zero or noSuchValue." 857 ::= { rsvpSenderEntry 29 } 859 rsvpSenderAdspecGuaranteedDtot OBJECT-TYPE 860 SYNTAX Integer32 861 UNITS "microseconds" 862 MAX-ACCESS read-create 863 STATUS current 864 DESCRIPTION 865 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 866 is the end-to-end composed value for the 867 guaranteed service 'D' parameter. A return of 868 zero or noSuchValue indicates one of the fol- 869 lowing conditions: 871 the invalid bit was set 872 the parameter was not present 874 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 875 returns zero or noSuchValue." 876 ::= { rsvpSenderEntry 30 } 878 rsvpSenderAdspecGuaranteedCsum OBJECT-TYPE 879 SYNTAX Integer32 880 UNITS "bytes" 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 885 is the composed value for the guaranteed ser- 886 vice 'C' parameter since the last reshaping 887 point. A return of zero or noSuchValue indi- 888 cates one of the following conditions: 890 the invalid bit was set 891 the parameter was not present 893 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 894 returns zero or noSuchValue." 895 ::= { rsvpSenderEntry 31 } 897 rsvpSenderAdspecGuaranteedDsum OBJECT-TYPE 898 SYNTAX Integer32 899 UNITS "microseconds" 900 MAX-ACCESS read-create 901 STATUS current 902 DESCRIPTION 903 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 904 is the composed value for the guaranteed ser- 905 vice 'D' parameter since the last reshaping 906 point. A return of zero or noSuchValue indi- 907 cates one of the following conditions: 909 the invalid bit was set 910 the parameter was not present 912 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 913 returns zero or noSuchValue." 914 ::= { rsvpSenderEntry 32 } 916 rsvpSenderAdspecGuaranteedHopCount OBJECT-TYPE 917 SYNTAX INTEGER (0..65535) 918 MAX-ACCESS read-create 919 STATUS current 920 DESCRIPTION 922 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 923 is the service-specific override of the hop 924 count general characterization parameter from 925 the ADSPEC. A return of zero or noSuchValue 926 indicates one of the following conditions: 928 the invalid bit was set 929 the parameter was not present 931 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 932 returns zero or noSuchValue." 933 ::= { rsvpSenderEntry 33 } 935 rsvpSenderAdspecGuaranteedPathBw OBJECT-TYPE 936 SYNTAX BitRate 937 UNITS "bits per second" 938 MAX-ACCESS read-create 939 STATUS current 940 DESCRIPTION 941 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 942 is the service-specific override of the path 943 bandwidth estimate general characterization 944 parameter from the ADSPEC. A return of zero or 945 noSuchValue indicates one of the following con- 946 ditions: 948 the invalid bit was set 949 the parameter was not present 951 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 952 returns zero or noSuchValue." 953 ::= { rsvpSenderEntry 34 } 955 rsvpSenderAdspecGuaranteedMinLatency OBJECT-TYPE 956 SYNTAX Integer32 957 UNITS "microseconds" 958 MAX-ACCESS read-create 959 STATUS current 960 DESCRIPTION 961 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 962 is the service-specific override of the minimum 963 path latency general characterization parameter 964 from the ADSPEC. A return of zero or noSuch- 965 Value indicates one of the following condi- 966 tions: 968 the invalid bit was set 969 the parameter was not present 971 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 972 returns zero or noSuchValue." 973 ::= { rsvpSenderEntry 35 } 975 rsvpSenderAdspecGuaranteedMtu OBJECT-TYPE 976 SYNTAX INTEGER (0..65535) 977 UNITS "bytes" 978 MAX-ACCESS read-create 979 STATUS current 980 DESCRIPTION 981 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 982 is the service-specific override of the com- 983 posed Maximum Transmission Unit general charac- 984 terization parameter from the ADSPEC. A return 985 of zero or noSuchValue indicates one of the 986 following conditions: 988 the invalid bit was set 989 the parameter was not present 991 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 992 returns zero or noSuchValue." 993 ::= { rsvpSenderEntry 36 } 995 rsvpSenderAdspecCtrlLoadSvc OBJECT-TYPE 996 SYNTAX TruthValue 997 MAX-ACCESS read-create 998 STATUS current 999 DESCRIPTION 1000 "If TRUE, the ADSPEC contains a Controlled Load 1001 Service fragment. If FALSE, the ADSPEC does 1002 not contain a Controlled Load Service frag- 1003 ment." 1004 ::= { rsvpSenderEntry 37 } 1006 rsvpSenderAdspecCtrlLoadBreak OBJECT-TYPE 1007 SYNTAX TruthValue 1008 MAX-ACCESS read-create 1009 STATUS current 1010 DESCRIPTION 1011 "If TRUE, the Controlled Load Service fragment 1012 has its 'break' bit set, indicating that one or 1013 more nodes along the path do not support the 1014 controlled load service. If FALSE, and 1015 rsvpSenderAdspecCtrlLoadSvc is TRUE, the 1016 'break' bit is not set. 1018 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1019 returns FALSE or noSuchValue." 1020 ::= { rsvpSenderEntry 38 } 1022 rsvpSenderAdspecCtrlLoadHopCount OBJECT-TYPE 1023 SYNTAX INTEGER (0..65535) 1024 MAX-ACCESS read-create 1025 STATUS current 1026 DESCRIPTION 1028 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1029 is the service-specific override of the hop 1030 count general characterization parameter from 1031 the ADSPEC. A return of zero or noSuchValue 1032 indicates one of the following conditions: 1034 the invalid bit was set 1035 the parameter was not present 1037 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1038 returns zero or noSuchValue." 1039 ::= { rsvpSenderEntry 39 } 1041 rsvpSenderAdspecCtrlLoadPathBw OBJECT-TYPE 1042 SYNTAX BitRate 1043 UNITS "bits per second" 1044 MAX-ACCESS read-create 1045 STATUS current 1046 DESCRIPTION 1047 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1048 is the service-specific override of the path 1049 bandwidth estimate general characterization 1050 parameter from the ADSPEC. A return of zero or 1051 noSuchValue indicates one of the following con- 1052 ditions: 1054 the invalid bit was set 1055 the parameter was not present 1057 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1058 returns zero or noSuchValue." 1059 ::= { rsvpSenderEntry 40 } 1061 rsvpSenderAdspecCtrlLoadMinLatency OBJECT-TYPE 1062 SYNTAX Integer32 1063 UNITS "microseconds" 1064 MAX-ACCESS read-create 1065 STATUS current 1066 DESCRIPTION 1067 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1068 is the service-specific override of the minimum 1069 path latency general characterization parameter 1070 from the ADSPEC. A return of zero or noSuch- 1071 Value indicates one of the following condi- 1072 tions: 1074 the invalid bit was set 1075 the parameter was not present 1077 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1078 returns zero or noSuchValue." 1079 ::= { rsvpSenderEntry 41 } 1081 rsvpSenderAdspecCtrlLoadMtu OBJECT-TYPE 1082 SYNTAX INTEGER (0..65535) 1083 UNITS "bytes" 1084 MAX-ACCESS read-create 1085 STATUS current 1086 DESCRIPTION 1087 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1088 is the service-specific override of the com- 1089 posed Maximum Transmission Unit general charac- 1090 terization parameter from the ADSPEC. A return 1091 of zero or noSuchValue indicates one of the 1092 following conditions: 1094 the invalid bit was set 1095 the parameter was not present 1097 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1098 returns zero or noSuchValue." 1099 ::= { rsvpSenderEntry 42 } 1101 rsvpSenderStatus OBJECT-TYPE 1102 SYNTAX RowStatus 1103 MAX-ACCESS read-create 1104 STATUS current 1105 DESCRIPTION 1106 "'active' for all active PATH messages. This 1107 object may be used to install static PATH in- 1108 formation or delete PATH information." 1109 ::= { rsvpSenderEntry 43 } 1111 -- The RSVP Reservation Requests Received Table contains the 1112 -- information displayed by receivers regarding their needs with 1113 -- respect to sessions and senders. It is in essence a list of the 1114 -- valid RESV messages that the RSVP Router or Host is receiving. 1116 rsvpResvNewIndex OBJECT-TYPE 1117 SYNTAX TestAndIncr 1118 MAX-ACCESS read-write 1119 STATUS current 1120 DESCRIPTION 1121 "This object is used to assign values to 1122 rsvpResvNumber as described in 'Textual Conven- 1123 tions for SNMPv2'. The network manager reads 1124 the object, and then writes the value back in 1125 the SET that creates a new instance of 1126 rsvpResvEntry. If the SET fails with the code 1127 'inconsistentValue', then the process must be 1128 repeated; If the SET succeeds, then the object 1129 is incremented, and the new instance is created 1130 according to the manager's directions." 1131 ::= { rsvpGenObjects 3 } 1133 rsvpResvTable OBJECT-TYPE 1134 SYNTAX SEQUENCE OF RsvpResvEntry 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 "Information describing the state information 1139 displayed by receivers in RESV messages." 1140 ::= { rsvpObjects 3 } 1142 rsvpResvEntry OBJECT-TYPE 1143 SYNTAX RsvpResvEntry 1144 MAX-ACCESS not-accessible 1145 STATUS current 1146 DESCRIPTION 1147 "Information describing the state information 1148 displayed by a single receiver's RESV message 1149 concerning a single sender." 1150 INDEX { rsvpSessionNumber, rsvpResvNumber } 1151 ::= { rsvpResvTable 1 } 1153 RsvpResvEntry ::= 1154 SEQUENCE { 1155 rsvpResvNumber SessionNumber, 1156 rsvpResvType SessionType, 1157 rsvpResvDestAddr OCTET STRING, 1158 rsvpResvSenderAddr OCTET STRING, 1159 rsvpResvDestAddrLength INTEGER, 1160 rsvpResvSenderAddrLength INTEGER, 1161 rsvpResvProtocol Protocol, 1162 rsvpResvDestPort Port, 1163 rsvpResvPort Port, 1164 rsvpResvHopAddr OCTET STRING, 1165 rsvpResvHopLih Integer32, 1166 rsvpResvInterface InterfaceIndex, 1167 rsvpResvService QosService, 1168 rsvpResvTSpecRate BitRate, 1169 rsvpResvTSpecPeakRate BitRate, 1170 rsvpResvTSpecBurst BurstSize, 1171 rsvpResvTSpecMinTU MessageSize, 1172 rsvpResvTSpecMaxTU MessageSize, 1173 rsvpResvRSpecRate BitRate, 1174 rsvpResvRSpecSlack Integer32, 1175 rsvpResvInterval RefreshInterval, 1176 rsvpResvScope OCTET STRING, 1177 rsvpResvShared TruthValue, 1178 rsvpResvExplicit TruthValue, 1179 rsvpResvRSVPHop TruthValue, 1180 rsvpResvLastChange TimeStamp, 1181 rsvpResvPolicy OCTET STRING, 1182 rsvpResvStatus RowStatus 1183 } 1185 rsvpResvNumber OBJECT-TYPE 1186 SYNTAX SessionNumber 1187 MAX-ACCESS not-accessible 1188 STATUS current 1189 DESCRIPTION 1190 "The number of this reservation request. This 1191 is for SNMP Indexing purposes only and has no 1192 relation to any protocol value." 1193 ::= { rsvpResvEntry 1 } 1195 rsvpResvType OBJECT-TYPE 1196 SYNTAX SessionType 1197 MAX-ACCESS read-create 1198 STATUS current 1199 DESCRIPTION 1200 "The type of session (IP4, IP6, IP6 with flow 1201 information, etc)." 1202 ::= { rsvpResvEntry 2 } 1204 rsvpResvDestAddr OBJECT-TYPE 1205 SYNTAX OCTET STRING (SIZE(4..16)) 1206 MAX-ACCESS read-create 1207 STATUS current 1208 DESCRIPTION 1209 "The destination address used by all senders in 1210 this session. This object may not be changed 1211 when the value of the RowStatus object is 'ac- 1212 tive'." 1213 ::= { rsvpResvEntry 3 } 1215 rsvpResvSenderAddr OBJECT-TYPE 1216 SYNTAX OCTET STRING (SIZE(4..16)) 1217 MAX-ACCESS read-create 1218 STATUS current 1219 DESCRIPTION 1220 "The source address of the sender selected by 1221 this reservation. The value of all zeroes in- 1222 dicates 'all senders'. This object may not be 1223 changed when the value of the RowStatus object 1224 is 'active'." 1225 ::= { rsvpResvEntry 4 } 1227 rsvpResvDestAddrLength OBJECT-TYPE 1228 SYNTAX INTEGER(0..128) 1229 MAX-ACCESS read-create 1230 STATUS current 1231 DESCRIPTION 1232 "The length of the destination address in bits. 1233 This is the CIDR Prefix Length, which for IP4 1234 hosts and multicast addresses is 32 bits. This 1235 object may not be changed when the value of the 1236 RowStatus object is 'active'." 1237 ::= { rsvpResvEntry 5 } 1239 rsvpResvSenderAddrLength OBJECT-TYPE 1240 SYNTAX INTEGER(0..128) 1241 MAX-ACCESS read-create 1242 STATUS current 1243 DESCRIPTION 1244 "The length of the sender's address in bits. 1245 This is the CIDR Prefix Length, which for IP4 1246 hosts and multicast addresses is 32 bits. This 1247 object may not be changed when the value of the 1248 RowStatus object is 'active'." 1249 ::= { rsvpResvEntry 6 } 1251 rsvpResvProtocol OBJECT-TYPE 1252 SYNTAX Protocol 1253 MAX-ACCESS read-create 1254 STATUS current 1255 DESCRIPTION 1256 "The IP Protocol used by this session. This 1257 object may not be changed when the value of the 1258 RowStatus object is 'active'." 1259 ::= { rsvpResvEntry 7 } 1261 rsvpResvDestPort OBJECT-TYPE 1262 SYNTAX Port 1263 MAX-ACCESS read-create 1264 STATUS current 1265 DESCRIPTION 1266 "The UDP or TCP port number used as a destina- 1267 tion port for all senders in this session. If 1268 the IP protocol in use, specified by 1269 rsvpResvProtocol, is 50 (ESP) or 51 (AH), this 1270 represents a virtual destination port number. 1271 A value of zero indicates that the IP protocol 1272 in use does not have ports. This object may 1273 not be changed when the value of the RowStatus 1274 object is 'active'." 1275 ::= { rsvpResvEntry 8 } 1277 rsvpResvPort OBJECT-TYPE 1278 SYNTAX Port 1279 MAX-ACCESS read-create 1280 STATUS current 1281 DESCRIPTION 1282 "The UDP or TCP port number used as a source 1283 port for this sender in this session. If the 1284 IP protocol in use, specified by rsvpResvProto- 1285 col is 50 (ESP) or 51 (AH), this represents a 1286 generalized port identifier (GPI). A value of 1287 zero indicates that the IP protocol in use does 1288 not have ports. This object may not be changed 1289 when the value of the RowStatus object is 'ac- 1290 tive'." 1291 ::= { rsvpResvEntry 9 } 1293 rsvpResvHopAddr OBJECT-TYPE 1294 SYNTAX OCTET STRING (SIZE(4..16)) 1295 MAX-ACCESS read-create 1296 STATUS current 1297 DESCRIPTION 1298 "The address used by the next RSVP hop (which 1299 may be the ultimate receiver)." 1300 ::= { rsvpResvEntry 10 } 1302 rsvpResvHopLih OBJECT-TYPE 1303 SYNTAX Integer32 1304 MAX-ACCESS read-create 1305 STATUS current 1306 DESCRIPTION 1307 "The Logical Interface Handle received from the 1308 previous RSVP hop (which may be the ultimate 1309 receiver)." 1310 ::= { rsvpResvEntry 11 } 1312 rsvpResvInterface OBJECT-TYPE 1313 SYNTAX InterfaceIndex 1314 MAX-ACCESS read-create 1315 STATUS current 1316 DESCRIPTION 1317 "The ifIndex value of the interface on which 1318 this RESV message was most recently received." 1319 ::= { rsvpResvEntry 12 } 1321 rsvpResvService OBJECT-TYPE 1322 SYNTAX QosService 1323 MAX-ACCESS read-create 1324 STATUS current 1325 DESCRIPTION 1326 "The QoS Service classification requested by 1327 the receiver." 1328 ::= { rsvpResvEntry 13 } 1330 rsvpResvTSpecRate OBJECT-TYPE 1331 SYNTAX BitRate 1332 UNITS "bits per second" 1333 MAX-ACCESS read-create 1334 STATUS current 1335 DESCRIPTION 1336 "The Average Bit Rate of the sender's data 1337 stream. Within a transmission burst, the ar- 1338 rival rate may be as fast as rsvpResvTSpec- 1339 PeakRate (if supported by the service model); 1340 however, averaged across two or more burst in- 1341 tervals, the rate should not exceed 1342 rsvpResvTSpecRate. 1344 Note that this is a prediction, often based on 1345 the general capability of a type of codec or 1346 particular encoding; the measured average rate 1347 may be significantly lower." 1348 ::= { rsvpResvEntry 14 } 1350 rsvpResvTSpecPeakRate OBJECT-TYPE 1351 SYNTAX BitRate 1352 UNITS "bits per second" 1353 MAX-ACCESS read-create 1354 STATUS current 1355 DESCRIPTION 1356 "The Peak Bit Rate of the sender's data stream. 1357 Traffic arrival is not expected to exceed this 1358 rate at any time, apart from the effects of 1359 jitter in the network. If not specified in the 1360 TSpec, this returns zero or noSuchValue." 1361 ::= { rsvpResvEntry 15 } 1363 rsvpResvTSpecBurst OBJECT-TYPE 1364 SYNTAX BurstSize 1365 UNITS "bytes" 1366 MAX-ACCESS read-create 1367 STATUS current 1368 DESCRIPTION 1369 "The size of the largest burst expected from 1370 the sender at a time. 1372 If this is less than the sender's advertised 1373 burst size, the receiver is asking the network 1374 to provide flow pacing beyond what would be 1375 provided under normal circumstances. Such pac- 1376 ing is at the network's option." 1377 ::= { rsvpResvEntry 16 } 1379 rsvpResvTSpecMinTU OBJECT-TYPE 1380 SYNTAX MessageSize 1381 MAX-ACCESS read-create 1382 STATUS current 1383 DESCRIPTION 1384 "The minimum message size for this flow. The 1385 policing algorithm will treat smaller messages 1386 as though they are this size." 1387 ::= { rsvpResvEntry 17 } 1389 rsvpResvTSpecMaxTU OBJECT-TYPE 1390 SYNTAX MessageSize 1391 MAX-ACCESS read-create 1392 STATUS current 1393 DESCRIPTION 1394 "The maximum message size for this flow. The 1395 admission algorithm will reject TSpecs whose 1396 Maximum Transmission Unit, plus the interface 1397 headers, exceed the interface MTU." 1398 ::= { rsvpResvEntry 18 } 1400 rsvpResvRSpecRate OBJECT-TYPE 1401 SYNTAX BitRate 1402 UNITS "bits per second" 1403 MAX-ACCESS read-create 1404 STATUS current 1405 DESCRIPTION 1406 "If the requested service is Guaranteed, as 1407 specified by rsvpResvService, this is the 1408 clearing rate that is being requested. Other- 1409 wise, it is zero, or the agent may return 1410 noSuchValue." 1411 ::= { rsvpResvEntry 19 } 1413 rsvpResvRSpecSlack OBJECT-TYPE 1414 SYNTAX Integer32 1415 UNITS "microseconds" 1416 MAX-ACCESS read-create 1417 STATUS current 1418 DESCRIPTION 1419 "If the requested service is Guaranteed, as 1420 specified by rsvpResvService, this is the delay 1421 slack. Otherwise, it is zero, or the agent may 1422 return noSuchValue." 1423 ::= { rsvpResvEntry 20 } 1425 rsvpResvInterval OBJECT-TYPE 1426 SYNTAX RefreshInterval 1427 MAX-ACCESS read-create 1428 STATUS current 1429 DESCRIPTION 1430 "The interval between refresh messages as ad- 1431 vertised by the Next Hop." 1432 ::= { rsvpResvEntry 21 } 1434 rsvpResvScope OBJECT-TYPE 1435 SYNTAX OCTET STRING (SIZE(0..65536)) 1436 MAX-ACCESS read-create 1437 STATUS current 1438 DESCRIPTION 1440 "The contents of the scope object, displayed as 1441 an uninterpreted string of octets, including 1442 the object header. In the absence of such an 1443 object, this should be of zero length. 1445 If the length is non-zero, this contains a 1446 series of IP4 or IP6 addresses." 1447 ::= { rsvpResvEntry 22 } 1449 rsvpResvShared OBJECT-TYPE 1450 SYNTAX TruthValue 1451 MAX-ACCESS read-create 1452 STATUS current 1453 DESCRIPTION 1454 "If TRUE, a reservation shared among senders is 1455 requested. If FALSE, a reservation specific to 1456 this sender is requested." 1457 ::= { rsvpResvEntry 23 } 1459 rsvpResvExplicit OBJECT-TYPE 1460 SYNTAX TruthValue 1461 MAX-ACCESS read-create 1462 STATUS current 1463 DESCRIPTION 1464 "If TRUE, individual senders are listed using 1465 Filter Specifications. If FALSE, all senders 1466 are implicitly selected. The Scope Object will 1467 contain a list of senders that need to receive 1468 this reservation request for the purpose of 1469 routing the RESV message." 1470 ::= { rsvpResvEntry 24 } 1472 rsvpResvRSVPHop OBJECT-TYPE 1473 SYNTAX TruthValue 1474 MAX-ACCESS read-create 1475 STATUS current 1476 DESCRIPTION 1477 "If TRUE, the node believes that the previous 1478 IP hop is an RSVP hop. If FALSE, the node be- 1479 lieves that the previous IP hop may not be an 1480 RSVP hop." 1481 ::= { rsvpResvEntry 25 } 1483 rsvpResvLastChange OBJECT-TYPE 1484 SYNTAX TimeStamp 1485 MAX-ACCESS read-only 1486 STATUS current 1487 DESCRIPTION 1488 "The time of the last change in this reserva- 1489 tion request; This is either the first time it 1490 was received or the time of the most recent 1491 change in parameters." 1492 ::= { rsvpResvEntry 26 } 1494 rsvpResvPolicy OBJECT-TYPE 1495 SYNTAX OCTET STRING (SIZE(0..65536)) 1496 MAX-ACCESS read-create 1497 STATUS current 1498 DESCRIPTION 1499 "The contents of the policy object, displayed 1500 as an uninterpreted string of octets, including 1501 the object header. In the absence of such an 1502 object, this should be of zero length." 1503 ::= { rsvpResvEntry 27 } 1505 rsvpResvStatus OBJECT-TYPE 1506 SYNTAX RowStatus 1507 MAX-ACCESS read-create 1508 STATUS current 1509 DESCRIPTION 1510 "'active' for all active RESV messages. This 1511 object may be used to install static RESV in- 1512 formation or delete RESV information." 1513 ::= { rsvpResvEntry 28 } 1515 -- The RSVP Reservation Requests Forwarded Table contains the 1516 -- information displayed by receivers regarding their needs with 1517 -- respect to sessions and senders. It is in essence a list of the 1518 -- valid RESV messages that the RSVP Router or Host is sending 1519 -- to its upstream neighbors. 1521 rsvpResvFwdNewIndex OBJECT-TYPE 1522 SYNTAX TestAndIncr 1523 MAX-ACCESS read-write 1524 STATUS current 1525 DESCRIPTION 1526 "This object is used to assign values to 1527 rsvpResvFwdNumber as described in 'Textual Con- 1528 ventions for SNMPv2'. The network manager 1529 reads the object, and then writes the value 1530 back in the SET that creates a new instance of 1531 rsvpResvFwdEntry. If the SET fails with the 1532 code 'inconsistentValue', then the process must 1533 be repeated; If the SET succeeds, then the ob- 1534 ject is incremented, and the new instance is 1535 created according to the manager's directions." 1536 ::= { rsvpGenObjects 4 } 1538 rsvpResvFwdTable OBJECT-TYPE 1539 SYNTAX SEQUENCE OF RsvpResvFwdEntry 1540 MAX-ACCESS not-accessible 1541 STATUS current 1542 DESCRIPTION 1543 "Information describing the state information 1544 displayed upstream in RESV messages." 1545 ::= { rsvpObjects 4 } 1547 rsvpResvFwdEntry OBJECT-TYPE 1548 SYNTAX RsvpResvFwdEntry 1549 MAX-ACCESS not-accessible 1550 STATUS current 1551 DESCRIPTION 1552 "Information describing the state information 1553 displayed upstream in an RESV message concern- 1554 ing a single sender." 1555 INDEX { rsvpSessionNumber, rsvpResvFwdNumber } 1556 ::= { rsvpResvFwdTable 1 } 1558 RsvpResvFwdEntry ::= 1559 SEQUENCE { 1560 rsvpResvFwdNumber SessionNumber, 1561 rsvpResvFwdType SessionType, 1562 rsvpResvFwdDestAddr OCTET STRING, 1563 rsvpResvFwdSenderAddr OCTET STRING, 1564 rsvpResvFwdDestAddrLength INTEGER, 1565 rsvpResvFwdSenderAddrLength INTEGER, 1566 rsvpResvFwdProtocol Protocol, 1567 rsvpResvFwdDestPort Port, 1568 rsvpResvFwdPort Port, 1569 rsvpResvFwdHopAddr OCTET STRING, 1570 rsvpResvFwdHopLih Integer32, 1571 rsvpResvFwdInterface InterfaceIndex, 1572 rsvpResvFwdService QosService, 1573 rsvpResvFwdTSpecRate BitRate, 1574 rsvpResvFwdTSpecPeakRate BitRate, 1575 rsvpResvFwdTSpecBurst BurstSize, 1576 rsvpResvFwdTSpecMinTU MessageSize, 1577 rsvpResvFwdTSpecMaxTU MessageSize, 1578 rsvpResvFwdRSpecRate BitRate, 1579 rsvpResvFwdRSpecSlack Integer32, 1580 rsvpResvFwdInterval RefreshInterval, 1581 rsvpResvFwdScope OCTET STRING, 1582 rsvpResvFwdShared TruthValue, 1583 rsvpResvFwdExplicit TruthValue, 1584 rsvpResvFwdRSVPHop TruthValue, 1585 rsvpResvFwdLastChange TimeStamp, 1586 rsvpResvFwdPolicy OCTET STRING, 1587 rsvpResvFwdStatus RowStatus 1588 } 1590 rsvpResvFwdNumber OBJECT-TYPE 1591 SYNTAX SessionNumber 1592 MAX-ACCESS not-accessible 1593 STATUS current 1594 DESCRIPTION 1595 "The number of this reservation request. This 1596 is for SNMP Indexing purposes only and has no 1597 relation to any protocol vaalue." 1598 ::= { rsvpResvFwdEntry 1 } 1600 rsvpResvFwdType OBJECT-TYPE 1601 SYNTAX SessionType 1602 MAX-ACCESS read-only 1603 STATUS current 1604 DESCRIPTION 1605 "The type of session (IP4, IP6, IP6 with flow 1606 information, etc)." 1607 ::= { rsvpResvFwdEntry 2 } 1609 rsvpResvFwdDestAddr OBJECT-TYPE 1610 SYNTAX OCTET STRING (SIZE(4..16)) 1611 MAX-ACCESS read-only 1612 STATUS current 1613 DESCRIPTION 1614 "The destination address used by all senders in 1615 this session. This object may not be changed 1616 when the value of the RowStatus object is 'ac- 1617 tive'." 1618 ::= { rsvpResvFwdEntry 3 } 1620 rsvpResvFwdSenderAddr OBJECT-TYPE 1621 SYNTAX OCTET STRING (SIZE(4..16)) 1622 MAX-ACCESS read-only 1623 STATUS current 1624 DESCRIPTION 1625 "The source address of the sender selected by 1626 this reservation. The value of all zeroes in- 1627 dicates 'all senders'. This object may not be 1628 changed when the value of the RowStatus object 1629 is 'active'." 1630 ::= { rsvpResvFwdEntry 4 } 1632 rsvpResvFwdDestAddrLength OBJECT-TYPE 1633 SYNTAX INTEGER(0..128) 1634 MAX-ACCESS read-only 1635 STATUS current 1636 DESCRIPTION 1637 "The length of the destination address in bits. 1638 This is the CIDR Prefix Length, which for IP4 1639 hosts and multicast addresses is 32 bits. This 1640 object may not be changed when the value of the 1641 RowStatus object is 'active'." 1642 ::= { rsvpResvFwdEntry 5 } 1644 rsvpResvFwdSenderAddrLength OBJECT-TYPE 1645 SYNTAX INTEGER(0..128) 1646 MAX-ACCESS read-only 1647 STATUS current 1648 DESCRIPTION 1649 "The length of the sender's address in bits. 1650 This is the CIDR Prefix Length, which for IP4 1651 hosts and multicast addresses is 32 bits. This 1652 object may not be changed when the value of the 1653 RowStatus object is 'active'." 1654 ::= { rsvpResvFwdEntry 6 } 1656 rsvpResvFwdProtocol OBJECT-TYPE 1657 SYNTAX Protocol 1658 MAX-ACCESS read-only 1659 STATUS current 1660 DESCRIPTION 1661 "The IP Protocol used by a session. for secure 1662 sessions, this indicates IP Security. This ob- 1663 ject may not be changed when the value of the 1664 RowStatus object is 'active'." 1665 ::= { rsvpResvFwdEntry 7 } 1667 rsvpResvFwdDestPort OBJECT-TYPE 1668 SYNTAX Port 1669 MAX-ACCESS read-only 1670 STATUS current 1671 DESCRIPTION 1672 "The UDP or TCP port number used as a destina- 1673 tion port for all senders in this session. If 1674 the IP protocol in use, specified by 1675 rsvpResvFwdProtocol, is 50 (ESP) or 51 (AH), 1676 this represents a virtual destination port 1677 number. A value of zero indicates that the IP 1678 protocol in use does not have ports. This ob- 1679 ject may not be changed when the value of the 1680 RowStatus object is 'active'." 1681 ::= { rsvpResvFwdEntry 8 } 1683 rsvpResvFwdPort OBJECT-TYPE 1684 SYNTAX Port 1685 MAX-ACCESS read-only 1686 STATUS current 1687 DESCRIPTION 1688 "The UDP or TCP port number used as a source 1689 port for this sender in this session. If the 1690 IP protocol in use, specified by 1691 rsvpResvFwdProtocol is 50 (ESP) or 51 (AH), 1692 this represents a generalized port identifier 1693 (GPI). A value of zero indicates that the IP 1694 protocol in use does not have ports. This ob- 1695 ject may not be changed when the value of the 1696 RowStatus object is 'active'." 1697 ::= { rsvpResvFwdEntry 9 } 1699 rsvpResvFwdHopAddr OBJECT-TYPE 1700 SYNTAX OCTET STRING (SIZE(4..16)) 1701 MAX-ACCESS read-only 1702 STATUS current 1703 DESCRIPTION 1704 "The address of the (previous) RSVP that will 1705 receive this message." 1706 ::= { rsvpResvFwdEntry 10 } 1708 rsvpResvFwdHopLih OBJECT-TYPE 1709 SYNTAX Integer32 1710 MAX-ACCESS read-only 1711 STATUS current 1712 DESCRIPTION 1713 "The Logical Interface Handle sent to the (pre- 1714 vious) RSVP that will receive this message." 1715 ::= { rsvpResvFwdEntry 11 } 1717 rsvpResvFwdInterface OBJECT-TYPE 1718 SYNTAX InterfaceIndex 1719 MAX-ACCESS read-only 1720 STATUS current 1721 DESCRIPTION 1722 "The ifIndex value of the interface on which 1723 this RESV message was most recently sent." 1724 ::= { rsvpResvFwdEntry 12 } 1726 rsvpResvFwdService OBJECT-TYPE 1727 SYNTAX QosService 1728 MAX-ACCESS read-only 1729 STATUS current 1730 DESCRIPTION 1731 "The QoS Service classification requested." 1732 ::= { rsvpResvFwdEntry 13 } 1734 rsvpResvFwdTSpecRate OBJECT-TYPE 1735 SYNTAX BitRate 1736 UNITS "bits per second" 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "The Average Bit Rate of the sender's data 1741 stream. Within a transmission burst, the ar- 1742 rival rate may be as fast as rsvpResvFwdTSpec- 1743 PeakRate (if supported by the service model); 1744 however, averaged across two or more burst in- 1745 tervals, the rate should not exceed 1746 rsvpResvFwdTSpecRate. 1748 Note that this is a prediction, often based on 1749 the general capability of a type of codec or 1750 particular encoding; the measured average rate 1751 may be significantly lower." 1752 ::= { rsvpResvFwdEntry 14 } 1754 rsvpResvFwdTSpecPeakRate OBJECT-TYPE 1755 SYNTAX BitRate 1756 UNITS "bits per second" 1757 MAX-ACCESS read-only 1758 STATUS current 1759 DESCRIPTION 1760 "The Peak Bit Rate of the sender's data stream 1761 Traffic arrival is not expected to exceed this 1762 rate at any time, apart from the effects of 1763 jitter in the network. If not specified in the 1764 TSpec, this returns zero or noSuchValue." 1765 ::= { rsvpResvFwdEntry 15 } 1767 rsvpResvFwdTSpecBurst OBJECT-TYPE 1768 SYNTAX BurstSize 1769 UNITS "bytes" 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1773 "The size of the largest burst expected from 1774 the sender at a time. 1776 If this is less than the sender's advertised 1777 burst size, the receiver is asking the network 1778 to provide flow pacing beyond what would be 1779 provided under normal circumstances. Such pac- 1780 ing is at the network's option." 1781 ::= { rsvpResvFwdEntry 16 } 1783 rsvpResvFwdTSpecMinTU OBJECT-TYPE 1784 SYNTAX MessageSize 1785 MAX-ACCESS read-only 1786 STATUS current 1787 DESCRIPTION 1788 "The minimum message size for this flow. The 1789 policing algorithm will treat smaller messages 1790 as though they are this size." 1791 ::= { rsvpResvFwdEntry 17 } 1793 rsvpResvFwdTSpecMaxTU OBJECT-TYPE 1794 SYNTAX MessageSize 1795 MAX-ACCESS read-only 1796 STATUS current 1797 DESCRIPTION 1798 "The maximum message size for this flow. The 1799 admission algorithm will reject TSpecs whose 1800 Maximum Transmission Unit, plus the interface 1801 headers, exceed the interface MTU." 1802 ::= { rsvpResvFwdEntry 18 } 1804 rsvpResvFwdRSpecRate OBJECT-TYPE 1805 SYNTAX BitRate 1806 UNITS "bytes per second" 1807 MAX-ACCESS read-only 1808 STATUS current 1809 DESCRIPTION 1810 "If the requested service is Guaranteed, as 1811 specified by rsvpResvService, this is the 1812 clearing rate that is being requested. Other- 1813 wise, it is zero, or the agent may return 1814 noSuchValue." 1815 ::= { rsvpResvFwdEntry 19 } 1817 rsvpResvFwdRSpecSlack OBJECT-TYPE 1818 SYNTAX Integer32 1819 UNITS "microseconds" 1820 MAX-ACCESS read-only 1821 STATUS current 1822 DESCRIPTION 1823 "If the requested service is Guaranteed, as 1824 specified by rsvpResvService, this is the delay 1825 slack. Otherwise, it is zero, or the agent may 1826 return noSuchValue." 1827 ::= { rsvpResvFwdEntry 20 } 1829 rsvpResvFwdInterval OBJECT-TYPE 1830 SYNTAX RefreshInterval 1831 MAX-ACCESS read-only 1832 STATUS current 1833 DESCRIPTION 1834 "The interval between refresh messages adver- 1835 tised to the Previous Hop." 1836 ::= { rsvpResvFwdEntry 21 } 1838 rsvpResvFwdScope OBJECT-TYPE 1839 SYNTAX OCTET STRING (SIZE(0..65536)) 1840 MAX-ACCESS read-only 1841 STATUS current 1842 DESCRIPTION 1843 "The contents of the scope object, displayed as 1844 an uninterpreted string of octets, including 1845 the object header. In the absence of such an 1846 object, this should be of zero length." 1847 ::= { rsvpResvFwdEntry 22 } 1849 rsvpResvFwdShared OBJECT-TYPE 1850 SYNTAX TruthValue 1851 MAX-ACCESS read-only 1852 STATUS current 1853 DESCRIPTION 1854 "If TRUE, a reservation shared among senders is 1855 requested. If FALSE, a reservation specific to 1856 this sender is requested." 1857 ::= { rsvpResvFwdEntry 23 } 1859 rsvpResvFwdExplicit OBJECT-TYPE 1860 SYNTAX TruthValue 1861 MAX-ACCESS read-only 1862 STATUS current 1863 DESCRIPTION 1864 "If TRUE, individual senders are listed using 1865 Filter Specifications. If FALSE, all senders 1866 are implicitly selected. The Scope Object will 1867 contain a list of senders that need to receive 1868 this reservation request for the purpose of 1869 routing the RESV message." 1870 ::= { rsvpResvFwdEntry 24 } 1872 rsvpResvFwdRSVPHop OBJECT-TYPE 1873 SYNTAX TruthValue 1874 MAX-ACCESS read-only 1875 STATUS current 1876 DESCRIPTION 1877 "If TRUE, the node believes that the next IP 1878 hop is an RSVP hop. If FALSE, the node be- 1879 lieves that the next IP hop may not be an RSVP 1880 hop." 1881 ::= { rsvpResvFwdEntry 25 } 1883 rsvpResvFwdLastChange OBJECT-TYPE 1884 SYNTAX TimeStamp 1885 MAX-ACCESS read-only 1886 STATUS current 1887 DESCRIPTION 1888 "The time of the last change in this request; 1889 This is either the first time it was sent or 1890 the time of the most recent change in parame- 1891 ters." 1892 ::= { rsvpResvFwdEntry 26 } 1894 rsvpResvFwdPolicy OBJECT-TYPE 1895 SYNTAX OCTET STRING (SIZE(0..65536)) 1896 MAX-ACCESS read-only 1897 STATUS current 1898 DESCRIPTION 1899 "The contents of the policy object, displayed 1900 as an uninterpreted string of octets, including 1901 the object header. In the absence of such an 1902 object, this should be of zero length." 1903 ::= { rsvpResvFwdEntry 27 } 1905 rsvpResvFwdStatus OBJECT-TYPE 1906 SYNTAX RowStatus 1907 MAX-ACCESS read-write 1908 STATUS current 1909 DESCRIPTION 1910 "'active' for all active RESV messages. This 1911 object may be used to delete RESV information." 1912 ::= { rsvpResvFwdEntry 28 } 1914 -- The RSVP Interface Attributes Database contains the 1915 -- RSVP-specific information for an interface. Information 1916 -- that is shared with other reservation procedures such 1917 -- as ST-II is in the Integrated Interface Attributes 1918 -- Database. 1920 rsvpIfTable OBJECT-TYPE 1921 SYNTAX SEQUENCE OF RsvpIfEntry 1922 MAX-ACCESS not-accessible 1923 STATUS current 1924 DESCRIPTION 1925 "The RSVP-specific attributes of the system's 1926 interfaces." 1927 ::= { rsvpObjects 6 } 1929 rsvpIfEntry OBJECT-TYPE 1930 SYNTAX RsvpIfEntry 1931 MAX-ACCESS not-accessible 1932 STATUS current 1933 DESCRIPTION 1934 "The RSVP-specific attributes of the a given 1935 interface." 1936 INDEX { ifIndex } 1937 ::= { rsvpIfTable 1 } 1939 RsvpIfEntry ::= 1940 SEQUENCE { 1941 rsvpIfUdpNbrs Gauge32, 1942 rsvpIfIpNbrs Gauge32, 1943 rsvpIfNbrs Gauge32, 1944 rsvpIfEnabled TruthValue, 1945 rsvpIfUdpRequired TruthValue, 1946 rsvpIfRefreshBlockadeMultiple INTEGER, 1947 rsvpIfRefreshMultiple INTEGER, 1948 rsvpIfTTL INTEGER, 1949 rsvpIfRefreshInterval TimeInterval, 1950 rsvpIfRouteDelay TimeInterval, 1951 rsvpIfStatus RowStatus 1952 } 1953 rsvpIfUdpNbrs OBJECT-TYPE 1954 SYNTAX Gauge32 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 "The number of neighbors perceived to be using 1959 only the RSVP UDP Encapsulation." 1960 ::= { rsvpIfEntry 1 } 1962 rsvpIfIpNbrs OBJECT-TYPE 1963 SYNTAX Gauge32 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "The number of neighbors perceived to be using 1968 only the RSVP IP Encapsulation." 1969 ::= { rsvpIfEntry 2 } 1971 rsvpIfNbrs OBJECT-TYPE 1972 SYNTAX Gauge32 1973 MAX-ACCESS read-only 1974 STATUS current 1975 DESCRIPTION 1976 "The number of neighbors currently perceived; 1977 this will exceed rsvpIfIpNbrs + rsvpIfUdpNbrs 1978 by the number of neighbors using both encapsu- 1979 lations." 1980 ::= { rsvpIfEntry 3 } 1982 rsvpIfRefreshBlockadeMultiple OBJECT-TYPE 1983 SYNTAX INTEGER (1..65536) 1984 MAX-ACCESS read-create 1985 STATUS current 1986 DESCRIPTION 1987 "The value of the RSVP value 'Kb', Which is the 1988 minimum number of refresh intervals that 1989 blockade state will last once entered." 1990 DEFVAL { 4 } 1991 ::= { rsvpIfEntry 4 } 1993 rsvpIfRefreshMultiple OBJECT-TYPE 1994 SYNTAX INTEGER (1..65536) 1995 MAX-ACCESS read-create 1996 STATUS current 1997 DESCRIPTION 1998 "The value of the RSVP value 'K', which is the 1999 number of refresh intervals which must elapse 2000 (minimum) before a PATH or RESV message which 2001 is not being refreshed will be aged out." 2002 DEFVAL { 3 } 2003 ::= { rsvpIfEntry 5 } 2005 rsvpIfTTL OBJECT-TYPE 2006 SYNTAX INTEGER (0..255) 2007 MAX-ACCESS read-create 2008 STATUS current 2009 DESCRIPTION 2010 "The value of SEND_TTL used on this interface 2011 for messages this node originates. If set to 2012 zero, the node determines the TTL via other 2013 means." 2014 DEFVAL { 0 } -- which is to say, no override 2015 ::= { rsvpIfEntry 6 } 2017 rsvpIfRefreshInterval OBJECT-TYPE 2018 SYNTAX TimeInterval 2019 UNITS "hundredths of a second" 2020 MAX-ACCESS read-create 2021 STATUS current 2022 DESCRIPTION 2023 "The value of the RSVP value 'R', which is the 2024 minimum period between refresh transmissions of 2025 a given PATH or RESV message on an interface." 2026 DEFVAL { 3000 } -- 30 seconds 2027 ::= { rsvpIfEntry 7 } 2029 rsvpIfRouteDelay OBJECT-TYPE 2030 SYNTAX TimeInterval 2031 UNITS "hundredths of a second" 2032 MAX-ACCESS read-create 2033 STATUS current 2034 DESCRIPTION 2035 "The approximate period from the time a route 2036 is changed to the time a resulting message ap- 2037 pears on the interface." 2038 DEFVAL { 200 } -- 2 seconds 2039 ::= { rsvpIfEntry 8 } 2041 rsvpIfEnabled OBJECT-TYPE 2042 SYNTAX TruthValue 2043 MAX-ACCESS read-create 2044 STATUS current 2045 DESCRIPTION 2046 "If TRUE, RSVP is enabled on this Interface. 2047 If FALSE, RSVP is not enabled on this inter- 2048 face." 2049 ::= { rsvpIfEntry 9 } 2051 rsvpIfUdpRequired OBJECT-TYPE 2052 SYNTAX TruthValue 2053 MAX-ACCESS read-create 2054 STATUS current 2055 DESCRIPTION 2056 "If TRUE, manual configuration forces the use 2057 of UDP encapsulation on the interface. If 2058 FALSE, UDP encapsulation is only used if rsvpI- 2059 fUdpNbrs is not zero." 2061 ::= { rsvpIfEntry 10 } 2063 rsvpIfStatus OBJECT-TYPE 2064 SYNTAX RowStatus 2065 MAX-ACCESS read-create 2066 STATUS current 2067 DESCRIPTION 2068 "'active' on interfaces that are configured for 2069 RSVP." 2070 ::= { rsvpIfEntry 11 } 2072 -- The RSVP Neighbor Database lists the neighbors the RSVP 2073 -- process currently is receiving messages from. 2075 rsvpNbrTable OBJECT-TYPE 2076 SYNTAX SEQUENCE OF RsvpNbrEntry 2077 MAX-ACCESS not-accessible 2078 STATUS current 2079 DESCRIPTION 2080 "Information describing the Neighbors of an 2081 RSVP system." 2082 ::= { rsvpObjects 7 } 2084 rsvpNbrEntry OBJECT-TYPE 2085 SYNTAX RsvpNbrEntry 2086 MAX-ACCESS not-accessible 2087 STATUS current 2088 DESCRIPTION 2089 "Information describing a single RSVP Neigh- 2090 bor." 2091 INDEX { ifIndex, rsvpNbrAddress } 2092 ::= { rsvpNbrTable 1 } 2094 RsvpNbrEntry ::= 2095 SEQUENCE { 2096 rsvpNbrAddress OCTET STRING, 2097 rsvpNbrProtocol RsvpEncapsulation, 2098 rsvpNbrStatus RowStatus 2099 } 2101 rsvpNbrAddress OBJECT-TYPE 2102 SYNTAX OCTET STRING (SIZE(4..16)) 2103 MAX-ACCESS not-accessible 2104 STATUS current 2105 DESCRIPTION 2106 "The IP4 or IP6 Address used by this neighbor. 2107 This object may not be changed when the value 2108 of the RowStatus object is 'active'." 2109 ::= { rsvpNbrEntry 1 } 2111 rsvpNbrProtocol OBJECT-TYPE 2112 SYNTAX RsvpEncapsulation 2113 MAX-ACCESS read-create 2114 STATUS current 2115 DESCRIPTION 2116 "The encapsulation being used by this neigh- 2117 bor." 2118 ::= { rsvpNbrEntry 2 } 2120 rsvpNbrStatus OBJECT-TYPE 2121 SYNTAX RowStatus 2122 MAX-ACCESS read-create 2123 STATUS current 2124 DESCRIPTION 2125 "'active' for all neighbors. This object may 2126 be used to configure neighbors. In the pres- 2127 ence of configured neighbors, the implementa- 2128 tion may (but is not required to) limit the set 2129 of valid neighbors to those configured." 2130 ::= { rsvpNbrEntry 3 } 2132 -- 2133 -- Notifications used to signal events 2134 -- 2136 newFlow NOTIFICATION-TYPE 2137 OBJECTS { 2138 intSrvFlowStatus, rsvpSessionDestAddr, 2139 rsvpResvFwdStatus, rsvpResvStatus, rsvpSenderStatus 2140 } 2141 STATUS current 2142 DESCRIPTION 2143 "The newFlow trap indicates that the originat- 2144 ing system has installed a new flow in its 2145 classifier, or (when reservation authorization 2146 is in view) is prepared to install such a flow 2147 in the classifier and is requesting authoriza- 2148 tion. The objects included with the Notifica- 2149 tion may be used to read further information 2150 using the Integrated Services and RSVP MIBs. 2151 Authorization or non-authorization may be 2152 enacted by a write to the variable intSrvFlowS- 2153 tatus." 2154 ::= { rsvpNotifications 1 } 2156 lostFlow NOTIFICATION-TYPE 2157 OBJECTS { 2158 intSrvFlowStatus, rsvpSessionDestAddr, 2159 rsvpResvFwdStatus, rsvpResvStatus, rsvpSenderStatus 2160 } 2161 STATUS current 2162 DESCRIPTION 2163 "The lostFlow trap indicates that the originat- 2164 ing system has removed a flow from its classif- 2165 ier." 2166 ::= { rsvpNotifications 2 } 2168 -- conformance information 2170 rsvpGroups OBJECT IDENTIFIER ::= { rsvpConformance 1 } 2171 rsvpCompliances OBJECT IDENTIFIER ::= { rsvpConformance 2 } 2173 -- compliance statements 2174 rsvpCompliance MODULE-COMPLIANCE 2175 STATUS current 2176 DESCRIPTION 2177 "The compliance statement. Note that the im- 2178 plementation of this module requires implemen- 2179 tation of the Integrated Services MIB as well." 2180 MODULE -- this module 2181 MANDATORY-GROUPS { 2182 rsvpSessionGroup, rsvpSenderGroup, rsvpResvGroup, 2183 rsvpIfGroup, rsvpNbrGroup 2184 } 2186 GROUP rsvpResvFwdGroup 2187 DESCRIPTION 2188 "The Reservation Requests table is appropriate 2189 in implementations that store upstream reserva- 2190 tion messages, but not appropriate in implemen- 2191 tations which calculate them on each transmis- 2192 sion." 2194 GROUP rsvpNotificationGroup 2195 DESCRIPTION 2196 "The notifications in this module are required 2197 when the MIB is used to implement RSVP Policy." 2199 OBJECT rsvpSenderType 2200 MIN-ACCESS read-only 2201 DESCRIPTION 2202 "read-create access is not required. This may be 2203 read-only." 2205 OBJECT rsvpSenderDestAddr 2206 MIN-ACCESS read-only 2207 DESCRIPTION 2208 "read-create access is not required. This may be 2209 read-only." 2211 OBJECT rsvpSenderAddr 2212 MIN-ACCESS read-only 2213 DESCRIPTION 2214 "read-create access is not required. This may be 2215 read-only." 2217 OBJECT rsvpSenderDestAddrLength 2218 MIN-ACCESS read-only 2219 DESCRIPTION 2220 "read-create access is not required. This may be 2221 read-only." 2223 OBJECT rsvpSenderAddrLength 2224 MIN-ACCESS read-only 2225 DESCRIPTION 2226 "read-create access is not required. This may be 2227 read-only." 2229 OBJECT rsvpSenderProtocol 2230 MIN-ACCESS read-only 2231 DESCRIPTION 2232 "read-create access is not required. This may be 2233 read-only." 2235 OBJECT rsvpSenderDestPort 2236 MIN-ACCESS read-only 2237 DESCRIPTION 2238 "read-create access is not required. This may be 2239 read-only." 2241 OBJECT rsvpSenderPort 2242 MIN-ACCESS read-only 2243 DESCRIPTION 2244 "read-create access is not required. This may be 2245 read-only." 2247 OBJECT rsvpSenderHopAddr 2248 MIN-ACCESS read-only 2249 DESCRIPTION 2250 "read-create access is not required. This may be 2251 read-only." 2253 OBJECT rsvpSenderHopLih 2254 MIN-ACCESS read-only 2255 DESCRIPTION 2256 "read-create access is not required. This may be 2257 read-only." 2259 OBJECT rsvpSenderInterface 2260 MIN-ACCESS read-only 2261 DESCRIPTION 2262 "read-create access is not required. This may be 2263 read-only." 2265 OBJECT rsvpSenderTSpecRate 2266 MIN-ACCESS read-only 2267 DESCRIPTION 2268 "read-create access is not required. This may be 2269 read-only." 2271 OBJECT rsvpSenderTSpecPeakRate 2272 MIN-ACCESS read-only 2273 DESCRIPTION 2274 "read-create access is not required. This may be 2275 read-only." 2277 OBJECT rsvpSenderTSpecBurst 2278 MIN-ACCESS read-only 2279 DESCRIPTION 2280 "read-create access is not required. This may be 2281 read-only." 2283 OBJECT rsvpSenderTSpecMinTU 2284 MIN-ACCESS read-only 2285 DESCRIPTION 2286 "read-create access is not required. This may be 2287 read-only." 2289 OBJECT rsvpSenderTSpecMaxTU 2290 MIN-ACCESS read-only 2291 DESCRIPTION 2292 "read-create access is not required. This may be 2293 read-only." 2295 OBJECT rsvpSenderInterval 2296 MIN-ACCESS read-only 2297 DESCRIPTION 2298 "read-create access is not required. This may be 2299 read-only." 2301 OBJECT rsvpSenderRSVPHop 2302 MIN-ACCESS read-only 2303 DESCRIPTION 2304 "read-create access is not required. This may be 2305 read-only." 2307 OBJECT rsvpSenderPolicy 2308 MIN-ACCESS read-only 2309 DESCRIPTION 2310 "read-create access is not required. This may be 2311 read-only." 2313 OBJECT rsvpSenderAdspecBreak 2314 MIN-ACCESS read-only 2315 DESCRIPTION 2316 "read-create access is not required. This may be 2317 read-only." 2319 OBJECT rsvpSenderAdspecHopCount 2320 MIN-ACCESS read-only 2321 DESCRIPTION 2322 "read-create access is not required. This may be 2323 read-only." 2325 OBJECT rsvpSenderAdspecPathBw 2326 MIN-ACCESS read-only 2327 DESCRIPTION 2328 "read-create access is not required. This may be 2329 read-only." 2331 OBJECT rsvpSenderAdspecMinLatency 2332 MIN-ACCESS read-only 2333 DESCRIPTION 2334 "read-create access is not required. This may be 2335 read-only." 2337 OBJECT rsvpSenderAdspecMtu 2338 MIN-ACCESS read-only 2339 DESCRIPTION 2340 "read-create access is not required. This may be 2341 read-only." 2343 OBJECT rsvpSenderAdspecGuaranteedSvc 2344 MIN-ACCESS read-only 2345 DESCRIPTION 2346 "read-create access is not required. This may be 2347 read-only." 2349 OBJECT rsvpSenderAdspecGuaranteedBreak 2350 MIN-ACCESS read-only 2351 DESCRIPTION 2352 "read-create access is not required. This may be 2353 read-only." 2355 OBJECT rsvpSenderAdspecGuaranteedCtot 2356 MIN-ACCESS read-only 2357 DESCRIPTION 2358 "read-create access is not required. This may be 2359 read-only." 2361 OBJECT rsvpSenderAdspecGuaranteedDtot 2362 MIN-ACCESS read-only 2363 DESCRIPTION 2364 "read-create access is not required. This may be 2365 read-only." 2367 OBJECT rsvpSenderAdspecGuaranteedCsum 2368 MIN-ACCESS read-only 2369 DESCRIPTION 2370 "read-create access is not required. This may be 2371 read-only." 2373 OBJECT rsvpSenderAdspecGuaranteedDsum 2374 MIN-ACCESS read-only 2375 DESCRIPTION 2376 "read-create access is not required. This may be 2377 read-only." 2379 OBJECT rsvpSenderAdspecGuaranteedHopCount 2380 MIN-ACCESS read-only 2381 DESCRIPTION 2382 "read-create access is not required. This may be 2383 read-only." 2385 OBJECT rsvpSenderAdspecGuaranteedPathBw 2386 MIN-ACCESS read-only 2387 DESCRIPTION 2388 "read-create access is not required. This may be 2389 read-only." 2391 OBJECT rsvpSenderAdspecGuaranteedMinLatency 2392 MIN-ACCESS read-only 2393 DESCRIPTION 2394 "read-create access is not required. This may be 2395 read-only." 2397 OBJECT rsvpSenderAdspecGuaranteedMtu 2398 MIN-ACCESS read-only 2399 DESCRIPTION 2400 "read-create access is not required. This may be 2401 read-only." 2403 OBJECT rsvpSenderAdspecCtrlLoadSvc 2404 MIN-ACCESS read-only 2405 DESCRIPTION 2406 "read-create access is not required. This may be 2407 read-only." 2409 OBJECT rsvpSenderAdspecCtrlLoadBreak 2410 MIN-ACCESS read-only 2411 DESCRIPTION 2412 "read-create access is not required. This may be 2413 read-only." 2415 OBJECT rsvpSenderAdspecCtrlLoadHopCount 2416 MIN-ACCESS read-only 2417 DESCRIPTION 2418 "read-create access is not required. This may be 2419 read-only." 2421 OBJECT rsvpSenderAdspecCtrlLoadPathBw 2422 MIN-ACCESS read-only 2423 DESCRIPTION 2424 "read-create access is not required. This may be 2425 read-only." 2427 OBJECT rsvpSenderAdspecCtrlLoadMinLatency 2428 MIN-ACCESS read-only 2429 DESCRIPTION 2430 "read-create access is not required. This may be 2431 read-only." 2433 OBJECT rsvpSenderAdspecCtrlLoadMtu 2434 MIN-ACCESS read-only 2435 DESCRIPTION 2436 "read-create access is not required. This may be 2437 read-only." 2439 OBJECT rsvpSenderStatus 2440 MIN-ACCESS read-only 2441 DESCRIPTION 2442 "read-create access is not required. This may be 2443 read-only." 2445 OBJECT rsvpResvType 2446 MIN-ACCESS read-only 2447 DESCRIPTION 2448 "read-create access is not required. This may be 2449 read-only." 2451 OBJECT rsvpResvDestAddr 2452 MIN-ACCESS read-only 2453 DESCRIPTION 2454 "read-create access is not required. This may be 2455 read-only." 2457 OBJECT rsvpResvSenderAddr 2458 MIN-ACCESS read-only 2459 DESCRIPTION 2460 "read-create access is not required. This may be 2461 read-only." 2463 OBJECT rsvpResvDestAddrLength 2464 MIN-ACCESS read-only 2465 DESCRIPTION 2466 "read-create access is not required. This may be 2467 read-only." 2469 OBJECT rsvpResvSenderAddrLength 2470 MIN-ACCESS read-only 2471 DESCRIPTION 2472 "read-create access is not required. This may be 2473 read-only." 2475 OBJECT rsvpResvProtocol 2476 MIN-ACCESS read-only 2477 DESCRIPTION 2478 "read-create access is not required. This may be 2479 read-only." 2481 OBJECT rsvpResvDestPort 2482 MIN-ACCESS read-only 2483 DESCRIPTION 2484 "read-create access is not required. This may be 2485 read-only." 2487 OBJECT rsvpResvPort 2488 MIN-ACCESS read-only 2489 DESCRIPTION 2490 "read-create access is not required. This may be 2491 read-only." 2493 OBJECT rsvpResvHopAddr 2494 MIN-ACCESS read-only 2495 DESCRIPTION 2496 "read-create access is not required. This may be 2497 read-only." 2499 OBJECT rsvpResvHopLih 2500 MIN-ACCESS read-only 2501 DESCRIPTION 2502 "read-create access is not required. This may be 2503 read-only." 2505 OBJECT rsvpResvInterface 2506 MIN-ACCESS read-only 2507 DESCRIPTION 2508 "read-create access is not required. This may be 2509 read-only." 2511 OBJECT rsvpResvService 2512 MIN-ACCESS read-only 2513 DESCRIPTION 2514 "read-create access is not required. This may be 2515 read-only." 2517 OBJECT rsvpResvTSpecRate 2518 MIN-ACCESS read-only 2519 DESCRIPTION 2520 "read-create access is not required. This may be 2521 read-only." 2523 OBJECT rsvpResvTSpecPeakRate 2524 MIN-ACCESS read-only 2525 DESCRIPTION 2526 "read-create access is not required. This may be 2527 read-only." 2529 OBJECT rsvpResvTSpecBurst 2530 MIN-ACCESS read-only 2531 DESCRIPTION 2532 "read-create access is not required. This may be 2533 read-only." 2535 OBJECT rsvpResvTSpecMinTU 2536 MIN-ACCESS read-only 2537 DESCRIPTION 2538 "read-create access is not required. This may be 2539 read-only." 2541 OBJECT rsvpResvTSpecMaxTU 2542 MIN-ACCESS read-only 2543 DESCRIPTION 2544 "read-create access is not required. This may be 2545 read-only." 2547 OBJECT rsvpResvRSpecRate 2548 MIN-ACCESS read-only 2549 DESCRIPTION 2550 "read-create access is not required. This may be 2551 read-only." 2553 OBJECT rsvpResvRSpecSlack 2554 MIN-ACCESS read-only 2555 DESCRIPTION 2556 "read-create access is not required. This may be 2557 read-only." 2559 OBJECT rsvpResvInterval 2560 MIN-ACCESS read-only 2561 DESCRIPTION 2562 "read-create access is not required. This may be 2563 read-only." 2565 OBJECT rsvpResvScope 2566 MIN-ACCESS read-only 2567 DESCRIPTION 2568 "read-create access is not required. This may be 2569 read-only." 2571 OBJECT rsvpResvShared 2572 MIN-ACCESS read-only 2573 DESCRIPTION 2574 "read-create access is not required. This may be 2575 read-only." 2577 OBJECT rsvpResvExplicit 2578 MIN-ACCESS read-only 2579 DESCRIPTION 2580 "read-create access is not required. This may be 2581 read-only." 2583 OBJECT rsvpResvRSVPHop 2584 MIN-ACCESS read-only 2585 DESCRIPTION 2586 "read-create access is not required. This may be 2587 read-only." 2589 OBJECT rsvpResvPolicy 2590 MIN-ACCESS read-only 2591 DESCRIPTION 2592 "read-create access is not required. This may be 2593 read-only." 2595 OBJECT rsvpResvStatus 2596 MIN-ACCESS read-only 2597 DESCRIPTION 2598 "read-create access is not required. This may be 2599 read-only." 2601 OBJECT rsvpResvFwdStatus 2602 MIN-ACCESS read-only 2603 DESCRIPTION 2604 "read-create access is not required. This may be 2605 read-only." 2607 ::= { rsvpCompliances 1 } 2609 rsvpSessionGroup OBJECT-GROUP 2610 OBJECTS { 2611 rsvpSessionType, rsvpSessionDestAddr, 2612 rsvpSessionDestAddrLength, rsvpSessionProtocol, 2613 rsvpSessionPort, rsvpSessionSenders, rsvpSessionReceivers, 2614 rsvpSessionRequests 2615 } 2616 STATUS current 2617 DESCRIPTION 2618 "These objects are required for RSVP Systems." 2619 ::= { rsvpGroups 1 } 2621 rsvpSenderGroup OBJECT-GROUP 2622 OBJECTS { 2623 rsvpSenderType, rsvpSenderDestAddr, rsvpSenderAddr, 2624 rsvpSenderDestAddrLength, rsvpSenderAddrLength, 2625 rsvpSenderProtocol, rsvpSenderDestPort, rsvpSenderPort, 2626 rsvpSenderHopAddr, rsvpSenderHopLih, rsvpSenderInterface, 2627 rsvpSenderTSpecRate, rsvpSenderTSpecPeakRate, 2628 rsvpSenderTSpecBurst, rsvpSenderTSpecMinTU, 2629 rsvpSenderTSpecMaxTU, rsvpSenderInterval, rsvpSenderLastChange, 2630 rsvpSenderStatus, rsvpSenderRSVPHop, rsvpSenderPolicy, 2631 rsvpSenderAdspecBreak, rsvpSenderAdspecHopCount, 2632 rsvpSenderAdspecPathBw, rsvpSenderAdspecMinLatency, 2633 rsvpSenderAdspecMtu, rsvpSenderAdspecGuaranteedSvc, 2634 rsvpSenderAdspecGuaranteedBreak, 2635 rsvpSenderAdspecGuaranteedCtot, rsvpSenderAdspecGuaranteedDtot, 2636 rsvpSenderAdspecGuaranteedCsum, rsvpSenderAdspecGuaranteedDsum, 2637 rsvpSenderAdspecGuaranteedHopCount, 2638 rsvpSenderAdspecGuaranteedPathBw, 2639 rsvpSenderAdspecGuaranteedMinLatency, 2640 rsvpSenderAdspecGuaranteedMtu, rsvpSenderAdspecCtrlLoadSvc, 2641 rsvpSenderAdspecCtrlLoadBreak, 2642 rsvpSenderAdspecCtrlLoadHopCount, 2643 rsvpSenderAdspecCtrlLoadPathBw, 2644 rsvpSenderAdspecCtrlLoadMinLatency, 2645 rsvpSenderAdspecCtrlLoadMtu, rsvpSenderNewIndex 2646 } 2647 STATUS current 2648 DESCRIPTION 2649 "These objects are required for RSVP Systems." 2650 ::= { rsvpGroups 2 } 2652 rsvpResvGroup OBJECT-GROUP 2653 OBJECTS { 2654 rsvpResvType, rsvpResvDestAddr, rsvpResvSenderAddr, 2655 rsvpResvDestAddrLength, rsvpResvSenderAddrLength, 2656 rsvpResvProtocol, rsvpResvDestPort, rsvpResvPort, 2657 rsvpResvHopAddr, rsvpResvHopLih, rsvpResvInterface, 2658 rsvpResvService, rsvpResvTSpecRate, rsvpResvTSpecBurst, 2659 rsvpResvTSpecPeakRate, rsvpResvTSpecMinTU, rsvpResvTSpecMaxTU, 2660 rsvpResvRSpecRate, rsvpResvRSpecSlack, rsvpResvInterval, 2661 rsvpResvScope, rsvpResvShared, rsvpResvExplicit, 2662 rsvpResvRSVPHop, rsvpResvLastChange, rsvpResvPolicy, 2663 rsvpResvStatus, rsvpResvNewIndex 2664 } 2665 STATUS current 2666 DESCRIPTION 2667 "These objects are required for RSVP Systems." 2668 ::= { rsvpGroups 3 } 2670 rsvpResvFwdGroup OBJECT-GROUP 2671 OBJECTS { 2672 rsvpResvFwdType, rsvpResvFwdDestAddr, rsvpResvFwdSenderAddr, 2673 rsvpResvFwdDestAddrLength, rsvpResvFwdSenderAddrLength, 2674 rsvpResvFwdProtocol, rsvpResvFwdDestPort, rsvpResvFwdPort, 2675 rsvpResvFwdHopAddr, rsvpResvFwdHopLih, rsvpResvFwdInterface, 2676 rsvpResvFwdNewIndex, rsvpResvFwdService, 2677 rsvpResvFwdTSpecPeakRate, rsvpResvFwdTSpecMinTU, 2678 rsvpResvFwdTSpecMaxTU, rsvpResvFwdTSpecRate, 2679 rsvpResvFwdTSpecBurst, rsvpResvFwdRSpecRate, 2680 rsvpResvFwdRSpecSlack, rsvpResvFwdInterval, rsvpResvFwdScope, 2681 rsvpResvFwdShared, rsvpResvFwdExplicit, rsvpResvFwdRSVPHop, 2682 rsvpResvFwdLastChange, rsvpResvFwdPolicy, rsvpResvFwdStatus 2683 } 2684 STATUS current 2685 DESCRIPTION 2686 "These objects are optional, used for some RSVP 2687 Systems." 2688 ::= { rsvpGroups 4 } 2690 rsvpIfGroup OBJECT-GROUP 2691 OBJECTS { 2692 rsvpIfUdpNbrs, rsvpIfIpNbrs, rsvpIfNbrs, rsvpIfEnabled, 2693 rsvpIfUdpRequired, rsvpIfRefreshBlockadeMultiple, 2694 rsvpIfRefreshMultiple, rsvpIfRefreshInterval, rsvpIfTTL, 2695 rsvpIfRouteDelay, rsvpIfStatus 2696 } 2697 STATUS current 2698 DESCRIPTION 2699 "These objects are required for RSVP Systems." 2700 ::= { rsvpGroups 6 } 2702 rsvpNbrGroup OBJECT-GROUP 2703 OBJECTS { 2704 rsvpNbrProtocol, rsvpNbrStatus 2705 } 2706 STATUS current 2707 DESCRIPTION 2708 "These objects are required for RSVP Systems." 2709 ::= { rsvpGroups 7 } 2711 rsvpNotificationGroup NOTIFICATION-GROUP 2712 NOTIFICATIONS { newFlow, lostFlow } 2713 STATUS current 2714 DESCRIPTION 2715 "This notification is required for Systems sup- 2716 porting the RSVP Policy Module using an SNMP 2717 interface to the Policy Manager." 2718 ::= { rsvpGroups 8 } 2720 END 2721 6. Security Issues 2723 Security issues for this MIB are entirely covered by the SNMP 2724 Security Architecture, and have not been expanded within the 2725 contents of this MIB. RSVP has its own set of security issues, 2726 which are outside the scope of this MIB. 2728 7. Authors' Addresses 2730 Fred Baker 2731 Postal: Cisco Systems 2732 519 Lado Drive 2733 Santa Barbara, California 93111 2734 Tel: +1 805 681 0115 2735 E-Mail: fred@cisco.com 2737 John Krawczyk 2738 Postal: Bay Networks, Inc 2739 2 Federal Street 2740 Billerica, Massachusetts 01821 2741 Tel: +1 508 436 3811 2742 E-Mail: jj@BayNetworks.com 2744 8. Acknowledgements 2746 This document was produced by the RSVP Working Group. 2748 9. References 2750 [1] M.T. Rose (editor), Management Information Base for 2751 Network Management of TCP/IP-based internets, Internet 2752 Working Group Request for Comments 1213. Network 2753 Information Center, SRI International, Menlo Park, 2754 California, (May, 1990). 2756 [2] Information processing systems - Open Systems 2757 Interconnection - Specification of Abstract Syntax 2758 Notation One (ASN.1), International Organization for 2759 Standardization. International Standard 8824, (December, 2760 1987). 2762 [3] Information processing systems - Open Systems 2763 Interconnection - Specification of Basic Encoding Rules 2764 for Abstract Notation One (ASN.1), International 2765 Organization for Standardization. International Standard 2766 8825, (December, 1987). 2768 Table of Contents 2770 1 Status of this Memo ................................... 1 2771 2 Abstract .............................................. 2 2772 3 The SNMPv2 Network Management Framework ............... 3 2773 3.1 Object Definitions .................................. 3 2774 4 Overview .............................................. 3 2775 4.1 Textual Conventions ................................. 3 2776 4.2 Structure of MIB .................................... 4 2777 4.3 Semantics of Writing the Path and Reservation 2778 State Databases .................................... 4 2779 4.4 Intended use of Flow Notifications .................. 5 2780 4.4.1 The lostFlow Notification ......................... 5 2781 4.4.2 The newFlow Notification .......................... 5 2782 5 Definitions ........................................... 7 2783 5.1 RSVP Session Statistics Database .................... 8 2784 5.1 RSVP Session Sender Database ........................ 12 2785 5.2 RSVP Reservations Requested Database ................ 31 2786 5.3 RSVP Reservation Requests Database .................. 43 2787 5.4 RSVP Interface Attributes Database .................. 55 2788 5.5 RSVP Neighbor Database .............................. 59 2789 5.4 Notifications ....................................... 61 2790 6 Security Issues ....................................... 77 2791 7 Authors' Addresses .................................... 77 2792 8 Acknowledgements ...................................... 77 2793 9 References ............................................ 78