idnits 2.17.1 draft-ietf-rsvp-mib-03.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-24) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 73 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.) ** The document seems to lack an Authors' Addresses Section. ** There are 325 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 5 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 178 has weird spacing: '... Number conve...' == Line 179 has weird spacing: '...numbers ident...' == Line 180 has weird spacing: '...mber in the ...' == Line 181 has weird spacing: '...eturned by a...' == Line 185 has weird spacing: '...nstance or...' == (320 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 (November 1996) is 10022 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 2412 looks like a reference -- Missing reference section? '2' on line 2418 looks like a reference -- Missing reference section? '3' on line 2424 looks like a reference Summary: 13 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 November 1996 4 RSVP Management Information Base 5 draft-ietf-rsvp-mib-03.txt 7 Fri Nov 1 14:17:05 PST 1996 9 Fred Baker 11 Cisco Systems 12 519 Lado Drive 13 Santa Barbara, California 93111 15 fred@cisco.com 17 John Krawczyk 19 Bay Networks, Inc 20 2 Federal Street 21 Billerica, Massachusetts 01821 23 jj@BayNetworks.com 25 1. Status of this Memo 27 This document is an Internet Draft. Internet Drafts are 28 working documents of the Internet Engineering Task Force 29 (IETF), its Areas, and its Working Groups. Note that other 30 groups may also distribute working documents as Internet 31 Drafts. 33 Internet Drafts are draft documents valid for a maximum of six 34 months. Internet Drafts may be updated, replaced, or obsoleted 35 by other documents at any time. It is not appropriate to use 36 Internet Drafts as reference material or to cite them other 37 than as a "working draft" or "work in progress." 39 Please check the I-D abstract listing contained in each 40 Internet Draft directory to learn the current status of this 41 or any other Internet Draft. 43 2. Abstract 45 This memo defines a portion of the Management Information Base 46 (MIB) for use with network management protocols in TCP/IP- 47 based internets. In particular, it defines objects for 48 managing the Resource Reservation Protocol (RSVP) within the 49 interface attributes defined in the Integrated Services Model. 50 Thus, the Integrated Services MIB is directly relevant to and 51 cross-referenced by this MIB. Comments should be made to the 52 RSVP Working Group, rsvp@isi.edu. 54 This memo does not, in its draft form, specify a standard for 55 the Internet community. 57 3. The SNMPv2 Network Management Framework 59 The SNMPv2 Network Management Framework consists of four major 60 components. They are: 62 o RFC 1441 which defines the SMI, the mechanisms used for 63 describing and naming objects for the purpose of 64 management. 66 o RFC 1213 defines MIB-II, the core set of managed objects 67 for the Internet suite of protocols. 69 o RFC 1445 which defines the administrative and other 70 architectural aspects of the framework. 72 o RFC 1448 which defines the protocol used for network 73 access to managed objects. 75 The Framework permits new objects to be defined for the 76 purpose of experimentation and evaluation. 78 3.1. Object Definitions 80 Managed objects are accessed via a virtual information store, 81 termed the Management Information Base or MIB. Objects in the 82 MIB are defined using the subset of Abstract Syntax Notation 83 One (ASN.1) defined in the SMI. In particular, each object 84 type is named by an OBJECT IDENTIFIER, an administratively 85 assigned name. The object type together with an object 86 instance serves to uniquely identify a specific instantiation 87 of the object. For human convenience, we often use a textual 88 string, termed the descriptor, to refer to the object type. 90 4. Overview 92 4.1. Textual Conventions 94 Several new data types are introduced as a textual convention 95 in this MIB document. These textual conventions enhance the 96 readability of the specification and can ease comparison with 97 other specifications if appropriate. It should be noted that 98 the introduction of the these textual conventions has no 99 effect on either the syntax nor the semantics of any managed 100 objects. The use of these is merely an artifact of the 101 explanatory method used. Objects defined in terms of one of 102 these methods are always encoded by means of the rules that 103 define the primitive type. Hence, no changes to the SMI or 104 the SNMP are necessary to accommodate these textual 105 conventions which are adopted merely for the convenience of 106 readers and writers in pursuit of the elusive goal of clear, 107 concise, and unambiguous MIB documents. 109 4.2. Structure of MIB 111 The MIB is composed of the following sections: 112 General Objects 113 Session Statistics Table 114 Session Sender Table 115 Reservation Requests Received Table 116 Reservation Requests Forwarded Table 117 RSVP Active Flows Table 118 RSVP Interface Attributes Table 119 RSVP Neighbor Table 121 As a general rule, it is difficult in SNMP to describe 122 arbitrarily long of complex messages; this MIB therefore seeks 123 to describe the Path State Database and the Reservation State 124 Database as though each flow and filter description received 125 in an aggregate message had been received in a separate 126 reservation message. 128 Thus, if a RESV message is received for session 129 224.1.2.3+UDP+4455 with two filter/flow spec groups describing 130 a sender 1.2.3.4 and another sender 1.2.7.8, these two will 131 show in the MIB as two separate rows: one for 132 224.1.2.3+UDP+4455 from 1.2.3.4 and the other for 133 224.1.2.3+UDP+4455 from 1.2.7.8. 135 5. Definitions 137 RSVP-MIB DEFINITIONS ::= BEGIN 139 IMPORTS 140 MODULE-IDENTITY, OBJECT-TYPE, Gauge32, NOTIFICATION-TYPE, 141 Integer32, experimental FROM SNMPv2-SMI 143 TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeStamp, 144 TestAndIncr, TimeInterval FROM SNMPv2-TC 146 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 147 BitRate, BurstSize FROM INTEGRATED-SERVICES-MIB 148 ifIndex, InterfaceIndex FROM IF-MIB; 150 rsvp MODULE-IDENTITY 151 LAST-UPDATED "9511030500Z" -- Fri Nov 1 14:17:05 PST 1996 152 ORGANIZATION "IETF RSVP Working Group" 153 CONTACT-INFO 154 " Fred Baker 155 Postal: Cisco Systems 156 519 Lado Drive 157 Santa Barbara, California 93111 158 Tel: +1 805 681 0115 159 E-Mail: fred@cisco.com 161 John Krawczyk 162 Postal: Bay Networks, Inc 163 2 Federal Street 164 Billerica, Massachusetts 01821 165 Tel: +1 508 916 3811 166 E-Mail: jj@BayNetworks.com" 167 DESCRIPTION 168 "The MIB module to describe the RSVP Protocol" 169 ::= { experimental 71 } 171 rsvpObjects OBJECT IDENTIFIER ::= { rsvp 1 } -- tables 172 rsvpGenObjects OBJECT IDENTIFIER ::= { rsvp 2 } -- global objects 173 rsvpNotifications OBJECT IDENTIFIER ::= { rsvp 3 } -- traps 174 rsvpConformance OBJECT IDENTIFIER ::= { rsvp 4 } -- conformance 175 SessionNumber ::= TEXTUAL-CONVENTION 176 STATUS current 177 DESCRIPTION 178 "The Session Number convention is used for 179 numbers identifying sessions or saved PATH or 180 RESV information. It is a number in the range 181 returned by a TestAndIncr variable, having no 182 protocol meaning whatsoever but serving instead 183 as simple identifier. 185 The alternative was a very complex instance or 186 instance object that became unwieldy." 187 SYNTAX INTEGER (0..2147483647) 189 Protocol ::= TEXTUAL-CONVENTION 190 DISPLAY-HINT "d" 191 STATUS current 192 DESCRIPTION 193 "The value of the IP Protocol field of an IP 194 Datagram Header. This identifies the protocol 195 layer above IP. For example, the value 6 is 196 used for TCP and the value 17 is used for UDP. 197 The values of this field are defined in the As- 198 signed Numbers RFC." 199 SYNTAX INTEGER (1..255) 201 SessionType ::= TEXTUAL-CONVENTION 202 STATUS current 203 DESCRIPTION 204 "The value of the C-Type field of a Session ob- 205 ject, as defined in the RSVP specification. 206 This value determines the lengths of octet 207 strings and use of certain objects such as the 208 'port' variables. If the C-Type calls for an 209 IP6 address, one would expect all source, des- 210 tination, and next/previous hop addresses to be 211 16 bytes long, and for the ports to be UDP/TCP 212 port numbers, for example." 213 SYNTAX INTEGER (1..255) 215 Port ::= TEXTUAL-CONVENTION 216 DISPLAY-HINT "d" 217 STATUS current 218 DESCRIPTION 219 "The value of the UDP or TCP Source or Destina- 220 tion Port field, a virtual destination port or 221 generalized port identifier used with the IPSEC 222 Authentication Header or Encapsulating Security 223 Payload, or other session discriminator. If it 224 is not used, the value should be of length 0. 225 This pair, when coupled with the IP Addresses 226 of the source and destination system and the IP 227 protocol field, uniquely identifies a data 228 stream." 229 SYNTAX OCTET STRING 231 RsvpEncapsulation ::= TEXTUAL-CONVENTION 232 STATUS current 233 DESCRIPTION 234 "This indicates the encapsulation that an RSVP 235 Neighbor is perceived to be using." 236 SYNTAX INTEGER { 237 ip (1), -- IP Protocol 46 238 udp (2), -- UDP Encapsulation 239 both (3) -- neighbor is using both encapsulations 240 } 242 RefreshInterval ::= TEXTUAL-CONVENTION 243 DISPLAY-HINT "d" 244 STATUS current 245 DESCRIPTION 246 "The number of milliseconds that are expected 247 to elapse between refreshes of path or reserva- 248 tion state. Unrefreshed Path or reservation 249 state is removed after a small multiple of this 250 period." 251 SYNTAX INTEGER (0..'7FFFFFFF'h) 253 QosService ::= TEXTUAL-CONVENTION 254 STATUS current 255 DESCRIPTION 256 "The class of service in use by a flow." 257 SYNTAX INTEGER { 258 guaranteedDelay (2), -- Guaranteed Delay 259 controlledLoad (5) -- Controlled Load 260 } 262 MessageSize ::= TEXTUAL-CONVENTION 263 DISPLAY-HINT "d" 264 STATUS current 265 DESCRIPTION 266 "The size of a message in bytes. This is used 267 to specify the minimum and maximum size of a 268 message along an integrated services route." 269 SYNTAX INTEGER (0..'7FFFFFFF'h) 271 -- The RSVP Session Statistics Database displays statistics 272 -- relating to the number of senders and receivers in each 273 -- session. 275 rsvpSessionNewIndex OBJECT-TYPE 276 SYNTAX TestAndIncr 277 MAX-ACCESS read-write 278 STATUS current 279 DESCRIPTION 280 "This object is used to assign values to 281 rsvpSessionNumber as described in 'Textual Con- 282 ventions for SNMPv2'. The network manager 283 reads the object, and then writes the value 284 back in the SET that creates a new instance of 285 rsvpSessionEntry. If the SET fails with the 286 code 'inconsistentValue', then the process must 287 be repeated; If the SET succeeds, then the ob- 288 ject is incremented, and the new instance is 289 created according to the manager's directions." 290 ::= { rsvpGenObjects 1 } 292 rsvpSessionTable OBJECT-TYPE 293 SYNTAX SEQUENCE OF RsvpSessionEntry 294 MAX-ACCESS not-accessible 295 STATUS current 296 DESCRIPTION 297 "Statistics concerning the sessions seen by a 298 given system." 299 ::= { rsvpObjects 1 } 301 rsvpSessionEntry OBJECT-TYPE 302 SYNTAX RsvpSessionEntry 303 MAX-ACCESS not-accessible 304 STATUS current 305 DESCRIPTION 306 "Statistics concerning a single RSVP session 307 seen by a given system." 308 INDEX { rsvpSessionNumber } 309 ::= { rsvpSessionTable 1 } 311 RsvpSessionEntry ::= 312 SEQUENCE { 313 rsvpSessionNumber SessionNumber, 314 rsvpSessionType SessionType, 315 rsvpSessionDestAddr OCTET STRING, 316 rsvpSessionProtocol Protocol, 317 rsvpSessionPort Port, 318 rsvpSessionSenders Gauge32, 319 rsvpSessionReceivers Gauge32, 320 rsvpSessionRequests Gauge32 321 } 323 rsvpSessionNumber OBJECT-TYPE 324 SYNTAX SessionNumber 325 MAX-ACCESS not-accessible 326 STATUS current 327 DESCRIPTION 328 "The number of this session. This is for SNMP 329 Indexing purposes only and has no relation to 330 any protocol value." 331 ::= { rsvpSessionEntry 1 } 333 rsvpSessionType OBJECT-TYPE 334 SYNTAX SessionType 335 MAX-ACCESS read-create 336 STATUS current 337 DESCRIPTION 338 "The type of session (IP4, IP6, IP6 with flow 339 information, etc)." 340 ::= { rsvpSessionEntry 2 } 342 rsvpSessionDestAddr OBJECT-TYPE 343 SYNTAX OCTET STRING 344 MAX-ACCESS read-create 345 STATUS current 346 DESCRIPTION 347 "The destination address used by all senders in 348 this session." 349 ::= { rsvpSessionEntry 3 } 351 rsvpSessionProtocol OBJECT-TYPE 352 SYNTAX Protocol 353 MAX-ACCESS read-create 354 STATUS current 355 DESCRIPTION 356 "The IP Protocol used by this session." 357 ::= { rsvpSessionEntry 4 } 359 rsvpSessionPort OBJECT-TYPE 360 SYNTAX Port 361 MAX-ACCESS read-create 362 STATUS current 363 DESCRIPTION 364 "The UDP or TCP port number used as a destina- 365 tion port for all senders in this session. If 366 the IP protocol in use, specified by rsvpSen- 367 derProtocol, is 50 (ESP) or 51 (AH), this 368 represents a virtual destination port number. 369 A value of zero indicates that the IP protocol 370 in use does not have ports." 371 ::= { rsvpSessionEntry 5 } 373 rsvpSessionSenders OBJECT-TYPE 374 SYNTAX Gauge32 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The number of senders currently known to be 379 part of this session." 380 ::= { rsvpSessionEntry 6 } 382 rsvpSessionReceivers OBJECT-TYPE 383 SYNTAX Gauge32 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The number of reservations being requested of 388 this system for this session." 389 ::= { rsvpSessionEntry 7 } 391 rsvpSessionRequests OBJECT-TYPE 392 SYNTAX Gauge32 393 MAX-ACCESS read-only 394 STATUS current 395 DESCRIPTION 396 "The number of reservation requests this system 397 is sending upstream for this session." 398 ::= { rsvpSessionEntry 8 } 400 -- Note that this is a read only table. If the corresponding 401 -- rsvpSenderTable, rsvpResvTable, and rsvpReqTable entries all 402 -- are removed, this entry goes away also. 404 -- The RSVP Session Sender Database contains the information 405 -- displayed by senders regarding their potential contribution 406 -- to session data content. It is in essence a list of the 407 -- valid PATH messages that the RSVP Router or Host is receiving. 409 rsvpSenderNewIndex OBJECT-TYPE 410 SYNTAX TestAndIncr 411 MAX-ACCESS read-write 412 STATUS current 413 DESCRIPTION 414 "This object is used to assign values to 415 rsvpSenderNumber as described in 'Textual Con- 416 ventions for SNMPv2'. The network manager 417 reads the object, and then writes the value 418 back in the SET that creates a new instance of 419 rsvpSenderEntry. If the SET fails with the 420 code 'inconsistentValue', then the process must 421 be repeated; If the SET succeeds, then the ob- 422 ject is incremented, and the new instance is 423 created according to the manager's directions." 424 ::= { rsvpGenObjects 2 } 426 rsvpSenderTable OBJECT-TYPE 427 SYNTAX SEQUENCE OF RsvpSenderEntry 428 MAX-ACCESS not-accessible 429 STATUS current 430 DESCRIPTION 431 "Information describing the state information 432 displayed by senders in PATH messages." 433 ::= { rsvpObjects 2 } 435 rsvpSenderEntry OBJECT-TYPE 436 SYNTAX RsvpSenderEntry 437 MAX-ACCESS not-accessible 438 STATUS current 439 DESCRIPTION 440 "Information describing the state information 441 displayed by a single sender's PATH message." 442 INDEX { rsvpSessionNumber, rsvpSenderNumber } 443 ::= { rsvpSenderTable 1 } 445 RsvpSenderEntry ::= 446 SEQUENCE { 447 rsvpSenderNumber SessionNumber, 448 rsvpSenderType SessionType, 449 rsvpSenderDestAddr OCTET STRING, 450 rsvpSenderSenderAddr OCTET STRING, 451 rsvpSenderProtocol Protocol, 452 rsvpSenderDestPort Port, 453 rsvpSenderPort Port, 454 rsvpSenderHopAddr OCTET STRING, 455 rsvpSenderHopLih Integer32, 456 rsvpSenderInterface InterfaceIndex, 457 rsvpSenderTSpecRate BitRate, 458 rsvpSenderTSpecPeakRate BitRate, 459 rsvpSenderTSpecBurst BurstSize, 460 rsvpSenderTSpecMinTU MessageSize, 461 rsvpSenderTSpecMaxTU MessageSize, 462 rsvpSenderInterval RefreshInterval, 463 rsvpSenderRSVPHop TruthValue, 464 rsvpSenderLastChange TimeStamp, 465 rsvpSenderPolicy OCTET STRING, 466 rsvpSenderAdspecBreak TruthValue, 467 rsvpSenderAdspecHopCount INTEGER, 468 rsvpSenderAdspecPathBw BitRate, 469 rsvpSenderAdspecMinLatency Integer32, 470 rsvpSenderAdspecMtu INTEGER, 471 rsvpSenderAdspecGuaranteedSvc TruthValue, 472 rsvpSenderAdspecGuaranteedBreak TruthValue, 473 rsvpSenderAdspecGuaranteedCtot Integer32, 474 rsvpSenderAdspecGuaranteedDtot Integer32, 475 rsvpSenderAdspecGuaranteedCsum Integer32, 476 rsvpSenderAdspecGuaranteedDsum Integer32, 477 rsvpSenderAdspecGuaranteedHopCount INTEGER, 478 rsvpSenderAdspecGuaranteedPathBw BitRate, 479 rsvpSenderAdspecGuaranteedMinLatency Integer32, 480 rsvpSenderAdspecGuaranteedMtu INTEGER, 481 rsvpSenderAdspecCtrlLoadSvc TruthValue, 482 rsvpSenderAdspecCtrlLoadBreak TruthValue, 483 rsvpSenderAdspecCtrlLoadHopCount INTEGER, 484 rsvpSenderAdspecCtrlLoadPathBw BitRate, 485 rsvpSenderAdspecCtrlLoadMinLatency Integer32, 486 rsvpSenderAdspecCtrlLoadMtu INTEGER, 487 rsvpSenderStatus RowStatus 488 } 489 rsvpSenderNumber OBJECT-TYPE 490 SYNTAX SessionNumber 491 MAX-ACCESS not-accessible 492 STATUS current 493 DESCRIPTION 494 "The number of this sender. This is for SNMP 495 Indexing purposes only and has no relation to 496 any protocol vaalue." 497 ::= { rsvpSenderEntry 1 } 499 rsvpSenderType OBJECT-TYPE 500 SYNTAX SessionType 501 MAX-ACCESS read-create 502 STATUS current 503 DESCRIPTION 504 "The type of session (IP4, IP6, IP6 with flow 505 information, etc)." 506 ::= { rsvpSenderEntry 2 } 508 rsvpSenderDestAddr OBJECT-TYPE 509 SYNTAX OCTET STRING 510 MAX-ACCESS read-create 511 STATUS current 512 DESCRIPTION 513 "The destination address used by all senders in 514 this session." 515 ::= { rsvpSenderEntry 3 } 517 rsvpSenderSenderAddr OBJECT-TYPE 518 SYNTAX OCTET STRING 519 MAX-ACCESS read-create 520 STATUS current 521 DESCRIPTION 522 "The source address used by this sender in this 523 session." 524 ::= { rsvpSenderEntry 4 } 526 rsvpSenderProtocol OBJECT-TYPE 527 SYNTAX Protocol 528 MAX-ACCESS read-create 529 STATUS current 530 DESCRIPTION 531 "The IP Protocol used by this session." 532 ::= { rsvpSenderEntry 5 } 534 rsvpSenderDestPort OBJECT-TYPE 535 SYNTAX Port 536 MAX-ACCESS read-create 537 STATUS current 538 DESCRIPTION 539 "The UDP or TCP port number used as a destina- 540 tion port for all senders in this session. If 541 the IP protocol in use, specified by rsvpSen- 542 derProtocol, is 50 (ESP) or 51 (AH), this 543 represents a virtual destination port number. 544 A value of zero indicates that the IP protocol 545 in use does not have ports." 546 ::= { rsvpSenderEntry 6 } 548 rsvpSenderPort OBJECT-TYPE 549 SYNTAX Port 550 MAX-ACCESS read-create 551 STATUS current 552 DESCRIPTION 553 "The UDP or TCP port number used as a source 554 port for this sender in this session. If the 555 IP protocol in use, specified by rsvpSenderPro- 556 tocol is 50 (ESP) or 51 (AH), this represents a 557 generalized port identifier (GPI). A value of 558 zero indicates that the IP protocol in use does 559 not have ports." 560 ::= { rsvpSenderEntry 7 } 562 rsvpSenderHopAddr OBJECT-TYPE 563 SYNTAX OCTET STRING 564 MAX-ACCESS read-create 565 STATUS current 566 DESCRIPTION 567 "The address used by the previous RSVP hop 568 (which may be the original sender)." 569 ::= { rsvpSenderEntry 8 } 571 rsvpSenderHopLih OBJECT-TYPE 572 SYNTAX Integer32 573 MAX-ACCESS read-create 574 STATUS current 575 DESCRIPTION 576 "The Logical Interface Handle used by the pre- 577 vious RSVP hop (which may be the original 578 sender)." 579 ::= { rsvpSenderEntry 9 } 581 rsvpSenderInterface OBJECT-TYPE 582 SYNTAX InterfaceIndex 583 MAX-ACCESS read-create 584 STATUS current 585 DESCRIPTION 586 "The ifIndex value of the interface on which 587 this PATH message was most recently received." 588 ::= { rsvpSenderEntry 10 } 590 rsvpSenderTSpecRate OBJECT-TYPE 591 SYNTAX BitRate 592 UNITS "bits per second" 593 MAX-ACCESS read-create 594 STATUS current 595 DESCRIPTION 596 "The Average Bit Rate of the sender's data 597 stream. Within a transmission burst, the ar- 598 rival rate may be as fast as rsvpSenderTSpec- 599 PeakRate (if supported by the service model); 600 however, averaged across two or more burst in- 601 tervals, the rate should not exceed rsvpSen- 602 derTSpecRate. 604 Note that this is a prediction, often based on 605 the general capability of a type of codec or 606 particular encoding; the measured average rate 607 may be significantly lower." 608 ::= { rsvpSenderEntry 11 } 610 rsvpSenderTSpecPeakRate OBJECT-TYPE 611 SYNTAX BitRate 612 UNITS "bits per second" 613 MAX-ACCESS read-create 614 STATUS current 615 DESCRIPTION 616 "The Peak Bit Rate of the sender's data stream. 617 Traffic arrival is not expected to exceed this 618 rate at any time, apart from the effects of 619 jitter in the network. If not specified in the 620 TSpec, this returns zero or noSuchValue." 621 ::= { rsvpSenderEntry 12 } 623 rsvpSenderTSpecBurst OBJECT-TYPE 624 SYNTAX BurstSize 625 UNITS "bytes" 626 MAX-ACCESS read-create 627 STATUS current 628 DESCRIPTION 629 "The size of the largest burst expected from 630 the sender at a time." 631 ::= { rsvpSenderEntry 13 } 633 rsvpSenderTSpecMinTU OBJECT-TYPE 634 SYNTAX MessageSize 635 MAX-ACCESS read-create 636 STATUS current 637 DESCRIPTION 638 "The minimum message size for this flow. The 639 policing algorithm will treat smaller messages 640 as though they are this size." 641 ::= { rsvpSenderEntry 14 } 643 rsvpSenderTSpecMaxTU OBJECT-TYPE 644 SYNTAX MessageSize 645 MAX-ACCESS read-create 646 STATUS current 647 DESCRIPTION 648 "The maximum message size for this flow. The 649 admission algorithm will reject TSpecs whose 650 Maximum Transmission Unit, plus the interface 651 headers, exceed the interface MTU." 652 ::= { rsvpSenderEntry 15 } 654 rsvpSenderInterval OBJECT-TYPE 655 SYNTAX RefreshInterval 656 MAX-ACCESS read-create 657 STATUS current 658 DESCRIPTION 659 "The interval between refresh messages as ad- 660 vertised by the Previous Hop." 661 ::= { rsvpSenderEntry 16 } 663 rsvpSenderRSVPHop OBJECT-TYPE 664 SYNTAX TruthValue 665 MAX-ACCESS read-create 666 STATUS current 667 DESCRIPTION 668 "If TRUE, the node believes that the previous 669 IP hop is an RSVP hop. If FALSE, the node be- 670 lieves that the previous IP hop may not be an 671 RSVP hop." 672 ::= { rsvpSenderEntry 17 } 674 rsvpSenderLastChange OBJECT-TYPE 675 SYNTAX TimeStamp 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "The time of the last change in this PATH mes- 680 sage; This is either the first time it was re- 681 ceived or the time of the most recent change in 682 parameters." 683 ::= { rsvpSenderEntry 18 } 685 rsvpSenderPolicy OBJECT-TYPE 686 SYNTAX OCTET STRING 687 MAX-ACCESS read-create 688 STATUS current 689 DESCRIPTION 690 "The contents of the policy object, displayed 691 as an uninterpreted string of octets, including 692 the object header. In the absence of such an 693 object, this should be of zero length." 694 ::= { rsvpSenderEntry 19 } 696 rsvpSenderAdspecBreak OBJECT-TYPE 697 SYNTAX TruthValue 698 MAX-ACCESS read-create 699 STATUS current 700 DESCRIPTION 701 "The global break bit general characterization 702 parameter from the ADSPEC. If TRUE, at least 703 one non-IS hop was detected in the path. If 704 FALSE, no non-IS hops were detected." 705 ::= { rsvpSenderEntry 20 } 707 rsvpSenderAdspecHopCount OBJECT-TYPE 708 SYNTAX INTEGER (0..65535) 709 MAX-ACCESS read-create 710 STATUS current 711 DESCRIPTION 712 "The hop count general characterization parame- 713 ter from the ADSPEC. A return of zero or 714 noSuchValue indicates one of the following con- 715 ditions: 717 the invalid bit was set 718 the parameter was not present" 719 ::= { rsvpSenderEntry 21 } 721 rsvpSenderAdspecPathBw OBJECT-TYPE 722 SYNTAX BitRate 723 UNITS "bits per second" 724 MAX-ACCESS read-create 725 STATUS current 726 DESCRIPTION 727 "The path bandwidth estimate general character- 728 ization parameter from the ADSPEC. A return of 729 zero or noSuchValue indicates one of the fol- 730 lowing conditions: 732 the invalid bit was set 733 the parameter was not present" 734 ::= { rsvpSenderEntry 22 } 736 rsvpSenderAdspecMinLatency OBJECT-TYPE 737 SYNTAX Integer32 738 UNITS "microseconds" 739 MAX-ACCESS read-create 740 STATUS current 741 DESCRIPTION 742 "The minimum path latency general characteriza- 743 tion parameter from the ADSPEC. A return of 744 zero or noSuchValue indicates one of the fol- 745 lowing conditions: 747 the invalid bit was set 748 the parameter was not present" 749 ::= { rsvpSenderEntry 23 } 751 rsvpSenderAdspecMtu OBJECT-TYPE 752 SYNTAX INTEGER (0..65535) 753 UNITS "bytes" 754 MAX-ACCESS read-create 755 STATUS current 756 DESCRIPTION 757 "The composed Maximum Transmission Unit general 758 characterization parameter from the ADSPEC. A 759 return of zero or noSuchValue indicates one of 760 the following conditions: 762 the invalid bit was set 763 the parameter was not present" 764 ::= { rsvpSenderEntry 24 } 766 rsvpSenderAdspecGuaranteedSvc OBJECT-TYPE 767 SYNTAX TruthValue 768 MAX-ACCESS read-create 769 STATUS current 770 DESCRIPTION 771 "If TRUE, the ADSPEC contains a Guaranteed Ser- 772 vice fragment. If FALSE, the ADSPEC does not 773 contain a Guaranteed Service fragment." 774 ::= { rsvpSenderEntry 25 } 776 rsvpSenderAdspecGuaranteedBreak OBJECT-TYPE 777 SYNTAX TruthValue 778 MAX-ACCESS read-create 779 STATUS current 780 DESCRIPTION 781 "If TRUE, the Guaranteed Service fragment has 782 its 'break' bit set, indicating that one or 783 more nodes along the path do not support the 784 guaranteed service. If FALSE, and rsvpSen- 785 derAdspecGuaranteedSvc is TRUE, the 'break' bit 786 is not set. 788 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 789 returns FALSE or noSuchValue." 790 ::= { rsvpSenderEntry 26 } 792 rsvpSenderAdspecGuaranteedCtot OBJECT-TYPE 793 SYNTAX Integer32 794 UNITS "bytes" 795 MAX-ACCESS read-create 796 STATUS current 797 DESCRIPTION 799 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 800 is the end-to-end composed value for the 801 guaranteed service 'C' parameter. A return of 802 zero or noSuchValue indicates one of the fol- 803 lowing conditions: 805 the invalid bit was set 806 the parameter was not present 808 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 809 returns zero or noSuchValue." 810 ::= { rsvpSenderEntry 27 } 812 rsvpSenderAdspecGuaranteedDtot OBJECT-TYPE 813 SYNTAX Integer32 814 UNITS "microseconds" 815 MAX-ACCESS read-create 816 STATUS current 817 DESCRIPTION 818 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 819 is the end-to-end composed value for the 820 guaranteed service 'D' parameter. A return of 821 zero or noSuchValue indicates one of the fol- 822 lowing conditions: 824 the invalid bit was set 825 the parameter was not present 827 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 828 returns zero or noSuchValue." 829 ::= { rsvpSenderEntry 28 } 831 rsvpSenderAdspecGuaranteedCsum OBJECT-TYPE 832 SYNTAX Integer32 833 UNITS "bytes" 834 MAX-ACCESS read-create 835 STATUS current 836 DESCRIPTION 837 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 838 is the composed value for the guaranteed ser- 839 vice 'C' parameter since the last reshaping 840 point. A return of zero or noSuchValue indi- 841 cates one of the following conditions: 843 the invalid bit was set 844 the parameter was not present 846 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 847 returns zero or noSuchValue." 848 ::= { rsvpSenderEntry 29 } 850 rsvpSenderAdspecGuaranteedDsum OBJECT-TYPE 851 SYNTAX Integer32 852 UNITS "microseconds" 853 MAX-ACCESS read-create 854 STATUS current 855 DESCRIPTION 856 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 857 is the composed value for the guaranteed ser- 858 vice 'D' parameter since the last reshaping 859 point. A return of zero or noSuchValue indi- 860 cates one of the following conditions: 862 the invalid bit was set 863 the parameter was not present 865 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 866 returns zero or noSuchValue." 867 ::= { rsvpSenderEntry 30 } 869 rsvpSenderAdspecGuaranteedHopCount OBJECT-TYPE 870 SYNTAX INTEGER (0..65535) 871 MAX-ACCESS read-create 872 STATUS current 873 DESCRIPTION 875 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 876 is the service-specific override of the hop 877 count general characterization parameter from 878 the ADSPEC. A return of zero or noSuchValue 879 indicates one of the following conditions: 881 the invalid bit was set 882 the parameter was not present 884 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 885 returns zero or noSuchValue." 886 ::= { rsvpSenderEntry 31 } 888 rsvpSenderAdspecGuaranteedPathBw OBJECT-TYPE 889 SYNTAX BitRate 890 UNITS "bits per second" 891 MAX-ACCESS read-create 892 STATUS current 893 DESCRIPTION 894 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 895 is the service-specific override of the path 896 bandwidth estimate general characterization 897 parameter from the ADSPEC. A return of zero or 898 noSuchValue indicates one of the following con- 899 ditions: 901 the invalid bit was set 902 the parameter was not present 904 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 905 returns zero or noSuchValue." 906 ::= { rsvpSenderEntry 32 } 908 rsvpSenderAdspecGuaranteedMinLatency OBJECT-TYPE 909 SYNTAX Integer32 910 UNITS "microseconds" 911 MAX-ACCESS read-create 912 STATUS current 913 DESCRIPTION 914 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 915 is the service-specific override of the minimum 916 path latency general characterization parameter 917 from the ADSPEC. A return of zero or noSuch- 918 Value indicates one of the following condi- 919 tions: 921 the invalid bit was set 922 the parameter was not present 924 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 925 returns zero or noSuchValue." 926 ::= { rsvpSenderEntry 33 } 928 rsvpSenderAdspecGuaranteedMtu OBJECT-TYPE 929 SYNTAX INTEGER (0..65535) 930 UNITS "bytes" 931 MAX-ACCESS read-create 932 STATUS current 933 DESCRIPTION 934 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 935 is the service-specific override of the com- 936 posed Maximum Transmission Unit general charac- 937 terization parameter from the ADSPEC. A return 938 of zero or noSuchValue indicates one of the 939 following conditions: 941 the invalid bit was set 942 the parameter was not present 944 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 945 returns zero or noSuchValue." 946 ::= { rsvpSenderEntry 34 } 948 rsvpSenderAdspecCtrlLoadSvc OBJECT-TYPE 949 SYNTAX TruthValue 950 MAX-ACCESS read-create 951 STATUS current 952 DESCRIPTION 953 "If TRUE, the ADSPEC contains a Controlled Load 954 Service fragment. If FALSE, the ADSPEC does 955 not contain a Controlled Load Service frag- 956 ment." 957 ::= { rsvpSenderEntry 35 } 959 rsvpSenderAdspecCtrlLoadBreak OBJECT-TYPE 960 SYNTAX TruthValue 961 MAX-ACCESS read-create 962 STATUS current 963 DESCRIPTION 964 "If TRUE, the Controlled Load Service fragment 965 has its 'break' bit set, indicating that one or 966 more nodes along the path do not support the 967 controlled load service. If FALSE, and 968 rsvpSenderAdspecCtrlLoadSvc is TRUE, the 969 'break' bit is not set. 971 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 972 returns FALSE or noSuchValue." 973 ::= { rsvpSenderEntry 36 } 975 rsvpSenderAdspecCtrlLoadHopCount OBJECT-TYPE 976 SYNTAX INTEGER (0..65535) 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 981 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 982 is the service-specific override of the hop 983 count general characterization parameter from 984 the ADSPEC. A return of zero or noSuchValue 985 indicates one of the following conditions: 987 the invalid bit was set 988 the parameter was not present 990 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 991 returns zero or noSuchValue." 992 ::= { rsvpSenderEntry 37 } 994 rsvpSenderAdspecCtrlLoadPathBw OBJECT-TYPE 995 SYNTAX BitRate 996 UNITS "bits per second" 997 MAX-ACCESS read-create 998 STATUS current 999 DESCRIPTION 1000 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1001 is the service-specific override of the path 1002 bandwidth estimate general characterization 1003 parameter from the ADSPEC. A return of zero or 1004 noSuchValue indicates one of the following con- 1005 ditions: 1007 the invalid bit was set 1008 the parameter was not present 1010 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1011 returns zero or noSuchValue." 1012 ::= { rsvpSenderEntry 38 } 1014 rsvpSenderAdspecCtrlLoadMinLatency OBJECT-TYPE 1015 SYNTAX Integer32 1016 UNITS "microseconds" 1017 MAX-ACCESS read-create 1018 STATUS current 1019 DESCRIPTION 1020 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1021 is the service-specific override of the minimum 1022 path latency general characterization parameter 1023 from the ADSPEC. A return of zero or noSuch- 1024 Value indicates one of the following condi- 1025 tions: 1027 the invalid bit was set 1028 the parameter was not present 1030 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1031 returns zero or noSuchValue." 1032 ::= { rsvpSenderEntry 39 } 1034 rsvpSenderAdspecCtrlLoadMtu OBJECT-TYPE 1035 SYNTAX INTEGER (0..65535) 1036 UNITS "bytes" 1037 MAX-ACCESS read-create 1038 STATUS current 1039 DESCRIPTION 1040 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1041 is the service-specific override of the com- 1042 posed Maximum Transmission Unit general charac- 1043 terization parameter from the ADSPEC. A return 1044 of zero or noSuchValue indicates one of the 1045 following conditions: 1047 the invalid bit was set 1048 the parameter was not present 1050 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1051 returns zero or noSuchValue." 1052 ::= { rsvpSenderEntry 40 } 1054 rsvpSenderStatus OBJECT-TYPE 1055 SYNTAX RowStatus 1056 MAX-ACCESS read-create 1057 STATUS current 1058 DESCRIPTION 1059 "'valid' for all active PATH messages. This 1060 object may be used to install static PATH in- 1061 formation or delete PATH information." 1062 ::= { rsvpSenderEntry 41 } 1064 -- The RSVP Reservation Requests Received Table contains the 1065 -- information displayed by receivers regarding their needs with 1066 -- respect to sessions and senders. It is in essence a list of the 1067 -- valid RESV messages that the RSVP Router or Host is receiving. 1069 rsvpResvNewIndex OBJECT-TYPE 1070 SYNTAX TestAndIncr 1071 MAX-ACCESS read-write 1072 STATUS current 1073 DESCRIPTION 1074 "This object is used to assign values to 1075 rsvpResvNumber as described in 'Textual Conven- 1076 tions for SNMPv2'. The network manager reads 1077 the object, and then writes the value back in 1078 the SET that creates a new instance of 1079 rsvpResvEntry. If the SET fails with the code 1080 'inconsistentValue', then the process must be 1081 repeated; If the SET succeeds, then the object 1082 is incremented, and the new instance is created 1083 according to the manager's directions." 1084 ::= { rsvpGenObjects 3 } 1086 rsvpResvTable OBJECT-TYPE 1087 SYNTAX SEQUENCE OF RsvpResvEntry 1088 MAX-ACCESS not-accessible 1089 STATUS current 1090 DESCRIPTION 1091 "Information describing the state information 1092 displayed by receivers in RESV messages." 1093 ::= { rsvpObjects 3 } 1095 rsvpResvEntry OBJECT-TYPE 1096 SYNTAX RsvpResvEntry 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "Information describing the state information 1101 displayed by a single receiver's RESV message 1102 concerning a single sender." 1103 INDEX { rsvpSessionNumber, rsvpResvNumber } 1104 ::= { rsvpResvTable 1 } 1106 RsvpResvEntry ::= 1107 SEQUENCE { 1108 rsvpResvNumber SessionNumber, 1109 rsvpResvType SessionType, 1110 rsvpResvDestAddr OCTET STRING, 1111 rsvpResvSenderAddr OCTET STRING, 1112 rsvpResvProtocol Protocol, 1113 rsvpResvDestPort Port, 1114 rsvpResvPort Port, 1115 rsvpResvHopAddr OCTET STRING, 1116 rsvpResvHopLih Integer32, 1117 rsvpResvInterface InterfaceIndex, 1118 rsvpResvService QosService, 1119 rsvpResvTSpecRate BitRate, 1120 rsvpResvTSpecPeakRate BitRate, 1121 rsvpResvTSpecBurst BurstSize, 1122 rsvpResvTSpecMinTU MessageSize, 1123 rsvpResvTSpecMaxTU MessageSize, 1124 rsvpResvRSpecRate BitRate, 1125 rsvpResvRSpecSlack Integer32, 1126 rsvpResvInterval RefreshInterval, 1127 rsvpResvScope OCTET STRING, 1128 rsvpResvShared TruthValue, 1129 rsvpResvExplicit TruthValue, 1130 rsvpResvRSVPHop TruthValue, 1131 rsvpResvLastChange TimeStamp, 1132 rsvpResvPolicy OCTET STRING, 1133 rsvpResvStatus RowStatus 1134 } 1136 rsvpResvNumber OBJECT-TYPE 1137 SYNTAX SessionNumber 1138 MAX-ACCESS not-accessible 1139 STATUS current 1140 DESCRIPTION 1141 "The number of this reservation request. This 1142 is for SNMP Indexing purposes only and has no 1143 relation to any protocol value." 1144 ::= { rsvpResvEntry 1 } 1146 rsvpResvType OBJECT-TYPE 1147 SYNTAX SessionType 1148 MAX-ACCESS read-create 1149 STATUS current 1150 DESCRIPTION 1151 "The type of session (IP4, IP6, IP6 with flow 1152 information, etc)." 1153 ::= { rsvpResvEntry 2 } 1155 rsvpResvDestAddr OBJECT-TYPE 1156 SYNTAX OCTET STRING 1157 MAX-ACCESS read-create 1158 STATUS current 1159 DESCRIPTION 1160 "The destination address used by all senders in 1161 this session." 1162 ::= { rsvpResvEntry 3 } 1164 rsvpResvSenderAddr OBJECT-TYPE 1165 SYNTAX OCTET STRING 1166 MAX-ACCESS read-create 1167 STATUS current 1168 DESCRIPTION 1169 "The source address of the sender selected by 1170 this reservation. The value of all zeroes in- 1171 dicates 'all senders'." 1172 ::= { rsvpResvEntry 4 } 1174 rsvpResvProtocol OBJECT-TYPE 1175 SYNTAX Protocol 1176 MAX-ACCESS read-create 1177 STATUS current 1178 DESCRIPTION 1179 "The IP Protocol used by this session." 1180 ::= { rsvpResvEntry 5 } 1182 rsvpResvDestPort OBJECT-TYPE 1183 SYNTAX Port 1184 MAX-ACCESS read-create 1185 STATUS current 1186 DESCRIPTION 1187 "The UDP or TCP port number used as a destina- 1188 tion port for all senders in this session. If 1189 the IP protocol in use, specified by 1190 rsvpResvProtocol, is 50 (ESP) or 51 (AH), this 1191 represents a virtual destination port number. 1192 A value of zero indicates that the IP protocol 1193 in use does not have ports." 1194 ::= { rsvpResvEntry 6 } 1196 rsvpResvPort OBJECT-TYPE 1197 SYNTAX Port 1198 MAX-ACCESS read-create 1199 STATUS current 1200 DESCRIPTION 1201 "The UDP or TCP port number used as a source 1202 port for this sender in this session. If the 1203 IP protocol in use, specified by rsvpResvProto- 1204 col is 50 (ESP) or 51 (AH), this represents a 1205 generalized port identifier (GPI). A value of 1206 zero indicates that the IP protocol in use does 1207 not have ports." 1208 ::= { rsvpResvEntry 7 } 1210 rsvpResvHopAddr OBJECT-TYPE 1211 SYNTAX OCTET STRING 1212 MAX-ACCESS read-create 1213 STATUS current 1214 DESCRIPTION 1215 "The address used by the next RSVP hop (which 1216 may be the ultimate receiver)." 1217 ::= { rsvpResvEntry 8 } 1219 rsvpResvHopLih OBJECT-TYPE 1220 SYNTAX Integer32 1221 MAX-ACCESS read-create 1222 STATUS current 1223 DESCRIPTION 1224 "The Logical Interface Handle received from the 1225 previous RSVP hop (which may be the ultimate 1226 receiver)." 1227 ::= { rsvpResvEntry 9 } 1229 rsvpResvInterface OBJECT-TYPE 1230 SYNTAX InterfaceIndex 1231 MAX-ACCESS read-create 1232 STATUS current 1233 DESCRIPTION 1234 "The ifIndex value of the interface on which 1235 this RESV message was most recently received." 1236 ::= { rsvpResvEntry 10 } 1238 rsvpResvService OBJECT-TYPE 1239 SYNTAX QosService 1240 MAX-ACCESS read-create 1241 STATUS current 1242 DESCRIPTION 1243 "The QoS Service classification requested by 1244 the receiver." 1245 ::= { rsvpResvEntry 11 } 1247 rsvpResvTSpecRate OBJECT-TYPE 1248 SYNTAX BitRate 1249 UNITS "bits per second" 1250 MAX-ACCESS read-create 1251 STATUS current 1252 DESCRIPTION 1253 "The Average Bit Rate of the sender's data 1254 stream. Within a transmission burst, the ar- 1255 rival rate may be as fast as rsvpResvTSpec- 1256 PeakRate (if supported by the service model); 1257 however, averaged across two or more burst in- 1258 tervals, the rate should not exceed 1259 rsvpResvTSpecRate. 1261 Note that this is a prediction, often based on 1262 the general capability of a type of codec or 1263 particular encoding; the measured average rate 1264 may be significantly lower." 1265 ::= { rsvpResvEntry 12 } 1267 rsvpResvTSpecPeakRate OBJECT-TYPE 1268 SYNTAX BitRate 1269 UNITS "bits per second" 1270 MAX-ACCESS read-create 1271 STATUS current 1272 DESCRIPTION 1273 "The Peak Bit Rate of the sender's data stream. 1274 Traffic arrival is not expected to exceed this 1275 rate at any time, apart from the effects of 1276 jitter in the network. If not specified in the 1277 TSpec, this returns zero or noSuchValue." 1278 ::= { rsvpResvEntry 13 } 1280 rsvpResvTSpecBurst OBJECT-TYPE 1281 SYNTAX BurstSize 1282 UNITS "bytes" 1283 MAX-ACCESS read-create 1284 STATUS current 1285 DESCRIPTION 1286 "The size of the largest burst expected from 1287 the sender at a time. 1289 If this is less than the sender's advertised 1290 burst size, the receiver is asking the network 1291 to provide flow pacing beyond what would be 1292 provided under normal circumstances. Such pac- 1293 ing is at the network's option." 1294 ::= { rsvpResvEntry 14 } 1296 rsvpResvTSpecMinTU OBJECT-TYPE 1297 SYNTAX MessageSize 1298 MAX-ACCESS read-create 1299 STATUS current 1300 DESCRIPTION 1301 "The minimum message size for this flow. The 1302 policing algorithm will treat smaller messages 1303 as though they are this size." 1304 ::= { rsvpResvEntry 15 } 1306 rsvpResvTSpecMaxTU OBJECT-TYPE 1307 SYNTAX MessageSize 1308 MAX-ACCESS read-create 1309 STATUS current 1310 DESCRIPTION 1311 "The maximum message size for this flow. The 1312 admission algorithm will reject TSpecs whose 1313 Maximum Transmission Unit, plus the interface 1314 headers, exceed the interface MTU." 1315 ::= { rsvpResvEntry 16 } 1317 rsvpResvRSpecRate OBJECT-TYPE 1318 SYNTAX BitRate 1319 UNITS "bits per second" 1320 MAX-ACCESS read-create 1321 STATUS current 1322 DESCRIPTION 1323 "If the requested service is Guaranteed, as 1324 specified by rsvpResvService, this is the 1325 clearing rate that is being requested. Other- 1326 wise, it is zero, or the agent may return 1327 noSuchValue." 1328 ::= { rsvpResvEntry 17 } 1330 rsvpResvRSpecSlack OBJECT-TYPE 1331 SYNTAX Integer32 1332 UNITS "microseconds" 1333 MAX-ACCESS read-create 1334 STATUS current 1335 DESCRIPTION 1336 "If the requested service is Guaranteed, as 1337 specified by rsvpResvService, this is the delay 1338 slack. Otherwise, it is zero, or the agent may 1339 return noSuchValue." 1340 ::= { rsvpResvEntry 18 } 1342 rsvpResvInterval OBJECT-TYPE 1343 SYNTAX RefreshInterval 1344 MAX-ACCESS read-create 1345 STATUS current 1346 DESCRIPTION 1347 "The interval between refresh messages as ad- 1348 vertised by the Next Hop." 1349 ::= { rsvpResvEntry 19 } 1351 rsvpResvScope OBJECT-TYPE 1352 SYNTAX OCTET STRING 1353 MAX-ACCESS read-create 1354 STATUS current 1355 DESCRIPTION 1357 "The contents of the scope object, displayed as 1358 an uninterpreted string of octets, including 1359 the object header. In the absence of such an 1360 object, this should be of zero length. 1362 If the length is non-zero, this contains a 1363 series of IP4 or IP6 addresses." 1364 ::= { rsvpResvEntry 20 } 1366 rsvpResvShared OBJECT-TYPE 1367 SYNTAX TruthValue 1368 MAX-ACCESS read-create 1369 STATUS current 1370 DESCRIPTION 1371 "If TRUE, a reservation shared among senders is 1372 requested. If FALSE, a reservation specific to 1373 this sender is requested." 1374 ::= { rsvpResvEntry 21 } 1376 rsvpResvExplicit OBJECT-TYPE 1377 SYNTAX TruthValue 1378 MAX-ACCESS read-create 1379 STATUS current 1380 DESCRIPTION 1381 "If TRUE, individual senders are listed using 1382 Filter Specifications. If FALSE, all senders 1383 are implicitly selected. The Scope Object will 1384 contain a list of senders that need to receive 1385 this reservation request for the purpose of 1386 routing the RESV message." 1387 ::= { rsvpResvEntry 22 } 1389 rsvpResvRSVPHop OBJECT-TYPE 1390 SYNTAX TruthValue 1391 MAX-ACCESS read-create 1392 STATUS current 1393 DESCRIPTION 1394 "If TRUE, the node believes that the previous 1395 IP hop is an RSVP hop. If FALSE, the node be- 1396 lieves that the previous IP hop may not be an 1397 RSVP hop." 1398 ::= { rsvpResvEntry 23 } 1400 rsvpResvLastChange OBJECT-TYPE 1401 SYNTAX TimeStamp 1402 MAX-ACCESS read-only 1403 STATUS current 1404 DESCRIPTION 1405 "The time of the last change in this reserva- 1406 tion request; This is either the first time it 1407 was received or the time of the most recent 1408 change in parameters." 1409 ::= { rsvpResvEntry 24 } 1411 rsvpResvPolicy OBJECT-TYPE 1412 SYNTAX OCTET STRING 1413 MAX-ACCESS read-create 1414 STATUS current 1415 DESCRIPTION 1416 "The contents of the policy object, displayed 1417 as an uninterpreted string of octets, including 1418 the object header. In the absence of such an 1419 object, this should be of zero length." 1420 ::= { rsvpResvEntry 25 } 1422 rsvpResvStatus OBJECT-TYPE 1423 SYNTAX RowStatus 1424 MAX-ACCESS read-create 1425 STATUS current 1426 DESCRIPTION 1427 "'valid' for all active RESV messages. This 1428 object may be used to install static RESV in- 1429 formation or delete RESV information." 1430 ::= { rsvpResvEntry 26 } 1432 -- The RSVP Reservation Requests Forwarded Table contains the 1433 -- information displayed by receivers regarding their needs with 1434 -- respect to sessions and senders. It is in essence a list of the 1435 -- valid RESV messages that the RSVP Router or Host is sending 1436 -- to its upstream neighbors. 1438 rsvpResvFwdNewIndex OBJECT-TYPE 1439 SYNTAX TestAndIncr 1440 MAX-ACCESS read-write 1441 STATUS current 1442 DESCRIPTION 1443 "This object is used to assign values to 1444 rsvpResvFwdNumber as described in 'Textual Con- 1445 ventions for SNMPv2'. The network manager 1446 reads the object, and then writes the value 1447 back in the SET that creates a new instance of 1448 rsvpResvFwdEntry. If the SET fails with the 1449 code 'inconsistentValue', then the process must 1450 be repeated; If the SET succeeds, then the ob- 1451 ject is incremented, and the new instance is 1452 created according to the manager's directions." 1453 ::= { rsvpGenObjects 4 } 1455 rsvpResvFwdTable OBJECT-TYPE 1456 SYNTAX SEQUENCE OF RsvpResvFwdEntry 1457 MAX-ACCESS not-accessible 1458 STATUS current 1459 DESCRIPTION 1460 "Information describing the state information 1461 displayed upstream in RESV messages." 1462 ::= { rsvpObjects 4 } 1464 rsvpResvFwdEntry OBJECT-TYPE 1465 SYNTAX RsvpResvFwdEntry 1466 MAX-ACCESS not-accessible 1467 STATUS current 1468 DESCRIPTION 1469 "Information describing the state information 1470 displayed upstream in an RESV message concern- 1471 ing a single sender." 1472 INDEX { rsvpSessionNumber, rsvpResvFwdNumber } 1473 ::= { rsvpResvFwdTable 1 } 1475 RsvpResvFwdEntry ::= 1476 SEQUENCE { 1477 rsvpResvFwdNumber SessionNumber, 1478 rsvpResvFwdType SessionType, 1479 rsvpResvFwdDestAddr OCTET STRING, 1480 rsvpResvFwdSenderAddr OCTET STRING, 1481 rsvpResvFwdProtocol Protocol, 1482 rsvpResvFwdDestPort Port, 1483 rsvpResvFwdPort Port, 1484 rsvpResvFwdHopAddr OCTET STRING, 1485 rsvpResvFwdHopLih Integer32, 1486 rsvpResvFwdInterface InterfaceIndex, 1487 rsvpResvFwdService QosService, 1488 rsvpResvFwdTSpecRate BitRate, 1489 rsvpResvFwdTSpecPeakRate BitRate, 1490 rsvpResvFwdTSpecBurst BurstSize, 1491 rsvpResvFwdTSpecMinTU MessageSize, 1492 rsvpResvFwdTSpecMaxTU MessageSize, 1493 rsvpResvFwdRSpecRate BitRate, 1494 rsvpResvFwdRSpecSlack Integer32, 1495 rsvpResvFwdInterval RefreshInterval, 1496 rsvpResvFwdScope OCTET STRING, 1497 rsvpResvFwdShared TruthValue, 1498 rsvpResvFwdExplicit TruthValue, 1499 rsvpResvFwdRSVPHop TruthValue, 1500 rsvpResvFwdLastChange TimeStamp, 1501 rsvpResvFwdPolicy OCTET STRING, 1502 rsvpResvFwdStatus RowStatus 1503 } 1505 rsvpResvFwdNumber OBJECT-TYPE 1506 SYNTAX SessionNumber 1507 MAX-ACCESS not-accessible 1508 STATUS current 1509 DESCRIPTION 1510 "The number of this reservation request. This 1511 is for SNMP Indexing purposes only and has no 1512 relation to any protocol vaalue." 1513 ::= { rsvpResvFwdEntry 1 } 1515 rsvpResvFwdType OBJECT-TYPE 1516 SYNTAX SessionType 1517 MAX-ACCESS read-create 1518 STATUS current 1519 DESCRIPTION 1520 "The type of session (IP4, IP6, IP6 with flow 1521 information, etc)." 1522 ::= { rsvpResvFwdEntry 2 } 1524 rsvpResvFwdDestAddr OBJECT-TYPE 1525 SYNTAX OCTET STRING 1526 MAX-ACCESS read-create 1527 STATUS current 1528 DESCRIPTION 1529 "The destination address used by all senders in 1530 this session." 1531 ::= { rsvpResvFwdEntry 3 } 1533 rsvpResvFwdSenderAddr OBJECT-TYPE 1534 SYNTAX OCTET STRING 1535 MAX-ACCESS read-create 1536 STATUS current 1537 DESCRIPTION 1538 "The source address of the sender selected by 1539 this reservation. The value of all zeroes in- 1540 dicates 'all senders'." 1541 ::= { rsvpResvFwdEntry 4 } 1543 rsvpResvFwdProtocol OBJECT-TYPE 1544 SYNTAX Protocol 1545 MAX-ACCESS read-create 1546 STATUS current 1547 DESCRIPTION 1548 "The IP Protocol used by a session. for secure 1549 sessions, this indicates IP Security." 1550 ::= { rsvpResvFwdEntry 5 } 1552 rsvpResvFwdDestPort OBJECT-TYPE 1553 SYNTAX Port 1554 MAX-ACCESS read-create 1555 STATUS current 1556 DESCRIPTION 1557 "The UDP or TCP port number used as a destina- 1558 tion port for all senders in this session. If 1559 the IP protocol in use, specified by 1560 rsvpResvFwdProtocol, is 50 (ESP) or 51 (AH), 1561 this represents a virtual destination port 1562 number. A value of zero indicates that the IP 1563 protocol in use does not have ports." 1564 ::= { rsvpResvFwdEntry 6 } 1566 rsvpResvFwdPort OBJECT-TYPE 1567 SYNTAX Port 1568 MAX-ACCESS read-create 1569 STATUS current 1570 DESCRIPTION 1571 "The UDP or TCP port number used as a source 1572 port for this sender in this session. If the 1573 IP protocol in use, specified by 1574 rsvpResvFwdProtocol is 50 (ESP) or 51 (AH), 1575 this represents a generalized port identifier 1576 (GPI). A value of zero indicates that the IP 1577 protocol in use does not have ports." 1578 ::= { rsvpResvFwdEntry 7 } 1580 rsvpResvFwdHopAddr OBJECT-TYPE 1581 SYNTAX OCTET STRING 1582 MAX-ACCESS read-create 1583 STATUS current 1584 DESCRIPTION 1585 "The address of the (previous) RSVP that will 1586 receive this message." 1587 ::= { rsvpResvFwdEntry 8 } 1589 rsvpResvFwdHopLih OBJECT-TYPE 1590 SYNTAX Integer32 1591 MAX-ACCESS read-create 1592 STATUS current 1593 DESCRIPTION 1594 "The Logical Interface Handle sent to the (pre- 1595 vious) RSVP that will receive this message." 1596 ::= { rsvpResvFwdEntry 9 } 1598 rsvpResvFwdInterface OBJECT-TYPE 1599 SYNTAX InterfaceIndex 1600 MAX-ACCESS read-create 1601 STATUS current 1602 DESCRIPTION 1603 "The ifIndex value of the interface on which 1604 this RESV message was most recently sent." 1605 ::= { rsvpResvFwdEntry 10 } 1607 rsvpResvFwdService OBJECT-TYPE 1608 SYNTAX QosService 1609 MAX-ACCESS read-create 1610 STATUS current 1611 DESCRIPTION 1612 "The QoS Service classification requested." 1613 ::= { rsvpResvFwdEntry 11 } 1615 rsvpResvFwdTSpecRate OBJECT-TYPE 1616 SYNTAX BitRate 1617 UNITS "bits per second" 1618 MAX-ACCESS read-create 1619 STATUS current 1620 DESCRIPTION 1621 "The Average Bit Rate of the sender's data 1622 stream. Within a transmission burst, the ar- 1623 rival rate may be as fast as rsvpResvFwdTSpec- 1624 PeakRate (if supported by the service model); 1625 however, averaged across two or more burst in- 1626 tervals, the rate should not exceed 1627 rsvpResvFwdTSpecRate. 1629 Note that this is a prediction, often based on 1630 the general capability of a type of codec or 1631 particular encoding; the measured average rate 1632 may be significantly lower." 1633 ::= { rsvpResvFwdEntry 12 } 1635 rsvpResvFwdTSpecPeakRate OBJECT-TYPE 1636 SYNTAX BitRate 1637 UNITS "bits per second" 1638 MAX-ACCESS read-create 1639 STATUS current 1640 DESCRIPTION 1641 "The Peak Bit Rate of the sender's data stream 1642 Traffic arrival is not expected to exceed this 1643 rate at any time, apart from the effects of 1644 jitter in the network. If not specified in the 1645 TSpec, this returns zero or noSuchValue." 1646 ::= { rsvpResvFwdEntry 13 } 1648 rsvpResvFwdTSpecBurst OBJECT-TYPE 1649 SYNTAX BurstSize 1650 UNITS "bytes" 1651 MAX-ACCESS read-create 1652 STATUS current 1653 DESCRIPTION 1654 "The size of the largest burst expected from 1655 the sender at a time. 1657 If this is less than the sender's advertised 1658 burst size, the receiver is asking the network 1659 to provide flow pacing beyond what would be 1660 provided under normal circumstances. Such pac- 1661 ing is at the network's option." 1662 ::= { rsvpResvFwdEntry 14 } 1664 rsvpResvFwdTSpecMinTU OBJECT-TYPE 1665 SYNTAX MessageSize 1666 MAX-ACCESS read-create 1667 STATUS current 1668 DESCRIPTION 1669 "The minimum message size for this flow. The 1670 policing algorithm will treat smaller messages 1671 as though they are this size." 1672 ::= { rsvpResvFwdEntry 15 } 1674 rsvpResvFwdTSpecMaxTU OBJECT-TYPE 1675 SYNTAX MessageSize 1676 MAX-ACCESS read-create 1677 STATUS current 1678 DESCRIPTION 1679 "The maximum message size for this flow. The 1680 admission algorithm will reject TSpecs whose 1681 Maximum Transmission Unit, plus the interface 1682 headers, exceed the interface MTU." 1683 ::= { rsvpResvFwdEntry 16 } 1685 rsvpResvFwdRSpecRate OBJECT-TYPE 1686 SYNTAX BitRate 1687 UNITS "bytes per second" 1688 MAX-ACCESS read-create 1689 STATUS current 1690 DESCRIPTION 1691 "If the requested service is Guaranteed, as 1692 specified by rsvpResvService, this is the 1693 clearing rate that is being requested. Other- 1694 wise, it is zero, or the agent may return 1695 noSuchValue." 1696 ::= { rsvpResvFwdEntry 17 } 1698 rsvpResvFwdRSpecSlack OBJECT-TYPE 1699 SYNTAX Integer32 1700 UNITS "microseconds" 1701 MAX-ACCESS read-create 1702 STATUS current 1703 DESCRIPTION 1704 "If the requested service is Guaranteed, as 1705 specified by rsvpResvService, this is the delay 1706 slack. Otherwise, it is zero, or the agent may 1707 return noSuchValue." 1708 ::= { rsvpResvFwdEntry 18 } 1710 rsvpResvFwdInterval OBJECT-TYPE 1711 SYNTAX RefreshInterval 1712 MAX-ACCESS read-create 1713 STATUS current 1714 DESCRIPTION 1715 "The interval between refresh messages adver- 1716 tised to the Previous Hop." 1717 ::= { rsvpResvFwdEntry 19 } 1719 rsvpResvFwdScope OBJECT-TYPE 1720 SYNTAX OCTET STRING 1721 MAX-ACCESS read-create 1722 STATUS current 1723 DESCRIPTION 1724 "The contents of the scope object, displayed as 1725 an uninterpreted string of octets, including 1726 the object header. In the absence of such an 1727 object, this should be of zero length." 1728 ::= { rsvpResvFwdEntry 20 } 1730 rsvpResvFwdShared OBJECT-TYPE 1731 SYNTAX TruthValue 1732 MAX-ACCESS read-create 1733 STATUS current 1734 DESCRIPTION 1735 "If TRUE, a reservation shared among senders is 1736 requested. If FALSE, a reservation specific to 1737 this sender is requested." 1738 ::= { rsvpResvFwdEntry 21 } 1740 rsvpResvFwdExplicit OBJECT-TYPE 1741 SYNTAX TruthValue 1742 MAX-ACCESS read-create 1743 STATUS current 1744 DESCRIPTION 1745 "If TRUE, individual senders are listed using 1746 Filter Specifications. If FALSE, all senders 1747 are implicitly selected. The Scope Object will 1748 contain a list of senders that need to receive 1749 this reservation request for the purpose of 1750 routing the RESV message." 1751 ::= { rsvpResvFwdEntry 22 } 1753 rsvpResvFwdRSVPHop OBJECT-TYPE 1754 SYNTAX TruthValue 1755 MAX-ACCESS read-create 1756 STATUS current 1757 DESCRIPTION 1758 "If TRUE, the node believes that the next IP 1759 hop is an RSVP hop. If FALSE, the node be- 1760 lieves that the next IP hop may not be an RSVP 1761 hop." 1762 ::= { rsvpResvFwdEntry 23 } 1764 rsvpResvFwdLastChange OBJECT-TYPE 1765 SYNTAX TimeStamp 1766 MAX-ACCESS read-only 1767 STATUS current 1768 DESCRIPTION 1769 "The time of the last change in this request; 1770 This is either the first time it was sent or 1771 the time of the most recent change in parame- 1772 ters." 1773 ::= { rsvpResvFwdEntry 24 } 1775 rsvpResvFwdPolicy OBJECT-TYPE 1776 SYNTAX OCTET STRING 1777 MAX-ACCESS read-create 1778 STATUS current 1779 DESCRIPTION 1780 "The contents of the policy object, displayed 1781 as an uninterpreted string of octets, including 1782 the object header. In the absence of such an 1783 object, this should be of zero length." 1784 ::= { rsvpResvFwdEntry 25 } 1786 rsvpResvFwdStatus OBJECT-TYPE 1787 SYNTAX RowStatus 1788 MAX-ACCESS read-create 1789 STATUS current 1790 DESCRIPTION 1791 "'valid' for all active RESV messages. This 1792 object may be used to install static RESV in- 1793 formation or delete RESV information." 1794 ::= { rsvpResvFwdEntry 26 } 1796 -- The RSVP Active Flows Database 1797 -- lists all flows active on an outgoing interface, including 1798 -- relevant attributes. 1800 rsvpFlowTable OBJECT-TYPE 1801 SYNTAX SEQUENCE OF RsvpFlowEntry 1802 MAX-ACCESS not-accessible 1803 STATUS current 1804 DESCRIPTION 1805 "Information describing the reserved flows us- 1806 ing the system's interfaces." 1807 ::= { rsvpObjects 5 } 1809 rsvpFlowEntry OBJECT-TYPE 1810 SYNTAX RsvpFlowEntry 1811 MAX-ACCESS not-accessible 1812 STATUS current 1813 DESCRIPTION 1814 "Information describing the use of a given in- 1815 terface by a given flow." 1816 INDEX { rsvpFlowNumber } 1817 ::= { rsvpFlowTable 1 } 1819 RsvpFlowEntry ::= 1820 SEQUENCE { 1821 rsvpFlowNumber SessionNumber, 1822 rsvpFlowType SessionType, 1823 rsvpFlowDestAddr OCTET STRING, 1824 rsvpFlowSenderAddr OCTET STRING, 1825 rsvpFlowProtocol Protocol, 1826 rsvpFlowDestPort Port, 1827 rsvpFlowPort Port, 1828 rsvpFlowInterface InterfaceIndex, 1829 rsvpFlowRate BitRate, 1830 rsvpFlowBurst BurstSize, 1831 rsvpFlowWeight Integer32, 1832 rsvpFlowQueue Integer32, 1833 rsvpFlowMinTU MessageSize, 1834 rsvpFlowDontAsk TimeInterval, 1835 rsvpFlowStatus RowStatus 1836 } 1838 rsvpFlowNumber OBJECT-TYPE 1839 SYNTAX SessionNumber 1840 MAX-ACCESS not-accessible 1841 STATUS current 1842 DESCRIPTION 1843 "The number of this flow. This is for SNMP In- 1844 dexing purposes only and has no relation to any 1845 protocol value." 1846 ::= { rsvpFlowEntry 1 } 1848 rsvpFlowType OBJECT-TYPE 1849 SYNTAX SessionType 1850 MAX-ACCESS read-create 1851 STATUS current 1852 DESCRIPTION 1853 "The type of session (IP4, IP6, IP6 with flow 1854 information, etc)." 1855 ::= { rsvpFlowEntry 2 } 1857 rsvpFlowDestAddr OBJECT-TYPE 1858 SYNTAX OCTET STRING 1859 MAX-ACCESS read-create 1860 STATUS current 1861 DESCRIPTION 1862 "The destination address used by all senders in 1863 this session." 1864 ::= { rsvpFlowEntry 3 } 1866 rsvpFlowSenderAddr OBJECT-TYPE 1867 SYNTAX OCTET STRING 1868 MAX-ACCESS read-create 1869 STATUS current 1870 DESCRIPTION 1871 "The source address of the sender selected by 1872 this reservation. The value of all zeroes in- 1873 dicates 'all senders'." 1874 ::= { rsvpFlowEntry 4 } 1876 rsvpFlowProtocol OBJECT-TYPE 1877 SYNTAX Protocol 1878 MAX-ACCESS read-create 1879 STATUS current 1880 DESCRIPTION 1881 "The IP Protocol used by a session." 1882 ::= { rsvpFlowEntry 5 } 1884 rsvpFlowDestPort OBJECT-TYPE 1885 SYNTAX Port 1886 MAX-ACCESS read-create 1887 STATUS current 1888 DESCRIPTION 1889 "The UDP or TCP port number used as a destina- 1890 tion port for all senders in this session. If 1891 the IP protocol in use, specified by 1892 rsvpResvFwdProtocol, is 50 (ESP) or 51 (AH), 1893 this represents a virtual destination port 1894 number. A value of zero indicates that the IP 1895 protocol in use does not have ports." 1896 ::= { rsvpFlowEntry 6 } 1898 rsvpFlowPort OBJECT-TYPE 1899 SYNTAX Port 1900 MAX-ACCESS read-create 1901 STATUS current 1902 DESCRIPTION 1903 "The UDP or TCP port number used as a source 1904 port for this sender in this session. If the 1905 IP protocol in use, specified by 1906 rsvpResvFwdProtocol is 50 (ESP) or 51 (AH), 1907 this represents a generalized port identifier 1908 (GPI). A value of zero indicates that the IP 1909 protocol in use does not have ports." 1910 ::= { rsvpFlowEntry 7 } 1912 rsvpFlowInterface OBJECT-TYPE 1913 SYNTAX InterfaceIndex 1914 MAX-ACCESS read-create 1915 STATUS current 1916 DESCRIPTION 1917 "The ifIndex value of the interface on which 1918 this reservation exists." 1919 ::= { rsvpFlowEntry 8 } 1921 rsvpFlowRate OBJECT-TYPE 1922 SYNTAX BitRate 1923 UNITS "bits per second" 1924 MAX-ACCESS read-create 1925 STATUS current 1926 DESCRIPTION 1927 "The Reserved Rate of the sender's data stream. 1928 If this is a Controlled Load service flow, this 1929 rate is derived from the Tspec rate parameter 1930 (r). If this is a Guaranteed service flow, 1931 this rate is derived from the Rspec clearing 1932 rate parameter (R)." 1933 ::= { rsvpFlowEntry 9 } 1935 rsvpFlowBurst OBJECT-TYPE 1936 SYNTAX BurstSize 1937 UNITS "bytes" 1938 MAX-ACCESS read-create 1939 STATUS current 1940 DESCRIPTION 1941 "The size of the largest burst expected from 1942 the sender at a time. 1944 If this is less than the sender's advertised 1945 burst size, the receiver is asking the network 1946 to provide flow pacing beyond what would be 1947 provided under normal circumstances. Such pac- 1948 ing is at the network's option." 1949 ::= { rsvpFlowEntry 10 } 1951 rsvpFlowWeight OBJECT-TYPE 1952 SYNTAX Integer32 1953 MAX-ACCESS read-create 1954 STATUS current 1955 DESCRIPTION 1956 "The weight used to prioritize the traffic. 1957 Note that the interpretation of this object is 1958 implementation-specific, as implementations 1959 vary in their use of weighting procedures." 1960 ::= { rsvpFlowEntry 11 } 1962 rsvpFlowQueue OBJECT-TYPE 1963 SYNTAX Integer32 1964 MAX-ACCESS read-create 1965 STATUS current 1966 DESCRIPTION 1967 "The number of the queue used by this traffic. 1968 Note that the interpretation of this object is 1969 implementation-specific, as implementations 1970 vary in their use of queue identifiers." 1971 ::= { rsvpFlowEntry 12 } 1973 rsvpFlowMinTU OBJECT-TYPE 1974 SYNTAX MessageSize 1975 MAX-ACCESS read-create 1976 STATUS current 1977 DESCRIPTION 1978 "The minimum message size for this flow. The 1979 policing algorithm will treat smaller messages 1980 as though they are this size." 1981 ::= { rsvpFlowEntry 13 } 1983 rsvpFlowDontAsk OBJECT-TYPE 1984 SYNTAX TimeInterval 1985 MAX-ACCESS read-create 1986 STATUS current 1987 DESCRIPTION 1988 "A period of time, measured in hundredths of a 1989 second, during which the agent is precluded 1990 from sending a newFlow notification for this 1991 conversation. 1993 If an authorizing application leaves rsvpFlowS- 1994 tatus in a state other than 'valid' and sets 1995 rsvpFlowDontAsk to a non-zero value, the agent 1996 must neither consider the flow active for ad- 1997 mission or queuing purposes, or re-request au- 1998 thorization to install it, until the indicated 1999 amount of time has elapsed." 2000 ::= { rsvpFlowEntry 14 } 2002 rsvpFlowStatus OBJECT-TYPE 2003 SYNTAX RowStatus 2004 MAX-ACCESS read-create 2005 STATUS current 2006 DESCRIPTION 2007 "'valid' for all active flows. This object may 2008 be used to install static classifier informa- 2009 tion, delete classifier information, or author- 2010 ize such." 2011 ::= { rsvpFlowEntry 15 } 2013 -- The RSVP Interface Attributes Database contains the 2014 -- RSVP-specific information for an interface. Information 2015 -- that is shared with other reservation procedures such 2016 -- as ST-II is in the Integrated Interface Attributes 2017 -- Database. 2019 rsvpIfTable OBJECT-TYPE 2020 SYNTAX SEQUENCE OF RsvpIfEntry 2021 MAX-ACCESS not-accessible 2022 STATUS current 2023 DESCRIPTION 2024 "The RSVP-specific attributes of the system's 2025 interfaces." 2026 ::= { rsvpObjects 6 } 2028 rsvpIfEntry OBJECT-TYPE 2029 SYNTAX RsvpIfEntry 2030 MAX-ACCESS not-accessible 2031 STATUS current 2032 DESCRIPTION 2033 "The RSVP-specific attributes of the a given 2034 interface." 2035 INDEX { ifIndex } 2037 ::= { rsvpIfTable 1 } 2039 RsvpIfEntry ::= 2040 SEQUENCE { 2041 rsvpIfUdpNbrs Gauge32, 2042 rsvpIfIpNbrs Gauge32, 2043 rsvpIfNbrs Gauge32, 2044 rsvpIfEnabled TruthValue, 2045 rsvpIfUdpRequired TruthValue, 2046 rsvpIfRefreshBlockadeMultiple INTEGER, 2047 rsvpIfRefreshMultiple INTEGER, 2048 rsvpIfTTL INTEGER, 2049 rsvpIfRefreshInterval TimeInterval, 2050 rsvpIfRouteDelay TimeInterval, 2051 rsvpIfStatus RowStatus 2052 } 2053 rsvpIfUdpNbrs OBJECT-TYPE 2054 SYNTAX Gauge32 2055 MAX-ACCESS read-only 2056 STATUS current 2057 DESCRIPTION 2058 "The number of neighbors perceived to be using 2059 only the RSVP UDP Encapsulation." 2060 ::= { rsvpIfEntry 1 } 2062 rsvpIfIpNbrs OBJECT-TYPE 2063 SYNTAX Gauge32 2064 MAX-ACCESS read-only 2065 STATUS current 2066 DESCRIPTION 2067 "The number of neighbors perceived to be using 2068 only the RSVP IP Encapsulation." 2069 ::= { rsvpIfEntry 2 } 2071 rsvpIfNbrs OBJECT-TYPE 2072 SYNTAX Gauge32 2073 MAX-ACCESS read-only 2074 STATUS current 2075 DESCRIPTION 2076 "The number of neighbors currently perceived; 2077 this will exceed rsvpIfIpNbrs + rsvpIfUdpNbrs 2078 by the number of neighbors using both encapsu- 2079 lations." 2080 ::= { rsvpIfEntry 3 } 2082 rsvpIfRefreshBlockadeMultiple OBJECT-TYPE 2083 SYNTAX INTEGER (1..65536) 2084 MAX-ACCESS read-create 2085 STATUS current 2086 DESCRIPTION 2087 "The value of the RSVP value 'Kb', Which is the 2088 minimum number of refresh intervals that 2089 blockade state will last once entered." 2090 DEFVAL { 4 } 2091 ::= { rsvpIfEntry 4 } 2093 rsvpIfRefreshMultiple OBJECT-TYPE 2094 SYNTAX INTEGER (1..65536) 2095 MAX-ACCESS read-create 2096 STATUS current 2097 DESCRIPTION 2098 "The value of the RSVP value 'K', which is the 2099 number of refresh intervals which must elapse 2100 (minimum) before a PATH or RESV message which 2101 is not being refreshed will be aged out." 2102 DEFVAL { 3 } 2103 ::= { rsvpIfEntry 5 } 2105 rsvpIfTTL OBJECT-TYPE 2106 SYNTAX INTEGER (0..255) 2107 MAX-ACCESS read-create 2108 STATUS current 2109 DESCRIPTION 2110 "The value of SEND_TTL used on this interface 2111 for messages this node originates. If set to 2112 zero, the node determines the TTL via other 2113 means." 2114 DEFVAL { 0 } -- which is to say, no override 2115 ::= { rsvpIfEntry 6 } 2117 rsvpIfRefreshInterval OBJECT-TYPE 2118 SYNTAX TimeInterval 2119 UNITS "hundredths of a second" 2120 MAX-ACCESS read-create 2121 STATUS current 2122 DESCRIPTION 2123 "The value of the RSVP value 'R', which is the 2124 minimum period between refresh transmissions of 2125 a given PATH or RESV message on an interface." 2126 DEFVAL { 3000 } -- 30 seconds 2127 ::= { rsvpIfEntry 7 } 2129 rsvpIfRouteDelay OBJECT-TYPE 2130 SYNTAX TimeInterval 2131 UNITS "hundredths of a second" 2132 MAX-ACCESS read-create 2133 STATUS current 2134 DESCRIPTION 2135 "The approximate period from the time a route 2136 is changed to the time a resulting message ap- 2137 pears on the interface." 2138 DEFVAL { 200 } -- 2 seconds 2139 ::= { rsvpIfEntry 8 } 2141 rsvpIfEnabled OBJECT-TYPE 2142 SYNTAX TruthValue 2143 MAX-ACCESS read-create 2144 STATUS current 2145 DESCRIPTION 2146 "If TRUE, RSVP is enabled on this Interface. 2147 If FALSE, RSVP is not enabled on this inter- 2148 face." 2149 ::= { rsvpIfEntry 9 } 2151 rsvpIfUdpRequired OBJECT-TYPE 2152 SYNTAX TruthValue 2153 MAX-ACCESS read-create 2154 STATUS current 2155 DESCRIPTION 2156 "If TRUE, manual configuration forces the use 2157 of UDP encapsulation on the interface. If 2158 FALSE, UDP encapsulation is only used if rsvpI- 2159 fUdpNbrs is not zero." 2161 ::= { rsvpIfEntry 10 } 2163 rsvpIfStatus OBJECT-TYPE 2164 SYNTAX RowStatus 2165 MAX-ACCESS read-create 2166 STATUS current 2167 DESCRIPTION 2168 "'valid' on interfaces that are configured for 2169 RSVP." 2170 ::= { rsvpIfEntry 11 } 2172 -- The RSVP Neighbor Database lists the neighbors the RSVP 2173 -- process currently is receiving messages from. 2175 rsvpNbrTable OBJECT-TYPE 2176 SYNTAX SEQUENCE OF RsvpNbrEntry 2177 MAX-ACCESS not-accessible 2178 STATUS current 2179 DESCRIPTION 2180 "Information describing the Neighbors of an 2181 RSVP system." 2182 ::= { rsvpObjects 7 } 2184 rsvpNbrEntry OBJECT-TYPE 2185 SYNTAX RsvpNbrEntry 2186 MAX-ACCESS not-accessible 2187 STATUS current 2188 DESCRIPTION 2189 "Information describing a single RSVP Neigh- 2190 bor." 2191 INDEX { ifIndex, rsvpNbrAddress } 2192 ::= { rsvpNbrTable 1 } 2194 RsvpNbrEntry ::= 2195 SEQUENCE { 2196 rsvpNbrAddress OCTET STRING, 2197 rsvpNbrProtocol RsvpEncapsulation, 2198 rsvpNbrStatus RowStatus 2199 } 2201 rsvpNbrAddress OBJECT-TYPE 2202 SYNTAX OCTET STRING (SIZE(4..16)) 2203 MAX-ACCESS not-accessible 2204 STATUS current 2205 DESCRIPTION 2206 "The IP4 or IP6 Address used by this neighbor." 2207 ::= { rsvpNbrEntry 1 } 2209 rsvpNbrProtocol OBJECT-TYPE 2210 SYNTAX RsvpEncapsulation 2211 MAX-ACCESS read-create 2212 STATUS current 2213 DESCRIPTION 2214 "The encapsulation being used by this neigh- 2215 bor." 2216 ::= { rsvpNbrEntry 2 } 2218 rsvpNbrStatus OBJECT-TYPE 2219 SYNTAX RowStatus 2220 MAX-ACCESS read-create 2221 STATUS current 2222 DESCRIPTION 2223 "'valid' for all neighbors. This object may be 2224 used to configure neighbors. In the presence 2225 of configured neighbors, the implementation may 2226 (but is not required to) limit the set of valid 2227 neighbors to those configured." 2228 ::= { rsvpNbrEntry 3 } 2230 -- 2231 -- Notifications used to signal events 2232 -- 2234 newFlow NOTIFICATION-TYPE 2235 OBJECTS { 2236 rsvpFlowNumber, rsvpFlowType, rsvpFlowDestAddr, 2237 rsvpFlowSenderAddr, rsvpFlowProtocol, rsvpFlowDestPort, 2238 rsvpFlowPort, rsvpFlowInterface, rsvpFlowRate, rsvpFlowBurst, 2239 rsvpFlowWeight, rsvpFlowQueue, rsvpFlowMinTU 2240 } 2241 STATUS current 2242 DESCRIPTION 2243 "The newFlow trap indicates that the originat- 2244 ing system has installed a new flow in its 2245 classifier, or (when reservation authorization 2246 is in view) is prepared to install such a flow 2247 in the classifier and is requesting authoriza- 2248 tion. The objects included with the Notifica- 2249 tion may be used to read further information 2250 using the RSVP MIB. Authorization or non- 2251 authorization may be enacted by a write to the 2252 variable rsvpFlowStatus." 2253 ::= { rsvpNotifications 1 } 2255 lostFlow NOTIFICATION-TYPE 2256 OBJECTS { 2257 rsvpFlowNumber, rsvpFlowType, rsvpFlowDestAddr, 2258 rsvpFlowSenderAddr, rsvpFlowProtocol, rsvpFlowDestPort, 2259 rsvpFlowPort, rsvpFlowInterface 2260 } 2261 STATUS current 2262 DESCRIPTION 2263 "The lostFlow trap indicates that the originat- 2264 ing system has removed a flow in its classif- 2265 ier." 2266 ::= { rsvpNotifications 2 } 2268 -- conformance information 2270 rsvpGroups OBJECT IDENTIFIER ::= { rsvpConformance 1 } 2271 rsvpCompliances OBJECT IDENTIFIER ::= { rsvpConformance 2 } 2273 -- compliance statements 2275 rsvpCompliance MODULE-COMPLIANCE 2276 STATUS current 2277 DESCRIPTION 2278 "The compliance statement. Note that the im- 2279 plementation of this module requires implemen- 2280 tation of the Integrated Services MIB as well." 2281 MODULE -- this module 2282 MANDATORY-GROUPS { 2283 rsvpSessionGroup, rsvpSenderGroup, rsvpResvGroup, 2284 rsvpResvFwdGroup, rsvpFlowGroup, rsvpIfGroup, 2285 rsvpNbrGroup 2286 } 2287 ::= { rsvpCompliances 1 } 2289 rsvpSessionGroup OBJECT-GROUP 2290 OBJECTS { 2291 rsvpSessionNewIndex, rsvpSessionType, rsvpSessionDestAddr, 2292 rsvpSessionProtocol, rsvpSessionPort, rsvpSessionSenders, 2293 rsvpSessionReceivers, rsvpSessionRequests 2294 } 2295 STATUS current 2296 DESCRIPTION 2297 "These objects are required for RSVP Systems." 2298 ::= { rsvpGroups 1 } 2300 rsvpSenderGroup OBJECT-GROUP 2301 OBJECTS { 2302 rsvpSenderType, rsvpSenderDestAddr, rsvpSenderSenderAddr, 2303 rsvpSenderProtocol, rsvpSenderDestPort, rsvpSenderPort, 2304 rsvpSenderHopAddr, rsvpSenderHopLih, 2305 rsvpSenderInterface, rsvpSenderTSpecRate, 2306 rsvpSenderTSpecPeakRate, rsvpSenderTSpecBurst, 2307 rsvpSenderTSpecMinTU, rsvpSenderTSpecMaxTU, 2308 rsvpSenderInterval, rsvpSenderLastChange, 2309 rsvpSenderStatus, rsvpSenderRSVPHop, rsvpSenderPolicy, 2310 rsvpSenderAdspecBreak, rsvpSenderAdspecHopCount, 2311 rsvpSenderAdspecPathBw, rsvpSenderAdspecMinLatency, 2312 rsvpSenderAdspecMtu, rsvpSenderAdspecGuaranteedSvc, 2313 rsvpSenderAdspecGuaranteedBreak, 2314 rsvpSenderAdspecGuaranteedCtot, 2315 rsvpSenderAdspecGuaranteedDtot, 2316 rsvpSenderAdspecGuaranteedCsum, 2317 rsvpSenderAdspecGuaranteedDsum, 2318 rsvpSenderAdspecGuaranteedHopCount, 2319 rsvpSenderAdspecGuaranteedPathBw, 2320 rsvpSenderAdspecGuaranteedMinLatency, 2321 rsvpSenderAdspecGuaranteedMtu, rsvpSenderAdspecCtrlLoadSvc, 2322 rsvpSenderAdspecCtrlLoadBreak, 2323 rsvpSenderAdspecCtrlLoadHopCount, 2324 rsvpSenderAdspecCtrlLoadPathBw, 2325 rsvpSenderAdspecCtrlLoadMinLatency, 2326 rsvpSenderAdspecCtrlLoadMtu, rsvpSenderNewIndex 2327 } 2328 STATUS current 2329 DESCRIPTION 2330 "These objects are required for RSVP Systems." 2331 ::= { rsvpGroups 2 } 2333 rsvpResvGroup OBJECT-GROUP 2334 OBJECTS { 2335 rsvpResvType, rsvpResvDestAddr, rsvpResvSenderAddr, 2336 rsvpResvProtocol, rsvpResvDestPort, rsvpResvPort, 2337 rsvpResvHopAddr, rsvpResvHopLih, 2338 rsvpResvInterface, rsvpResvService, 2339 rsvpResvTSpecRate, rsvpResvTSpecBurst, rsvpResvTSpecPeakRate, 2340 rsvpResvTSpecMinTU, rsvpResvTSpecMaxTU, rsvpResvRSpecRate, 2341 rsvpResvRSpecSlack, 2342 rsvpResvInterval, rsvpResvScope, rsvpResvShared, 2343 rsvpResvExplicit, rsvpResvRSVPHop, rsvpResvLastChange, 2344 rsvpResvPolicy, rsvpResvStatus, rsvpResvNewIndex 2345 } 2346 STATUS current 2347 DESCRIPTION 2348 "These objects are required for RSVP Systems." 2349 ::= { rsvpGroups 3 } 2351 rsvpResvFwdGroup OBJECT-GROUP 2352 OBJECTS { 2353 rsvpResvFwdType, rsvpResvFwdDestAddr, rsvpResvFwdSenderAddr, 2354 rsvpResvFwdProtocol, rsvpResvFwdDestPort, rsvpResvFwdPort, 2355 rsvpResvFwdHopAddr, rsvpResvFwdHopLih, 2356 rsvpResvFwdInterface, rsvpResvFwdNewIndex, rsvpResvFwdService, 2357 rsvpResvFwdTSpecPeakRate, rsvpResvFwdTSpecMinTU, 2358 rsvpResvFwdTSpecMaxTU, rsvpResvFwdTSpecRate, 2359 rsvpResvFwdTSpecBurst, rsvpResvFwdRSpecRate, 2360 rsvpResvFwdRSpecSlack, 2361 rsvpResvFwdInterval, rsvpResvFwdScope, rsvpResvFwdShared, 2362 rsvpResvFwdExplicit, rsvpResvFwdRSVPHop, 2363 rsvpResvFwdLastChange, 2364 rsvpResvFwdPolicy, rsvpResvFwdStatus 2365 } 2366 STATUS current 2367 DESCRIPTION 2368 "These objects are required for RSVP Systems." 2369 ::= { rsvpGroups 4 } 2371 rsvpFlowGroup OBJECT-GROUP 2372 OBJECTS { 2373 rsvpFlowType, rsvpFlowDestAddr, rsvpFlowSenderAddr, 2374 rsvpFlowProtocol, rsvpFlowDestPort, rsvpFlowPort, 2375 rsvpFlowInterface, rsvpFlowDontAsk, rsvpFlowRate, 2376 rsvpFlowBurst, rsvpFlowWeight, rsvpFlowQueue, rsvpFlowMinTU, 2377 rsvpFlowStatus 2378 } 2379 STATUS current 2380 DESCRIPTION 2381 "These objects are required for RSVP Systems." 2382 ::= { rsvpGroups 5 } 2384 rsvpIfGroup OBJECT-GROUP 2385 OBJECTS { 2386 rsvpIfUdpNbrs, rsvpIfIpNbrs, rsvpIfNbrs, rsvpIfEnabled, 2387 rsvpIfUdpRequired, rsvpIfRefreshBlockadeMultiple, 2388 rsvpIfRefreshMultiple, rsvpIfRefreshInterval, rsvpIfTTL, 2389 rsvpIfRouteDelay, rsvpIfStatus 2390 } 2391 STATUS current 2392 DESCRIPTION 2393 "These objects are required for RSVP Systems." 2394 ::= { rsvpGroups 6 } 2396 rsvpNbrGroup OBJECT-GROUP 2397 OBJECTS { 2398 rsvpNbrProtocol, rsvpNbrStatus 2399 } 2400 STATUS current 2401 DESCRIPTION 2402 "These objects are required for RSVP Systems." 2403 ::= { rsvpGroups 7 } 2405 END 2406 6. Acknowledgements 2408 This document was produced by the RSVP Working Group. 2410 7. References 2412 [1] M.T. Rose (editor), Management Information Base for 2413 Network Management of TCP/IP-based internets, Internet 2414 Working Group Request for Comments 1213. Network 2415 Information Center, SRI International, Menlo Park, 2416 California, (May, 1990). 2418 [2] Information processing systems - Open Systems 2419 Interconnection - Specification of Abstract Syntax 2420 Notation One (ASN.1), International Organization for 2421 Standardization. International Standard 8824, (December, 2422 1987). 2424 [3] Information processing systems - Open Systems 2425 Interconnection - Specification of Basic Encoding Rules 2426 for Abstract Notation One (ASN.1), International 2427 Organization for Standardization. International Standard 2428 8825, (December, 1987). 2430 Table of Contents 2432 1 Status of this Memo ................................... 1 2433 2 Abstract .............................................. 2 2434 3 The SNMPv2 Network Management Framework ............... 3 2435 3.1 Object Definitions .................................. 3 2436 4 Overview .............................................. 3 2437 4.1 Textual Conventions ................................. 3 2438 4.2 Structure of MIB .................................... 4 2439 5 Definitions ........................................... 5 2440 5.1 RSVP Session Statistics Database .................... 8 2441 5.1 RSVP Session Sender Database ........................ 12 2442 5.2 RSVP Reservations Requested Database ................ 30 2443 5.3 RSVP Reservation Requests Database .................. 41 2444 5.3 RSVP Interface Flows Database ....................... 52 2445 5.4 RSVP Interface Attributes Database .................. 58 2446 5.5 RSVP Neighbor Database .............................. 63 2447 5.4 Notifications ....................................... 65 2448 6 Acknowledgements ...................................... 71 2449 7 References ............................................ 72