idnits 2.17.1 draft-ietf-issll-is802-sbm-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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 is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 48 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (October 1999) is 8958 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: 'INTERFACEMIB' is mentioned on line 148, but not defined == Unused Reference: 'RSVP' is defined on line 1165, but no explicit reference was found in the text == Unused Reference: 'IS802' is defined on line 1170, but no explicit reference was found in the text == Unused Reference: 'SBM' is defined on line 1177, but no explicit reference was found in the text == Unused Reference: 'IS802MAP' is defined on line 1183, but no explicit reference was found in the text == Unused Reference: 'RSVPMIB' is defined on line 1189, but no explicit reference was found in the text == Unused Reference: 'HCRMON' is defined on line 1271, but no explicit reference was found in the text == Unused Reference: 'ASN1' is defined on line 1276, but no explicit reference was found in the text == Unused Reference: 'ASN1BER' is defined on line 1282, but no explicit reference was found in the text == Unused Reference: 'PROCESS' is defined on line 1296, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IS802' -- Possible downref: Non-RFC (?) normative reference: ref. 'SBM' -- Possible downref: Non-RFC (?) normative reference: ref. 'IS802MAP' ** Obsolete normative reference: RFC 2571 (ref. 'ARCH') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'V1PROTO') ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'V1TRAPS') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'V2COMMUNITY') ** Obsolete normative reference: RFC 1906 (ref. 'V2TRANS') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1905 (ref. 'V2PROTO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2570 (ref. 'V3INTRO') (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2572 (ref. 'V3MPC') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. 'V3USM') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2573 (ref. 'V3APPS') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. 'V3VACM') (Obsoleted by RFC 3415) -- Possible downref: Non-RFC (?) normative reference: ref. 'HCRMON' -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN1BER' Summary: 18 errors (**), 0 flaws (~~), 11 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft A. Smith 2 Expires April 2000 Extreme Networks 3 draft-ietf-issll-is802-sbm-mib-01.txt R. Pabbati 4 Microsoft 5 October 1999 7 Definitions of Managed Parameters for SBM network nodes 9 Status of this Memo 11 This document is an Internet Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. Internet Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its Areas, and 14 its Working Groups. Note that other groups may also distribute working 15 documents as Internet Drafts. 17 Internet Drafts are draft documents valid for a maximum of six months. 18 Internet Drafts may be updated, replaced, or obsoleted by other 19 documents at any time. It is not appropriate to use Internet Drafts as 20 reference material or to cite them other than as a "working draft" or 21 "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 This document is a product of the IETF's Integrated Services over 30 Specific Lower- Layers (ISSLL) Working Group. Copyright (C) The 31 Internet Society (1999). All Rights Reserved. 33 Abstract 35 This memo includes a list of manageable parameters for RSVP/SBM server 36 implementations. These are in addition to those already described in RFC 37 2206 and RFC 2213. Specifically, it describes parameters for control of 38 the base signaling protocols themselves, as well as some of the 39 admission control decisions. These definitions are not intended to be 40 exhaustive but they have been identified as useful for practical 41 implementations. 43 1. Introduction 45 SBM server components of the ISSLL/IS802 architecture require some 46 configuration parameters for operational use. These fall into 2 main 47 areas: configuration of RSVP protocol operation and configuration of 48 SBM-specific parts. For the former, RFC 2206 and RFC 2213 cover some 49 configuration operations as SNMP MIBS and some additional objects are 50 provided here. 52 This memo includes a MIB module in a manner that is compliant to the 53 SNMPv2 SMI [V2SMI]. 55 2. The SNMP Management Framework 57 The SNMP Management Framework presently consists of five major 58 components: 60 o An overall architecture, described in an Architecture for 61 Describing SNMP Management Frameworks [ARCH]. 63 o Mechanisms for describing and naming objects and events for the 64 purpose of management. The first version of this Structure of 65 Management Information (SMI) is called SMIv1 and described in 66 RFC 1155 [V1SMI], STD 16, RFC 1212 [V1CONCISE] and RFC 1215 67 [V1TRAPS]. The second version, called SMIv2, is described in 68 STD 58, RFC 2578 [V2SMI], STD 58, RFC 2579 [V2TC] and STD 58, 69 RFC 2580 [V2CONFORM]. 71 o Message protocols for transferring management information. The 72 first version of the SNMP message protocol is called SNMPv1 and 73 described in STD 15, RFC 1157 [V1PROTO]. A second version of 74 the SNMP message protocol, which is not an Internet standards 75 track protocol, is called SNMPv2c and described in RFC 1901 76 [V2COMMUNITY] and RFC 1906 [V2TRANS]. The third version of the 77 message protocol is called SNMPv3 and described in RFC1906 78 [V2TRANS], Message Processing and Dispatching [V3MPC] and User- 79 based Scurity Model [V3USM]. 81 o Protocol operations for accessing management information. The 82 first set of protocol operations and associated PDU formats is 83 described in STD 15, RFC 1157 [V1PROTO]. A second set of 84 protocol operations and associated PDU formats is described in 85 RFC 1905 [V2PROTO]. 87 o A set of fundamental applications described in SNMPv3 88 Applications [V3APPS] and the view-based access control 89 mechanism described in View-based Access Control Model [V3VACM]. 91 A more detailed introduction to the current SNMP Management Framework 92 can be found in RFC 2570 [V3INTRO]. 94 Managed objects are accessed via a virtual information store, termed the 95 Management Information Base or MIB. Objects in the MIB are defined 96 using the mechanisms defined in the SMI. 98 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 99 conforming to the SMIv1 can be produced through the appropriate 100 translations. The resulting translated MIB must be semantically 101 equivalent, except where objects or events are omitted because no 102 translation is possible (use of Counter64). Some machine readable 103 information in SMIv2 will be converted into textual descriptions in 104 SMIv1 during the translation process. However, this loss of machine 105 readable information is not considered to change the semantics of the 106 MIB. 108 3. Structure of SBM Server MIB 110 Objects in this MIB are arranged into groups. Each group is organized 111 as a set of related objects. The overall structure is described below. 113 3.1. sbmSbmConfigGroup 115 This group contains objects for configuration of SBM operation. The 116 sbmConfigTable includes the reporting of some hard-coded parameters 117 of an SBM implementation and some current state variables. The 118 sbmTrafficClassConfigTable controls the admission of RSVP sessions 119 into IEEE 802 traffic classes. 121 3.2. sbmRsvpConfigGroup 123 This group contains objects that control operation of the RSVP 124 protocol for each SBM instance. The sbmRsvpConfigTable controls 125 behaviour related to policy control on RSVP sessions. 127 3.3. sbmSbmStatisticsGroup and sbmSbmHCStatisticsGroup 129 These groups contains objects in the sbmStatsTable that represent 130 protocol statistics for the RSVP/SBM protocol. The 131 sbmSbmHCStatisticsGroup includes objects that only need to be 132 implemented for high speed interfaces where 32-bit counters are 133 insufficient to represent the values. 135 3.4. Relationship to Other MIBs 137 3.4.1. Relationship to the 'system' group 139 In MIB-II, the 'system' group is defined as being mandatory for all 140 systems such that each managed entity contains one instance of each 141 object in the 'system' group. Thus, those objects apply to the 142 entity as a whole irrespective of whether the entity's sole 143 functionality is the SBM protocol or whether this is only a subset 144 of the entity's functionality. 146 3.4.2. Relation to Interfaces MIB 148 The Interface MIB Evolution [INTERFACEMIB], requires that any MIB 149 which is an adjunct of the Interface MIB, clarify specific areas 150 within the Interface MIB. These areas were intentionally left 151 vague in the Interface MIB Evolution to avoid over-constraining the 152 MIB, thereby precluding management of certain media-types. 154 3.4.3. Relation to Integrated Services MIBs 156 SBM interfaces which are capable of handling outgoing sessions 157 should each be represented by an entry in the per-interface tables 158 of this MIB [INTSERVMIB]. . 160 SBM interfaces which are capable of handling outgoing Guaranteed 161 Service sessions should be represented by an entry in 162 intSrvGuaranteedIfTable [INTSERVGSMIB. This entry can be used to 163 characterise the delay parameters that the SBM will use in its 164 admission control algorithms. 166 4. Editorial information 168 169 4.1. Open Issues resolved in this draft 171 (1) Should we include DCLASS as well as TCLASS config info here? NO. 173 (3) Should we allow creation of new SBM instances? (MIB currently only 174 allows configuration of existing SBMs and assumes that the agent 175 will create SBM instances appropriately). NO. 177 4.2. Other changes in this draft 179 (4) Modified descriptive text for tables e.g. sbmConfigTable to 180 indicate what entries are expected for what types of SBM. Added new 181 variable sbmType to describe whether this SBM instance is for a 182 whole subnet, for half-duplex interface (both directions) or full- 183 duplex interface (one direction only). 185 (5) Added references to IEEE 802.1D traffic classes. 187 (6) Added DEFVAL "enabled" for sbmTrafficClassEnabled. 189 (7) Added descriptions for stats counters. 191 (9) Added sbmDsbmElectionState to report the current DSBM election 192 state and sbmDsbmLastStateChange, a timestamp for when it got 193 there. 195 (10) sbmStatsActiveOutgoingFlows, sbmStatsAllocatedOutgoingBits, 196 sbmStatsMaxAllocatedBandwidthBits: changed from Counter32 to 197 Gauge32. 199 (11) Added 64-bit versions of sbmStatsAllocatedOutgoingBits, 200 sbmStatsMaxAllocatedBandwidthBits with appropriate conformance 201 clauses. These rely on HCRMON's Gauge64 TC. 203 (12) Merged sbmStatsInPolicyControlFailures and 204 sbmStatsOutPolicyControlFailures into 205 sbmStatsPolicyControlFailures. 207 Miscellaneous editorial fixes. 209 4.3. Still Open Issues 211 (2) How to represent more detailed e.g. per-queue/per-class 212 information. We could use the per-interface tables from 213 RFC2213/RFC2214 int-serv MIBs but we would then need one of these 214 per queue per interface. this might need ifStackTable to group them 215 together. Could also try to use the intSrvflowQueue object for 216 this. 218 (8) Should counters be zeroed whenever a SBM enters I_AM_DSBM state? 219 (Propose: NO) 221 5. Definitions for SBM Server MIB 223 SBM-SERVER-MIB DEFINITIONS ::= BEGIN 225 -- ------------------------------------------------------------- 226 -- ------------------------------------------------------------- 228 IMPORTS 229 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 230 Integer32, Gauge32 231 FROM SNMPv2-SMI 232 RmonGauge64 233 FROM HC-RMON-MIB 234 TimeStamp, TruthValue 235 FROM SNMPv2-TC 236 InterfaceIndex 237 FROM IF-MIB 238 SnmpAdminString 239 FROM SNMP-FRAMEWORK-MIB 240 MODULE-COMPLIANCE, OBJECT-GROUP 241 FROM SNMPv2-CONF 242 BurstSize, BitRate, MessageSize 243 FROM INTEGRATED-SERVICES-MIB; 245 -- 246 -- REFERENCE 247 -- "Resource Reservation Protocol (RSVP) - Version 1 Functional 248 -- Specification", RFC 2205" 249 -- 250 -- "SBM (Subnet Bandwidth Manager): A Protocol for Admission 251 -- Control over IEEE 802-style Networks" (draft-ietf-issll-sbm-08.txt) 253 sbmMIB MODULE-IDENTITY 254 LAST-UPDATED "9910190000Z" 255 ORGANIZATION "IETF Integrated Services over Specific Lower-Layers 256 Working Group" 257 CONTACT-INFO 258 " John Wroclawski (Co-chair of ISSLL WG) 259 Phone: +1 617 253 7885 260 Email: jtw@lcs.mit.edu 262 Eric Crawley (Co-chair of ISSLL WG) 263 Phone: +1 978 486 0665 x125 264 Email: esc@argon.com 265 Editor: Andrew Smith 266 Phone: +1 408 579 2821 267 Email: andrew@extremenetworks.com 269 Editor: Ramesh Pabbati 270 Phone: +1 425 936 9438 271 Email: rameshpa@microsoft.com" 272 DESCRIPTION 273 "The SBM MIB module" 275 REVISION "9910190000Z" 276 DESCRIPTION "This version published as draft-ietf-issll-is80-sbm-mib-01." 278 ::= { xxx 1 } 280 sbmMIBObjects OBJECT IDENTIFIER ::= { sbmMIB 1 } 282 -- ------------------------------------------------------------- 283 -- SBM Server Parameters 284 -- ------------------------------------------------------------- 286 sbmConfigTable OBJECT-TYPE 287 SYNTAX SEQUENCE OF SbmConfigEntry 288 MAX-ACCESS not-accessible 289 STATUS current 290 DESCRIPTION 291 "A table of configuration information per SBM instance. There may be 292 one instance per subnet for a shared LAN. For a switched LAN there 293 may be once instance per LAN segment/network-interface. For a full- 294 duplex switched LAN segment the SBM instance only represents the 295 transmit direction: in this case the receive controls will have no 296 effect. 298 Entries in this table are created automatically by the agent 299 when a new SBM entity is created e.g. by addition of new physical 300 hardware or creation of a new subnet." 301 ::= { sbmMIBObjects 1 } 303 sbmConfigEntry OBJECT-TYPE 304 SYNTAX SbmConfigEntry 305 MAX-ACCESS not-accessible 306 STATUS current 307 DESCRIPTION 308 "A set of SBM protocol configuration variables for a given 309 SBM instance." 310 INDEX { sbmIndex } 311 ::= { sbmConfigTable 1 } 313 SbmConfigEntry ::= 314 SEQUENCE { 315 sbmIndex Integer32, 316 sbmDescription SnmpAdminString, 317 sbmType INTEGER, 318 sbmIfIndex InterfaceIndex, 319 sbmEnable TruthValue, 320 sbmDsbmRefreshInterval Integer32, 321 sbmDsbmDeadInterval Integer32, 322 sbmDsbmElectionPriority INTEGER, 323 sbmDsbmElectionState INTEGER, 324 sbmDsbmLastStateChange TimeStamp, 325 sbmDsbmMaxNonResvTxBucketRate BitRate, 326 sbmDsbmMaxNonResvTxBucketDepth BurstSize, 327 sbmDsbmMaxNonResvTxPeakRate BitRate, 328 sbmDsbmMaxNonResvTxMinPolicedSize MessageSize, 329 sbmDsbmMaxNonResvTxMaxPacketSize MessageSize 330 } 332 sbmIndex OBJECT-TYPE 333 SYNTAX Integer32 334 MAX-ACCESS not-accessible 335 STATUS current 336 DESCRIPTION 337 "An integer representing a particular SBM instance." 338 ::= { sbmConfigEntry 1 } 340 sbmDescription OBJECT-TYPE 341 SYNTAX SnmpAdminString 342 MAX-ACCESS read-write 343 STATUS current 344 DESCRIPTION 345 "A description of this SBM instance." 346 ::= { sbmConfigEntry 2 } 348 sbmType OBJECT-TYPE 349 SYNTAX INTEGER { 350 sbmTypeOther(1), 351 sbmTypeUnknown(2), 352 sbmTypeSubnet(3), 353 sbmTypeHalfDuplexInterface(4), 354 sbmTypeFullDuplexTxInterface(5) 355 } 356 MAX-ACCESS read-only 357 STATUS current 358 DESCRIPTION 359 "An indicator of the type of LAN segment or domain of control 360 of this SBM instance. 362 A value of sbmTypeSubnet(3) indicates that this SBM instance 363 performs RSVP admission control for a complete IP subnet 364 that is reached through the interface indicated by sbmIfIndex. 366 A value of sbmTypeHalfDuplexInterface(4) indicated that this 367 SBM instance performs RSVP admission control for just the LAN 368 segment that is reached through the interface indicated by 369 sbmIfIndex which is a half-duplex segment with other potential 370 transmitters on it. 372 A value of sbmTypeFullDuplexTxInterface(5) indicates that this 373 SBM instance performs RSVP admission control for just the 374 transmit direction of the full-duplex LAN segment that is 375 reached through the interface indicated by sbmIfIndex: this 376 segment, by definition, will have no other transmitters on it. 377 In this case, the receive statistics in sbmStatsTable may be 378 invalid. 380 A value of sbmTypeUnknown(2) indicates that the domain of control 381 for this SBM instance is not yet known. A value of sbmTypeOther(1) 382 indicates that this SBM instance has some other domain of control." 383 ::= { sbmConfigEntry 3 } 385 sbmIfIndex OBJECT-TYPE 386 SYNTAX InterfaceIndex 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "The interface index representing the domain of 391 control of this SBM instance: e.g. this might be a physical 392 interface on a switch device or it might be a subnet represented by 393 a propVirtual(53) interface entry. A value of 0 represents an SBM 394 instance that has no association to any one particular ifTable entry." 395 ::= { sbmConfigEntry 4 } 397 sbmEnable OBJECT-TYPE 398 SYNTAX TruthValue 399 MAX-ACCESS read-write 400 STATUS current 401 DESCRIPTION 402 "Control the SBM processing of messages. This SBM will only 403 attempt to become DSBM and actually control allocation if it 404 wins the DSBM election procedure, as controlled by the following 405 parameters. If this SBM does not win that procedure but this flag 406 is still true(1) then it will act as a client in the SBM protocol 407 and will forward RSVP/SBM messages to the elected DSBM. 409 If this flag is false(2) then this node will act as a normal RSVP 410 protocol entity." 411 DEFVAL { true } 412 ::= { sbmConfigEntry 5 } 414 sbmDsbmRefreshInterval OBJECT-TYPE 415 SYNTAX Integer32 416 UNITS "seconds" 417 MAX-ACCESS read-write 418 STATUS current 419 DESCRIPTION 420 "DSBM refresh interval." 421 DEFVAL { 5 } 422 ::= { sbmConfigEntry 6 } 424 sbmDsbmDeadInterval OBJECT-TYPE 425 SYNTAX Integer32 426 UNITS "seconds" 427 MAX-ACCESS read-write 428 STATUS current 429 DESCRIPTION 430 "DSBM Election dead time." 431 DEFVAL { 15 } 432 ::= { sbmConfigEntry 7 } 434 sbmDsbmElectionPriority OBJECT-TYPE 435 SYNTAX INTEGER (0..255) 436 MAX-ACCESS read-write 437 STATUS current 438 DESCRIPTION 439 "Election bid for this SBM to become DSBM." 440 DEFVAL { 4 } 441 ::= { sbmConfigEntry 8 } 443 sbmDsbmElectionState OBJECT-TYPE 444 SYNTAX INTEGER { 445 sbmStateOther(1), 446 sbmStateUnknown(2), 447 sbmStateDetectDsbm(3), 448 sbmStateElectDsbm(4), 449 sbmStateIdle(5), 450 sbmStateIAmDsbm(6), 451 sbmStateShutdown(7) 452 } 453 MAX-ACCESS read-only 454 STATUS current 455 DESCRIPTION 456 "The current state of DSBM election for this SBM instance. 458 Values of sbmStateOther(1) or sbmStateUnknown(2) indicate that 459 this SBM instance is in a non-standard or an unknown state. 461 Values of sbmStateDetectDsbm(3) and sbmStateElectDsbm(4) 462 indicate that this SBM instance is participating in an DSBM 463 election procedure that has not yet completed. 465 A value of sbmStateIdle(5) indicates that this SBM instance 466 has discovered another SBM within its domain of control that 467 has a higher election priority and so it is acting as a SBM client. 469 A value of sbmStateIAmDsbm(6) indicates that this SBM instance 470 is in control of admission control over its domain of control. 472 A value of sbmStateShutdown(7) indicates that this SBM instance 473 is not participating in DSBM election." 474 REFERENCE "draft-ietf-issll-is802-sbm-08 Appendix A." 475 ::= { sbmConfigEntry 9 } 477 sbmDsbmLastStateChange OBJECT-TYPE 478 SYNTAX TimeStamp 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "The time at which this SBM instance entered the current DSBM 483 election state." 484 ::= { sbmConfigEntry 10 } 486 sbmDsbmMaxNonResvTxBucketRate OBJECT-TYPE 487 SYNTAX BitRate 488 UNITS "bits per second" 489 MAX-ACCESS read-write 490 STATUS current 491 DESCRIPTION 492 "Maximum Bucket rate that can be sent with out a reservation. 493 This is one of the parameters of the effective Tspec that senders 494 are allowed to use before any reservation is in place." 495 REFERENCE "RFC2210 section 3.1" 496 ::= { sbmConfigEntry 11 } 498 sbmDsbmMaxNonResvTxBucketDepth OBJECT-TYPE 499 SYNTAX BurstSize 500 UNITS "bytes" 501 MAX-ACCESS read-write 502 STATUS current 503 DESCRIPTION 504 "Maximum Bucket Depth that can be sent with out a reservation. 505 This is one of the parameters of the effective Tspec that senders 506 are allowed to use before any reservation is in place." 507 REFERENCE "RFC2210 section 3.1" 508 ::= { sbmConfigEntry 12 } 510 sbmDsbmMaxNonResvTxPeakRate OBJECT-TYPE 511 SYNTAX BitRate 512 UNITS "bits per second" 513 MAX-ACCESS read-write 514 STATUS current 515 DESCRIPTION 516 "Maximum Peak rate that can be sent with out a reservation. This is 517 one of the parameters of the effective Tspec that senders are 518 allowed to use before any reservation is in place." 519 REFERENCE "RFC2210 section 3.1" 520 ::= { sbmConfigEntry 13 } 522 sbmDsbmMaxNonResvTxMinPolicedSize OBJECT-TYPE 523 SYNTAX MessageSize 524 UNITS "bytes" 525 MAX-ACCESS read-write 526 STATUS current 527 DESCRIPTION 528 "Minimum Policed size that can be sent with out a reservation. 529 This is one of the parameters of the effective Tspec that senders are 530 allowed to use before any reservation is in place." 531 REFERENCE "RFC2210 section 3.1" 532 ::= { sbmConfigEntry 14 } 534 sbmDsbmMaxNonResvTxMaxPacketSize OBJECT-TYPE 535 SYNTAX MessageSize 536 UNITS "bytes" 537 MAX-ACCESS read-write 538 STATUS current 539 DESCRIPTION 540 "Maximum packet length that can be sent with out a reservation. 541 This is one of the parameters of the effective Tspec that senders are 542 allowed to use before any reservation is in place." 543 REFERENCE "RFC2210 section 3.1" 544 ::= { sbmConfigEntry 15 } 546 -- ------------------------------------------------------------- 547 -- SBM Traffic Class Mapping Table 548 -- ------------------------------------------------------------- 550 sbmTrafficClassConfigTable OBJECT-TYPE 551 SYNTAX SEQUENCE OF SbmTrafficClassConfigEntry 552 MAX-ACCESS not-accessible 553 STATUS current 554 DESCRIPTION 555 "A table of parameters for configuring the characteristics of 556 the mapping of sessions into layer-2 traffic classes." 557 ::= { sbmMIBObjects 2 } 559 sbmTrafficClassConfigEntry OBJECT-TYPE 560 SYNTAX SbmTrafficClassConfigEntry 561 MAX-ACCESS not-accessible 562 STATUS current 563 DESCRIPTION 564 "A set of RSVP protocol configuration variables for a given 565 SBM instance." 566 INDEX { sbmIndex, sbmTrafficClass } 567 ::= { sbmTrafficClassConfigTable 1 } 569 SbmTrafficClassConfigEntry ::= 570 SEQUENCE { 571 sbmTrafficClass INTEGER (0..7), 572 sbmDelayBoundTarget Integer32, 573 sbmTrafficClassEnabled TruthValue 574 } 576 sbmTrafficClass OBJECT-TYPE 577 SYNTAX INTEGER (0..7) 578 MAX-ACCESS not-accessible 579 STATUS current 580 DESCRIPTION 581 "Traffic Class (802.1p user_priority)." 582 REFERENCE 583 "ISO/IEC 15802-3: 1998" 584 ::= { sbmTrafficClassConfigEntry 1 } 586 sbmDelayBoundTarget OBJECT-TYPE 587 SYNTAX Integer32 588 UNITS "micro-seconds" 589 MAX-ACCESS read-write 590 STATUS current 591 DESCRIPTION 592 "Target delay bound on flows admitted to this class. 593 A value of 0 indicates that there is no quantitative delay bound 594 target associated with this class. Suitable default values for 595 these targets are discussed in a companion document." 596 REFERENCE 597 "draft-ietf-issll-is802-svc-mapping-04.txt" 598 ::= { sbmTrafficClassConfigEntry 2 } 600 sbmTrafficClassEnabled OBJECT-TYPE 601 SYNTAX TruthValue 602 MAX-ACCESS read-write 603 STATUS current 604 DESCRIPTION 605 "Enable admission of flows to this class." 606 DEFVAL { true } 607 ::= { sbmTrafficClassConfigEntry 3 } 609 -- ------------------------------------------------------------- 610 -- RSVP Configuration Parameters 611 -- ------------------------------------------------------------- 613 sbmRsvpConfigTable OBJECT-TYPE 614 SYNTAX SEQUENCE OF SbmRsvpConfigEntry 615 MAX-ACCESS not-accessible 616 STATUS current 617 DESCRIPTION 618 "A table of configuration information for the RSVP protocol 619 per SBM instance. There may be one instance per subnet for a 620 shared LAN. For a switched LAN there may be once instance per 621 LAN segment/network-interface. For a full-duplex switched LAN 622 segment the SBM instance only represents the transmit direction: 623 in this case the receive controls will have no effect. 625 Entries in this table are created automatically by the agent 626 when a new SBM entity is created e.g. by addition of new physical 627 hardware or creation of a new subnet." 628 ::= { sbmMIBObjects 3 } 630 sbmRsvpConfigEntry OBJECT-TYPE 631 SYNTAX SbmRsvpConfigEntry 632 MAX-ACCESS not-accessible 633 STATUS current 634 DESCRIPTION 635 "A set of RSVP protocol configuration variables for a given 636 SBM instance." 637 INDEX { sbmIndex } 638 ::= { sbmRsvpConfigTable 1 } 640 SbmRsvpConfigEntry ::= 641 SEQUENCE { 642 sbmRsvpCopsEnabled TruthValue, 643 sbmRsvpSenderPolicyEnabled TruthValue, 644 sbmRsvpReceiverPolicyEnabled TruthValue 645 } 647 sbmRsvpCopsEnabled OBJECT-TYPE 648 SYNTAX TruthValue 649 MAX-ACCESS read-write 650 STATUS current 651 DESCRIPTION 652 "Enable outsourcing of local policy decisions via the COPS protocol." 653 DEFVAL { false } 654 ::= { sbmRsvpConfigEntry 1 } 656 sbmRsvpSenderPolicyEnabled OBJECT-TYPE 657 SYNTAX TruthValue 658 MAX-ACCESS read-write 659 STATUS current 660 DESCRIPTION 661 "Enable processing of RSVP policy objects in PATH messages." 662 DEFVAL { false } 663 ::= { sbmRsvpConfigEntry 2 } 665 sbmRsvpReceiverPolicyEnabled OBJECT-TYPE 666 SYNTAX TruthValue 667 MAX-ACCESS read-write 668 STATUS current 669 DESCRIPTION 670 "Enable processing of RSVP policy objects in RESV messages." 671 DEFVAL { false } 672 ::= { sbmRsvpConfigEntry 3 } 674 -- ------------------------------------------------------------- 675 -- SBM statistics 676 -- ------------------------------------------------------------- 678 sbmStatsTable OBJECT-TYPE 679 SYNTAX SEQUENCE OF SbmStatsEntry 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "A table of statistics per SBM instance. There may be one 684 instance per subnet for a shared LAN. For a switched LAN there 685 may be once instance per LAN segment/network-interface. For a 686 full-duplex switched LAN segment the SBM instance only represents 687 the transmit direction: in this case the receive statistics will 688 not be valid. 690 Entries in this table are created automatically by the agent 691 when a new SBM entity is created e.g. by addition of new physical 692 hardware or creation of a new subnet. Counters are continuous 693 from restart of the agent." 694 ::= { sbmMIBObjects 4 } 696 sbmStatsEntry OBJECT-TYPE 697 SYNTAX SbmStatsEntry 698 MAX-ACCESS not-accessible 699 STATUS current 700 DESCRIPTION 701 "A set of SBM protocol statistics for a given SBM instance." 702 INDEX { sbmIndex } 703 ::= { sbmStatsTable 1 } 705 SbmStatsEntry ::= 706 SEQUENCE { 707 sbmStatsSbmSentBytes Counter32, 708 sbmStatsSbmReceivedBytes Counter32, 709 sbmStatsReceivedRsvpPathMsgs Counter32, 710 sbmStatsReceivedRsvpResvMsgs Counter32, 711 sbmStatsReceivedRsvpPathErrMsgs Counter32, 712 sbmStatsReceivedRsvpResvErrMsgs Counter32, 713 sbmStatsReceivedRsvpPathTearMsgs Counter32, 714 sbmStatsReceivedRsvpResvTearMsgs Counter32, 715 sbmStatsReceivedRsvpConfirmMsgs Counter32, 716 sbmStatsReceivedRsvpBadMsgs Counter32, 717 sbmStatsSentRsvpPathMsgs Counter32, 718 sbmStatsSentRsvpResvMsgs Counter32, 719 sbmStatsSentRsvpPathErrMsgs Counter32, 720 sbmStatsSentRsvpResvErrMsgs Counter32, 721 sbmStatsSentRsvpPathTearMsgs Counter32, 722 sbmStatsSentRsvpResvTearMsgs Counter32, 723 sbmStatsSentRsvpConfirmMsgs Counter32, 724 sbmStatsAdmissionControlFailures Counter32, 725 sbmStatsPolicyControlFailures Counter32, 726 sbmStatsOtherFailures Counter32, 727 sbmStatsInBlockadeStateResvs Counter32, 728 sbmStatsResvTimeOuts Counter32, 729 sbmStatsPathTimeOuts Counter32, 730 sbmStatsReceiveFailsBigMsg Counter32, 731 sbmStatsSendFailsBigMsg Counter32, 732 sbmStatsReceiveFailsNoResource Counter32, 733 sbmStatsSendFailsNoResource Counter32, 734 sbmStatsActiveOutgoingFlows Gauge32, 735 sbmStatsAllocatedOutgoingBits Gauge32, 736 sbmStatsMaxAllocatedBandwidthBits Gauge32, 737 sbmStatsHCAllocatedOutgoingBits RmonGauge64, 738 sbmStatsHCMaxAllocatedBandwidthBits RmonGauge64 739 } 741 sbmStatsSbmSentBytes OBJECT-TYPE 742 SYNTAX Counter32 743 UNITS "bytes" 744 MAX-ACCESS read-only 745 STATUS current 746 DESCRIPTION 747 "The number of bytes of RSVP messages sent by this SBM 748 instance. This includes only the contents of the messages, 749 not any IP or lower-layer framing headers." 750 ::= { sbmStatsEntry 1 } 752 sbmStatsSbmReceivedBytes OBJECT-TYPE 753 SYNTAX Counter32 754 UNITS "bytes" 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "The number of bytes of RSVP messages received by this SBM 759 instance. This includes only the contents of the messages, 760 not any IP or lower-layer framing headers." 761 ::= { sbmStatsEntry 2 } 763 sbmStatsReceivedRsvpPathMsgs OBJECT-TYPE 764 SYNTAX Counter32 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "The number of RSVP PATH messages received by this SBM 769 instance." 770 ::= { sbmStatsEntry 3 } 772 sbmStatsReceivedRsvpResvMsgs OBJECT-TYPE 773 SYNTAX Counter32 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "The number of RSVP RESV messages received by this SBM 778 instance." 779 ::= { sbmStatsEntry 4 } 781 sbmStatsReceivedRsvpPathErrMsgs OBJECT-TYPE 782 SYNTAX Counter32 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION 786 "The number of RSVP PATH ERROR messages received by this SBM 787 instance." 788 ::= { sbmStatsEntry 5 } 790 sbmStatsReceivedRsvpResvErrMsgs OBJECT-TYPE 791 SYNTAX Counter32 792 MAX-ACCESS read-only 793 STATUS current 794 DESCRIPTION 795 "The number of RSVP RESV ERROR messages received by this SBM 796 instance." 797 ::= { sbmStatsEntry 6 } 799 sbmStatsReceivedRsvpPathTearMsgs OBJECT-TYPE 800 SYNTAX Counter32 801 MAX-ACCESS read-only 802 STATUS current 803 DESCRIPTION 804 "The number of RSVP PATH TEAR messages received by this SBM 805 instance." 806 ::= { sbmStatsEntry 7 } 808 sbmStatsReceivedRsvpResvTearMsgs OBJECT-TYPE 809 SYNTAX Counter32 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "The number of RSVP RESV TEAR messages received by this SBM 814 instance." 815 ::= { sbmStatsEntry 8 } 817 sbmStatsReceivedRsvpConfirmMsgs OBJECT-TYPE 818 SYNTAX Counter32 819 MAX-ACCESS read-only 820 STATUS current 821 DESCRIPTION 822 "The number of RSVP CONFIRM messages received by this SBM 823 instance." 824 ::= { sbmStatsEntry 9 } 826 sbmStatsReceivedRsvpBadMsgs OBJECT-TYPE 827 SYNTAX Counter32 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "The number of RSVP messages received by this SBM instance 832 with bad syntax or semantics." 833 ::= { sbmStatsEntry 10 } 835 sbmStatsSentRsvpPathMsgs OBJECT-TYPE 836 SYNTAX Counter32 837 MAX-ACCESS read-only 838 STATUS current 839 DESCRIPTION 840 "The number of RSVP PATH messages sent by this SBM instance." 841 ::= { sbmStatsEntry 11 } 843 sbmStatsSentRsvpResvMsgs OBJECT-TYPE 844 SYNTAX Counter32 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION 848 "The number of RSVP RESV messages sent by this SBM instance." 850 ::= { sbmStatsEntry 12 } 852 sbmStatsSentRsvpPathErrMsgs OBJECT-TYPE 853 SYNTAX Counter32 854 MAX-ACCESS read-only 855 STATUS current 856 DESCRIPTION 857 "The number of RSVP PATH ERROR messages sent by this SBM 858 instance." 859 ::= { sbmStatsEntry 13 } 861 sbmStatsSentRsvpResvErrMsgs OBJECT-TYPE 862 SYNTAX Counter32 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "The number of RSVP RESV ERROR messages sent by this SBM 867 instance." 868 ::= { sbmStatsEntry 14 } 870 sbmStatsSentRsvpPathTearMsgs OBJECT-TYPE 871 SYNTAX Counter32 872 MAX-ACCESS read-only 873 STATUS current 874 DESCRIPTION 875 "The number of RSVP PATH TEAR messages sent by this SBM 876 instance." 877 ::= { sbmStatsEntry 15 } 879 sbmStatsSentRsvpResvTearMsgs OBJECT-TYPE 880 SYNTAX Counter32 881 MAX-ACCESS read-only 882 STATUS current 883 DESCRIPTION 884 "The number of RSVP RESV TEAR messages sent by this SBM 885 instance." 886 ::= { sbmStatsEntry 16 } 888 sbmStatsSentRsvpConfirmMsgs OBJECT-TYPE 889 SYNTAX Counter32 890 MAX-ACCESS read-only 891 STATUS current 892 DESCRIPTION 893 "The number of RSVP CONFIRM messages sent by this SBM 894 instance." 896 ::= { sbmStatsEntry 17 } 898 sbmStatsAdmissionControlFailures OBJECT-TYPE 899 SYNTAX Counter32 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "The number of times an RSVP session was denied due to lack 904 of data-path resources by this SBM instance." 905 ::= { sbmStatsEntry 18 } 907 sbmStatsPolicyControlFailures OBJECT-TYPE 908 SYNTAX Counter32 909 MAX-ACCESS read-only 910 STATUS current 911 DESCRIPTION 912 "The number of times an RSVP session was denied due to failure 913 of policy controls applied by this SBM instance." 914 ::= { sbmStatsEntry 19 } 916 sbmStatsOtherFailures OBJECT-TYPE 917 SYNTAX Counter32 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "The number of times an RSVP session was denied by this SBM instance 922 due to other reasons." 923 ::= { sbmStatsEntry 20 } 925 sbmStatsInBlockadeStateResvs OBJECT-TYPE 926 SYNTAX Counter32 927 MAX-ACCESS read-only 928 STATUS current 929 DESCRIPTION 930 "The number of times an RSVP message caused the creation of blockade 931 state by this SBM instance." 932 ::= { sbmStatsEntry 21 } 934 sbmStatsResvTimeOuts OBJECT-TYPE 935 SYNTAX Counter32 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "The number of times an RSVP session was torn down by this SBM instance 940 due to timeout of RESV refreshes." 942 ::= { sbmStatsEntry 22 } 944 sbmStatsPathTimeOuts OBJECT-TYPE 945 SYNTAX Counter32 946 MAX-ACCESS read-only 947 STATUS current 948 DESCRIPTION 949 "The number of times an RSVP session was torn down by this SBM instance 950 due to timeout of PATH refreshes." 951 ::= { sbmStatsEntry 23 } 953 sbmStatsReceiveFailsBigMsg OBJECT-TYPE 954 SYNTAX Counter32 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION 958 "The number of times an RSVP message was received by this SBM instance 959 but discarded due to excessive size." 960 ::= { sbmStatsEntry 24 } 962 sbmStatsSendFailsBigMsg OBJECT-TYPE 963 SYNTAX Counter32 964 MAX-ACCESS read-only 965 STATUS current 966 DESCRIPTION 967 "The number of times an RSVP message should have been transmitted by 968 this SBM instance but was prevented due to excessive size." 969 ::= { sbmStatsEntry 25 } 971 sbmStatsReceiveFailsNoResource OBJECT-TYPE 972 SYNTAX Counter32 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION 976 "The number of times an RSVP message was received by this SBM instance 977 but was discarded due to insufficient resources to process it." 978 ::= { sbmStatsEntry 26 } 980 sbmStatsSendFailsNoResource OBJECT-TYPE 981 SYNTAX Counter32 982 MAX-ACCESS read-only 983 STATUS current 984 DESCRIPTION 985 "The number of times an RSVP message should have been transmitted by 986 this SBM instance but was prevented due to insufficient resources 987 to send it." 988 ::= { sbmStatsEntry 27 } 990 sbmStatsActiveOutgoingFlows OBJECT-TYPE 991 SYNTAX Gauge32 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "The current number of flows reserved by RSVP by this SBM instance 996 that are outgoing on this interface." 997 ::= { sbmStatsEntry 28 } 999 sbmStatsAllocatedOutgoingBits OBJECT-TYPE 1000 SYNTAX Gauge32 1001 UNITS "bps" 1002 MAX-ACCESS read-only 1003 STATUS current 1004 DESCRIPTION 1005 "The current allocation of bandwidth to flows reserved by RSVP 1006 by this SBM instance that are outgoing on this interface." 1007 ::= { sbmStatsEntry 29 } 1009 sbmStatsMaxAllocatedBandwidthBits OBJECT-TYPE 1010 SYNTAX Gauge32 1011 UNITS "bps" 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "The maximum allocation of bandwidth to flows reserved 1016 by RSVP by this SBM instance that are outgoing on this interface 1017 that has ever occured since the agent restarted." 1018 ::= { sbmStatsEntry 30 } 1020 sbmStatsHCAllocatedOutgoingBits OBJECT-TYPE 1021 SYNTAX RmonGauge64 1022 UNITS "bps" 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "The current allocation of bandwidth to flows reserved by RSVP 1027 by this SBM instance that are outgoing on this interface. This 1028 is a high-capacity version of sbmStatsAllocatedOutgoingBits." 1029 ::= { sbmStatsEntry 31 } 1031 sbmStatsHCMaxAllocatedBandwidthBits OBJECT-TYPE 1032 SYNTAX RmonGauge64 1033 UNITS "bps" 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "The maximum allocation of bandwidth to flows reserved 1038 by RSVP by this SBM instance that are outgoing on this interface 1039 that has ever occured since the agent restarted. This 1040 is a high-capacity version of sbmStatsMaxAllocatedBandwidthBits." 1041 ::= { sbmStatsEntry 32 } 1043 -- ------------------------------------------------------------- 1044 -- Conformance Information 1045 -- ------------------------------------------------------------- 1047 sbmConformance OBJECT IDENTIFIER ::= { sbmMIB 2 } 1049 sbmGroups OBJECT IDENTIFIER ::= { sbmConformance 1 } 1050 sbmCompliances OBJECT IDENTIFIER ::= { sbmConformance 2 } 1052 -- ------------------------------------------------------------- 1053 -- units of conformance 1054 -- ------------------------------------------------------------- 1056 sbmSbmConfigGroup OBJECT-GROUP 1057 OBJECTS { 1058 sbmDescription, sbmType, sbmIfIndex, sbmEnable, 1059 sbmDsbmRefreshInterval, sbmDsbmDeadInterval, 1060 sbmDsbmElectionPriority, sbmDsbmElectionState, 1061 sbmDsbmLastStateChange, sbmDsbmMaxNonResvTxBucketRate, 1062 sbmDsbmMaxNonResvTxBucketDepth, sbmDsbmMaxNonResvTxPeakRate, 1063 sbmDsbmMaxNonResvTxMinPolicedSize, 1064 sbmDsbmMaxNonResvTxMaxPacketSize, 1065 sbmDelayBoundTarget, sbmTrafficClassEnabled 1066 } 1067 STATUS current 1068 DESCRIPTION 1069 "A collection of objects providing per-SBM control over operation 1070 of the SBM protocol." 1071 ::= { sbmGroups 1 } 1073 sbmRsvpConfigGroup OBJECT-GROUP 1074 OBJECTS { 1075 sbmRsvpCopsEnabled, sbmRsvpSenderPolicyEnabled, 1076 sbmRsvpReceiverPolicyEnabled 1078 } 1079 STATUS current 1080 DESCRIPTION 1081 "A collection of objects providing per-SBM control over operation 1082 of the RSVP protocol." 1083 ::= { sbmGroups 2 } 1085 sbmSbmStatisticsGroup OBJECT-GROUP 1086 OBJECTS { 1087 sbmStatsSbmSentBytes, sbmStatsSbmReceivedBytes, 1088 sbmStatsReceivedRsvpPathMsgs, 1089 sbmStatsReceivedRsvpResvMsgs, 1090 sbmStatsReceivedRsvpPathErrMsgs, 1091 sbmStatsReceivedRsvpResvErrMsgs, 1092 sbmStatsReceivedRsvpPathTearMsgs, 1093 sbmStatsReceivedRsvpResvTearMsgs, 1094 sbmStatsReceivedRsvpConfirmMsgs, 1095 sbmStatsReceivedRsvpBadMsgs, 1096 sbmStatsSentRsvpPathMsgs, sbmStatsSentRsvpResvMsgs, 1097 sbmStatsSentRsvpPathErrMsgs, sbmStatsSentRsvpResvErrMsgs, 1098 sbmStatsSentRsvpPathTearMsgs, 1099 sbmStatsSentRsvpResvTearMsgs, 1100 sbmStatsSentRsvpConfirmMsgs, 1101 sbmStatsAdmissionControlFailures, 1102 sbmStatsPolicyControlFailures, sbmStatsOtherFailures, 1103 sbmStatsInBlockadeStateResvs, sbmStatsResvTimeOuts, 1104 sbmStatsPathTimeOuts, sbmStatsReceiveFailsBigMsg, 1105 sbmStatsSendFailsBigMsg, sbmStatsReceiveFailsNoResource, 1106 sbmStatsSendFailsNoResource, 1107 sbmStatsActiveOutgoingFlows, 1108 sbmStatsAllocatedOutgoingBits, 1109 sbmStatsMaxAllocatedBandwidthBits 1110 } 1111 STATUS current 1112 DESCRIPTION 1113 "A collection of objects providing per-SBM statistics of RSVP 1114 protocol operations." 1115 ::= { sbmGroups 3 } 1117 sbmSbmHCStatisticsGroup OBJECT-GROUP 1118 OBJECTS { 1119 sbmStatsHCAllocatedOutgoingBits, 1120 sbmStatsHCMaxAllocatedBandwidthBits 1121 } 1122 STATUS current 1123 DESCRIPTION 1124 "A collection of objects providing per-SBM statistics of RSVP 1125 protocol operations for high-capacity interfaces, defined 1126 as those that have the value of the corresponding instance of 1127 ifSpeed greater than 4^^32-1 bits/second." 1128 ::= { sbmGroups 4 } 1130 -- ------------------------------------------------------------- 1131 -- compliance statements 1132 -- ------------------------------------------------------------- 1134 sbmCompliance MODULE-COMPLIANCE 1135 STATUS current 1136 DESCRIPTION 1137 "The compliance statement for SNMP entities 1138 which manage SBM protocol entities." 1140 MODULE -- this module 1141 MANDATORY-GROUPS 1142 { 1143 sbmSbmConfigGroup, 1144 sbmRsvpConfigGroup, 1145 sbmSbmStatisticsGroup 1146 } 1148 GROUP sbmSbmHCStatisticsGroup 1149 DESCRIPTION 1150 "This group is mandatory for SBM implementations that support 1151 high-capacity interfaces. It is optional for all other 1152 implementations." 1154 OBJECT sbmRsvpEnabled 1155 MIN-ACCESS read-only 1156 DESCRIPTION 1157 "Read-only access is allowed." 1159 ::= { sbmCompliances 1 } 1161 END 1163 6. References 1165 [RSVP] 1166 Braden, R., L. Zhang, S. Berson, S. Herzog, S. Jamin, "Resource 1167 Reservation Protocol (RSVP) - Version 1 Functional Specification", 1168 RFC 2205, September 1997 1170 [IS802] 1171 Ghanwani, A., Pace, W., Srinivasan, V., Smith, A., Seaman, M., "A 1172 Framework for Providing Integrated Services Over Shared and 1173 Switched LAN Technologies", Internet Draft, June 1999. 1174 http://www.ietf.org/internet-drafts/draft-ietf-issll- 1175 is802-framework-07.txt 1177 [SBM] 1178 Yavatkar, R., Hoffman, D., Bernet, Y., Baker, F., Speer, M., "SBM 1179 (Subnet Bandwidth Manager): A Protocol for Admission Control over 1180 IEEE 802-style Networks", Internet Draft, April 1999. 1181 http://www.ietf.org/internet-drafts/draft-ietf-issll-sbm-08.txt 1183 [IS802MAP] 1184 Seaman, M., Smith, A., Crawley, E., "Integrated Service Mappings on 1185 IEEE 802 Networks", Internet Draft, Cmetric, Extreme Networks, 1186 Argon Networks, June 1999. http://www.ietf.org/internet- 1187 drafts/draft-ietf-issll-is802-svc-mapping-04.txt 1189 [RSVPMIB] 1190 Baker, F., Krawczyk, J., Sastry, A., "RSVP Management Information 1191 Base using SMIv2", RFC 2206, Sepember 1997 1193 [INTSERVMIB] 1194 Baker, F., Krawczyk, J., Sastry, A., "Integrated Services 1195 Management Information Base using SMIv2", RFC 2213, Sepember 1997 1197 [ARCH] 1198 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1199 Describing SNMP Management Frameworks", RFC 2571, April 1999 1201 [V1PROTO] 1202 Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network 1203 Management Protocol", STD 15, RFC 1157, May 1990. 1205 [V1SMI] 1206 Rose, M., and K. McCloghrie, "Structure and Identification of 1207 Management Information for TCP/IP-based Internets", STD 16, RFC 1208 1155, May 1990 1210 [V1CONCISE] 1211 Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212 1212, March 1991 1214 [V1TRAPS] 1215 M. Rose, "A Convention for Defining Traps for use with the SNMP", 1216 RFC 1215, March 1991 1218 [V2SMI] 1219 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1220 and S. Waldbusser, "Structure of Management Information Version 2 1221 (SMIv2)", STD 58, RFC 2578, April 1999. 1223 [V2TC] 1224 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1225 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1226 2579, April 1999. 1228 [V2CONFORM] 1229 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1230 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1231 2580, April 1999. 1233 [V2COMMUNITY] 1234 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction 1235 to Community-based SNMPv2", RFC 1901, January 1996. 1237 [V2TRANS] 1238 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport 1239 Mappings for Version 2 of the Simple Network Management Protocol 1240 (SNMPv2)", RFC 1906, January 1996. 1242 [V2PROTO] 1243 Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Protocol 1244 Operations for Version 2 of the Simple Network Management Protocol 1245 (SNMPv2)", RFC 1905, January 1996. 1247 [V3INTRO] 1248 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to 1249 Version 3 of the Internet-standard Network Management Framework", 1250 RFC 2570, April 1999. 1252 [V3MPC] 1253 Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 1254 Processing and Dispatching for the Simple Network Management 1255 Protocol (SNMP)", RFC 2572, April 1999. 1257 [V3USM] 1258 Blumenthal, U. and B. Wijnen, "The User-Based Security Model (USM) 1259 for Version 3 of the Simple Network Management Protocol (SNMPv3)", 1260 RFC 2574, April 1999. 1262 [V3APPS] 1263 Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573, 1264 April 1999. 1266 [V3VACM] 1267 Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 1268 Control Model for the Simple Network Management Protocol (SNMP)", 1269 RFC 2575, April 1999. 1271 [HCRMON] 1272 Waldbusser, S., "Remote Network Monitoring Management Information 1273 Base for High Capacity Networks", http://www.ietf.org/internet- 1274 drafts/draft-ietf-rmonmib-hcrmon-06.txt, June 1999. 1276 [ASN1] 1277 Information processing systems - Open Systems Interconnection - 1278 Specification of Abstract Syntax Notation One (ASN.1), 1279 International Organization for Standardization, International 1280 Standard 8824, December 1987. 1282 [ASN1BER] 1283 Information processing systems - Open Systems Interconnection - 1284 Specification of Basic Encoding Rules for Abstract Notation One 1285 (ASN.1), International Organization for Standardization, 1286 International Standard 8825, December 1987. 1288 [802.1D] 1289 "Information technology - Telecommunications and information 1290 exchange between systems - Local and metropolitan area networks - 1291 Common specifications - Part 3: Media Access Control (MAC) Bridges: 1292 Revision. This is a revision of ISO/IEC 10038: 1993, 802.1j-1992 1293 and 802.6k-1992. It incorporates P802.11c, P802.1p and P802.12e." 1294 ISO/IEC 15802-3: 1998. 1296 [PROCESS] 1297 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, 1298 RFC 2026, October 1996. 1300 7. Security Considerations 1302 There are a number of management objects defined in this MIB that have a 1303 MAX-ACCESS clause of read-write. Such objects may be considered 1304 sensitive or vulnerable in some network environments. The support for 1305 SET operations in a non-secure environment without proper protection can 1306 have a negative effect on network operations. 1308 SNMPv1 by itself is not a secure environment. Even if the network 1309 itself is secure (for example by using IPSec), even then, there is no 1310 control as to who on the secure network is allowed to access and GET/SET 1311 (read/change/create/delete) the objects in this MIB. 1313 It is recommended that the implementers consider the security features 1314 as provided by the SNMPv3 framework. Specifically, the use of the User- 1315 based Security Model [V3USM] and the View-based Access Control Model 1316 [V3VACM] is recommended. 1318 It is then a customer/user responsibility to ensure that the SNMP entity 1319 giving access to an instance of this MIB, is properly configured to give 1320 access to the objects only to those principals (users) that have 1321 legitimate rights to indeed GET or SET (change/create/delete) them. 1323 8. Authors' Addresses 1325 Andrew Smith 1326 Extreme Networks 1327 3585 Monroe St. 1328 Santa Clara CA 95051 1329 USA 1330 Phone: +1 408 579 2821 1331 EMail: andrew@extremenetworks.com 1333 Ramesh Pabbati 1334 Microsoft 1335 1 Microsoft Way 1336 Redmond, WA 98052 1337 USA 1338 Phone: +1 206 936 9438 1339 Email: rameshpa@microsoft.com 1341 Copyright (C) The Internet Society (1999). All Rights Reserved. 1343 This document and translations of it may be copied and furnished 1344 to others, and derivative works that comment on or otherwise 1345 explain it or assist in its implmentation may be prepared, copied, 1346 published and distributed, in whole or in part, without 1347 restriction of any kind, provided that the above copyright notice 1348 and this paragraph are included on all such copies and derivative 1349 works. However, this document itself may not be modified in any 1350 way, such as by removing the copyright notice or references to the 1351 Internet Society or other Internet organizations, except as needed 1352 for the purpose of developing Internet standards in which case the 1353 procedures for copyrights defined in the Internet Standards 1354 process must be followed, or as required to translate it into 1355 languages other than English. 1357 The limited permissions granted above are perpetual and will not 1358 be revoked by the Internet Society or its successors or assigns. 1360 This document and the information contained herein is provided on 1361 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1362 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1363 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1364 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1365 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.