idnits 2.17.1 draft-ietf-snmpconf-diffpolicy-02.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): ---------------------------------------------------------------------------- ** 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: ---------------------------------------------------------------------------- == 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 5 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** The abstract seems to contain references ([DIFFSERVMIB]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 2 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 48: '...erty clause, the MUST, MAY, SHOULD stu...' RFC 2119 keyword, line 318: '...mation in that MIB module which MAY be...' RFC 2119 keyword, line 407: '...cheme of actions MAY be used for the s...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 381 has weird spacing: '... appear that ...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 2000) is 8716 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'SNMPBCP' is defined on line 1379, but no explicit reference was found in the text == Unused Reference: 'COPS-PR' is defined on line 1382, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) -- Possible downref: Non-RFC (?) normative reference: ref. 'PBCM' -- Possible downref: Non-RFC (?) normative reference: ref. 'DIFFSERVMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'POLICYMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'SNMPBCP' -- Possible downref: Non-RFC (?) normative reference: ref. 'COPS-PR' -- Possible downref: Non-RFC (?) normative reference: ref. 'IPSEC' -- Possible downref: Non-RFC (?) normative reference: ref. 'BGP MIB' Summary: 18 errors (**), 0 flaws (~~), 6 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft DiffServ Policy MIB June 2000 4 The DiffServ Policy MIB 5 draft-ietf-snmpconf-diffpolicy-02.txt 6 Document Revision: 1.4 8 June 2000 10 Harrie Hazewinkel 11 TBD 12 harrie.hazewinkel@bigfoot.com 14 David Partain 15 Ericsson 16 David.Partain@ericsson.com 18 Status of this Memo 20 This document is an Internet-Draft and is in full conformance 21 with all provisions of Section 10 of RFC2026. 23 Internet-Drafts are working documents of the Internet 24 Engineering Task Force (IETF), its areas, and its working 25 groups. Note that other groups may also distribute working 26 documents as Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six 29 months and may be updated, replaced, or obsoleted by other 30 documents at any time. It is inappropriate to use Internet- 31 Drafts as reference material or to cite them other than as 32 "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt 37 The list of Internet-Draft Shadow Directories can be accessed 38 at http://www.ietf.org/shadow.html. 40 Copyright Notice 41 Copyright (C) The Internet Society (2000). All Rights Reserved. 43 "Open Issues" 45 * administrivia: various template things need to be put in 46 (the internet standard management framework, appropriate 47 references, security boilerplate, verify intellectual 48 property clause, the MUST, MAY, SHOULD stuff, etc.) There 49 are unresolved references. 51 * Matt White comments: "I think the "What does this MIB do?" 52 aspect needs to be expanded upon and clarified. Is it an 53 abstraction of the DiffServ MIB? Is it a DiffServ macro 54 storage facility? Is it a little of both? DLP: I've put in 55 a place-holder, but the text is not written. 57 * We need to include at least one example of usage. This will 58 be put in after Pittsburgh based upon the presentation that 59 we do there. After we're sure that our example reflects what 60 is needed, we'll put it into this MIB. 62 * to what degree do implementation-specific modules convey 63 information about state or utilization and how do we get 64 that information, and how is it shown in the policy system. 66 * for each domain, we may need to understand capacity and 67 utilization. If so, we need to have appropriate MIB 68 objects that allow you to get this. 70 1. Abstract 72 The MIB Module described in this document provides a 73 conceptual layer between high-level "network-wide" policy 74 definitions that affect configuration of the differentiated 75 services (DiffServ) subsystem and the instance-specific 76 information that would include such details as the parameters 77 for all the queues associated with each interface in a system. 78 This essentially provides an interface for configuring 79 DiffServ at a conceptually higher layer than that of the 80 DiffServ Architecture MIB [DIFFSERVMIB]. 82 This version of this memo is aligned with the DIFF-SERV-MIB 83 [DIFFSERVMIB] found in draft-ietf-diffserv-mib-03.txt. This 84 MIB module will be aligned with that work as updates are made. 86 2. The SNMP Management Framework 88 The SNMP Management Framework presently consists of five major 89 components: 91 o An overall architecture, described in RFC 2571 [1]. 93 o Mechanisms for describing and naming objects and events 94 for the purpose of management. The first version of this 95 Structure of Management Information (SMI) is called SMIv1 96 and described in RFC 1155 [2], RFC 1212 [3] and RFC 1215 97 [4]. The second version, called SMIv2, is described in 98 RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 100 o Message protocols for transferring management 101 information. The first version of the SNMP message 102 protocol is called SNMPv1 and described in RFC 1157 103 [8]. A second version of the SNMP message protocol, 104 which is not an Internet standards track protocol, is 105 called SNMPv2c and described in RFC 1901 [9] and RFC 106 1906 [10]. The third version of the message protocol is 107 called SNMPv3 and described in RFC 1906 [10], RFC 2572 108 [11] and RFC 2574 [12]. 110 o Protocol operations for accessing management 111 information. The first set of protocol operations and 112 associated PDU formats is described in RFC 1157 [8]. A 113 second set of protocol operations and associated PDU 114 formats is described in RFC 1905 [13]. 116 o A set of fundamental applications described in RFC 2573 [14] 117 and the view-based access control mechanism described 118 in RFC 2575 [15]. 120 A more detailed introduction to the current SNMP Management 121 Framework can be found in RFC 2570 [16]. 123 Managed objects are accessed via a virtual information store, 124 termed the Management Information Base or MIB. Objects in the 125 MIB are defined using the mechanisms defined in the SMI. 127 This memo specifies a MIB module that is compliant to the 128 SMIv2. A MIB conforming to the SMIv1 can be produced through 129 the appropriate translations. The resulting translated MIB 130 must be semantically equivalent, except where objects or 131 events are omitted because no translation is possible (use of 132 Counter64). Some machine-readable information in SMIv2 will be 133 converted into textual descriptions in SMIv1 during the 134 translation process. However, this loss of machine readable 135 information is not considered to change the semantics of the 136 MIB. 138 3. Introduction 140 This memo defines a MIB module which can be used to convey 141 information about desired network-wide DiffServ-based policy 142 behavior. This module is designed to integrate with the 143 Policy-based Management MIB module [POLICYMIB] as well as the 144 DiffServ Architecture MIB module [DIFFSERVMIB] published by 145 the DiffServ working group. Together these three documents 146 represent an instance of an integrated architecture for both 147 device-specific and network-wide policy management which is 148 fully integrated with the Internet Standard Management 149 Framework. 151 This is the first of what is expected to be a wide number of 152 other network-wide policy modules to be developed in the 153 future in a wide range of areas. 155 Within the DiffServ architecture a MIB module is already 156 defined [DIFFSERVMIB] that operates on a device level. The 157 MIB module in this memo (the DIFFSERV-POLICY-MIB) creates a 158 coherent policy configuration management view (domain- 159 specific) as an umbrella over this mechanism-specific MIB. 160 That is, DIFFSERV-POLICY-MIB provides a conceptual API for 161 configuration of DiffServ parameters in a device at a higher 162 level than the DiffServ Architecture MIB [DIFFSERVMIB]. 164 4. Definitions 166 Terminology used in discussing policy-based configuration 167 management have been the source of much discussion and 168 confusion. [PBCM] provides a discussion of the terms used in 169 discussing this topic. 171 Note that this is simply a template which needs to be altered 172 to fit into the documents better. 174 "Much of the information in this section is an adaptation and 175 expansion of a presentations given at the 47th IETF in during 176 the Policy Framework Working Group session. By adopting terms 177 used by the Policy Framework Working Group wherever feasible; 178 the SNMP Configuration Working Group hopes to reduce the 179 terminology confusion that has existed in this area. Work is 180 ongoing in the SNMP Configuration and Policy Framework groups 181 as well as others; so some change is inevitable. Here are 182 terms that are used to describe policy information at 183 different levels of abstraction moving from the most general 184 to the most specific. 186 1. Domain Specific. 188 A domain is a general area of technology such as service 189 quality or security. Services, or service level agreements, 190 may span several domains, each of them potentially 191 including many policies. As a general rule, people will 192 not discuss these domains in the abstract. They will most 193 often be discussed with technology or application-specific 194 examples. Examples of technical domains include IPSec 195 and Differentiated Services. When expressed in terms 196 specific to a particular domain, a policy is said to be 197 at the Domain Specific level of detail. 199 There is little in common between how one would configure 200 differentiated services with how one would configure IPsec 201 [IPSEC]. They may both be required for a particular service 202 agreement however. For example, people who want to use 203 a voice over IP application might also want to ensure a 204 certain level of security for these communications. 206 2. Mechanism Specific 208 Mechanisms are technologies used within a particular 209 domain. For example, in the differentiated services domain, 210 RED or WRED (Weighted Random Early Detection) might be 211 used as one of the mechanisms that devices employ to 212 support differentiated services and the applications 213 on which they rely. Policy descriptions that include 214 the details associated with a particular mechanism, 215 are said to be mechanism specific. 217 3. Implementation Specific 218 Implementation specific details are those parameters 219 that a particular vendor might use in an implementation 220 that augment a standard set of mechanism-specific 221 parameters. Vendors often add special capabilities to 222 basic mechanisms as a way of meeting special customer 223 requirements or differentiating themselves from their 224 competitors. These special capabilities are often a result 225 of the implementation approach that a vendor has used for 226 the product, thus the term, Implementation Specific. For 227 example, if a router vendor implemented a particular 228 routing protocol, they would have the mechanism specific 229 parameters that control the behavior of that software. The 230 vendor might have chosen to run several instances of 231 that routing protocol, perhaps on different processors, 232 for performance reasons. The parameters that are used 233 to control the distribution of work on the different 234 processors for that protocol would be implementation 235 specific. 237 4. Instance Specific 239 Network operators are most familiar and comfortable with 240 information of this type. Instance specific information 241 is information refers to parameter values that have 242 been associated with a specific instance in a managed 243 element. For example, The Border Gateway Protocol is a 244 routing protocol that has a number of parameters that 245 describe information about a particular router's view 246 of other routers that it is sharing information with, 247 peer routers. One such parameter defined in the BGP 248 MIB Module [BGP MIB] is the desired connection retry 249 interval for a peer, bgpPeerConnectRetryInterval. An 250 example value would be 120 (seconds). When expressed 251 with this level of specificity, one would say that this 252 is mechanism specific data. If we were to see a value of 253 bgpPeerConnectRetryInterval. 10.0.0.1 = 120 we would be 254 looking at the retry interval of the peer router found 255 at IP address 10.0.0.1. The value for this instance is 256 120 seconds, instance specific data. 258 One of the goals of policy-based (configuration) 259 management is to improve the efficiency of configuration 260 operations. This is accomplished in part by eliminating the 261 necessity of sending to the managed device a configuration 262 object for every instance of that object in a system. For 263 example, if we wanted to change one of the BGP parameters 264 referenced above on a large system for each interface 265 that is supporting the BGP, there may be many individual 266 commands needed to accomplish this task. If a command 267 line interface were used as the primary configuration 268 tool in this example, many configuration commands would 269 be needed as well. 271 When we say that a a policy is at the instance independent 272 level of abstraction, we mean that the value for a 273 particular parameter is independent of the instances to 274 which it will be applied." 276 5. What this MIB Module Provides 278 To be written: to provide a high-level description of what 279 this MIB does. 281 6. Relationship to other MIBs 283 In this section we describe the relationship of this MIB 284 module to other MIB modules. The overall architecture used 285 for policy configuration management is described in 286 [POLICYMIB]. 288 6.1. The Policy-based Management MIB module 290 [POLICYMIB] defines a MIB module that enables policy-based 291 configuration management of infrastructure using the Internet 292 Standard Management Framework. The document includes a table 293 for configuring policies to be implemented, tables for storing 294 the roles of elements on a particular device, a table for 295 representing the capabilities of a device with respect to 296 policy management, a table for referencing elements affected 297 by a policy, and a table which points to into the mechanism- 298 specific MIB (this memo). This last table of pointers enables 299 management applications to determine the mechanism-specific 300 configuration to which a particular policy applies. The 301 primary purpose of this is to enable the manager to correct 302 errors in installed policies. 304 The pmPolicyMechanismTable (as the table in [POLICYMIB] is 305 tentatively called), points into mechanism-specific MIBs and 306 includes a RowPointer object pointing into a row in the 307 diffPolicyPHBTable defined below. 309 See [POLICYMIB] for a full description of the policy-based 310 configuration framework it provides. 312 6.2. The DiffServ MIB module 314 The DiffServ Architecture MIB module [DIFFSERVMIB] provides a 315 common set of managed objects useful for configuring DiffServ 316 parameters on a particular device. This is what is refered to 317 as instance-level configuration. It is the alteration of the 318 instance-level information in that MIB module which MAY be 319 done via the objects provided by the DiffServ Policy MIB 320 module defined in this memo. 322 It is recognized that vendors may include additional managed 323 objects in their devices (via vendor-specific MIB modules) for 324 configuring DiffServ parameters. If a vendor chooses to use 325 the objects defined in this memo for configuration, the vendor 326 should also provide additional managed objects in a similar 327 approach as defined for the DiffServ Architecture MIB module 328 and the DiffServ Policy MIB module. 330 The remainder of this subsection describes the relationship of 331 each table in the DiffServ Architecture MIB module to this MIB 332 module. 334 - diffServClassifierTable: instantiates the traffic 335 classification data path. Whenever a configuration in the 336 DiffServ Policy MIB module is made active, a new entry in 337 the diffServClassifierTable will be created 338 with data path configuration as defined in the 339 diffPolicyPerHopBehaviorTable. 341 - diffServSixTupleClfrTable: traffic identification table 342 and does not have a direct influence on the per-hop-behavior. 343 Entries identifying traffic can be used directly by the 344 subsystem implementing the DiffServ Policy MIB module. 346 - diffServMeterTable is a possible target table for the 347 diffPolicyMeterTable. 349 - diffServTBMeterTable is also a target table for the 350 diffPolicyMeterTable. When per-hop-behavior configurations 351 are made active, the meter configuration used will be 352 instantiated in the diffServTBMeterTable 354 - diffServActionTable instantiates actions that can be 355 performed on a stream of traffic. This table is the target 356 for the diffPolicyActionTable whenever a configuration is 357 made active. 359 - diffServDscpMarkActTable is a configuration table for traffic 360 marking. It is possible to have mark actions defined in this 361 table that are not used for the traffic. For this reason 362 the manager can use this table directly in conjunction with 363 the DiffServ Policy MIB module. 365 - diffServAlgDropTable is a configuration table for dropping 366 traffic. It is possible to have mark actions defined in this 367 table that are not used for the traffic. For this reason 368 the manager can use this table directly in conjunction with 369 the DiffServ Policy MIB module. 371 The following tables are not used for configuration and are 372 not referenced in any way: 374 - diffServCountActTable 375 - diffServCountActXTable 376 - diffServDropActXTable 377 - diffServQMeasureTable 379 The Differentiated Services Policy MIB module was designed to 380 have configuration templates for the Differentiated Services 381 MIB module. Therefore, it may appear that the Differentiated 382 Services Policy MIB is largely a copy of the DIFF-SERV-MIB. 383 However, there is a significant difference in the semantics of 384 the managed objects. 386 In the DIFF-SERV-MIB [DIFFSERVMIB], meters, actions, queues 387 and schedulers are directly related to interfaces and their 388 interface direction. The objects directly influence traffic 389 behavior. This is in contrast to the objects in the 390 Differentiated Services Policy MIB module, where only 391 configuration templates are defined. The values of a template 392 are only to be applied when a per-hop-behavior is activated 393 via a policy. Only in that case are the values connected to an 394 interface and its direction, which could be seen as being 396 7. MIB Module Design 398 In this section the overall design of the DiffServ Policy MIB 399 module is described. The first part will describe how this 400 module is positioned within the overall architecture. 402 The DiffServ Policy MIB module of the SNMP-based configuration 403 management framework is positioned between the Policy-based 404 Management MIB module and the instance-specific MIB module 405 (the DiffServ Architecture MIB module) as described above. 407 The following scheme of actions MAY be used for the subsystem: 409 1) The instance-specific MIB module (for this document the 410 DiffServ Architecture MIB module) is assumed to be 411 implemented on the device already. 413 2) The Policy-based Management MIB module includes the filters 414 and actions and is implemented on the device. 416 3) The mechanism-specific policy MIB module (in this case 417 the DiffServ Policy MIB module) registers its capability 418 in the capability table of the Policy-based Management MIB 419 module. 421 4) If a device has knowledge of default configurations, it can 422 create the required managed objects for the default 423 configurations in the tables of the mechanism-specific 424 policy MIB module. 426 5) The manager can then read the capability table after which 427 it knows about the capabilities and can start configuring 428 the mechanism-specific policy MIB module and the various 429 roles that may exist (this defines the configurations and 430 associations as necessary) 432 6) The manager can then map/instantiate policies as required 433 via the policy table. 435 The MIB module is designed with the following tables: 437 - A per-hop-behavior table (diffPolicyPHBTable) 438 - A meter table (diffPolicyMeterTable) 439 - An action table (diffPolicyActionTable) 440 - A queue table (diffPolicyQTable) 441 - A scheduler table (diffPolicySchedulerTable) 443 Unlike most MIB modules, changes on the managed objects in 444 this MIB module do not cause a change in the device. This MIB 445 module is used to set up per-hop-behavior configurations. As 446 soon as configurations are made active via the POLICY- 447 MANAGEMENT-MIB, the configurations defined within this MIB 448 module will be instantiated on the instance specific MIB, the 449 DIFF-SERV-MIB. 451 Note that this is a conceptual process. That is, the 452 configuration may not actually go through an API available in 453 the subsystem which implements the DIFF-SERV-MIB module. 454 However, configuration via the DiffServ Policy MIB module will 455 alter the same instrumentation as the DIFF-SERV-MIB module 456 whether it does it via the DIFF-SERV-MIB module or not. 458 The tables in the MIB module are: 460 - The diffPolicyPHBTable provides managed objects for 461 per-hop-behavior configuration. This table contains 462 RowPointers into subsequent tables in such a way that the 463 Traffic Control Block (TCB) can be created as soon as a 464 configuration is made active. 466 - The diffPolicyMeterTable provides the managed objects for the 467 meters used in the per-hop-behavior configuration. 468 This table also contains RowPointers into next data-path 469 elements if the traffic conforms to the meter or not. 471 - The diffPolicyActionTable provides managed objects for 472 configuring actions that are connected with meters. 473 Via this table, and using 'diffPolicyMeterFailNext' and/or 474 'diffPolicyMeterSucceedNext', the specific action can 475 be configured. 477 - The diffPolicyQTable provides managed objects for setting up 478 individual queue configurations. The individual queues can 479 be configured with the sample interval and the weight of 480 the queue. 482 - The diffPolicySchedulerTable enumerates policy configuration 483 templates for packet schedulers. 485 8. Managed objects definitions (MIB module) 487 -- This version of the MIB is aligned with the DIFF-SERV-MIB 488 -- found in draft-ietf-diffserv-mib-03.txt. This MIB module will 489 -- be aligned with that work as updates are made. 491 DIFFSERV-POLICY-MIB DEFINITIONS ::= BEGIN 493 IMPORTS 495 Unsigned32, Integer32, OBJECT-TYPE, MODULE-IDENTITY, zeroDotZero, mib-2 496 FROM SNMPv2-SMI 498 RowStatus, RowPointer, TestAndIncr, DateAndTime 499 FROM SNMPv2-TC 501 MODULE-COMPLIANCE, OBJECT-GROUP 502 FROM SNMPv2-CONF 504 SnmpAdminString 505 FROM SNMP-FRAMEWORK-MIB; 507 diffPolicyMib MODULE-IDENTITY 508 LAST-UPDATED "200006301100Z" -- June 30, 2000, 13:00 Italy 509 ORGANIZATION "SNMPCONF WG" 510 CONTACT-INFO 511 "SNMPCONF Working Group 512 http://www.ietf.org/html.charters/snmpconf-charter.html 513 Editors: 515 Harrie Hazewinkel 516 Postal: Titanstraat 2 517 9933 CE Delfzijl 518 The Netherlands 519 Tel: +31 596 615843 or +39 331974135 520 FAX: +39 0331974135 521 E-mail: harrie.hazewinkel@bigfoot.com 523 David Partain 524 Postal: Ericsson Radio Systems 525 P.O. Box 1248 526 SE-581 12 Linkoping 527 Sweden 528 Tel: +46 13 28 41 44 529 E-mail: David.Partain@ericsson.com" 530 DESCRIPTION 531 "This MIB module contains differentiated services 532 specific managed objects to perform policy-based 533 configuration management. This MIB defines 534 'templates' to be used to instantiate 535 per-hop-behaviors to be assigned when a policy is 536 created and activated." 537 ::= { mib-2 22222222 } -- Needs to be assigned by IANA 539 diffPolicyMIBObjects OBJECT IDENTIFIER ::= { diffPolicyMib 1 } 540 diffPolicyMIBConformance OBJECT IDENTIFIER ::= { diffPolicyMib 3 } 542 -- 543 -- The per-hop-behavior 544 -- 546 -- Issues: 547 -- Do we want a spin-lock on this whole table or on each row 548 -- of the table, or not at all? 550 diffPolicyPHBUnique OBJECT-TYPE 551 SYNTAX TestAndIncr 552 MAX-ACCESS read-write 553 STATUS current 554 DESCRIPTION 555 "The diffPolicyPHBUnique object yields a unique new 556 value for diffPolicyPHBId when read and subsequently 557 set. This value must be tested for uniqueness." 558 ::= { diffPolicyMIBObjects 1 } 560 diffPolicyPHBTable OBJECT-TYPE 561 SYNTAX SEQUENCE OF DiffPolicyPHBEntry 562 MAX-ACCESS not-accessible 563 STATUS current 564 DESCRIPTION 565 "A table which defines the various per-hop-behaviors 566 for which the system has default 'templates'." 567 ::= { diffPolicyMIBObjects 2 } 569 diffPolicyPHBEntry OBJECT-TYPE 570 SYNTAX DiffPolicyPHBEntry 571 MAX-ACCESS not-accessible 572 STATUS current 573 DESCRIPTION 574 "An entry defining a per-hop-behavior. 575 Each entry in this table combines the various 576 parameters (entries) into a specific per-hop-behavior. 577 Entries in this table can as well being defined by 578 a vendor (preconfigured) or as well being defined 579 by a management application." 580 INDEX { diffPolicyPHBId } 581 ::= { diffPolicyPHBTable 1 } 583 DiffPolicyPHBEntry ::= SEQUENCE { 584 diffPolicyPHBId Integer32, 585 diffPolicyPHBDescr SnmpAdminString, 586 diffPolicyPHBOwner SnmpAdminString, 587 diffPolicyPHBLastChange DateAndTime, 588 diffPolicyPHBTrafficID RowPointer, 589 diffPolicyPHBClassPrecedence Unsigned32, 590 diffPolicyPHBMeter RowPointer, 591 diffPolicyPHBAction RowPointer, 592 diffPolicyPHBQueue RowPointer, 593 diffPolicyPHBScheduler RowPointer, 594 diffPolicyPHBStatus RowStatus 595 } 597 diffPolicyPHBId OBJECT-TYPE 598 SYNTAX Integer32 (1..2147483647) 599 MAX-ACCESS not-accessible 600 STATUS current 601 DESCRIPTION 602 "A unique id for the per-hop-behavior policy." 603 ::= { diffPolicyPHBEntry 1 } 605 diffPolicyPHBDescr OBJECT-TYPE 606 SYNTAX SnmpAdminString 607 MAX-ACCESS read-create 608 STATUS current 609 DESCRIPTION 610 "A human-readable description to identify this 611 defined per-hop-behavior. 612 Note that this is an SnmpAdminString, which 613 permits UTF-8 strings." 614 ::= { diffPolicyPHBEntry 2 } 616 diffPolicyPHBOwner OBJECT-TYPE 617 SYNTAX SnmpAdminString 618 MAX-ACCESS read-create 619 STATUS current 620 DESCRIPTION 621 "The owner who creates this entry." 622 ::= { diffPolicyPHBEntry 3 } 624 diffPolicyPHBLastChange OBJECT-TYPE 625 SYNTAX DateAndTime 626 MAX-ACCESS read-only 627 STATUS current 628 DESCRIPTION 629 "The date and time when this entry was changed for 630 the last time." 631 ::= { diffPolicyPHBEntry 4 } 633 diffPolicyPHBTrafficID OBJECT-TYPE 634 SYNTAX RowPointer 635 MAX-ACCESS read-create 636 STATUS current 637 DESCRIPTION 638 "The pointer to traffic identification used for this 639 per-hop-behavior definition. 640 This value points to a traffic classifying entry in 641 the 'diffServClassifierTable' or 642 the 'diffServSixTupleClfrTable'. 644 NOTE: The traffic classifying tables of the DIFF-SERV-MIB 645 can be used for policy configuration in this MIB module 646 because the entries in the tables 'diffServClassifierTable' or 647 the 'diffServSixTupleClfrTable' configure traffic filter 648 templates." 649 ::= { diffPolicyPHBEntry 5 } 651 diffPolicyPHBClassPrecedence OBJECT-TYPE 652 SYNTAX Unsigned32 653 MAX-ACCESS read-write 654 STATUS current 655 DESCRIPTION 656 "The precedence of the classifier for this 657 per-hop-behavior definition." 658 ::= { diffPolicyPHBEntry 6 } 660 diffPolicyPHBMeter OBJECT-TYPE 661 SYNTAX RowPointer 662 MAX-ACCESS read-create 663 STATUS current 664 DESCRIPTION 665 "The meter which is next in the data path for the 666 defined classifier applicable to this per-hop-behavior 667 configuration. 669 The value points to an entry in the 'diffPolicyMeterTable'." 670 DEFVAL { zeroDotZero } 671 ::= { diffPolicyPHBEntry 7 } 673 diffPolicyPHBAction OBJECT-TYPE 674 SYNTAX RowPointer 675 MAX-ACCESS read-create 676 STATUS current 677 DESCRIPTION 678 "The action which is next in the data path for the 679 defined classifier applicable to this per-hop-behavior 680 definition. 682 The value points to an entry in the 'diffPolicyActionTable'. 684 The value 'zeroDotZero' is used when there is no 685 action associated with the per-hop-behavior." 686 DEFVAL { zeroDotZero } 687 ::= { diffPolicyPHBEntry 8 } 689 diffPolicyPHBQueue OBJECT-TYPE 690 SYNTAX RowPointer 691 MAX-ACCESS read-create 692 STATUS current 693 DESCRIPTION 694 "The queue defined that is used for the 695 configuration of this per-hop-behavior. 697 The value points to an entry in the 'diffPolicyQTable'. 699 The value 'zeroDotZero' is used when there is no 700 queue associated with the per-hop-behavior." 701 DEFVAL { zeroDotZero } 702 ::= { diffPolicyPHBEntry 9 } 704 diffPolicyPHBScheduler OBJECT-TYPE 705 SYNTAX RowPointer 706 MAX-ACCESS read-create 707 STATUS current 708 DESCRIPTION 709 "The Scheduler defined that is used for the 710 configuration of this per-hop-behavior. 712 The value points to an entry in the 'diffPolicySchedulerTable'. 714 The value 'zeroDotZero' is used when there is no 715 scheduler associated with the per-hop-behavior" 716 DEFVAL { zeroDotZero } 717 ::= { diffPolicyPHBEntry 10 } 719 diffPolicyPHBStatus OBJECT-TYPE 720 SYNTAX RowStatus 721 MAX-ACCESS read-create 722 STATUS current 723 DESCRIPTION 724 "RowStatus object used for creation and deletion of 725 rows in this table." 726 ::= { diffPolicyPHBEntry 11 } 728 -- 729 -- Meters Configuration 730 -- 732 diffPolicyMeterUnique OBJECT-TYPE 733 SYNTAX TestAndIncr 734 MAX-ACCESS read-write 735 STATUS current 736 DESCRIPTION 737 "The diffPolicyMeterUnique object yields a unique new 738 value for diffPolicyMeterId when read and subsequently 739 set. This value must be tested for uniqueness." 740 ::= { diffPolicyMIBObjects 3 } 742 diffPolicyMeterTable OBJECT-TYPE 743 SYNTAX SEQUENCE OF DiffPolicyMeterEntry 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "This table enumerates templates for configuration of 748 specific token bucket meters that can be used for 749 per-hop-behavior definitions. 751 This tables provides policy configuration templates 752 for the 'diffServMeterTable' and the 'diffServTBMeterTable'. 754 When changes are made in this table the behavior of the 755 DiffServ router is not changed. The behavior only changes 756 when the policy of which this meter is part is applied." 757 ::= { diffPolicyMIBObjects 4 } 759 diffPolicyMeterEntry OBJECT-TYPE 760 SYNTAX DiffPolicyMeterEntry 761 MAX-ACCESS not-accessible 762 STATUS current 763 DESCRIPTION 764 "An entry in the meter table." 765 INDEX { diffPolicyMeterId } 766 ::= { diffPolicyMeterTable 1 } 768 DiffPolicyMeterEntry ::= SEQUENCE { 769 diffPolicyMeterId Integer32, 770 diffPolicyMeterRate Unsigned32, 771 diffPolicyMeterBurstSize Unsigned32, 772 diffPolicyMeterFailNext RowPointer, 773 diffPolicyMeterSucceedNext RowPointer, 774 diffPolicyMeterStatus RowStatus 775 } 777 diffPolicyMeterId OBJECT-TYPE 778 SYNTAX Integer32 (1..2147483647) 779 MAX-ACCESS not-accessible 780 STATUS current 781 DESCRIPTION 782 "An index to make MeterId for each entry." 783 ::= { diffPolicyMeterEntry 1 } 785 diffPolicyMeterRate OBJECT-TYPE 786 SYNTAX Unsigned32 787 UNITS "KBPS" -- kilobits 788 MAX-ACCESS read-create 789 STATUS current 790 DESCRIPTION 791 "The token bucket rate, in kilo-bits per second (KBPS) 792 applicable for this Meter definition." 793 ::= { diffPolicyMeterEntry 2 } 795 diffPolicyMeterBurstSize OBJECT-TYPE 796 SYNTAX Unsigned32 797 UNITS "bytes" 798 MAX-ACCESS read-create 799 STATUS current 800 DESCRIPTION 801 "The configuration value of the number of bytes 802 in a single transmission burst when this policy 803 configuration is applied to a Meter." 804 ::= { diffPolicyMeterEntry 3 } 806 diffPolicyMeterFailNext OBJECT-TYPE 807 SYNTAX RowPointer 808 MAX-ACCESS read-create 809 STATUS current 810 DESCRIPTION 811 "The next Meter or Action configured that will handle the traffic 812 when the meter does not conform the meter. 814 This value points can point towards an entry in the 815 diffPolicyMeterTable, diffPolicyActionTable. 817 The value 'zeroDotZero' is used when there is no 818 next component in the data path." 819 DEFVAL { zeroDotZero } 820 ::= { diffPolicyMeterEntry 4 } 822 diffPolicyMeterSucceedNext OBJECT-TYPE 823 SYNTAX RowPointer 824 MAX-ACCESS read-create 825 STATUS current 826 DESCRIPTION 827 "The next Meter or Action configured that will handle the traffic 828 when the meter does conform the meter. 829 This value points can point towards an entry in the 830 diffPolicyMeterTable, diffPolicyActionTable. 832 The value 'zeroDotZero' is used when there is no 833 next component in the data path." 834 DEFVAL { zeroDotZero } 835 ::= { diffPolicyMeterEntry 5 } 837 diffPolicyMeterStatus OBJECT-TYPE 838 SYNTAX RowStatus 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "The RowStatus variable controls the creation 843 or deletion of a meter configuration." 844 ::= { diffPolicyMeterEntry 6 } 846 -- 847 -- Actions 848 -- 850 diffPolicyActionUnique OBJECT-TYPE 851 SYNTAX TestAndIncr 852 MAX-ACCESS read-write 853 STATUS current 854 DESCRIPTION 855 "The diffPolicyActionUnique object yields a unique new 856 value for diffPolicyActionId when read and subsequently 857 set. This value must be tested for uniqueness." 858 ::= { diffPolicyMIBObjects 5 } 860 diffPolicyActionTable OBJECT-TYPE 861 SYNTAX SEQUENCE OF DiffPolicyActionEntry 862 MAX-ACCESS not-accessible 863 STATUS current 864 DESCRIPTION 865 "This Table enumerates templates for actions that can be 866 performed on a stream of traffic. Various templates 867 can be concatenated. 869 This table can be used for configuration of the 870 'diffServActionTable' and 'diffServDscpMarkActTable'. 871 For policy configuration for these 2 tables they 872 are combined in 1 table." 873 ::= { diffPolicyMIBObjects 6 } 875 diffPolicyActionEntry OBJECT-TYPE 876 SYNTAX DiffPolicyActionEntry 877 MAX-ACCESS not-accessible 878 STATUS current 879 DESCRIPTION 880 "An entry in the action table describes the actions 881 applied to traffic exiting a given meter." 882 INDEX { diffPolicyActionId } 883 ::= { diffPolicyActionTable 1 } 885 DiffPolicyActionEntry ::= SEQUENCE { 886 diffPolicyActionId Unsigned32, 887 diffPolicyActionNext RowPointer, 888 diffPolicyActionType INTEGER, 889 diffPolicyActionStatus RowStatus 890 } 892 diffPolicyActionId OBJECT-TYPE 893 SYNTAX Unsigned32 (1..2147483647) 894 MAX-ACCESS not-accessible 895 STATUS current 896 DESCRIPTION 897 "Action Id enumerates the Action entry for 898 a per-hop-behavior definition." 899 ::= { diffPolicyActionEntry 1 } 901 diffPolicyActionNext OBJECT-TYPE 902 SYNTAX RowPointer 903 MAX-ACCESS read-create 904 STATUS current 905 DESCRIPTION 906 "The Next pointer indicates the next data path element 907 to handle the traffic that is applicable to this 908 per-hop-behavior definition. 910 The value 'zeroDotZero' is used when there is no 911 next component in the data path." 912 DEFVAL { zeroDotZero } 913 ::= { diffPolicyActionEntry 2 } 915 diffPolicyActionType OBJECT-TYPE 916 SYNTAX INTEGER { 917 other(1), -- types not specified here. 918 mark(2), -- mark or remark 919 count(3), -- count 920 alwaysDrop(4), -- disallow traffic 921 tailDrop(5), -- fix queue size Drop 922 randomDrop(6), -- Random Drop 923 deterDrop(7) -- Deterministic Drop 924 } 925 MAX-ACCESS read-write 926 STATUS current 927 DESCRIPTION 928 "Indicates the type of action for this configuration." 929 ::= { diffPolicyActionEntry 3 } 931 diffPolicyActionStatus OBJECT-TYPE 932 SYNTAX RowStatus 933 MAX-ACCESS read-create 934 STATUS current 935 DESCRIPTION 936 "The RowStatus variable controls the creation, 937 or deletion of a action configuration." 938 ::= { diffPolicyActionEntry 4 } 940 -- 941 -- Queues 942 -- 944 diffPolicyQUnique OBJECT-TYPE 945 SYNTAX TestAndIncr 946 MAX-ACCESS read-write 947 STATUS current 948 DESCRIPTION 949 "The diffPolicyQUnique object yields a unique new value 950 for diffPolicyQId when read and subsequently set. This 951 value must be tested for uniqueness." 952 ::= { diffPolicyMIBObjects 7 } 954 diffPolicyQTable OBJECT-TYPE 955 SYNTAX SEQUENCE OF DiffPolicyQEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "The Queue Table enumerates the queues that 960 can be assigned when a per-hop-behavior is assigned. 961 This table includes the measure values which 962 are defined in the DIFF-SERV-MIB in a separate table." 963 ::= { diffPolicyMIBObjects 8 } 965 diffPolicyQEntry OBJECT-TYPE 966 SYNTAX DiffPolicyQEntry 967 MAX-ACCESS not-accessible 968 STATUS current 969 DESCRIPTION 970 "An entry in the Queue Table describes a single FIFO 971 queue." 972 INDEX { diffPolicyQId, diffPolicyQId } 973 ::= { diffPolicyQTable 1 } 975 DiffPolicyQEntry ::= SEQUENCE { 976 diffPolicyQId Integer32, 977 diffPolicyQPriority Unsigned32, 978 diffPolicyQMinRateAbs Unsigned32, 979 diffPolicyQMinRateRel Unsigned32, 980 diffPolicyQMaxRateAbs Unsigned32, 981 diffPolicyQMaxRateRel Unsigned32, 982 diffPolicyQStatus RowStatus 983 } 985 diffPolicyQId OBJECT-TYPE 986 SYNTAX Integer32 (1..2147483647) 987 MAX-ACCESS not-accessible 988 STATUS current 989 DESCRIPTION 990 "The Queue Id enumerates the Queue entry." 991 ::= { diffPolicyQEntry 1 } 993 diffPolicyQPriority OBJECT-TYPE 994 SYNTAX Unsigned32 995 MAX-ACCESS read-create 996 STATUS current 997 DESCRIPTION 998 "The priority of the queue." 999 ::= { diffPolicyQEntry 2 } 1001 diffPolicyQMinRateAbs OBJECT-TYPE 1002 SYNTAX Unsigned32 1003 UNITS "kilobits per second" 1004 MAX-ACCESS read-create 1005 STATUS current 1006 DESCRIPTION 1007 "The minimum absolute rate, in kilobits/sec, with which 1008 a downstream scheduler element should configured." 1009 REFERENCE 1010 "diffServQMinRateAbs from [DIFFSERVMIB]" 1011 ::= { diffPolicyQEntry 3 } 1013 diffPolicyQMinRateRel OBJECT-TYPE 1014 SYNTAX Unsigned32 1015 MAX-ACCESS read-create 1016 STATUS current 1017 DESCRIPTION 1018 "The minimum rate with which a downstream scheduler element 1019 should be configured." 1020 REFERENCE 1021 "diffServQMinRateRel from [DIFFSERVMIB]" 1022 ::= { diffPolicyQEntry 4 } 1024 diffPolicyQMaxRateAbs OBJECT-TYPE 1025 SYNTAX Unsigned32 1026 UNITS "kilobits per second" 1027 MAX-ACCESS read-create 1028 STATUS current 1029 DESCRIPTION 1030 "The maximum absolute rate, in kilobits/sec, with which 1031 a downstream scheduler element should configured." 1032 REFERENCE 1033 "diffServQMaxRateAbs from [DIFFSERVMIB]" 1034 ::= { diffPolicyQEntry 5 } 1036 diffPolicyQMaxRateRel OBJECT-TYPE 1037 SYNTAX Unsigned32 1038 MAX-ACCESS read-create 1039 STATUS current 1040 DESCRIPTION 1041 "The maximum rate with which a downstream scheduler element 1042 should be configured." 1043 REFERENCE 1044 "diffServQMaxRateRel from [DIFFSERVMIB]" 1045 ::= { diffPolicyQEntry 6 } 1047 diffPolicyQStatus OBJECT-TYPE 1048 SYNTAX RowStatus 1049 MAX-ACCESS read-create 1050 STATUS current 1051 DESCRIPTION 1052 "The RowStatus variable controls the creation, 1053 or deletion of a queue configuration." 1054 ::= { diffPolicyQEntry 7 } 1056 -- 1057 -- Scheduler 1058 -- 1060 diffPolicySchedulerUnique OBJECT-TYPE 1061 SYNTAX TestAndIncr 1062 MAX-ACCESS read-write 1063 STATUS current 1064 DESCRIPTION 1065 "The diffPolicySchedulerUnique object yields a unique new value for 1066 diffPolicySchedulerId when read and subsequently set. This value 1067 must be tested for uniqueness and can be used by a configuring 1068 system to obtain a unique value for diffPolicySchedulerId for 1069 purposes of row creation in the diffPolicySchedulerTable." 1070 ::= { diffPolicyMIBObjects 9 } 1072 diffPolicySchedulerTable OBJECT-TYPE 1073 SYNTAX SEQUENCE OF DiffPolicySchedulerEntry 1074 MAX-ACCESS not-accessible 1075 STATUS current 1076 DESCRIPTION 1077 "The Scheduler Table enumerates policy configuration 1078 templates for packet schedulers." 1079 ::= { diffPolicyMIBObjects 10 } 1081 diffPolicySchedulerEntry OBJECT-TYPE 1082 SYNTAX DiffPolicySchedulerEntry 1083 MAX-ACCESS not-accessible 1084 STATUS current 1085 DESCRIPTION 1086 "An entry in the Policy Scheduler Table describing a 1087 single configuration template for a scheduling algorithm." 1088 INDEX { diffPolicySchedulerId } 1089 ::= { diffPolicySchedulerTable 1 } 1091 DiffPolicySchedulerEntry ::= SEQUENCE { 1092 diffPolicySchedulerId Integer32, 1093 diffPolicySchedulerMethod INTEGER, 1094 diffPolicySchedulerNext RowPointer, 1095 diffPolicySchedulerStatus RowStatus 1096 } 1098 diffPolicySchedulerId OBJECT-TYPE 1099 SYNTAX Integer32 (0..2147483647) 1100 MAX-ACCESS not-accessible 1101 STATUS current 1102 DESCRIPTION 1103 "The Policy Scheduler Id enumerates the Policy Scheduler entry." 1104 ::= { diffPolicySchedulerEntry 1 } 1106 diffPolicySchedulerMethod OBJECT-TYPE 1107 SYNTAX INTEGER { 1108 other(1), -- not listed here 1109 priorityq(2), -- Priority Queueing 1110 wrr(3) -- Weighed Round Robin 1111 } 1112 MAX-ACCESS read-create 1113 STATUS current 1114 DESCRIPTION 1115 "The scheduling algorithm used when this policy is applied 1116 to a Scheduler." 1117 REFERENCE 1118 "diffServSchedulerMethod [DIFFSERV-MIB]" 1119 ::= { diffPolicySchedulerEntry 2 } 1121 diffPolicySchedulerNext OBJECT-TYPE 1122 SYNTAX RowPointer 1123 MAX-ACCESS read-create 1124 STATUS current 1125 DESCRIPTION 1126 "The next data path component that is applicable for 1127 this scheduler configuration. 1129 The value can point to an entry in the 'diffPolicyMeterTable', 1130 'diffPolicyActionTable', 'diffPolicyQTable' or the 1131 'diffPolicySchedulerTable'. 1133 The value 'zeroDotZero' is used when there is no 1134 next component in the data path." 1135 DEFVAL { zeroDotZero } 1136 ::= { diffPolicySchedulerEntry 3 } 1138 diffPolicySchedulerStatus OBJECT-TYPE 1139 SYNTAX RowStatus 1140 MAX-ACCESS read-create 1141 STATUS current 1142 DESCRIPTION 1143 "The RowStatus variable via which this configuration 1144 template can be created, deleted or modified." 1145 ::= { diffPolicySchedulerEntry 4 } 1147 -- 1148 -- MIB Compliance statements. 1149 -- 1151 diffPolicyMIBCompliances OBJECT IDENTIFIER ::= { diffPolicyMIBConformance 1 } 1152 diffPolicyMIBGroups OBJECT IDENTIFIER ::= { diffPolicyMIBConformance 2 } 1154 diffPolicyMIBFullCompliance MODULE-COMPLIANCE 1155 STATUS current 1156 DESCRIPTION 1157 "The full compliance for this MIB module." 1158 MODULE -- This module 1159 MANDATORY-GROUPS { diffPolicyMIBPerHopBehaviorGroup, 1160 diffPolicyMIBMeterGroup, 1161 diffPolicyMIBActionGroup, 1162 diffPolicyMIBQueueGroup, 1163 diffPolicyMIBSchedulerGroup } 1164 ::= { diffPolicyMIBCompliances 1 } 1166 diffPolicyMIBPerHopBehaviorGroup OBJECT-GROUP 1167 OBJECTS { diffPolicyPHBDescr, 1168 diffPolicyPHBOwner, 1169 diffPolicyPHBLastChange, 1170 diffPolicyPHBTrafficID, 1171 diffPolicyPHBClassPrecedence, 1172 diffPolicyPHBMeter, 1173 diffPolicyPHBAction, 1174 diffPolicyPHBQueue, 1175 diffPolicyPHBScheduler, 1176 diffPolicyPHBStatus 1177 } 1178 STATUS current 1179 DESCRIPTION 1180 "The per-hop-behavior Group defines the MIB Objects that 1181 describe the configuration template for the per-hop-behavior." 1182 ::= { diffPolicyMIBGroups 1 } 1184 diffPolicyMIBMeterGroup OBJECT-GROUP 1185 OBJECTS { diffPolicyMeterRate, 1186 diffPolicyMeterBurstSize, 1187 diffPolicyMeterFailNext, 1188 diffPolicyMeterSucceedNext, 1189 diffPolicyMeterStatus 1190 } 1191 STATUS current 1192 DESCRIPTION 1193 "The Meter Group defines the objects used for configuring a generic 1194 meter and token bucket elements." 1195 ::= { diffPolicyMIBGroups 2 } 1197 diffPolicyMIBActionGroup OBJECT-GROUP 1198 OBJECTS { diffPolicyActionNext, 1199 diffPolicyActionType, 1200 diffPolicyActionStatus 1201 } 1202 STATUS current 1203 DESCRIPTION 1204 "The Action Group defines the objects used for configuration of 1205 actions." 1206 ::= { diffPolicyMIBGroups 3 } 1208 diffPolicyMIBQueueGroup OBJECT-GROUP 1209 OBJECTS { diffPolicyQPriority, 1210 diffPolicyQMinRateAbs, 1211 diffPolicyQMinRateRel, 1212 diffPolicyQMaxRateAbs, 1213 diffPolicyQMaxRateRel, 1214 diffPolicyQStatus 1215 } 1216 STATUS current 1217 DESCRIPTION 1218 "The Queue Group contains the objects which can 1219 be used for configuration of Queues." 1220 ::= { diffPolicyMIBGroups 4 } 1222 diffPolicyMIBSchedulerGroup OBJECT-GROUP 1223 OBJECTS { diffPolicySchedulerMethod, 1224 diffPolicySchedulerNext, 1225 diffPolicySchedulerStatus 1226 } 1227 STATUS current 1228 DESCRIPTION 1229 "The Scheduler Group contains the objects that are used 1230 for configuration of packet schedulers on interfaces." 1231 ::= { diffPolicyMIBGroups 5 } 1233 END 1234 9. Security Considerations 1236 Security information here 1238 10. Editors' Addresses 1240 Harrie Hazewinkel 1241 Titanstraat 2 1242 9933 CE Delfzijl 1243 The Netherlands 1244 Phone: +31 596 615843 or +39 331974135 1245 EMail: harrie.hazewinkel@bigfoot.com 1247 David Partain 1248 Ericsson Radio Systems 1249 Research and Innovation 1250 P.O. Box 1248 1251 SE-581 12 Linkoping 1252 Sweden 1253 Phone: +46 13 28 41 44 1254 EMail: David.Partain@ericsson.com 1256 11. Full Copyright Statement 1258 Copyright (C) The Internet Society (2000). All Rights 1259 Reserved. 1261 This document and translations of it may be copied and 1262 furnished to others, and derivative works that comment on or 1263 otherwise explain it or assist in its implementation may be 1264 prepared, copied, published and distributed, in whole or in 1265 part, without restriction of any kind, provided that the above 1266 copyright notice and this paragraph are included on all such 1267 copies and derivative works. However, this document itself 1268 may not be modified in any way, such as by removing the 1269 copyright notice or references to the Internet Society or 1270 other Internet organizations, except as needed for the purpose 1271 of developing Internet standards in which case the procedures 1272 for copyrights defined in the Internet Standards process must 1273 be followed, or as required to translate it into languages 1274 other than English. 1276 The limited permissions granted above are perpetual and will 1277 not be revoked by the Internet Society or its successors or 1278 assigns. 1280 This document and the information contained herein is provided 1281 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1282 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1283 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 1284 USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 1285 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1286 PARTICULAR PURPOSE." 1288 12. References 1290 Others to be added as time goes by! 1292 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1293 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1294 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1295 1999 1297 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1298 Management Information for TCP/IP-based Internets", RFC 1155, STD 1299 16, Performance Systems International, Hughes LAN Systems, May 1990 1301 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1302 STD 16, Performance Systems International, Hughes LAN Systems, 1303 March 1991 1305 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1306 RFC 1215, Performance Systems International, March 1991 1308 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1309 and S. Waldbusser, "Structure of Management Information Version 2 1310 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1311 Braunschweig, SNMP Research, First Virtual Holdings, International 1312 Network Services, April 1999 1314 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1315 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1316 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1317 Virtual Holdings, International Network Services, April 1999 1319 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1320 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1321 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1322 First Virtual Holdings, International Network Services, April 1999 1324 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1325 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1326 Systems International, Performance Systems International, MIT 1327 Laboratory for Computer Science, May 1990. 1329 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1330 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1331 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1332 International Network Services, January 1996. 1334 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1335 Mappings for Version 2 of the Simple Network Management Protocol 1336 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1337 Dover Beach Consulting, Inc., International Network Services, 1338 January 1996. 1340 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1341 Processing and Dispatching for the Simple Network Management 1342 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1343 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 1345 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1346 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1347 2574, IBM T. J. Watson Research, April 1999 1349 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1350 Operations for Version 2 of the Simple Network Management Protocol 1351 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1352 Dover Beach Consulting, Inc., International Network Services, 1353 January 1996. 1355 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1356 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1357 Systems, April 1999 1359 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1360 Control Model (VACM) for the Simple Network Management Protocol 1361 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1362 Cisco Systems, Inc., April 1999 1364 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 1365 Version 3 of the Internet-standard Network Management Framework", 1366 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, 1367 Inc., Ericsson, Cisco Systems, April 1999 1369 [PBCM] J. Saperia, "Policy-based Configuration Management", Work 1370 in Progress, June 2000. 1372 [DIFFSERVMIB] Baker, F., K. Chan, and A. Smith, Management 1373 Information Base for the Differentiated Services 1374 Architecture, Work in Progress, May 2000. 1376 [POLICYMIB] Waldbusser, S., J. Saperia, T. Hongal, Policy Based 1377 Management MIB, Work in Progress, May 2000. 1379 [SNMPBCP] MacFaden M., J. Saperia, CONFIGURING NETWORKS AND DEVICES 1380 WITH SNMP, Work in Progress, May 2000. 1382 [COPS-PR] Chan, K.H.., D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. 1383 Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, COPS Usage 1384 for Policy Provisioning, Work in Progress, March 2000. 1386 [IPSEC] To be added 1388 [BGP MIB] to be added if necessary. 1390 Table of Contents 1392 1 Abstract .............................................. 2 1393 2 The SNMP Management Framework ......................... 3 1394 3 Introduction .......................................... 4 1395 4 Definitions ........................................... 4 1396 5 What this MIB Module Provides ......................... 7 1397 6 Relationship to other MIBs ............................ 7 1398 6.1 The Policy-based Management MIB module .............. 7 1399 6.2 The DiffServ MIB module ............................. 8 1400 7 MIB Module Design ..................................... 10 1401 8 Managed objects definitions (MIB module) .............. 12 1402 9 Security Considerations ............................... 29 1403 10 Editors' Addresses ................................... 29 1404 11 Full Copyright Statement ............................. 29 1405 12 References ........................................... 30