idnits 2.17.1 draft-ietf-diffserv-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-03-28) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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 == The page length should not exceed 58 lines per page, but there was 52 longer pages, the longest (page 1) being 61 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 52 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 6 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** There are 1899 instances of lines with control characters in the document. ** 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 360: '... counters MUST be used. For interfa...' RFC 2119 keyword, line 362: '... packet counters MUST be used and 64-b...' RFC 2119 keyword, line 363: '... octet counters MUST be used. For int...' RFC 2119 keyword, line 365: '... 64-bit octet counters MUST be used....' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 932 has weird spacing: '...between meter...' == Line 1076 has weird spacing: '...between meter...' -- 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 8931 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 2145 looks like a reference -- Missing reference section? '2' on line 2150 looks like a reference -- Missing reference section? '3' on line 2155 looks like a reference -- Missing reference section? '4' on line 2159 looks like a reference -- Missing reference section? '5' on line 2163 looks like a reference -- Missing reference section? '6' on line 2170 looks like a reference -- Missing reference section? '7' on line 2176 looks like a reference -- Missing reference section? '8' on line 2182 looks like a reference -- Missing reference section? '9' on line 2188 looks like a reference -- Missing reference section? '10' on line 2197 looks like a reference -- Missing reference section? '11' on line 2203 looks like a reference -- Missing reference section? '12' on line 2209 looks like a reference -- Missing reference section? '13' on line 2214 looks like a reference -- Missing reference section? '14' on line 2220 looks like a reference -- Missing reference section? '15' on line 2224 looks like a reference -- Missing reference section? '16' on line 2230 looks like a reference -- Missing reference section? 'Model' on line 2254 looks like a reference -- Missing reference section? 'DSCP' on line 2236 looks like a reference -- Missing reference section? 'DSARCH' on line 245 looks like a reference -- Missing reference section? 'DSMODEL' on line 246 looks like a reference -- Missing reference section? 'IFMIB' on line 2258 looks like a reference -- Missing reference section? 'Architecture' on line 2243 looks like a reference -- Missing reference section? 'AF' on line 2248 looks like a reference -- Missing reference section? 'EF' on line 2251 looks like a reference Summary: 15 errors (**), 0 flaws (~~), 5 warnings (==), 26 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Draft Differentiated Services MIB October 1999 3 Fred Baker 4 Kwok Ho Chan 5 Nortel Networks 6 Andrew Smith 7 Extreme Networks 9 Management Information Base for the 10 Differentiated Services Architecture 12 draft-ietf-diffserv-mib-01.txt 14 Abstract 16 This memo describes a proposed MIB for the Differentiated 17 Services Architecture. 19 1. Status of this Memo 21 This document is an Internet-Draft and is in full conformance 22 with all provisions of Section 10 of RFC 2026. Internet-Drafts 23 are working documents of the Internet Engineering Task Force 24 (IETF), its areas, and its working groups. Note that other 25 groups may also distribute working documents as Internet- 26 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 This particular draft is being developed in the Differentiated 41 Services Working Group. Discussion of it therefore belongs on 42 that list. The charter for Differentiated Services may be 43 found at http://www.ietf.org/html.charters/diffserv- 44 charter.html 46 2. The SNMP Management Framework 48 The SNMP Management Framework presently consists of five major 49 components: 51 o An overall architecture, described in RFC 2571 [1]. 53 o Mechanisms for describing and naming objects and 54 events for the purpose of management. The first 55 version of this Structure of Management Information 57 Draft Differentiated Services MIB October 1999 59 (SMI) is called SMIv1 and described in RFC 1155 [2], 60 RFC 1212 [3] and RFC 1215 [4]. The second version, 61 called SMIv2, is described in RFC 2578 [5], RFC 2579 62 [6] and RFC 2580 [7]. 64 o Message protocols for transferring management 65 information. The first version of the SNMP message 66 protocol is called SNMPv1 and described in RFC 1157 67 [8]. A second version of the SNMP message protocol, 68 which is not an Internet standards track protocol, is 69 called SNMPv2c and described in RFC 1901 [9] and RFC 70 1906 [10]. The third version of the message protocol 71 is called SNMPv3 and described in RFC 1906 [10], RFC 72 2572 [11] and RFC 2574 [12]. 74 o Protocol operations for accessing management 75 information. The first set of protocol operations and 76 associated PDU formats is described in RFC 1157 [8]. A 77 second set of protocol operations and associated PDU 78 formats is described in RFC 1905 [13]. 80 o A set of fundamental applications described in RFC 81 2573 [14] and the view-based access control mechanism 82 described in RFC 2575 [15]. 84 A more detailed introduction to the current SNMP Management 85 Framework can be found in RFC 2570 [16]. 87 Managed objects are accessed via a virtual information store, 88 termed the Management Information Base or MIB. Objects in the 89 MIB are defined using the mechanisms defined in the SMI. 91 This memo specifies a MIB module that is compliant to the 92 SMIv2. A MIB conforming to the SMIv1 can be produced through 93 the appropriate translations. The resulting translated MIB 94 must be semantically equivalent, except where objects or 95 events are omitted because no translation is possible (use of 96 Counter64). Some machine-readable information in SMIv2 will be 97 converted into textual descriptions in SMIv1 during the 98 translation process. However, this loss of machine readable 99 information is not considered to change the semantics of the 100 MIB. 102 Draft Differentiated Services MIB October 1999 104 3. Structure of this MIB 106 This MIB is designed according to the Differentiated Services 107 implementation conceptual model documented in [Model]. 109 3.1. Overview 111 In principle, if one were to construct a network entirely out 112 of two-port routers (in appropriate places connected by LANs 113 or similar media), then it would be necessary for each router 114 to perform exactly four QoS control functions on traffic in 115 each direction: 117 - Classify each message according to some set of rules 119 - In edge devices, determine whether the data stream the 120 message is part of is within or outside its rate 122 - Perform some set of resulting actions, minimally 123 including applying a drop policy appropriate to the 124 classification and queue in question, and in edge devices 125 perhaps additionally marking the traffic with a 126 Differentiated Services Code Point (DSCP) as defined in 127 [DSCP]. 129 - Enqueue the traffic for output in the appropriate queue, 130 which may shape the traffic or simply forward it with 131 some minimum rate or maximum latency. 133 If we build the network out of N-port routers, we expect the 134 behavior of the network to be identical. We are forced, 135 therefore, to provide essentially the same set of functions on 136 the ingress port of a router as on the egress port of a 137 router. Some interfaces will be "edge" interfaces and some 138 will be "interior" to the Differentiated Services domain. The 139 one point of difference between an ingress and an egress 140 interface is that all traffic on an egress interface is 141 queued, while traffic on an ingress interface will typically 142 be queued only for shaping purposes. 144 Hence, in this MIB, we model them identically, making the 145 distinction between ingress and egress interfaces an index 146 variable. 148 The MIB therefore contains six elements: 149 - Behavior Aggregate Classification Table 150 - Multi-Field Classification Table 152 Draft Differentiated Services MIB October 1999 154 - Classifier Table 155 - Meter Table 156 - Action Table 157 - Queue Table 159 3.2. Classifier Table 161 The classifier table indicates how traffic is sorted out. It 162 identifies separable classes of traffic, by reference to an 163 appropriate classifier, which may be anything from an 164 individual micro-flow to aggregates identified by DSCP. It 165 then sends these classified streams to an appropriate meter or 166 action. In a multi-stage meter, sub-classes of traffic may be 167 sent to different stages. For example, in AF1, AF11 traffic 168 might be sent to the first meter, AF12 traffic might be sent 169 to the second, and AF13 traffic sent to the second meter 170 stage's failure action. 172 The structure of the classifier table is a sequence of 173 unambiguous tests. Within each step in the sequence, it should 174 not be important in order - if order is present at all - the 175 tests are made. This is to facilitate optimized 176 implementations such as index trees. Sequence is present in 177 order to resolve ambiguity. 179 For example, one might want first to disallow certain 180 applications from using the network at all, or to classify 181 some individual traffic streams that are not diff-serv marked. 182 Traffic that fails those tests might then be inspected for a 183 DSCP. "Then" implies sequence, and the sequence must be 184 somehow specified. 186 An important form of classifier is "everything else". The 187 final stage of the classifier should be configured to be 188 complete, as the result of an incomplete classifier is not 189 necessarily deterministic. 191 Two forms of classifiers are Behavior Aggregate (BA) and 192 Multi-Field (MF) Classifiers. These classifiers are specified 193 here at the per interface level, they can be derived from 194 some higher level policies. For example, QoS Policies 195 provisioned via QoS PIB (Policy Information Base), Routing 196 Policies with QoS information via BGP Policy setting 197 mechanism, and Routing Policies with QoS information from 198 traffic engineered routes. The source of classifier is 199 indicated by the diffServClassifierConfigType attribute of the 200 diffServClassifierEntry object. The attribute 202 Draft Differentiated Services MIB October 1999 204 diffServClassifierConfigTypeInfo can be used to further 205 associate the classifier with specific grouping based on the 206 ConfigType. For example, with PIB ConfigType, the 207 ConfigTypeInfo attribute can hold the RoleCombination from 208 which the classifier is derived. With BGP ConfigType, the 209 ConfigTypeInfo can hold the BGP Community String that 210 identifies the BGP Routing Policy from which the classifier is 211 derived. With the use of higher level policies, the 212 classifier table is used primarily for monitoring purpose, but 213 this does not exclude its use for configuration purpose. 215 3.2.1. Behavior Aggregate Classification Table 217 The Behavior Aggregate Classification Table is present for 218 several reasons. First, the DSCP must be identified somewhere 219 for identifying tagged streams of traffic. This could be done 220 in-line, and is not. 222 The reason the BA Classifier is pulled out into a separate 223 table is that we envisage the use of other tables for other 224 kinds of classifiers, public or proprietary. For example, the 225 typical "five-tuple" used in per-flow classification (as in 226 RSVP) might be represented by a table whose objects include 227 the necessary IP Addresses, the IP protocol, the necessary 228 TCP/UDP port numbers, and a RowStatus variable. By pulling the 229 classifier itself into a table that can be referenced via a 230 RowPointer, we enable the use of any sort of classification 231 table that one might wish to design. That classifier table 232 need not be found in this MIB. When ambiguity is present, we 233 disambiguate by explicitly ordering the application of 234 classification rules. 236 3.2.2. Multi-Field Classification Table 238 In the same spirit as the BA Classification Table, the Multi- 239 Field Classification Table is in a separate table that can be 240 referenced via a RowPointer, namely 241 diffServClassifierMatchObject attribute of 242 diffServClassifierEntry object. Each entry in the MF 243 Classification Table defines a MF Classifier. With the use of 244 InetEndpoint for both IPv4 and IPv6 addressing. The use of MF 245 Classifiers is discussed in [DSARCH] and abstract examples of 246 how they might be configured are provided in [DSMODEL]. 248 Draft Differentiated Services MIB October 1999 250 3.3. Meter Table 252 A meter, according to the conceptual model, measures the rate 253 at which a stream of traffic passes it, compares it to some 254 set of thresholds, and produces some number (two or more) 255 potential results. A given message is said to "conform" to the 256 meter if at the time that the message is being looked at the 257 stream appears to be within the meter's limit rate. In the 258 MIB, the structure of SNMP makes it easiest to implement this 259 as a set of one or more simple pass/fail tests, which are 260 cascaded. It is to be understood that the meter in a Traffic 261 Control Block is therefore implemented as a set of if-then- 262 else constructs. 264 The result of metering traffic is always some action. 266 The concept of conformance to a meter bears a comment. The 267 concept applied in several rate-control architectures, 268 including ATM, Frame Relay, Integrated Services, and 269 Differentiated Services, is variously described as a "leaky 270 bucket" or a "token bucket". 272 A leaky bucket algorithm is primarily used for traffic 273 shaping: traffic theoretically departs from the switch at a 274 flat rate of one bit every so many time units, and in fact 275 departs in packets at a rate approximating that. It is also 276 possible to build multi-rate leaky buckets, in which traffic 277 departs from the switch at varying rates depending on recent 278 activity or inactivity. 280 A token bucket is used to measure the behavior of a peer's 281 leaky bucket, for verification purposes. It is, by definition, 282 a relationship 284 interval = burst/rate, or 285 rate = burst/interval 287 for some defined burst size, in bits, rate, in bits per 288 second, and time interval. Multi-rate token buckets (token 289 buckets with both a peak and a mean rate, and sometimes more 290 rates) are commonly used. In this case, the burst size for the 291 baseline traffic is conventionally referred to as the 292 "committed burst", and the time interval is as specified by 294 interval = committed burst/mean rate 296 Draft Differentiated Services MIB October 1999 298 but additional burst sizes (each an increment over its 299 predecessor) are defined, which are conventionally referred to 300 as "excess" burst sizes. The peak rate therefore equals the 301 sum of the burst sizes per interval. 303 A data stream is said to "conform" to a simple token bucket if 304 the switch receives at most the burst size in a given time 305 interval. In the multi-rate case, the traffic is said to 306 conform to the token bucket at a given level if its rate does 307 not exceed the sum of the relevant burst sizes in a given 308 interval. Received traffic pre-classified at one of the 309 "excess" rates (e.g., AF12 or AF13 traffic) is only compared 310 to the relevant excess buckets. 312 The fact that data is organized into variable length packets 313 introduces some uncertainty in this. For this reason, the 314 token bucket accepts a packet if any of its bits would have 315 been accepted, and "borrows" any excess capacity required from 316 that allotted to equivalently classified traffic in a 317 subsequent interval. More information about this is available 318 in [Model]. 320 Multiple classes of traffic, as identified by the classifier 321 table, may be presented to the same meter. Imagine, for 322 example, that we desire to drop all traffic that uses any DSCP 323 that has not been publicly defined. A classifier entry might 324 exist for each such DSCP, shunting it to an "accepts 325 everything" meter, and dropping all traffic that conforms to 326 only that meter. 328 Clearly, it is necessary to identify what is to be done with 329 messages that conform to the meter, and with messages that do 330 not. It is also necessary for the meter to be arbitrarily 331 extensible, as some PHBs require the successive application of 332 an arbitrary number of meters. The approach taken in this 333 design is to have each meter indicate what action is to be 334 taken for conforming traffic, and what meter is to be used for 335 traffic which fails to conform. With the definition of a 336 special type of meter to which all traffic conforms, we now 337 have the necessary flexibility. 339 3.4. Action Table 341 Considerable discussion has taken place regarding the possible 342 actions. Suggested actions include "no action", "mark the 343 traffic", "drop the traffic, randomly or all of it", and 344 "shape the traffic." In this MIB, three actions are 346 Draft Differentiated Services MIB October 1999 348 contemplated: marking the traffic, counting the traffic that 349 passes that route, applying a drop policy. The author notes 350 that marking the traffic with the same DSCP as it already has 351 no effect, and all traffic must expect to come up against some 352 drop policy. 354 Two sizes of objects are defined for some counters. These are 355 defined in accordance with the method found in [IFMIB]; both 356 32 and 64 bit counters are defined, with the expectation that 357 the 32 bit counter is simply the least significant bits of the 358 64 bit counter. For interfaces that operate at 20,000,000 (20 359 million) bits per second or less, 32-bit byte and packet 360 counters MUST be used. For interfaces that operate faster 361 than 20,000,000 bits/second, and slower than 650,000,000 362 bits/second, 32-bit packet counters MUST be used and 64-bit 363 octet counters MUST be used. For interfaces that operate at 364 650,000,000 bits/second or faster, 64-bit packet counters AND 365 64-bit octet counters MUST be used. 367 Traffic conforming to a meter and not dropped is presented to 368 a queue for further processing. 370 3.5. Queue Table 372 In this version of the MIB, a relatively simple FIFO queue is 373 envisaged within the Traffic Control Block (TCB). Each queue 374 is capable of acting as a work-conserving queue (one which 375 transmits as rapidly as its weight allows, but guarantees to 376 its class of traffic, as a side effect of its weight, a 377 minimum rate), or as a non-work-conserving or "shaping" queue. 378 Queue structure can be built from these FIFO queues, including 379 chain of queues using the NextTCB attribute. The scheduling 380 discipline of a queue amongst the queue set of an inter- face 381 is specified. When all the queues in a queue set uses 382 priority queue discipline, the queue set will use strict 383 priority queue scheduling using each queue's priority 384 attribute. When all the queues in a queue set uses weighted 385 fair queue discipline, the queue set will use weighted fair 386 queue scheduling, with the weight specified by the minimum 387 rate attribute. A mixed scheduling discipline can be built 388 for a queue set. For example, with the following queue set: 389 Q Number Q Discipline Q MinRate Q Priority 390 -------- ------------ --------- ---------- 391 11 PQ 0 10 392 12 PQ 0 9 393 13 WFQ 800 KBPS 8 394 14 WFQ 600 KBPS 8 396 Draft Differentiated Services MIB October 1999 398 15 WFQ 300 KBPS 8 400 All traffic in queue 11 will be serviced first, then all 401 traffic in queue 12 will be serviced second. After traffic in 402 queues 11 and 12 are serviced, queues 13, 14, 15 are serviced 403 among themselves in a round robin fashion, with their 404 respective weights indicated by their minimum rate attribute. 406 The queue can also operate as a traffic shaper by using the 407 maximum rate attribute. 409 In addition some dropping algorithms rely on an averaged queue 410 depth to measure sustained, as opposed to instantaneous, 411 congestion. There are several methods for averaging the queue 412 depth. All of these methods share a mechanism specifying the 413 influence of the actual queue depth on the averaged queue 414 depth. Hence the attribute diffServQueueOccupancyWeight is 415 used. 417 Multiple meters may direct their traffic to the same queue. 418 For example, the Assured Forwarding PHB suggests that all 419 traffic marked AF11, AF12, or AF13 be placed in the same queue 420 without reordering. 422 Some discussion has elapsed concerning the structure of the 423 queue in question, and its functions. It is expected that the 424 description of the queuing system will grow during working 425 group discussion. This is an area where vendors differ 426 markedly in their architectures. 428 3.6. The use of RowPointer 430 RowPointer is a textual convention used to identify a 431 conceptual row in an SNMP Table by pointing to one of its 432 objects. In this MIB, it is used in two ways: to indicate 433 indirection, and to indicate succession. 435 When used for indirection, as in the Classifier table, the 436 idea is to allow other MIBs, including proprietary ones, to 437 identify new and arcane classifiers - MAC headers, IP4 and IP6 438 headers, BGP Communities, and all sorts of things. 440 When used for succession, it answers the question "what 441 happens next?". Rather than presume that the next table must 442 be as specified in the conceptual model and providing its 443 index, the RowPointer takes you to the MIB row representing 444 that thing. In the Meter Table, for example, the "FailNext" 446 Draft Differentiated Services MIB October 1999 448 RowPointer might take you to another meter, while the 449 "SucceedNext" RowPointer would take you to an action. 451 Draft Differentiated Services MIB October 1999 453 4. MIB Definition 455 DIFF-SERV-MIB DEFINITIONS ::= BEGIN 457 IMPORTS 458 Unsigned32, Counter32, Counter64, OBJECT-TYPE, 459 MODULE-IDENTITY, zeroDotZero, mib-2 FROM SNMPv2-SMI 460 TEXTUAL-CONVENTION, RowStatus, RowPointer, TestAndIncr 461 FROM SNMPv2-TC 462 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 463 ifIndex FROM IF-MIB; 464 InetEndpointType, InetEndpoint FROM INET-ENDPOINT-MIB; 466 diffServMib MODULE-IDENTITY 467 LAST-UPDATED "9907190100Z" -- Mon Jul 19 01:00:00 PDT 1999 468 ORGANIZATION "Cisco Systems" 469 CONTACT-INFO 470 " Fred Baker 471 Postal: 519 Lado Drive 472 Santa Barbara, California 93111 473 Tel: +1 (408)526-4257 474 FAX: +1 (805)681-0115 475 E-mail: fred@cisco.com" 476 " Kwok Ho Chan 477 Postal: 600 Technology Park Drive 478 Billerica, Massachusetts 01821, USA 479 Tel: +1 (978)288-8175 480 E-mail: khchan@nortelnetworks.com" 481 " Andrew Smith 482 Postal: 3585 Monroe St. 483 Santa Clara, California 95051 484 Tel: +1 (408) 579 2821 485 FAX: +1 (408) 579 3000 486 E-mail: andrew@extremenetworks.com" 487 DESCRIPTION 488 "This MIB defines the objects necessary to manage a 489 device that uses the Differentiated Services 490 Architecture described in RFC 2475." 491 REVISION "9907190100Z" -- Mon Jul 19 01:00:00 PDT 1999 492 DESCRIPTION 493 "Initial version, published as RFC xxxx." 494 ::= { mib-2 12345 } -- anybody who uses this 495 -- unassigned number 496 -- deserves the wrath of IANA 498 diffServObjects OBJECT IDENTIFIER ::= { diffServMib 1 } 499 diffServTables OBJECT IDENTIFIER ::= { diffServMib 2 } 501 Draft Differentiated Services MIB October 1999 503 diffServMIBConformance OBJECT IDENTIFIER ::= { diffServMib 3 } 505 Draft Differentiated Services MIB October 1999 507 -- The tools necessary to perform basic Behavior 508 -- Aggregate Classification 509 -- 510 Dscp ::= TEXTUAL-CONVENTION 511 DISPLAY-HINT "d" 512 STATUS current 513 DESCRIPTION 514 "The code point used for discriminating a traffic 515 stream." 516 SYNTAX INTEGER (0..63) 518 diffServAggregateTable OBJECT-TYPE 519 SYNTAX SEQUENCE OF DiffServAggregateEntry 520 MAX-ACCESS not-accessible 521 STATUS current 522 DESCRIPTION 523 "The 'Aggregate' Table enumerates Behavior Aggregate 524 classifiers (DSCPs) that a system may identify traffic 525 using." 526 ::= { diffServTables 1 } 528 diffServAggregateEntry OBJECT-TYPE 529 SYNTAX DiffServAggregateEntry 530 MAX-ACCESS not-accessible 531 STATUS current 532 DESCRIPTION 533 "An 'aggregate' entry describes a single BA 534 classifier." 535 INDEX { diffServAggregateDSCP } 536 ::= { diffServAggregateTable 1 } 538 DiffServAggregateEntry ::= SEQUENCE { 539 diffServAggregateDSCP Dscp 540 } 542 diffServAggregateDSCP OBJECT-TYPE 543 SYNTAX Dscp 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "This is the Differentiated Services Code Point (DSCP) 548 for the classifier. This object is only meant to be 549 pointed to by a RowPointer from other tables, such as 550 the diffServClassifierMatchObject, and is not actually 551 configured or changed." 552 ::= { diffServAggregateEntry 1 } 554 Draft Differentiated Services MIB October 1999 556 -- The tools for MultiField Classification. 557 -- 558 -- This textual convention has no effect on either the syntax 559 -- nor the semantics of any managed object. Objects defined 560 -- using this convention are always encoded by means of the 561 -- rules that define their primitive type. 562 -- 563 MFClassifierL4Port ::= TEXTUAL-CONVENTION 564 DISPLAY-HINT "d" 565 STATUS current 566 DESCRIPTION 567 "A value indicating a Layer-4 protocol port number." 568 SYNTAX INTEGER (0..65535) 570 -- This object allows a configuring system to obtain a 571 -- unique value for diffServClassifierNumber for purposes of 572 -- configuration. 574 diffServMFClassifierUnique OBJECT-TYPE 575 SYNTAX TestAndIncr 576 MAX-ACCESS read-write 577 STATUS current 578 DESCRIPTION 579 "The diffServMFClassifierUnique object yields a 580 unique new value for diffServMFClassifierIndex when read and 581 subsequently set. This value must be tested for 582 uniqueness." 583 ::= { diffServObjects 1 } 585 diffServMFClassifierTable OBJECT-TYPE 586 SYNTAX SEQUENCE OF diffServMFClassifierEntry 587 MAX-ACCESS not-accessible 588 STATUS current 589 DESCRIPTION 590 "A table of MF (IP 6-tuple multi-field) classifier 591 entries that a system may use to identify traffic." 592 ::= { diffServTables 2 } 594 diffServMFClassifierEntry OBJECT-TYPE 595 SYNTAX DiffServMFClassifierEntry 596 MAX-ACCESS not-accessible 597 STATUS current 598 DESCRIPTION 599 "A multi-field classifier entry describes a single MF 600 classifier." 601 INDEX { diffServMFClassifierIndex } 602 ::= { diffServMFClassifierTable 1 } 604 Draft Differentiated Services MIB October 1999 606 DiffServMFClassifierEntry ::= SEQUENCE { 607 diffServMFClassifierIndex INTEGER, 608 diffServMFClassifierAddrType InetEndpointType, 609 diffServMFClassifierDstAddr InetEndpoint, 610 diffServMFClassifierDstAddrMask InetEndpoint, 611 diffServMFClassifierSrcAddr InetEndpoint, 612 diffServMFClassifierSrcAddrMask InetEndpoint, 613 diffServMFClassifierDscp INTEGER, 614 diffServMFClassifierProtocol INTEGER, 615 diffServMFClassifierDstL4PortMin MFClassifierL4Port, 616 diffServMFClassifierDstL4PortMax MFClassifierL4Port, 617 diffServMFClassifierSrcL4PortMin MFClassifierL4Port, 618 diffServMFClassifierSrcL4PortMax MFClassifierL4Port, 619 diffServMFClassifierStatus RowStatus 620 } 622 diffServMFClassifierIndex OBJECT-TYPE 623 SYNTAX INTEGER (1..2147483647) 624 MAX-ACCESS not-accessible 625 STATUS current 626 DESCRIPTION 627 "This is a unique index for the classifier. This object 628 is meant to be pointed to by a RowPointer from other 629 tables, such as the diffServClassifierMatchObject." 630 ::= { diffServMFClassifierEntry 1 } 632 diffServMFClassifierAddrType OBJECT-TYPE 633 SYNTAX InetEndpointType 634 MAX-ACCESS read-create 635 STATUS current 636 DESCRIPTION 637 "The type of IP address used by this classifier entry." 638 ::= { diffServMFClassifierEntry 2 } 640 diffServMFClassifierDstAddr OBJECT-TYPE 641 SYNTAX InetEndpoint 642 MAX-ACCESS read-create 643 STATUS current 644 DESCRIPTION 645 "The IP address to match against the packet's 646 destination IP address." 647 ::= { diffServMFClassifierEntry 3 } 649 diffServMFClassifierDstAddrMask OBJECT-TYPE 650 SYNTAX InetEndpoint 651 MAX-ACCESS read-create 652 STATUS current 654 Draft Differentiated Services MIB October 1999 656 DESCRIPTION 657 "A mask for the matching of the destination IP address. 658 A zero bit in the mask means that the corresponding bit 659 in the address always matches." 660 ::= { diffServMFClassifierEntry 4 } 662 diffServMFClassifierSrcAddr OBJECT-TYPE 663 SYNTAX InetEndpoint 664 MAX-ACCESS read-create 665 STATUS current 666 DESCRIPTION 667 "The IP address to match against the source IP address 668 of each packet." 669 ::= { diffServMFClassifierEntry 5 } 671 diffServMFClassifierSrcAddrMask OBJECT-TYPE 672 SYNTAX InetEndpoint 673 MAX-ACCESS read-create 674 STATUS current 675 DESCRIPTION 676 "A mask for the matching of the source IP address." 677 ::= { diffServMFClassifierEntry 6 } 679 diffServMFClassifierDscp OBJECT-TYPE 680 SYNTAX INTEGER (-1 | 0..63) 681 MAX-ACCESS read-create 682 STATUS current 683 DESCRIPTION 684 "The value that the DSCP in the packet must have to 685 match this entry. A value of -1 indicates that a 686 specific DSCP value has not been defined and thus all 687 DSCP values are considered a match." 688 ::= { diffServMFClassifierEntry 7 } 690 diffServMFClassifierProtocol OBJECT-TYPE 691 SYNTAX INTEGER (0..255) 692 MAX-ACCESS read-create 693 STATUS current 694 DESCRIPTION 695 "The IP protocol to match against the IPv4 protocol 696 number in the packet. A value of zero means match all." 697 ::= { diffServMFClassifierEntry 8 } 699 diffServMFClassifierDstL4PortMin OBJECT-TYPE 700 SYNTAX MFClassifierL4Port 701 MAX-ACCESS read-create 702 STATUS current 704 Draft Differentiated Services MIB October 1999 706 DESCRIPTION 707 "The minimum value that the layer-4 destination port 708 number in the packet must have in order to match this 709 classifier entry." 710 ::= { diffServMFClassifierEntry 9 } 712 diffServMFClassifierDstL4PortMax OBJECT-TYPE 713 SYNTAX MFClassifierL4Port 714 MAX-ACCESS read-create 715 STATUS current 716 DESCRIPTION 717 "The maximum value that the layer-4 destination port 718 number in the packet must have in order to match this 719 classifier entry. This value must be equal to or 720 greater that the value specified for this entry in 721 diffServMFClassifierDstL4PortMin." 722 ::= { diffServMFClassifierEntry 10 } 724 diffServMFClassifierSrcL4PortMin OBJECT-TYPE 725 SYNTAX MFClassifierL4Port 726 MAX-ACCESS read-create 727 STATUS current 728 DESCRIPTION 729 "The minimum value that the layer-4 source port number 730 in the packet must have in order to match this 731 classifier entry." 732 ::= { diffServMFClassifierEntry 11 } 734 diffServMFClassifierSrcL4PortMax OBJECT-TYPE 735 SYNTAX MFClassifierL4Port 736 MAX-ACCESS read-create 737 STATUS current 738 DESCRIPTION 739 "The maximum value that the layer-4 source port number 740 in the packet must have in oder to match this 741 classifier entry. This value must be equal to or 742 greater that the value specified for this entry in 743 dsSixTupleIpSrcL4PortMin." 744 ::= { diffServMFClassifierEntry 12 } 746 diffServMFClassifierStatus OBJECT-TYPE 747 SYNTAX RowStatus 748 MAX-ACCESS read-create 749 STATUS current 750 DESCRIPTION 751 "This indicates the status of this classifier entry." 752 ::= { diffServMFClassifierEntry 13 } 754 Draft Differentiated Services MIB October 1999 756 -- This object allows a configuring system to obtain a 757 -- unique value for diffServClassifierNumber for purposes of 758 -- configuration 760 diffServClassifierUnique OBJECT-TYPE 761 SYNTAX TestAndIncr 762 MAX-ACCESS read-write 763 STATUS current 764 DESCRIPTION 765 "The diffServClassifierUnique object yields a unique 766 new value for diffServClassifierNumber when read and 767 subsequently set. This value must be tested for 768 uniqueness." 769 ::= { diffServObjects 2 } 771 -- The Classifier Table allows us to enumerate the 772 -- relationship between arbitrary classifiers and 773 -- the meters which apply to classified streams. 775 diffServClassifierTable OBJECT-TYPE 776 SYNTAX SEQUENCE OF DiffServClassifierEntry 777 MAX-ACCESS not-accessible 778 STATUS current 779 DESCRIPTION 780 "The classifier table enumerates specific classifiers 781 that a system may apply, including Differentiated 782 Services Code Points (DSCPs) and Multi-field 783 discriminators such as {Source IP Address, Destination 784 IP Address, IP Protocol, Source TCP/UDP Port, 785 Destination TCP/UDP Port)." 786 ::= { diffServTables 3 } 788 diffServClassifierEntry OBJECT-TYPE 789 SYNTAX DiffServClassifierEntry 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "An entry in the classifier table describes a single 794 classifier." 795 INDEX { ifIndex, diffServInterfaceDirection, 796 diffServClassifierNumber } 797 ::= { diffServClassifierTable 1 } 799 DiffServClassifierEntry ::= SEQUENCE { 800 diffServInterfaceDirection INTEGER, 801 diffServClassifierNumber INTEGER, 802 diffServClassifierMatchObject RowPointer, 804 Draft Differentiated Services MIB October 1999 806 diffServClassifierNext RowPointer, 807 diffServClassifierSequence Unsigned32, 808 diffServClassifierConfigType INTEGER, 809 diffServClassifierConfigTypeInfo OCTET STRING, 810 diffServClassifierStatus RowStatus 811 } 813 diffServInterfaceDirection OBJECT-TYPE 814 SYNTAX INTEGER { 815 inbound(1), -- ingress interface 816 outbound(2) -- egress interface 817 } 818 MAX-ACCESS not-accessible 819 STATUS current 820 DESCRIPTION 821 "Specifies the direction for this entry on the 822 interface. 'inbound' traffic is operated on during 823 receipt, while 'outbound' traffic is operated on prior 824 to transmission." 825 ::= { diffServClassifierEntry 1 } 827 diffServClassifierNumber OBJECT-TYPE 828 SYNTAX INTEGER (1..2147483647) 829 MAX-ACCESS not-accessible 830 STATUS current 831 DESCRIPTION 832 "diffServClassifierNumber enumerates the classifier 833 entry." 834 ::= { diffServClassifierEntry 2 } 836 diffServClassifierMatchObject OBJECT-TYPE 837 SYNTAX RowPointer 838 MAX-ACCESS read-create 839 STATUS current 840 DESCRIPTION 841 "A pointer to the row that describes the applicable 842 classifier. An obvious choice would be the 843 diffServAggregateEntry for a given DSCP, but other 844 choices include tables describing any classifier that 845 may be of interest. If the row pointed to does not 846 exist, the classifier is ignored. 848 The NULL OID zeroDotZero is interpreted to match 849 anything not matched by another classifier." 850 DEFVAL { zeroDotZero } 851 ::= { diffServClassifierEntry 3 } 853 Draft Differentiated Services MIB October 1999 855 diffServClassifierNext OBJECT-TYPE 856 SYNTAX RowPointer 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "The 'next' variable selects the appropriate meter or 861 action to apply to this class of traffic." 862 ::= { diffServClassifierEntry 4 } 864 diffServClassifierSequence OBJECT-TYPE 865 SYNTAX Unsigned32 866 MAX-ACCESS read-create 867 STATUS current 868 DESCRIPTION 869 "The sequence in which classifiers are applied, in 870 ascending order. Classifiers with the same sequence 871 number must be unambiguous. Classifiers with different 872 sequence numbers may overlap in their ranges, with the 873 understanding that the first applied classifier to 874 match a packet is taken." 875 DEFVAL { 0 } 876 ::= { diffServClassifierEntry 5 } 878 diffServClassifierConfigType OBJECT-TYPE 879 SYNTAX INTEGER { 880 OTHER (0), 881 MIB (1), -- Configured via MIB 882 PIB (2), -- Configured via PIB 883 BGP (3) -- Configured via BGP 884 } 885 MAX-ACCESS read-write 886 STATUS current 887 DESCRIPTION 888 "Used to indicate how the classifer is configured." 889 ::= { diffServClassifierEntry 6 } 891 diffServClassifierConfigTypeInfo OBJECT-TYPE 892 SYNTAX OCTET STRING 893 MAX-ACCESS read-write 894 STATUS current 895 DESCRIPTION 896 "Additional information associated with how the 897 classifier is configured." 898 ::= { diffServClassifierEntry 7 } 900 diffServClassifierStatus OBJECT-TYPE 901 SYNTAX RowStatus 903 Draft Differentiated Services MIB October 1999 905 MAX-ACCESS read-create 906 STATUS current 907 DESCRIPTION 908 "The RowStatus variable controls the activation, 909 deactivation, or deletion of a classifier. Any writable 910 variable may be modified whether the row is active or 911 notInService." 912 ::= { diffServClassifierEntry 8 } 914 Draft Differentiated Services MIB October 1999 916 -- This object allows a configuring system to obtain a 917 -- unique value for diffServClassifierNumber for purposes of 918 -- configuration 920 diffServTBMeterUnique OBJECT-TYPE 921 SYNTAX TestAndIncr 922 MAX-ACCESS read-write 923 STATUS current 924 DESCRIPTION 925 "The diffServTBMeterUnique object yieldiffServ a unique 926 new value for diffServTBMeterNumber when read and 927 subsequently set. This value must be tested for 928 uniqueness." 929 ::= { diffServObjects 3 } 931 -- The Meter Table allows us to enumerate the 932 -- relationship between meters and the actions, other 933 -- meters, and queues that result from them. 935 diffServTBMeterTable OBJECT-TYPE 936 SYNTAX SEQUENCE OF DiffServTBMeterEntry 937 MAX-ACCESS not-accessible 938 STATUS current 939 DESCRIPTION 940 "The Meter Table enumerates specific token bucket 941 meters that a system may use to police a stream of 942 classified traffic. Such a stream may include a single 943 micro-flow, all traffic from a given source to a given 944 destination, all traffic conforming to a single 945 classifier, or any other cut of the traffic, including 946 all of it. 948 Note that the conceptual model requires all traffic to 949 pass through one or more meters, and that the last 950 meter configured in such a sequence must always 951 conform. 953 Counters in this table start counting on creation of 954 the meter that specifies their existence." 955 ::= { diffServTables 4 } 957 diffServTBMeterEntry OBJECT-TYPE 958 SYNTAX DiffServTBMeterEntry 959 MAX-ACCESS not-accessible 960 STATUS current 961 DESCRIPTION 962 "An entry in the meter table describes a single token 964 Draft Differentiated Services MIB October 1999 966 bucket meter. Note that a meter has exactly one rate, 967 defined as the burst size each time interval. Multiple 968 meters may be cascaded should a multi-rate token bucket 969 be needed in a given Per-Hop Behavior. An example of 970 such a PHB is AF." 971 INDEX { ifIndex, diffServInterfaceDirection, 972 diffServTBMeterNumber } 973 ::= { diffServTBMeterTable 1 } 975 DiffServTBMeterEntry ::= SEQUENCE { 976 diffServTBMeterNumber INTEGER, 977 diffServTBMeterInterval Unsigned32, 978 diffServTBMeterBurstSize Unsigned32, 979 diffServTBMeterFailNext RowPointer, 980 diffServTBMeterSucceedNext RowPointer, 981 diffServTBMeterStatus RowStatus 982 } 984 diffServTBMeterNumber OBJECT-TYPE 985 SYNTAX INTEGER (1..2147483647) 986 MAX-ACCESS not-accessible 987 STATUS current 988 DESCRIPTION 989 "The number of the meter, for reference from the 990 classifier or in cascade from another meter." 991 ::= { diffServTBMeterEntry 1 } 993 diffServTBMeterInterval OBJECT-TYPE 994 SYNTAX Unsigned32 995 UNITS "microseconds" 996 MAX-ACCESS read-create 997 STATUS current 998 DESCRIPTION 999 "The number of microseconds in the token bucket 1000 interval for this meter. Note that implementations 1001 frequently do not keep time in microseconds internally, 1002 so in implementation the effect of this value must be 1003 approximated." 1004 ::= { diffServTBMeterEntry 2 } 1006 diffServTBMeterBurstSize OBJECT-TYPE 1007 SYNTAX Unsigned32 1008 UNITS "bytes" 1009 MAX-ACCESS read-create 1010 STATUS current 1011 DESCRIPTION 1012 "The number of bytes in a single transmission burst. 1014 Draft Differentiated Services MIB October 1999 1016 The rate at which the metered traffic may run is one 1017 burst per interval. Note that if multiple meters are 1018 cascaded onto one PHB, such as in AF, their intervals 1019 must be equal, and the peak rate of the data stream is 1020 the sum of their intervals per interval." 1021 ::= { diffServTBMeterEntry 3 } 1023 diffServTBMeterFailNext OBJECT-TYPE 1024 SYNTAX RowPointer 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "If the traffic does not conform to the meter, the next 1029 meter or action to enquire of." 1030 ::= { diffServTBMeterEntry 4 } 1032 diffServTBMeterSucceedNext OBJECT-TYPE 1033 SYNTAX RowPointer 1034 MAX-ACCESS read-create 1035 STATUS current 1036 DESCRIPTION 1037 "The 'Succeed Next' pointer selects which action or 1038 queue on the interface that to be used with the 1039 message. Incoming traffic may use the value zeroDotZero 1040 in this variable to indicate that no queuing on receipt 1041 occurs. Incoming interfaces generally use queuing 1042 either to divert routing traffic for speedier 1043 processing during a flap, or for shaping purposes." 1044 DEFVAL { zeroDotZero } 1045 ::= { diffServTBMeterEntry 5 } 1047 diffServTBMeterStatus OBJECT-TYPE 1048 SYNTAX RowStatus 1049 MAX-ACCESS read-create 1050 STATUS current 1051 DESCRIPTION 1052 "The RowStatus variable controls the activation, 1053 deactivation, or deletion of a meter. Any writable 1054 variable may be modified whether the row is active or 1055 notInService." 1056 ::= { diffServTBMeterEntry 6 } 1058 Draft Differentiated Services MIB October 1999 1060 -- This object allows a configuring system to obtain a 1061 -- unique value for diffServActionNumber for purposes of 1062 -- configuration 1064 diffServActionUnique OBJECT-TYPE 1065 SYNTAX TestAndIncr 1066 MAX-ACCESS read-write 1067 STATUS current 1068 DESCRIPTION 1069 "The diffServActionUnique object yields a unique new 1070 value for diffServActionNumber when read and 1071 subsequently set. This value must be tested for 1072 uniqueness." 1073 ::= { diffServObjects 4 } 1075 -- The Meter Table allows us to enumerate the 1076 -- relationship between meters and the actions, other meters, 1077 -- and queues that result from them. 1079 diffServActionTable OBJECT-TYPE 1080 SYNTAX SEQUENCE OF DiffServActionEntry 1081 MAX-ACCESS not-accessible 1082 STATUS current 1083 DESCRIPTION 1084 "The Action Table enumerates specific apply to a stream 1085 of classified traffic. Such a stream may include a 1086 single micro-flow, all traffic from a given source to a 1087 given destination, all traffic conforming to a single 1088 classifier, or any other cut of the traffic, including 1089 all of it. 1091 Counters in this table start counting on creation of 1092 the action that specifies their existence." 1093 ::= { diffServTables 5 } 1095 diffServActionEntry OBJECT-TYPE 1096 SYNTAX DiffServActionEntry 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "An entry in the action table describes the actions 1101 applied to traffic conforming to a given meter." 1102 INDEX { ifIndex, diffServInterfaceDirection, 1103 diffServActionNumber } 1104 ::= { diffServActionTable 1 } 1106 DiffServActionEntry ::= SEQUENCE { 1108 Draft Differentiated Services MIB October 1999 1110 diffServActionNumber INTEGER, 1111 diffServActionNext RowPointer, 1112 diffServActionDSCP Dscp, 1113 diffServActionMinThreshold Unsigned32, 1114 diffServActionMaxThreshold Unsigned32, 1115 diffServActionDropPolicy INTEGER, 1116 diffServActionHCConformingPackets Counter64, 1117 diffServActionConformingPackets Counter32, 1118 diffServActionHCConformingOctets Counter64, 1119 diffServActionConformingOctets Counter32, 1120 diffServActionTailDrops Counter32, 1121 diffServActionHCTailDrops Counter64, 1122 diffServActionRandomDrops Counter32, 1123 diffServActionHCRandomDrops Counter64, 1124 diffServActionStatus RowStatus 1125 } 1127 diffServActionNumber OBJECT-TYPE 1128 SYNTAX INTEGER (1..2147483647) 1129 MAX-ACCESS not-accessible 1130 STATUS current 1131 DESCRIPTION 1132 "The number of the meter, for reference from the 1133 classifier or in cascade from another meter." 1134 ::= { diffServActionEntry 1 } 1136 diffServActionNext OBJECT-TYPE 1137 SYNTAX RowPointer 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION 1141 "The 'Next' pointer selects which queue or Traffic 1142 Control Block on the interface. Incoming traffic may 1143 use the value zeroDotZero in this variable to indicate 1144 that no queuing on receipt occurs. Incoming interfaces 1145 generally use queuing either to divert routing traffic 1146 for speedier processing during a flap, or for shaping 1147 purposes." 1148 DEFVAL { zeroDotZero } 1149 ::= { diffServActionEntry 2 } 1151 diffServActionDSCP OBJECT-TYPE 1152 SYNTAX Dscp 1153 MAX-ACCESS read-create 1154 STATUS current 1155 DESCRIPTION 1156 "The DSCP that traffic conforming to this classifier 1158 Draft Differentiated Services MIB October 1999 1160 and this meter is remarked with. Note that if the 1161 classifier is working from the same DSCP value, no 1162 effective change in the DSCP results. 1164 Differentiated Services may result in packet remarking 1165 both on ingress to a network and on egress, and it is 1166 quite possible that ingress and egress would occur in 1167 the same router." 1168 ::= { diffServActionEntry 3 } 1170 diffServActionMinThreshold OBJECT-TYPE 1171 SYNTAX Unsigned32 1172 UNITS "packets" 1173 MAX-ACCESS read-create 1174 STATUS current 1175 DESCRIPTION 1176 "The min-threshold is the queue depth that a random 1177 drop process will seek to manage the queue's depth to. 1179 This object is in the action table rather than the 1180 queue table because Differentiated Services PHBs, such 1181 as the Assured Service, permit differently classified 1182 traffic to have different drop parameters even though 1183 they occupy the same queue." 1184 ::= { diffServActionEntry 4 } 1186 diffServActionMaxThreshold OBJECT-TYPE 1187 SYNTAX Unsigned32 1188 UNITS "packets" 1189 MAX-ACCESS read-create 1190 STATUS current 1191 DESCRIPTION 1192 "The max-threshold is the maximum permissible queue 1193 depth. In tail drop scenarios, the queue will drop if a 1194 packet is presented to it and it is instantaneously 1195 full by this measure. In random drop scenarios, the 1196 queue will drop if a packet is presented to it and the 1197 average queue depth exceeds the max-threshold. 1199 This object is in the action table rather than the 1200 queue table because Differentiated Services PHBs, such 1201 as the Assured Service, permit differently classified 1202 traffic to have different drop parameters even though 1203 they occupy the same queue." 1204 ::= { diffServActionEntry 5 } 1206 diffServActionDropPolicy OBJECT-TYPE 1208 Draft Differentiated Services MIB October 1999 1210 SYNTAX INTEGER { 1211 other(1), 1212 alwaysDrop (2), -- Disallowed traffic 1213 tailDrop(3), -- Fixed Queue Size 1214 randomDrop(4) -- RED w/thresholds 1215 -- per class 1216 } 1217 MAX-ACCESS read-create 1218 STATUS current 1219 DESCRIPTION 1220 "The drop policy applied to traffic." 1221 ::= { diffServActionEntry 6 } 1223 diffServActionHCConformingPackets OBJECT-TYPE 1224 SYNTAX Counter64 1225 UNITS "bytes" 1226 MAX-ACCESS read-only 1227 STATUS current 1228 DESCRIPTION 1229 "The number of Packets conforming to this meter. This 1230 object is used on high speed interfaces. 1232 Discontinuities in the value of this counter can occur 1233 at re-initialization of the management system, and at 1234 other times as indicated by the value of 1235 ifCounterDiscontinuityTime." 1236 ::= { diffServActionEntry 7 } 1238 diffServActionConformingPackets OBJECT-TYPE 1239 SYNTAX Counter32 1240 UNITS "bytes" 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "The number of Packets conforming to this meter. This 1245 object may be used on low speed interfaces, and 1246 represents the least significant 32 bits of 1247 diffServActionHCConformingPackets. 1249 Discontinuities in the value of this counter can occur 1250 at re-initialization of the management system, and at 1251 other times as indicated by the value of 1252 ifCounterDiscontinuityTime." 1253 ::= { diffServActionEntry 8 } 1255 diffServActionHCConformingOctets OBJECT-TYPE 1256 SYNTAX Counter64 1258 Draft Differentiated Services MIB October 1999 1260 UNITS "bytes" 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "The number of octets conforming to this meter. This 1265 object is used on high speed interfaces. 1267 Discontinuities in the value of this counter can occur 1268 at re-initialization of the management system, and at 1269 other times as indicated by the value of 1270 ifCounterDiscontinuityTime." 1271 ::= { diffServActionEntry 9 } 1273 diffServActionConformingOctets OBJECT-TYPE 1274 SYNTAX Counter32 1275 UNITS "bytes" 1276 MAX-ACCESS read-only 1277 STATUS current 1278 DESCRIPTION 1279 "The number of octets conforming to this meter. This 1280 object may be used on low speed interfaces, and 1281 represents the least significant 32 bits of 1282 diffServActionHCConformingOctets. 1284 Discontinuities in the value of this counter can occur 1285 at re-initialization of the management system, and at 1286 other times as indicated by the value of 1287 ifCounterDiscontinuityTime." 1288 ::= { diffServActionEntry 10 } 1290 diffServActionTailDrops OBJECT-TYPE 1291 SYNTAX Counter32 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION 1295 "The number of packets conforming to this classifier 1296 and meter that have been dropped because either the 1297 meter always drops, or the queue's depth exceeds the 1298 max-threshold value. On high speed devices, this 1299 object implements the least significant 32 bits of 1300 diffServActionHCTailDrops . 1302 Discontinuities in the value of this counter can occur 1303 at re-initialization of the management system, and at 1304 other times as indicated by the value of 1305 ifCounterDiscontinuityTime." 1306 ::= { diffServActionEntry 11 } 1308 Draft Differentiated Services MIB October 1999 1310 diffServActionHCTailDrops OBJECT-TYPE 1311 SYNTAX Counter64 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "The number of packets conforming to this classifier 1316 and meter that have been dropped because either the 1317 meter always drops, or the queue's depth exceeds the 1318 max-threshold value. This object should be used on 1319 high speed interfaces. 1321 Discontinuities in the value of this counter can occur 1322 at re-initialization of the management system, and at 1323 other times as indicated by the value of 1324 ifCounterDiscontinuityTime." 1325 ::= { diffServActionEntry 12 } 1327 diffServActionRandomDrops OBJECT-TYPE 1328 SYNTAX Counter32 1329 MAX-ACCESS read-only 1330 STATUS current 1331 DESCRIPTION 1332 "The number of packets conforming to this classifier 1333 and meter that have been dropped by a random drop 1334 process because the queue is over-full. On high speed 1335 lines, this object reflects the least significant 32 1336 bits of diffServActionHCRandomDrops. 1338 Discontinuities in the value of this counter can occur 1339 at re-initialization of the management system, and at 1340 other times as indicated by the value of 1341 ifCounterDiscontinuityTime." 1342 ::= { diffServActionEntry 13 } 1344 diffServActionHCRandomDrops OBJECT-TYPE 1345 SYNTAX Counter64 1346 MAX-ACCESS read-only 1347 STATUS current 1348 DESCRIPTION 1349 "The number of packets conforming to this classifier 1350 and meter that have been dropped by a random drop 1351 process because the queue is over-full. This object is 1352 used on high speed lines. 1354 Discontinuities in the value of this counter can occur 1355 at re-initialization of the management system, and at 1356 other times as indicated by the value of 1358 Draft Differentiated Services MIB October 1999 1360 ifCounterDiscontinuityTime." 1361 ::= { diffServActionEntry 14 } 1363 diffServActionStatus OBJECT-TYPE 1364 SYNTAX RowStatus 1365 MAX-ACCESS read-create 1366 STATUS current 1367 DESCRIPTION 1368 "The RowStatus variable controls the activation, 1369 deactivation, or deletion of a meter. Any writable 1370 variable may be modified whether the row is active or 1371 notInService." 1372 ::= { diffServActionEntry 15 } 1374 Draft Differentiated Services MIB October 1999 1376 -- This object allows a configuring system to obtain a 1377 -- unique value for diffServQueueNumber for purposes of 1378 -- configuration 1380 diffServQueueUnique OBJECT-TYPE 1381 SYNTAX TestAndIncr 1382 MAX-ACCESS read-write 1383 STATUS current 1384 DESCRIPTION 1385 "The diffServQueueUnique object yields a unique new 1386 value for diffServQueueNumber when read and 1387 subsequently set. This value must be tested for 1388 uniqueness." 1389 ::= { diffServObjects 5 } 1391 -- The Queue Table allows us to describe queues 1393 diffServQueueTable OBJECT-TYPE 1394 SYNTAX SEQUENCE OF DiffServQueueEntry 1395 MAX-ACCESS not-accessible 1396 STATUS current 1397 DESCRIPTION 1398 "The Queue Table enumerates the queues on an interface. 1399 Queues are used to store traffic during intervals when 1400 the arrival rate exceeds the departure rate for a class 1401 of traffic. Because some PHBs indicate that the use of 1402 a priority queue may be advisable, each queue in this 1403 system is seen as having a priority. Those queues that 1404 share the same priority operate in what may externally 1405 appear to be a Weighted Round Robin manner, and preempt 1406 the traffic belonging to any lower priority. For this 1407 reason, it is strongly urged that traffic placed into 1408 prioritized queues be strongly policed to avoid traffic 1409 lockout. 1411 Queues in this table also have a minimum and a maximum 1412 rate. When a maximum rate is specified, the queue acts 1413 as a shaper if it has sufficient traffic and capacity 1414 is available. If it is a minimum rate, then the weight 1415 in the WRR is effectively set to this rate divided by 1416 the sum of the rates of queues on the interface, 1417 guaranteeing it at least that throughput rate. If it is 1418 a maximum rate, the queue operates as a shaper. A 1419 shaper potentially reduces the rate of traffic through 1420 it to the indicated rate, and minimizes variations in 1421 rate." 1422 ::= { diffServTables 6 } 1424 Draft Differentiated Services MIB October 1999 1426 diffServQueueEntry OBJECT-TYPE 1427 SYNTAX DiffServQueueEntry 1428 MAX-ACCESS not-accessible 1429 STATUS current 1430 DESCRIPTION 1431 "An entry in the Queue Table describes a single FIFO 1432 queue." 1433 INDEX { ifIndex, diffServInterfaceDirection, 1434 diffServQueueNumber } 1435 ::= { diffServQueueTable 1 } 1437 DiffServQueueEntry ::= SEQUENCE { 1438 diffServQueueNumber INTEGER, 1439 diffServQueueMinimumRate Unsigned32, 1440 diffServQueueMaximumRate Unsigned32, 1441 diffServQueuePriority Unsigned32, 1442 diffServQueueNextTCB RowPointer, 1443 diffServQueueOccupancyWeight Unsigned32, 1444 diffServQueueStatus RowStatus 1445 } 1447 diffServQueueNumber OBJECT-TYPE 1448 SYNTAX INTEGER (1..2147483647) 1449 MAX-ACCESS not-accessible 1450 STATUS current 1451 DESCRIPTION 1452 "The number of the queue." 1453 ::= { diffServQueueEntry 1 } 1455 diffServQueueMinimumRate OBJECT-TYPE 1456 SYNTAX Unsigned32 1457 UNITS "KBPS" 1458 MAX-ACCESS read-create 1459 STATUS current 1460 DESCRIPTION 1461 "The rate of the queue, in kilobits per second (KBPS). 1462 This unit is chosen because interfaces exist at the 1463 time of this writing which exceed the number of bits 1464 per second which may be represented in a 32 bit number. 1466 If the value is zero, then there is effectively no 1467 minimum rate. If the value is non-zero, the queue set 1468 will seek to assure this class of traffic at least this 1469 rate." 1470 ::= { diffServQueueEntry 2 } 1472 diffServQueueMaximumRate OBJECT-TYPE 1474 Draft Differentiated Services MIB October 1999 1476 SYNTAX Unsigned32 1477 UNITS "KBPS" 1478 MAX-ACCESS read-create 1479 STATUS current 1480 DESCRIPTION 1481 "The rate of the queue, in kilobits per second (KBPS). 1482 This unit is chosen because interfaces exist at the 1483 time of this writing which exceed the number of bits 1484 per second which may be represented in a 32 bit number. 1486 If the value is zero, then there is effectively no 1487 maximum rate. If the value is non-zero, the queue set 1488 will seek to assure this class of traffic at most this 1489 rate." 1490 ::= { diffServQueueEntry 3 } 1492 diffServQueuePriority OBJECT-TYPE 1493 SYNTAX Unsigned32 1494 MAX-ACCESS read-create 1495 STATUS current 1496 DESCRIPTION 1497 "The priority of the queue. If multiple queues exist on 1498 the same interface at the same priority, they are 1499 effectively given Weighted Round Robin service. If 1500 multiple priorities are configured on an interface, 1501 traffic with a numerically higher priority number is 1502 deemed to have higher priority than other traffic, and 1503 is preemptively serviced." 1504 ::= { diffServQueueEntry 4 } 1506 diffServQueueNextTCB OBJECT-TYPE 1507 SYNTAX RowPointer 1508 MAX-ACCESS read-create 1509 STATUS current 1510 DESCRIPTION 1511 "The 'Next' pointer selects the successor TCB on the 1512 interface. Incoming traffic may use the value 1513 zeroDotZero in this variable to indicate that the 1514 packet is now to be routed; outbound traffic may use 1515 the same value to indicate that no subsequent queuing 1516 applies. Ingress interfaces generally use queuing 1517 either to divert routing traffic for speedier 1518 processing during a flap, or for shaping purposes." 1519 DEFVAL { zeroDotZero } 1520 ::= { diffServQueueEntry 5 } 1522 diffServQueueOccupancyWeight OBJECT-TYPE 1524 Draft Differentiated Services MIB October 1999 1526 SYNTAX Unsigned32 1527 MAX-ACCESS read-create 1528 STATUS current 1529 DESCRIPTION 1530 "The amount, in the form of a factor, that the current, 1531 actual queue occupancy should influence the averaged 1532 queue occupancy. The averaged queue occupancy can be 1533 used for comparison to configured drop thresholds in 1534 RED or RED-like dropper implementations. Larger the 1535 weight, the greater the instantaneous queue occupancy 1536 influences the averaged queue occupancy. Usually, 1537 dramatic changes in the instantaneous queue occupancy 1538 is the result of bursty input streams. Notice this 1539 numeric attribute is divided by 10,000 to get the 1540 effective fractional factor used in the actual 1541 calculations." 1542 ::= { diffServQueueEntry 6 } 1544 diffServQueueStatus OBJECT-TYPE 1545 SYNTAX RowStatus 1546 MAX-ACCESS read-create 1547 STATUS current 1548 DESCRIPTION 1549 "The RowStatus variable controls the activation, 1550 deactivation, or deletion of a queue. Any writable 1551 variable may be modified whether the row is active or 1552 notInService." 1553 ::= { diffServQueueEntry 7 } 1555 Draft Differentiated Services MIB October 1999 1557 -- MIB Compliance statements. Three variations of 1558 -- compliance are described, for optical, LAN, and low speed 1559 -- interfaces. The difference is the implementation of 1560 -- diffServActionHCConformingOctets 1561 -- and diffServActionHCConformingPackets 1563 diffServMIBCompliances OBJECT IDENTIFIER ::= { diffServMIBConformance 1 } 1564 diffServMIBGroups OBJECT IDENTIFIER ::= { diffServMIBConformance 2 } 1566 diffServMIBCompliance MODULE-COMPLIANCE 1567 STATUS current 1568 DESCRIPTION 1569 "This MIB may be implemented as a read-only or as a 1570 read-create MIB. As a result, it may be used for 1571 monitoring or for configuration. 1573 Standard compliance implies that the implementation 1574 complies for interfaces for which an interface's octet 1575 counter might wrap at most once an hour, which by the 1576 IFMIB's convention applies to interfaces under 20 MBPS. 1577 It thus applies to any device which might implement a 1578 low speed serial line, Ethernet, Token Ring." 1579 MODULE -- This Module 1580 MANDATORY-GROUPS { 1581 diffServMIBClassifierGroup, diffServMIBMeterGroup, 1582 diffServMIBQueueGroup, diffServMIBActionGroup 1584 -- note that diffServMIBHCCounterGroup is 1585 -- mandatory for medium and high speed interfaces 1587 -- note that diffServMIBVHCCounterGroup is 1588 -- mandatory for high speed interfaces 1590 -- note that the diffServMIBStaticGroup is 1591 -- mandatory for implementations that implement a 1592 -- read-write or read-create mode. 1593 } 1595 GROUP diffServMIBHCCounterGroup 1596 DESCRIPTION 1597 "This group is mandatory for those network interfaces 1598 for which the value of the corresponding instance of 1599 ifSpeed is greater than 20,000,000 bits/second." 1601 GROUP diffServMIBVHCCounterGroup 1602 DESCRIPTION 1603 "This group is mandatory for those network interfaces 1605 Draft Differentiated Services MIB October 1999 1607 for which the value of the corresponding instance of 1608 ifSpeed is greater than 650,000,000 bits/second." 1610 OBJECT diffServClassifierMatchObject 1611 MIN-ACCESS read-only 1612 DESCRIPTION 1613 "Write access is not required." 1615 OBJECT diffServClassifierNext 1616 MIN-ACCESS read-only 1617 DESCRIPTION 1618 "Write access is not required." 1620 OBJECT diffServClassifierSequence 1621 MIN-ACCESS read-only 1622 DESCRIPTION 1623 "Write access is not required." 1625 OBJECT diffServClassifierStatus 1626 MIN-ACCESS read-only 1627 DESCRIPTION 1628 "Write access is not required." 1630 OBJECT diffServTBMeterInterval 1631 MIN-ACCESS read-only 1632 DESCRIPTION 1633 "Write access is not required." 1635 OBJECT diffServTBMeterBurstSize 1636 MIN-ACCESS read-only 1637 DESCRIPTION 1638 "Write access is not required." 1640 OBJECT diffServTBMeterFailNext 1641 MIN-ACCESS read-only 1642 DESCRIPTION 1643 "Write access is not required." 1645 OBJECT diffServTBMeterSucceedNext 1646 MIN-ACCESS read-only 1647 DESCRIPTION 1648 "Write access is not required." 1650 OBJECT diffServTBMeterStatus 1651 MIN-ACCESS read-only 1652 DESCRIPTION 1653 "Write access is not required." 1655 Draft Differentiated Services MIB October 1999 1657 OBJECT diffServActionNext 1658 MIN-ACCESS read-only 1659 DESCRIPTION 1660 "Write access is not required." 1662 OBJECT diffServActionDSCP 1663 MIN-ACCESS read-only 1664 DESCRIPTION 1665 "Write access is not required." 1667 OBJECT diffServActionMinThreshold 1668 MIN-ACCESS read-only 1669 DESCRIPTION 1670 "Write access is not required." 1672 OBJECT diffServActionMaxThreshold 1673 MIN-ACCESS read-only 1674 DESCRIPTION 1675 "Write access is not required." 1677 OBJECT diffServActionDropPolicy 1678 MIN-ACCESS read-only 1679 DESCRIPTION 1680 "Write access is not required." 1682 OBJECT diffServActionStatus 1683 MIN-ACCESS read-only 1684 DESCRIPTION 1685 "Write access is not required." 1687 OBJECT diffServQueueMinimumRate 1688 MIN-ACCESS read-only 1689 DESCRIPTION 1690 "Write access is not required." 1692 OBJECT diffServQueueMaximumRate 1693 MIN-ACCESS read-only 1694 DESCRIPTION 1695 "Write access is not required." 1697 OBJECT diffServQueuePriority 1698 MIN-ACCESS read-only 1699 DESCRIPTION 1700 "Write access is not required." 1702 OBJECT diffServQueueNextTCB 1703 MIN-ACCESS read-only 1705 Draft Differentiated Services MIB October 1999 1707 DESCRIPTION 1708 "Write access is not required." 1710 OBJECT diffServQueueStatus 1711 MIN-ACCESS read-only 1712 DESCRIPTION 1713 "Write access is not required." 1714 ::= { diffServMIBCompliances 1 } 1716 Draft Differentiated Services MIB October 1999 1718 diffServMIBVHCCompliance MODULE-COMPLIANCE 1719 STATUS current 1720 DESCRIPTION 1721 "This MIB may be implemented as a read-only or as a 1722 read-create MIB. As a result, it may be used for 1723 monitoring or for configuration. 1725 Very High Speed compliance implies that the 1726 implementation complies for interfaces for which an 1727 interface's packet or octet counters might wrap more 1728 than once an hour, which by the IFMIB's convention 1729 applies to interfaces over 650 MBPS, or OC-12." 1730 MODULE -- This Module 1731 MANDATORY-GROUPS { 1732 diffServMIBClassifierGroup, diffServMIBMeterGroup, 1733 diffServMIBQueueGroup, diffServMIBHCCounterGroup, 1734 diffServMIBVHCCounterGroup, diffServMIBActionGroup 1736 -- note that the diffServMIBStaticGroup is 1737 -- mandatory for implementations that implement a 1738 -- read-write or read-create mode. 1739 } 1741 OBJECT diffServClassifierMatchObject 1742 MIN-ACCESS read-only 1743 DESCRIPTION 1744 "Write access is not required." 1746 OBJECT diffServClassifierNext 1747 MIN-ACCESS read-only 1748 DESCRIPTION 1749 "Write access is not required." 1751 OBJECT diffServClassifierSequence 1752 MIN-ACCESS read-only 1753 DESCRIPTION 1754 "Write access is not required." 1756 OBJECT diffServClassifierStatus 1757 MIN-ACCESS read-only 1758 DESCRIPTION 1759 "Write access is not required." 1761 OBJECT diffServTBMeterInterval 1762 MIN-ACCESS read-only 1763 DESCRIPTION 1765 Draft Differentiated Services MIB October 1999 1767 "Write access is not required." 1769 OBJECT diffServTBMeterBurstSize 1770 MIN-ACCESS read-only 1771 DESCRIPTION 1772 "Write access is not required." 1774 OBJECT diffServTBMeterFailNext 1775 MIN-ACCESS read-only 1776 DESCRIPTION 1777 "Write access is not required." 1779 OBJECT diffServTBMeterSucceedNext 1780 MIN-ACCESS read-only 1781 DESCRIPTION 1782 "Write access is not required." 1784 OBJECT diffServTBMeterStatus 1785 MIN-ACCESS read-only 1786 DESCRIPTION 1787 "Write access is not required." 1789 OBJECT diffServActionNext 1790 MIN-ACCESS read-only 1791 DESCRIPTION 1792 "Write access is not required." 1794 OBJECT diffServActionDSCP 1795 MIN-ACCESS read-only 1796 DESCRIPTION 1797 "Write access is not required." 1799 OBJECT diffServActionMinThreshold 1800 MIN-ACCESS read-only 1801 DESCRIPTION 1802 "Write access is not required." 1804 OBJECT diffServActionMaxThreshold 1805 MIN-ACCESS read-only 1806 DESCRIPTION 1807 "Write access is not required." 1809 OBJECT diffServActionDropPolicy 1810 MIN-ACCESS read-only 1811 DESCRIPTION 1812 "Write access is not required." 1814 Draft Differentiated Services MIB October 1999 1816 OBJECT diffServActionStatus 1817 MIN-ACCESS read-only 1818 DESCRIPTION 1819 "Write access is not required." 1821 OBJECT diffServQueueMinimumRate 1822 MIN-ACCESS read-only 1823 DESCRIPTION 1824 "Write access is not required." 1826 OBJECT diffServQueueMaximumRate 1827 MIN-ACCESS read-only 1828 DESCRIPTION 1829 "Write access is not required." 1831 OBJECT diffServQueuePriority 1832 MIN-ACCESS read-only 1833 DESCRIPTION 1834 "Write access is not required." 1836 OBJECT diffServQueueNextTCB 1837 MIN-ACCESS read-only 1838 DESCRIPTION 1839 "Write access is not required." 1841 OBJECT diffServQueueStatus 1842 MIN-ACCESS read-only 1843 DESCRIPTION 1844 "Write access is not required." 1845 ::= { diffServMIBCompliances 2 } 1847 Draft Differentiated Services MIB October 1999 1849 diffServMIBHCCompliance MODULE-COMPLIANCE 1850 STATUS current 1851 DESCRIPTION 1852 "This MIB may be implemented as a read-only or as a 1853 read-create MIB. As a result, it may be used for 1854 monitoring or for configuration. 1856 High Speed compliance implies that the implementation 1857 complies for interfaces for which an interface's octet 1858 counters might wrap more than once an hour, which by 1859 the IFMIB's convention applies to interfaces over 20 1860 MBPS, but under 650 MBPS. It thus applies to devices 1861 which implement a 100 MBPS Ethernet, FDDI, E3, DS3, or 1862 SONET/SDH interface up to OC-12." 1863 MODULE -- This Module 1864 MANDATORY-GROUPS { 1865 diffServMIBClassifierGroup, diffServMIBMeterGroup, 1866 diffServMIBQueueGroup, diffServMIBHCCounterGroup, 1867 diffServMIBActionGroup 1869 -- note that diffServMIBVHCCounterGroup is 1870 -- mandatory for high speed interfaces 1872 -- note that the diffServMIBStaticGroup is 1873 -- mandatory for implementations that implement a 1874 -- read-write or read-create mode. 1875 } 1877 GROUP diffServMIBVHCCounterGroup 1878 DESCRIPTION 1879 "This group is mandatory for those network interfaces 1880 for which the value of the corresponding instance of 1881 ifSpeed is greater than 650,000,000 bits/second." 1883 OBJECT diffServClassifierMatchObject 1884 MIN-ACCESS read-only 1885 DESCRIPTION 1886 "Write access is not required." 1888 OBJECT diffServClassifierNext 1889 MIN-ACCESS read-only 1890 DESCRIPTION 1891 "Write access is not required." 1893 OBJECT diffServClassifierSequence 1894 MIN-ACCESS read-only 1895 DESCRIPTION 1897 Draft Differentiated Services MIB October 1999 1899 "Write access is not required." 1901 OBJECT diffServClassifierStatus 1902 MIN-ACCESS read-only 1903 DESCRIPTION 1904 "Write access is not required." 1906 OBJECT diffServTBMeterInterval 1907 MIN-ACCESS read-only 1908 DESCRIPTION 1909 "Write access is not required." 1911 OBJECT diffServTBMeterBurstSize 1912 MIN-ACCESS read-only 1913 DESCRIPTION 1914 "Write access is not required." 1916 OBJECT diffServTBMeterFailNext 1917 MIN-ACCESS read-only 1918 DESCRIPTION 1919 "Write access is not required." 1921 OBJECT diffServTBMeterSucceedNext 1922 MIN-ACCESS read-only 1923 DESCRIPTION 1924 "Write access is not required." 1926 OBJECT diffServTBMeterStatus 1927 MIN-ACCESS read-only 1928 DESCRIPTION 1929 "Write access is not required." 1931 OBJECT diffServActionNext 1932 MIN-ACCESS read-only 1933 DESCRIPTION 1934 "Write access is not required." 1936 OBJECT diffServActionDSCP 1937 MIN-ACCESS read-only 1938 DESCRIPTION 1939 "Write access is not required." 1941 OBJECT diffServActionMinThreshold 1942 MIN-ACCESS read-only 1943 DESCRIPTION 1944 "Write access is not required." 1946 Draft Differentiated Services MIB October 1999 1948 OBJECT diffServActionMaxThreshold 1949 MIN-ACCESS read-only 1950 DESCRIPTION 1951 "Write access is not required." 1953 OBJECT diffServActionDropPolicy 1954 MIN-ACCESS read-only 1955 DESCRIPTION 1956 "Write access is not required." 1958 OBJECT diffServActionStatus 1959 MIN-ACCESS read-only 1960 DESCRIPTION 1961 "Write access is not required." 1963 OBJECT diffServQueueMinimumRate 1964 MIN-ACCESS read-only 1965 DESCRIPTION 1966 "Write access is not required." 1968 OBJECT diffServQueueMaximumRate 1969 MIN-ACCESS read-only 1970 DESCRIPTION 1971 "Write access is not required." 1973 OBJECT diffServQueuePriority 1974 MIN-ACCESS read-only 1975 DESCRIPTION 1976 "Write access is not required." 1978 OBJECT diffServQueueNextTCB 1979 MIN-ACCESS read-only 1980 DESCRIPTION 1981 "Write access is not required." 1983 OBJECT diffServQueueStatus 1984 MIN-ACCESS read-only 1985 DESCRIPTION 1986 "Write access is not required." 1987 ::= { diffServMIBCompliances 3 } 1989 Draft Differentiated Services MIB October 1999 1991 diffServMIBClassifierGroup OBJECT-GROUP 1992 OBJECTS { 1993 diffServAggregateDSCP, 1994 diffServClassifierMatchObject, 1995 diffServClassifierNext, 1996 diffServClassifierSequence, 1997 diffServClassifierStatus 1998 } 1999 STATUS current 2000 DESCRIPTION 2001 "The Classifier Group defines the MIB Objects that 2002 describe a classifier." 2003 ::= { diffServMIBGroups 1 } 2005 diffServMIBMeterGroup OBJECT-GROUP 2006 OBJECTS { 2007 diffServTBMeterInterval, diffServTBMeterBurstSize, 2008 diffServTBMeterSucceedNext, diffServTBMeterFailNext, 2009 diffServTBMeterStatus 2010 } 2011 STATUS current 2012 DESCRIPTION 2013 "The Meter Group defines the objects used in describing 2014 a meter." 2015 ::= { diffServMIBGroups 2 } 2017 diffServMIBActionGroup OBJECT-GROUP 2018 OBJECTS { 2019 diffServActionDropPolicy, 2020 diffServActionRandomDrops, 2021 diffServActionTailDrops, 2022 diffServActionMinThreshold, 2023 diffServActionMaxThreshold, diffServActionDSCP, 2024 diffServActionNext, 2025 diffServActionConformingPackets, 2026 diffServActionConformingOctets, 2027 diffServActionStatus 2028 } 2029 STATUS current 2030 DESCRIPTION 2031 "The Action Group defines the objects used in 2032 describing an action." 2033 ::= { diffServMIBGroups 3 } 2035 diffServMIBHCCounterGroup OBJECT-GROUP 2036 OBJECTS { 2037 diffServActionHCConformingOctets 2039 Draft Differentiated Services MIB October 1999 2041 } 2042 STATUS current 2043 DESCRIPTION 2044 "At 20,000,000 bits per second or greater, the number 2045 of octets a given class may count can overflow a 32 bit 2046 counter in under an hour. Therefore, by convention 2047 established in the IFMIB, the 64 bit counter must be 2048 implemented as well." 2049 ::= { diffServMIBGroups 4 } 2051 diffServMIBVHCCounterGroup OBJECT-GROUP 2052 OBJECTS { 2053 diffServActionHCConformingPackets, 2054 diffServActionHCRandomDrops, 2055 diffServActionHCTailDrops 2056 } 2057 STATUS current 2058 DESCRIPTION 2059 "At 650,000,000 bits per second or greater, the number 2060 of packets a given class may count can overflow a 32 2061 bit counter in under an hour. Therefore, by convention 2062 established in the IFMIB, the 64 bit counter must be 2063 implemented as well." 2064 ::= { diffServMIBGroups 5 } 2066 diffServMIBQueueGroup OBJECT-GROUP 2067 OBJECTS { 2068 diffServQueueMinimumRate, 2069 diffServQueueMaximumRate, 2070 diffServQueuePriority, diffServQueueStatus, 2071 diffServQueueNextTCB 2072 } 2073 STATUS current 2074 DESCRIPTION 2075 "The Queue Group contains the objects that describe an 2076 interface's queues." 2077 ::= { diffServMIBGroups 6 } 2079 diffServMIBStaticGroup OBJECT-GROUP 2080 OBJECTS { 2081 diffServClassifierUnique, diffServTBMeterUnique, 2082 diffServQueueUnique, diffServActionUnique 2083 } 2084 STATUS current 2085 DESCRIPTION 2086 "The Static Group contains scalar objects used in 2087 creating unique enumerations for classifiers, meters, 2089 Draft Differentiated Services MIB October 1999 2091 and queues." 2092 ::= { diffServMIBGroups 7 } 2093 END 2095 Draft Differentiated Services MIB October 1999 2097 5. Acknowledgments 2099 This MIB has been developed with active involvement from a 2100 number of sources, but most notably Yoram Bernet, Steve Blake, 2101 Brian Carpenter, Kwok Chan, Dave Durham, Jeremy Greene, Roch 2102 Guerin, Scott Hahn, Keith McCloghrie, Kathleen Nichols, Ping 2103 Pan, Andrew Smith, and Bert Wijnen. 2105 6. Security Considerations 2107 It is clear that this MIB is potentially useful for 2108 configuration, and anything that can be configured can be 2109 misconfigured, with potentially disastrous effect. 2111 At this writing, no security holes have been identified beyond 2112 those that SNMP Security is itself intended to address. These 2113 relate to primarily controlled access to sensitive information 2114 and the ability to configure a device - or which might result 2115 from operator error, which is beyond the scope of any security 2116 architecture. 2118 There are a number of management objects defined in this MIB 2119 that have a MAX-ACCESS clause of read-write and/or read- 2120 create. Such objects may be considered sensitive or vulnerable 2121 in some network environments. The support for SET operations 2122 in a non-secure environment without proper protection can have 2123 a negative effect on network operations. The use of SNMP 2124 Version 3 is recommended over prior versions, for 2125 configuration control, as its security model is improved. 2127 There are a number of managed objects in this MIB that may 2128 contain information that may be sensitive from a business 2129 perspective, in that they may represent a customer's service 2130 contract or the filters that the service provider chooses to 2131 apply to a customer's ingress or egress traffic. There are no 2132 objects which are sensitive in their own right, such as 2133 passwords or monetary amounts. 2135 It may be important to control even GET access to these 2136 objects and possibly to even encrypt the values of these 2137 object when sending them over the network via SNMP. Not all 2138 versions of SNMP provide features for such a secure 2139 environment. 2141 Draft Differentiated Services MIB October 1999 2143 7. References 2145 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An 2146 Architecture for Describing SNMP Management Frameworks", 2147 RFC 2571, Cabletron Systems, Inc., BMC Software, Inc., 2148 IBM T. J. Watson Research, April 1999 2150 [2] Rose, M., and K. McCloghrie, "Structure and 2151 Identification of Management Information for TCP/IP-based 2152 Internets", RFC 1155, STD 16, Performance Systems 2153 International, Hughes LAN Systems, May 1990 2155 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 2156 RFC 1212, STD 16, Performance Systems International, 2157 Hughes LAN Systems, March 1991 2159 [4] M. Rose, "A Convention for Defining Traps for use with 2160 the SNMP", RFC 1215, Performance Systems International, 2161 March 1991 2163 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2164 Rose, M., and S. Waldbusser, "Structure of Management 2165 Information Version 2 (SMIv2)", RFC 2578, STD 58, Cisco 2166 Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 2167 Virtual Holdings, International Network Services, April 2168 1999 2170 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2171 Rose, M., and S. Waldbusser, "Textual Conventions for 2172 SMIv2", RFC 2579, STD 58, Cisco Systems, SNMPinfo, TU 2173 Braunschweig, SNMP Research, First Virtual Holdings, 2174 International Network Services, April 1999 2176 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2177 Rose, M., and S. Waldbusser, "Conformance Statements for 2178 SMIv2", RFC 2580, STD 58, Cisco Systems, SNMPinfo, TU 2179 Braunschweig, SNMP Research, First Virtual Holdings, 2180 International Network Services, April 1999 2182 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2183 "Simple Network Management Protocol", RFC 1157, STD 15, 2184 SNMP Research, Performance Systems International, 2185 Performance Systems International, MIT Laboratory for 2186 Computer Science, May 1990. 2188 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2189 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 2191 Draft Differentiated Services MIB October 1999 2193 Research, Inc., Cisco Systems, Inc., Dover Beach 2194 Consulting, Inc., International Network Services, January 2195 1996. 2197 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2198 "Transport Mappings for Version 2 of the Simple Network 2199 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, 2200 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2201 International Network Services, January 1996. 2203 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2204 "Message Processing and Dispatching for the Simple 2205 Network Management Protocol (SNMP)", RFC 2572, SNMP 2206 Research, Inc., Cabletron Systems, Inc., BMC Software, 2207 Inc., IBM T. J. Watson Research, April 1999 2209 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model 2210 (USM) for version 3 of the Simple Network Management 2211 Protocol (SNMPv3)", RFC 2574, IBM T. J. Watson Research, 2212 April 1999 2214 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2215 "Protocol Operations for Version 2 of the Simple Network 2216 Management Protocol (SNMPv2)", RFC 1905, SNMP Research, 2217 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2218 International Network Services, January 1996. 2220 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2221 Applications", RFC 2573, SNMP Research, Inc., Secure 2222 Computing Corporation, Cisco Systems, April 1999 2224 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2225 Access Control Model (VACM) for the Simple Network 2226 Management Protocol (SNMP)", RFC 2575, IBM T. J. Watson 2227 Research, BMC Software, Inc., Cisco Systems, Inc., April 2228 1999 2230 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, 2231 "Introduction to Version 3 of the Internet-standard 2232 Network Management Framework", RFC 2570, SNMP Research, 2233 Inc., TIS Labs at Network Associates, Inc., Ericsson, 2234 Cisco Systems, April 1999 2236 [DSCP] 2237 K. Nichols, S. Blake, F. Baker, D. Black, "Definition of 2238 the Differentiated Services Field (DS Field) in the IPv4 2239 and IPv6 Headers." RFC 2474, December 1998. 2241 Draft Differentiated Services MIB October 1999 2243 [Architecture] 2244 S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W. 2245 Weiss, "An Architecture for Differentiated Service." RFC 2246 2475, December 1998. 2248 [AF] J. Heinanen, F. Baker, W. Weiss, J. Wroclawski, "Assured 2249 Forwarding PHB Group." RFC 2597, June 1999. 2251 [EF] V. Jacobson, K. Nichols, K. Poduri. "An Expedited 2252 Forwarding PHB." RFC 2598, June 1999. 2254 [Model] 2255 Bernet et al, "A Conceptual Model for Diffserv Routers", 2256 06/25/1999, draft-ietf-diffserv-model-00.txt 2258 [IFMIB] 2259 K. McCloghrie, F. Kastenholz. "The Interfaces Group MIB 2260 using SMIv2", Request for Comments 2233, November 1997. 2262 8. Authors' Addresses: 2264 Fred Baker 2265 519 Lado Drive 2266 Santa Barbara, California 93111 2267 fred@cisco.com 2269 Kwok Ho Chan 2270 Nortel Networks 2271 600 Technology Park Drive 2272 Billerica, MA 01821 2273 khchan@nortelnetworks.com 2275 Andrew Smith 2276 Extreme Networks 2277 3585 Monroe Street 2278 Santa Clara, CA 95051 2279 USA 2280 andrew@extremenetworks.com