draft-ietf-diffserv-mib-00.txt   draft-ietf-diffserv-mib-01.txt 
Draft Differentiated Services MIB October 1999
Fred Baker Fred Baker
Kwok Ho Chan
Nortel Networks
Andrew Smith
Extreme Networks
Management Information Base for the Management Information Base for the
Differentiated Services Architecture Differentiated Services Architecture
draft-ietf-diffserv-mib-00.txt draft-ietf-diffserv-mib-01.txt
Abstract Abstract
This memo describes a proposed MIB for the Differentiated This memo describes a proposed MIB for the Differentiated
Services Architecture. Services Architecture.
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC 2026. Internet-Drafts with all provisions of Section 10 of RFC 2026. Internet-Drafts
skipping to change at page 2, line 4 skipping to change at page 2, line 4
2. The SNMP Management Framework 2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [1]. o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and o Mechanisms for describing and naming objects and
events for the purpose of management. The first events for the purpose of management. The first
version of this Structure of Management Information version of this Structure of Management Information
Draft Differentiated Services MIB October 1999
(SMI) is called SMIv1 and described in RFC 1155 [2], (SMI) is called SMIv1 and described in RFC 1155 [2],
RFC 1212 [3] and RFC 1215 [4]. The second version, RFC 1212 [3] and RFC 1215 [4]. The second version,
called SMIv2, is described in RFC 2578 [5], RFC 2579 called SMIv2, is described in RFC 2578 [5], RFC 2579
[6] and RFC 2580 [7]. [6] and RFC 2580 [7].
o Message protocols for transferring management o Message protocols for transferring management
information. The first version of the SNMP message information. The first version of the SNMP message
protocol is called SNMPv1 and described in RFC 1157 protocol is called SNMPv1 and described in RFC 1157
[8]. A second version of the SNMP message protocol, [8]. A second version of the SNMP message protocol,
which is not an Internet standards track protocol, is which is not an Internet standards track protocol, is
skipping to change at page 3, line 5 skipping to change at page 3, line 5
SMIv2. A MIB conforming to the SMIv1 can be produced through SMIv2. A MIB conforming to the SMIv1 can be produced through
the appropriate translations. The resulting translated MIB the appropriate translations. The resulting translated MIB
must be semantically equivalent, except where objects or must be semantically equivalent, except where objects or
events are omitted because no translation is possible (use of events are omitted because no translation is possible (use of
Counter64). Some machine-readable information in SMIv2 will be Counter64). Some machine-readable information in SMIv2 will be
converted into textual descriptions in SMIv1 during the converted into textual descriptions in SMIv1 during the
translation process. However, this loss of machine readable translation process. However, this loss of machine readable
information is not considered to change the semantics of the information is not considered to change the semantics of the
MIB. MIB.
Draft Differentiated Services MIB October 1999
3. Structure of this MIB 3. Structure of this MIB
This MIB is designed according to the Differentiated Services This MIB is designed according to the Differentiated Services
implementation conceptual model documented in [Model]. implementation conceptual model documented in [Model].
3.1. Overview 3.1. Overview
In principle, if one were to construct a network entirely out In principle, if one were to construct a network entirely out
of two-port routers (in appropriate places connected by LANs of two-port routers (in appropriate places connected by LANs
or similar media), then it would be necessary for each router or similar media), then it would be necessary for each router
skipping to change at page 3, line 49 skipping to change at page 3, line 51
will be "interior" to the Differentiated Services domain. The will be "interior" to the Differentiated Services domain. The
one point of difference between an ingress and an egress one point of difference between an ingress and an egress
interface is that all traffic on an egress interface is interface is that all traffic on an egress interface is
queued, while traffic on an ingress interface will typically queued, while traffic on an ingress interface will typically
be queued only for shaping purposes. be queued only for shaping purposes.
Hence, in this MIB, we model them identically, making the Hence, in this MIB, we model them identically, making the
distinction between ingress and egress interfaces an index distinction between ingress and egress interfaces an index
variable. variable.
The MIB therefore contains five elements: The MIB therefore contains six elements:
- Behavior Aggregate Classification Table - Behavior Aggregate Classification Table
- Multi-Field Classification Table
Draft Differentiated Services MIB October 1999
- Classifier Table - Classifier Table
- Meter Table - Meter Table
- Action Table - Action Table
- Queue Table - Queue Table
3.2. Behavior Aggregate Classification Table 3.2. Classifier Table
The Behavior Aggregate Classification Table is present for
several reasons. First, the DSCP must be identified somewhere
for identifying tagged streams of traffic. This could be done
in-line, and is not.
The reason the BA Classifier is pulled out into a separate
table is that we envisage the use of other tables for other
kinds of classifiers, public or proprietary. For example, the
typical "five-tuple" used in per-flow classification (as in
RSVP) might be represented by a table whose objects include
the necessary IP Addresses, the IP protocol, the necessary
TCP/UDP port numbers, and a RowStatus variable. By pulling the
classifier itself into a table that can be referenced via a
RowPointer, we enable the use of any sort of classification
table that one might wish to design. That classifier table
need not be found in this MIB. When ambiguity is present, we
disambiguate by explicitly ordering the application of
classification rules.
3.3. Classifier Table
The classifier table, now, indicates how traffic is sorted The classifier table indicates how traffic is sorted out. It
out. It identifies separable classes of traffic, by reference identifies separable classes of traffic, by reference to an
to an appropriate classifier, which may be anything from an appropriate classifier, which may be anything from an
individual micro-flow to aggregates identified by DSCP. It individual micro-flow to aggregates identified by DSCP. It
then sends these classified streams to an appropriate meter or then sends these classified streams to an appropriate meter or
action. In a multi-stage meter, sub-classes of traffic may be action. In a multi-stage meter, sub-classes of traffic may be
sent to different stages. For example, in AF1, AF11 traffic sent to different stages. For example, in AF1, AF11 traffic
might be sent to the first meter, AF12 traffic might be sent might be sent to the first meter, AF12 traffic might be sent
to the second, and AF13 traffic sent to the second meter to the second, and AF13 traffic sent to the second meter
stage's failure action. stage's failure action.
The structure of the classifier table is a sequence of The structure of the classifier table is a sequence of
unambiguous tests. Within each step in the sequence, it should unambiguous tests. Within each step in the sequence, it should
skipping to change at page 5, line 14 skipping to change at page 4, line 44
some individual traffic streams that are not diff-serv marked. some individual traffic streams that are not diff-serv marked.
Traffic that fails those tests might then be inspected for a Traffic that fails those tests might then be inspected for a
DSCP. "Then" implies sequence, and the sequence must be DSCP. "Then" implies sequence, and the sequence must be
somehow specified. somehow specified.
An important form of classifier is "everything else". The An important form of classifier is "everything else". The
final stage of the classifier should be configured to be final stage of the classifier should be configured to be
complete, as the result of an incomplete classifier is not complete, as the result of an incomplete classifier is not
necessarily deterministic. necessarily deterministic.
3.4. Meter Table Two forms of classifiers are Behavior Aggregate (BA) and
Multi-Field (MF) Classifiers. These classifiers are specified
here at the per interface level, they can be derived from
some higher level policies. For example, QoS Policies
provisioned via QoS PIB (Policy Information Base), Routing
Policies with QoS information via BGP Policy setting
mechanism, and Routing Policies with QoS information from
traffic engineered routes. The source of classifier is
indicated by the diffServClassifierConfigType attribute of the
diffServClassifierEntry object. The attribute
Draft Differentiated Services MIB October 1999
diffServClassifierConfigTypeInfo can be used to further
associate the classifier with specific grouping based on the
ConfigType. For example, with PIB ConfigType, the
ConfigTypeInfo attribute can hold the RoleCombination from
which the classifier is derived. With BGP ConfigType, the
ConfigTypeInfo can hold the BGP Community String that
identifies the BGP Routing Policy from which the classifier is
derived. With the use of higher level policies, the
classifier table is used primarily for monitoring purpose, but
this does not exclude its use for configuration purpose.
3.2.1. Behavior Aggregate Classification Table
The Behavior Aggregate Classification Table is present for
several reasons. First, the DSCP must be identified somewhere
for identifying tagged streams of traffic. This could be done
in-line, and is not.
The reason the BA Classifier is pulled out into a separate
table is that we envisage the use of other tables for other
kinds of classifiers, public or proprietary. For example, the
typical "five-tuple" used in per-flow classification (as in
RSVP) might be represented by a table whose objects include
the necessary IP Addresses, the IP protocol, the necessary
TCP/UDP port numbers, and a RowStatus variable. By pulling the
classifier itself into a table that can be referenced via a
RowPointer, we enable the use of any sort of classification
table that one might wish to design. That classifier table
need not be found in this MIB. When ambiguity is present, we
disambiguate by explicitly ordering the application of
classification rules.
3.2.2. Multi-Field Classification Table
In the same spirit as the BA Classification Table, the Multi-
Field Classification Table is in a separate table that can be
referenced via a RowPointer, namely
diffServClassifierMatchObject attribute of
diffServClassifierEntry object. Each entry in the MF
Classification Table defines a MF Classifier. With the use of
InetEndpoint for both IPv4 and IPv6 addressing. The use of MF
Classifiers is discussed in [DSARCH] and abstract examples of
how they might be configured are provided in [DSMODEL].
Draft Differentiated Services MIB October 1999
3.3. Meter Table
A meter, according to the conceptual model, measures the rate A meter, according to the conceptual model, measures the rate
at which a stream of traffic passes it, compares it to some at which a stream of traffic passes it, compares it to some
set of thresholds, and produces some number (two or more) set of thresholds, and produces some number (two or more)
potential results. A given message is said to "conform" to the potential results. A given message is said to "conform" to the
meter if at the time that the message is being looked at the meter if at the time that the message is being looked at the
stream appears to be within the meter's limit rate. In the stream appears to be within the meter's limit rate. In the
MIB, the structure of SNMP makes it easiest to implement this MIB, the structure of SNMP makes it easiest to implement this
as a set of one or more simple pass/fail tests, which are as a set of one or more simple pass/fail tests, which are
cascaded. It is to be understood that the meter in a Traffic cascaded. It is to be understood that the meter in a Traffic
skipping to change at page 6, line 4 skipping to change at page 6, line 43
possible to build multi-rate leaky buckets, in which traffic possible to build multi-rate leaky buckets, in which traffic
departs from the switch at varying rates depending on recent departs from the switch at varying rates depending on recent
activity or inactivity. activity or inactivity.
A token bucket is used to measure the behavior of a peer's A token bucket is used to measure the behavior of a peer's
leaky bucket, for verification purposes. It is, by definition, leaky bucket, for verification purposes. It is, by definition,
a relationship a relationship
interval = burst/rate, or interval = burst/rate, or
rate = burst/interval rate = burst/interval
for some defined burst size, in bits, rate, in bits per for some defined burst size, in bits, rate, in bits per
second, and time interval. Multi-rate token buckets (token second, and time interval. Multi-rate token buckets (token
buckets with both a peak and a mean rate, and sometimes more buckets with both a peak and a mean rate, and sometimes more
rates) are commonly used. In this case, the burst size for the rates) are commonly used. In this case, the burst size for the
baseline traffic is conventionally referred to as the baseline traffic is conventionally referred to as the
"committed burst", and the time interval is as specified by "committed burst", and the time interval is as specified by
interval = committed burst/mean rate interval = committed burst/mean rate
Draft Differentiated Services MIB October 1999
but additional burst sizes (each an increment over its but additional burst sizes (each an increment over its
predecessor) are defined, which are conventionally referred to predecessor) are defined, which are conventionally referred to
as "excess" burst sizes. The peak rate therefore equals the as "excess" burst sizes. The peak rate therefore equals the
sum of the burst sizes per interval. sum of the burst sizes per interval.
A data stream is said to "conform" to a simple token bucket if A data stream is said to "conform" to a simple token bucket if
the switch receives at most the burst size in a given time the switch receives at most the burst size in a given time
interval. In the multi-rate case, the traffic is said to interval. In the multi-rate case, the traffic is said to
conform to the token bucket at a given level if its rate does conform to the token bucket at a given level if its rate does
not exceed the sum of the relevant burst sizes in a given not exceed the sum of the relevant burst sizes in a given
skipping to change at page 7, line 7 skipping to change at page 7, line 48
messages that conform to the meter, and with messages that do messages that conform to the meter, and with messages that do
not. It is also necessary for the meter to be arbitrarily not. It is also necessary for the meter to be arbitrarily
extensible, as some PHBs require the successive application of extensible, as some PHBs require the successive application of
an arbitrary number of meters. The approach taken in this an arbitrary number of meters. The approach taken in this
design is to have each meter indicate what action is to be design is to have each meter indicate what action is to be
taken for conforming traffic, and what meter is to be used for taken for conforming traffic, and what meter is to be used for
traffic which fails to conform. With the definition of a traffic which fails to conform. With the definition of a
special type of meter to which all traffic conforms, we now special type of meter to which all traffic conforms, we now
have the necessary flexibility. have the necessary flexibility.
3.5. Action Table 3.4. Action Table
Considerable discussion has taken place regarding the possible Considerable discussion has taken place regarding the possible
actions. Suggested actions include "no action", "mark the actions. Suggested actions include "no action", "mark the
traffic", "drop the traffic, randomly or all of it", and traffic", "drop the traffic, randomly or all of it", and
"shape the traffic." In this MIB, three actions are "shape the traffic." In this MIB, three actions are
Draft Differentiated Services MIB October 1999
contemplated: marking the traffic, counting the traffic that contemplated: marking the traffic, counting the traffic that
passes that route, applying a drop policy. The author notes passes that route, applying a drop policy. The author notes
that marking the traffic with the same DSCP as it already has that marking the traffic with the same DSCP as it already has
no effect, and all traffic must expect to come up against some no effect, and all traffic must expect to come up against some
drop policy. drop policy.
Two sizes of objects are defined for some counters. These are Two sizes of objects are defined for some counters. These are
defined in accordance with the method found in [IFMIB]; both defined in accordance with the method found in [IFMIB]; both
32 and 64 bit counters are defined, with the expectation that 32 and 64 bit counters are defined, with the expectation that
the 32 bit counter is simply the least significant bits of the the 32 bit counter is simply the least significant bits of the
skipping to change at page 7, line 35 skipping to change at page 8, line 29
counters MUST be used. For interfaces that operate faster counters MUST be used. For interfaces that operate faster
than 20,000,000 bits/second, and slower than 650,000,000 than 20,000,000 bits/second, and slower than 650,000,000
bits/second, 32-bit packet counters MUST be used and 64-bit bits/second, 32-bit packet counters MUST be used and 64-bit
octet counters MUST be used. For interfaces that operate at octet counters MUST be used. For interfaces that operate at
650,000,000 bits/second or faster, 64-bit packet counters AND 650,000,000 bits/second or faster, 64-bit packet counters AND
64-bit octet counters MUST be used. 64-bit octet counters MUST be used.
Traffic conforming to a meter and not dropped is presented to Traffic conforming to a meter and not dropped is presented to
a queue for further processing. a queue for further processing.
3.6. Queue Table 3.5. Queue Table
In this version of the MIB, a relatively simple FIFO queue is In this version of the MIB, a relatively simple FIFO queue is
envisaged within the Traffic Control Block. Scheduling among envisaged within the Traffic Control Block (TCB). Each queue
TCBs is done by some external scheduler. We presume some form is capable of acting as a work-conserving queue (one which
of Class Weighted Round Robin within one or more sets of transmits as rapidly as its weight allows, but guarantees to
queues, each of which enjoys preemptive priority over lower its class of traffic, as a side effect of its weight, a
numbered priorities of queue sets. Each queue is capable of minimum rate), or as a non-work-conserving or "shaping" queue.
acting as a work-conserving queue (one which transmits as Queue structure can be built from these FIFO queues, including
rapidly as its weight allows, but guarantees to its class of chain of queues using the NextTCB attribute. The scheduling
traffic, as a side-effect of its weight, a minimum rate), or discipline of a queue amongst the queue set of an inter- face
as a non-work-conserving or "shaping" queue. Queue sets and is specified. When all the queues in a queue set uses
more complex queue types - which are common and required to priority queue discipline, the queue set will use strict
correctly implement Differentiated Services, are modeled as priority queue scheduling using each queue's priority
several of these FIFO queues. attribute. When all the queues in a queue set uses weighted
fair queue discipline, the queue set will use weighted fair
queue scheduling, with the weight specified by the minimum
rate attribute. A mixed scheduling discipline can be built
for a queue set. For example, with the following queue set:
Q Number Q Discipline Q MinRate Q Priority
-------- ------------ --------- ----------
11 PQ 0 10
12 PQ 0 9
13 WFQ 800 KBPS 8
14 WFQ 600 KBPS 8
Draft Differentiated Services MIB October 1999
15 WFQ 300 KBPS 8
All traffic in queue 11 will be serviced first, then all
traffic in queue 12 will be serviced second. After traffic in
queues 11 and 12 are serviced, queues 13, 14, 15 are serviced
among themselves in a round robin fashion, with their
respective weights indicated by their minimum rate attribute.
The queue can also operate as a traffic shaper by using the
maximum rate attribute.
In addition some dropping algorithms rely on an averaged queue
depth to measure sustained, as opposed to instantaneous,
congestion. There are several methods for averaging the queue
depth. All of these methods share a mechanism specifying the
influence of the actual queue depth on the averaged queue
depth. Hence the attribute diffServQueueOccupancyWeight is
used.
Multiple meters may direct their traffic to the same queue. Multiple meters may direct their traffic to the same queue.
For example, the Assured Forwarding PHB suggests that all For example, the Assured Forwarding PHB suggests that all
traffic marked AF11, AF12, or AF13 be placed in the same queue traffic marked AF11, AF12, or AF13 be placed in the same queue
without reordering. without reordering.
Some discussion has elapsed concerning the structure of the Some discussion has elapsed concerning the structure of the
queue in question, and its functions. It is expected that the queue in question, and its functions. It is expected that the
description of the queuing system will grow during working description of the queuing system will grow during working
group discussion. This is an area where vendors differ group discussion. This is an area where vendors differ
markedly in their architectures. markedly in their architectures.
3.7. The use of RowPointer 3.6. The use of RowPointer
RowPointer is a textual convention used to identify a RowPointer is a textual convention used to identify a
conceptual row in an SNMP Table by pointing to one of its conceptual row in an SNMP Table by pointing to one of its
objects. In this MIB, it is used in two ways: to indicate objects. In this MIB, it is used in two ways: to indicate
indirection, and to indicate succession. indirection, and to indicate succession.
When used for indirection, as in the Classifier table, the When used for indirection, as in the Classifier table, the
idea is to allow other MIBs, including proprietary ones, to idea is to allow other MIBs, including proprietary ones, to
identify new and arcane classifiers - MAC headers, IP4 and IP6 identify new and arcane classifiers - MAC headers, IP4 and IP6
headers, BGP Communities, and all sorts of things. headers, BGP Communities, and all sorts of things.
When used for succession, it answers the question "what When used for succession, it answers the question "what
happens next?". Rather than presume that the next table must happens next?". Rather than presume that the next table must
be as specified in the conceptual model and providing its be as specified in the conceptual model and providing its
index, the RowPointer takes you to the MIB row representing index, the RowPointer takes you to the MIB row representing
that thing. In the Meter Table, for example, the "FailNext" that thing. In the Meter Table, for example, the "FailNext"
Draft Differentiated Services MIB October 1999
RowPointer might take you to another meter, while the RowPointer might take you to another meter, while the
"SucceedNext" RowPointer would take you to an action. "SucceedNext" RowPointer would take you to an action.
Draft Differentiated Services MIB October 1999
4. MIB Definition 4. MIB Definition
DIFF-SERV-MIB DEFINITIONS ::= BEGIN DIFF-SERV-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Unsigned32, Counter32, Counter64, OBJECT-TYPE, Unsigned32, Counter32, Counter64, OBJECT-TYPE,
MODULE-IDENTITY, zeroDotZero, mib-2 FROM SNMPv2-SMI MODULE-IDENTITY, zeroDotZero, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, RowPointer, TestAndIncr TEXTUAL-CONVENTION, RowStatus, RowPointer, TestAndIncr
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
ifIndex FROM IF-MIB; ifIndex FROM IF-MIB;
InetEndpointType, InetEndpoint FROM INET-ENDPOINT-MIB;
diffServMib MODULE-IDENTITY diffServMib MODULE-IDENTITY
LAST-UPDATED "9907150732Z" -- Thu Jul 15 07:32:36 PDT 1999 LAST-UPDATED "9907190100Z" -- Mon Jul 19 01:00:00 PDT 1999
ORGANIZATION "Cisco Systems" ORGANIZATION "Cisco Systems"
CONTACT-INFO CONTACT-INFO
" Fred Baker " Fred Baker
Postal: 519 Lado Drive Postal: 519 Lado Drive
Santa Barbara, California 93111 Santa Barbara, California 93111
Tel: +1 (408)526-4257 Tel: +1 (408)526-4257
FAX: +1 (805)681-0115 FAX: +1 (805)681-0115
E-mail: fred@cisco.com" E-mail: fred@cisco.com"
" Kwok Ho Chan
Postal: 600 Technology Park Drive
Billerica, Massachusetts 01821, USA
Tel: +1 (978)288-8175
E-mail: khchan@nortelnetworks.com"
" Andrew Smith
Postal: 3585 Monroe St.
Santa Clara, California 95051
Tel: +1 (408) 579 2821
FAX: +1 (408) 579 3000
E-mail: andrew@extremenetworks.com"
DESCRIPTION DESCRIPTION
"This MIB defines the objects necessary to manage a "This MIB defines the objects necessary to manage a
device that uses the Differentiated Services device that uses the Differentiated Services
Architecture described in RFC 2475." Architecture described in RFC 2475."
REVISION "9907150732Z" -- Thu Jul 15 07:32:36 PDT 1999 REVISION "9907190100Z" -- Mon Jul 19 01:00:00 PDT 1999
DESCRIPTION DESCRIPTION
"Initial version, published as RFC xxxx." "Initial version, published as RFC xxxx."
::= { mib-2 12345 } -- anybody who uses this ::= { mib-2 12345 } -- anybody who uses this
-- unassigned number -- unassigned number
-- deserves the wrath of IANA -- deserves the wrath of IANA
diffServObjects OBJECT IDENTIFIER ::= { diffServMib 1 } diffServObjects OBJECT IDENTIFIER ::= { diffServMib 1 }
diffServTables OBJECT IDENTIFIER ::= { diffServMib 2 } diffServTables OBJECT IDENTIFIER ::= { diffServMib 2 }
Draft Differentiated Services MIB October 1999
diffServMIBConformance OBJECT IDENTIFIER ::= { diffServMib 3 } diffServMIBConformance OBJECT IDENTIFIER ::= { diffServMib 3 }
Draft Differentiated Services MIB October 1999
-- The tools necessary to perform basic Behavior -- The tools necessary to perform basic Behavior
-- Aggregate Classification -- Aggregate Classification
-- --
Dscp ::= TEXTUAL-CONVENTION Dscp ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The code point used for discriminating a traffic "The code point used for discriminating a traffic
stream." stream."
SYNTAX INTEGER (0..63) SYNTAX INTEGER (0..63)
skipping to change at page 10, line 47 skipping to change at page 13, line 50
} }
diffServAggregateDSCP OBJECT-TYPE diffServAggregateDSCP OBJECT-TYPE
SYNTAX Dscp SYNTAX Dscp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the Differentiated Services Code Point (DSCP) "This is the Differentiated Services Code Point (DSCP)
for the classifier. This object is only meant to be for the classifier. This object is only meant to be
pointed to by a RowPointer from other tables, such as pointed to by a RowPointer from other tables, such as
the diffServClassifierMatchObject, and is no actually the diffServClassifierMatchObject, and is not actually
configured or changed." configured or changed."
::= { diffServAggregateEntry 1 } ::= { diffServAggregateEntry 1 }
Draft Differentiated Services MIB October 1999
-- The tools for MultiField Classification.
--
-- This textual convention has no effect on either the syntax
-- nor the semantics of any managed object. Objects defined
-- using this convention are always encoded by means of the
-- rules that define their primitive type.
--
MFClassifierL4Port ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A value indicating a Layer-4 protocol port number."
SYNTAX INTEGER (0..65535)
-- This object allows a configuring system to obtain a
-- unique value for diffServClassifierNumber for purposes of
-- configuration.
diffServMFClassifierUnique OBJECT-TYPE
SYNTAX TestAndIncr
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The diffServMFClassifierUnique object yields a
unique new value for diffServMFClassifierIndex when read and
subsequently set. This value must be tested for
uniqueness."
::= { diffServObjects 1 }
diffServMFClassifierTable OBJECT-TYPE
SYNTAX SEQUENCE OF diffServMFClassifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of MF (IP 6-tuple multi-field) classifier
entries that a system may use to identify traffic."
::= { diffServTables 2 }
diffServMFClassifierEntry OBJECT-TYPE
SYNTAX DiffServMFClassifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A multi-field classifier entry describes a single MF
classifier."
INDEX { diffServMFClassifierIndex }
::= { diffServMFClassifierTable 1 }
Draft Differentiated Services MIB October 1999
DiffServMFClassifierEntry ::= SEQUENCE {
diffServMFClassifierIndex INTEGER,
diffServMFClassifierAddrType InetEndpointType,
diffServMFClassifierDstAddr InetEndpoint,
diffServMFClassifierDstAddrMask InetEndpoint,
diffServMFClassifierSrcAddr InetEndpoint,
diffServMFClassifierSrcAddrMask InetEndpoint,
diffServMFClassifierDscp INTEGER,
diffServMFClassifierProtocol INTEGER,
diffServMFClassifierDstL4PortMin MFClassifierL4Port,
diffServMFClassifierDstL4PortMax MFClassifierL4Port,
diffServMFClassifierSrcL4PortMin MFClassifierL4Port,
diffServMFClassifierSrcL4PortMax MFClassifierL4Port,
diffServMFClassifierStatus RowStatus
}
diffServMFClassifierIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is a unique index for the classifier. This object
is meant to be pointed to by a RowPointer from other
tables, such as the diffServClassifierMatchObject."
::= { diffServMFClassifierEntry 1 }
diffServMFClassifierAddrType OBJECT-TYPE
SYNTAX InetEndpointType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of IP address used by this classifier entry."
::= { diffServMFClassifierEntry 2 }
diffServMFClassifierDstAddr OBJECT-TYPE
SYNTAX InetEndpoint
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address to match against the packet's
destination IP address."
::= { diffServMFClassifierEntry 3 }
diffServMFClassifierDstAddrMask OBJECT-TYPE
SYNTAX InetEndpoint
MAX-ACCESS read-create
STATUS current
Draft Differentiated Services MIB October 1999
DESCRIPTION
"A mask for the matching of the destination IP address.
A zero bit in the mask means that the corresponding bit
in the address always matches."
::= { diffServMFClassifierEntry 4 }
diffServMFClassifierSrcAddr OBJECT-TYPE
SYNTAX InetEndpoint
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address to match against the source IP address
of each packet."
::= { diffServMFClassifierEntry 5 }
diffServMFClassifierSrcAddrMask OBJECT-TYPE
SYNTAX InetEndpoint
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A mask for the matching of the source IP address."
::= { diffServMFClassifierEntry 6 }
diffServMFClassifierDscp OBJECT-TYPE
SYNTAX INTEGER (-1 | 0..63)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value that the DSCP in the packet must have to
match this entry. A value of -1 indicates that a
specific DSCP value has not been defined and thus all
DSCP values are considered a match."
::= { diffServMFClassifierEntry 7 }
diffServMFClassifierProtocol OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP protocol to match against the IPv4 protocol
number in the packet. A value of zero means match all."
::= { diffServMFClassifierEntry 8 }
diffServMFClassifierDstL4PortMin OBJECT-TYPE
SYNTAX MFClassifierL4Port
MAX-ACCESS read-create
STATUS current
Draft Differentiated Services MIB October 1999
DESCRIPTION
"The minimum value that the layer-4 destination port
number in the packet must have in order to match this
classifier entry."
::= { diffServMFClassifierEntry 9 }
diffServMFClassifierDstL4PortMax OBJECT-TYPE
SYNTAX MFClassifierL4Port
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum value that the layer-4 destination port
number in the packet must have in order to match this
classifier entry. This value must be equal to or
greater that the value specified for this entry in
diffServMFClassifierDstL4PortMin."
::= { diffServMFClassifierEntry 10 }
diffServMFClassifierSrcL4PortMin OBJECT-TYPE
SYNTAX MFClassifierL4Port
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The minimum value that the layer-4 source port number
in the packet must have in order to match this
classifier entry."
::= { diffServMFClassifierEntry 11 }
diffServMFClassifierSrcL4PortMax OBJECT-TYPE
SYNTAX MFClassifierL4Port
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum value that the layer-4 source port number
in the packet must have in oder to match this
classifier entry. This value must be equal to or
greater that the value specified for this entry in
dsSixTupleIpSrcL4PortMin."
::= { diffServMFClassifierEntry 12 }
diffServMFClassifierStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This indicates the status of this classifier entry."
::= { diffServMFClassifierEntry 13 }
Draft Differentiated Services MIB October 1999
-- This object allows a configuring system to obtain a -- This object allows a configuring system to obtain a
-- unique value for diffServClassifierNumber for purposes of -- unique value for diffServClassifierNumber for purposes of
-- configuration -- configuration
diffServClassifierUnique OBJECT-TYPE diffServClassifierUnique OBJECT-TYPE
SYNTAX TestAndIncr SYNTAX TestAndIncr
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The diffServClassifierUnique object yields a unique "The diffServClassifierUnique object yields a unique
new value for diffServClassifierNumber when read and new value for diffServClassifierNumber when read and
subsequently set. This value must be tested for subsequently set. This value must be tested for
uniqueness." uniqueness."
::= { diffServObjects 1 } ::= { diffServObjects 2 }
-- The Classifier Table allows us to enumerate the -- The Classifier Table allows us to enumerate the
-- relationship between arbitrary classifiers and -- relationship between arbitrary classifiers and
-- the meters which apply to classified streams. -- the meters which apply to classified streams.
diffServClassifierTable OBJECT-TYPE diffServClassifierTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServClassifierEntry SYNTAX SEQUENCE OF DiffServClassifierEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The classifier table enumerates specific classifiers "The classifier table enumerates specific classifiers
that a system may apply, including Differentiated that a system may apply, including Differentiated
Services Code Points (DSCPs) and Multi-field Services Code Points (DSCPs) and Multi-field
discriminators such as {Source IP Address, Destination discriminators such as {Source IP Address, Destination
IP Address, IP Protocol, Source TCP/UDP Port, IP Address, IP Protocol, Source TCP/UDP Port,
Destination TCP/UDP Port)." Destination TCP/UDP Port)."
::= { diffServTables 2 } ::= { diffServTables 3 }
diffServClassifierEntry OBJECT-TYPE diffServClassifierEntry OBJECT-TYPE
SYNTAX DiffServClassifierEntry SYNTAX DiffServClassifierEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the classifier table describes a single "An entry in the classifier table describes a single
classifier." classifier."
INDEX { ifIndex, diffServInterfaceDirection, INDEX { ifIndex, diffServInterfaceDirection,
diffServClassifierNumber } diffServClassifierNumber }
::= { diffServClassifierTable 1 } ::= { diffServClassifierTable 1 }
DiffServClassifierEntry ::= SEQUENCE { DiffServClassifierEntry ::= SEQUENCE {
diffServInterfaceDirection INTEGER, diffServInterfaceDirection INTEGER,
diffServClassifierNumber INTEGER, diffServClassifierNumber INTEGER,
diffServClassifierMatchObject RowPointer, diffServClassifierMatchObject RowPointer,
Draft Differentiated Services MIB October 1999
diffServClassifierNext RowPointer, diffServClassifierNext RowPointer,
diffServClassifierSequence Unsigned32, diffServClassifierSequence Unsigned32,
diffServClassifierConfigType INTEGER,
diffServClassifierConfigTypeInfo OCTET STRING,
diffServClassifierStatus RowStatus diffServClassifierStatus RowStatus
} }
diffServInterfaceDirection OBJECT-TYPE diffServInterfaceDirection OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
inbound(1), -- ingress interface inbound(1), -- ingress interface
outbound(2) -- egress interface outbound(2) -- egress interface
} }
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 12, line 49 skipping to change at page 20, line 5
diffServAggregateEntry for a given DSCP, but other diffServAggregateEntry for a given DSCP, but other
choices include tables describing any classifier that choices include tables describing any classifier that
may be of interest. If the row pointed to does not may be of interest. If the row pointed to does not
exist, the classifier is ignored. exist, the classifier is ignored.
The NULL OID zeroDotZero is interpreted to match The NULL OID zeroDotZero is interpreted to match
anything not matched by another classifier." anything not matched by another classifier."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { diffServClassifierEntry 3 } ::= { diffServClassifierEntry 3 }
Draft Differentiated Services MIB October 1999
diffServClassifierNext OBJECT-TYPE diffServClassifierNext OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The 'next' variable selects the appropriate meter or "The 'next' variable selects the appropriate meter or
action to apply to this class of traffic." action to apply to this class of traffic."
::= { diffServClassifierEntry 4 } ::= { diffServClassifierEntry 4 }
diffServClassifierSequence OBJECT-TYPE diffServClassifierSequence OBJECT-TYPE
skipping to change at page 13, line 25 skipping to change at page 20, line 30
DESCRIPTION DESCRIPTION
"The sequence in which classifiers are applied, in "The sequence in which classifiers are applied, in
ascending order. Classifiers with the same sequence ascending order. Classifiers with the same sequence
number must be unambiguous. Classifiers with different number must be unambiguous. Classifiers with different
sequence numbers may overlap in their ranges, with the sequence numbers may overlap in their ranges, with the
understanding that the first applied classifier to understanding that the first applied classifier to
match a packet is taken." match a packet is taken."
DEFVAL { 0 } DEFVAL { 0 }
::= { diffServClassifierEntry 5 } ::= { diffServClassifierEntry 5 }
diffServClassifierConfigType OBJECT-TYPE
SYNTAX INTEGER {
OTHER (0),
MIB (1), -- Configured via MIB
PIB (2), -- Configured via PIB
BGP (3) -- Configured via BGP
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Used to indicate how the classifer is configured."
::= { diffServClassifierEntry 6 }
diffServClassifierConfigTypeInfo OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Additional information associated with how the
classifier is configured."
::= { diffServClassifierEntry 7 }
diffServClassifierStatus OBJECT-TYPE diffServClassifierStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
Draft Differentiated Services MIB October 1999
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, "The RowStatus variable controls the activation,
deactivation, or deletion of a classifier. Any writable deactivation, or deletion of a classifier. Any writable
variable may be modified whether the row is active or variable may be modified whether the row is active or
notInService." notInService."
::= { diffServClassifierEntry 6 } ::= { diffServClassifierEntry 8 }
Draft Differentiated Services MIB October 1999
-- This object allows a configuring system to obtain a -- This object allows a configuring system to obtain a
-- unique value for diffServClassifierNumber for purposes of -- unique value for diffServClassifierNumber for purposes of
-- configuration -- configuration
diffServTBMeterUnique OBJECT-TYPE diffServTBMeterUnique OBJECT-TYPE
SYNTAX TestAndIncr SYNTAX TestAndIncr
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The diffServTBMeterUnique object yieldiffServ a unique "The diffServTBMeterUnique object yieldiffServ a unique
new value for diffServTBMeterNumber when read and new value for diffServTBMeterNumber when read and
subsequently set. This value must be tested for subsequently set. This value must be tested for
uniqueness." uniqueness."
::= { diffServObjects 2 } ::= { diffServObjects 3 }
-- The Meter Table allows us to enumerate the -- The Meter Table allows us to enumerate the
-- relationship between meters and the actions, other -- relationship between meters and the actions, other
-- meters, and queues that result from them. -- meters, and queues that result from them.
diffServTBMeterTable OBJECT-TYPE diffServTBMeterTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServTBMeterEntry SYNTAX SEQUENCE OF DiffServTBMeterEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 14, line 43 skipping to change at page 22, line 46
classifier, or any other cut of the traffic, including classifier, or any other cut of the traffic, including
all of it. all of it.
Note that the conceptual model requires all traffic to Note that the conceptual model requires all traffic to
pass through one or more meters, and that the last pass through one or more meters, and that the last
meter configured in such a sequence must always meter configured in such a sequence must always
conform. conform.
Counters in this table start counting on creation of Counters in this table start counting on creation of
the meter that specifies their existence." the meter that specifies their existence."
::= { diffServTables 3 } ::= { diffServTables 4 }
diffServTBMeterEntry OBJECT-TYPE diffServTBMeterEntry OBJECT-TYPE
SYNTAX DiffServTBMeterEntry SYNTAX DiffServTBMeterEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the meter table describes a single token "An entry in the meter table describes a single token
Draft Differentiated Services MIB October 1999
bucket meter. Note that a meter has exactly one rate, bucket meter. Note that a meter has exactly one rate,
defined as the burst size each time interval. Multiple defined as the burst size each time interval. Multiple
meters may be cascaded should a multi-rate token bucket meters may be cascaded should a multi-rate token bucket
be needed in a given Per-Hop Behavior. An example of be needed in a given Per-Hop Behavior. An example of
such a PHB is AF." such a PHB is AF."
INDEX { ifIndex, diffServInterfaceDirection, INDEX { ifIndex, diffServInterfaceDirection,
diffServTBMeterNumber } diffServTBMeterNumber }
::= { diffServTBMeterTable 1 } ::= { diffServTBMeterTable 1 }
DiffServTBMeterEntry ::= SEQUENCE { DiffServTBMeterEntry ::= SEQUENCE {
skipping to change at page 16, line 5 skipping to change at page 24, line 5
::= { diffServTBMeterEntry 2 } ::= { diffServTBMeterEntry 2 }
diffServTBMeterBurstSize OBJECT-TYPE diffServTBMeterBurstSize OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of bytes in a single transmission burst. "The number of bytes in a single transmission burst.
Draft Differentiated Services MIB October 1999
The rate at which the metered traffic may run is one The rate at which the metered traffic may run is one
burst per interval. Note that if multiple meters are burst per interval. Note that if multiple meters are
cascaded onto one PHB, such as in AF, their intervals cascaded onto one PHB, such as in AF, their intervals
must be equal, and the peak rate of the data stream is must be equal, and the peak rate of the data stream is
the sum of their intervals per interval." the sum of their intervals per interval."
::= { diffServTBMeterEntry 3 } ::= { diffServTBMeterEntry 3 }
diffServTBMeterFailNext OBJECT-TYPE diffServTBMeterFailNext OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 17, line 4 skipping to change at page 25, line 4
diffServTBMeterStatus OBJECT-TYPE diffServTBMeterStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, "The RowStatus variable controls the activation,
deactivation, or deletion of a meter. Any writable deactivation, or deletion of a meter. Any writable
variable may be modified whether the row is active or variable may be modified whether the row is active or
notInService." notInService."
::= { diffServTBMeterEntry 6 } ::= { diffServTBMeterEntry 6 }
Draft Differentiated Services MIB October 1999
-- This object allows a configuring system to obtain a -- This object allows a configuring system to obtain a
-- unique value for diffServActionNumber for purposes of -- unique value for diffServActionNumber for purposes of
-- configuration -- configuration
diffServActionUnique OBJECT-TYPE diffServActionUnique OBJECT-TYPE
SYNTAX TestAndIncr SYNTAX TestAndIncr
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The diffServActionUnique object yields a unique new "The diffServActionUnique object yields a unique new
value for diffServActionNumber when read and value for diffServActionNumber when read and
subsequently set. This value must be tested for subsequently set. This value must be tested for
uniqueness." uniqueness."
::= { diffServObjects 3 } ::= { diffServObjects 4 }
-- The Meter Table allows us to enumerate the -- The Meter Table allows us to enumerate the
-- relationship between meters and the actions, other meters, -- relationship between meters and the actions, other meters,
-- and queues that result from them. -- and queues that result from them.
diffServActionTable OBJECT-TYPE diffServActionTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServActionEntry SYNTAX SEQUENCE OF DiffServActionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Action Table enumerates specific apply to a stream "The Action Table enumerates specific apply to a stream
of classified traffic. Such a stream may include a of classified traffic. Such a stream may include a
single micro-flow, all traffic from a given source to a single micro-flow, all traffic from a given source to a
given destination, all traffic conforming to a single given destination, all traffic conforming to a single
classifier, or any other cut of the traffic, including classifier, or any other cut of the traffic, including
all of it. all of it.
Counters in this table start counting on creation of Counters in this table start counting on creation of
the action that specifies their existence." the action that specifies their existence."
::= { diffServTables 4 } ::= { diffServTables 5 }
diffServActionEntry OBJECT-TYPE diffServActionEntry OBJECT-TYPE
SYNTAX DiffServActionEntry SYNTAX DiffServActionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the action table describes the actions "An entry in the action table describes the actions
applied to traffic conforming to a given meter." applied to traffic conforming to a given meter."
INDEX { ifIndex, diffServInterfaceDirection, INDEX { ifIndex, diffServInterfaceDirection,
diffServActionNumber } diffServActionNumber }
::= { diffServActionTable 1 } ::= { diffServActionTable 1 }
DiffServActionEntry ::= SEQUENCE { DiffServActionEntry ::= SEQUENCE {
Draft Differentiated Services MIB October 1999
diffServActionNumber INTEGER, diffServActionNumber INTEGER,
diffServActionNext RowPointer, diffServActionNext RowPointer,
diffServActionDSCP Dscp, diffServActionDSCP Dscp,
diffServActionMinThreshold Unsigned32, diffServActionMinThreshold Unsigned32,
diffServActionMaxThreshold Unsigned32, diffServActionMaxThreshold Unsigned32,
diffServActionDropPolicy INTEGER, diffServActionDropPolicy INTEGER,
diffServActionHCConformingPackets Counter64, diffServActionHCConformingPackets Counter64,
diffServActionConformingPackets Counter32, diffServActionConformingPackets Counter32,
diffServActionHCConformingOctets Counter64, diffServActionHCConformingOctets Counter64,
diffServActionConformingOctets Counter32, diffServActionConformingOctets Counter32,
skipping to change at page 19, line 4 skipping to change at page 27, line 4
purposes." purposes."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { diffServActionEntry 2 } ::= { diffServActionEntry 2 }
diffServActionDSCP OBJECT-TYPE diffServActionDSCP OBJECT-TYPE
SYNTAX Dscp SYNTAX Dscp
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DSCP that traffic conforming to this classifier "The DSCP that traffic conforming to this classifier
Draft Differentiated Services MIB October 1999
and this meter is remarked with. Note that if the and this meter is remarked with. Note that if the
classifier is working from the same DSCP value, no classifier is working from the same DSCP value, no
effective change in the DSCP results. effective change in the DSCP results.
Differentiated Services may result in packet remarking Differentiated Services may result in packet remarking
both on ingress to a network and on egress, and it is both on ingress to a network and on egress, and it is
quite possible that ingress and egress would occur in quite possible that ingress and egress would occur in
the same router." the same router."
::= { diffServActionEntry 3 } ::= { diffServActionEntry 3 }
skipping to change at page 20, line 4 skipping to change at page 28, line 4
average queue depth exceeds the max-threshold. average queue depth exceeds the max-threshold.
This object is in the action table rather than the This object is in the action table rather than the
queue table because Differentiated Services PHBs, such queue table because Differentiated Services PHBs, such
as the Assured Service, permit differently classified as the Assured Service, permit differently classified
traffic to have different drop parameters even though traffic to have different drop parameters even though
they occupy the same queue." they occupy the same queue."
::= { diffServActionEntry 5 } ::= { diffServActionEntry 5 }
diffServActionDropPolicy OBJECT-TYPE diffServActionDropPolicy OBJECT-TYPE
Draft Differentiated Services MIB October 1999
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
alwaysDrop (2), -- Disallowed traffic alwaysDrop (2), -- Disallowed traffic
tailDrop(3), -- Fixed Queue Size tailDrop(3), -- Fixed Queue Size
randomDrop(4) -- RED w/thresholds randomDrop(4) -- RED w/thresholds
-- per class -- per class
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 21, line 4 skipping to change at page 29, line 4
diffServActionHCConformingPackets. diffServActionHCConformingPackets.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
ifCounterDiscontinuityTime." ifCounterDiscontinuityTime."
::= { diffServActionEntry 8 } ::= { diffServActionEntry 8 }
diffServActionHCConformingOctets OBJECT-TYPE diffServActionHCConformingOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
Draft Differentiated Services MIB October 1999
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets conforming to this meter. This "The number of octets conforming to this meter. This
object is used on high speed interfaces. object is used on high speed interfaces.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
skipping to change at page 22, line 4 skipping to change at page 30, line 4
meter always drops, or the queue's depth exceeds the meter always drops, or the queue's depth exceeds the
max-threshold value. On high speed devices, this max-threshold value. On high speed devices, this
object implements the least significant 32 bits of object implements the least significant 32 bits of
diffServActionHCTailDrops . diffServActionHCTailDrops .
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
ifCounterDiscontinuityTime." ifCounterDiscontinuityTime."
::= { diffServActionEntry 11 } ::= { diffServActionEntry 11 }
Draft Differentiated Services MIB October 1999
diffServActionHCTailDrops OBJECT-TYPE diffServActionHCTailDrops OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets conforming to this classifier "The number of packets conforming to this classifier
and meter that have been dropped because either the and meter that have been dropped because either the
meter always drops, or the queue's depth exceeds the meter always drops, or the queue's depth exceeds the
max-threshold value. This object should be used on max-threshold value. This object should be used on
high speed interfaces. high speed interfaces.
skipping to change at page 23, line 4 skipping to change at page 31, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets conforming to this classifier "The number of packets conforming to this classifier
and meter that have been dropped by a random drop and meter that have been dropped by a random drop
process because the queue is over-full. This object is process because the queue is over-full. This object is
used on high speed lines. used on high speed lines.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialization of the management system, and at
other times as indicated by the value of other times as indicated by the value of
Draft Differentiated Services MIB October 1999
ifCounterDiscontinuityTime." ifCounterDiscontinuityTime."
::= { diffServActionEntry 14 } ::= { diffServActionEntry 14 }
diffServActionStatus OBJECT-TYPE diffServActionStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, "The RowStatus variable controls the activation,
deactivation, or deletion of a meter. Any writable deactivation, or deletion of a meter. Any writable
variable may be modified whether the row is active or variable may be modified whether the row is active or
notInService." notInService."
::= { diffServActionEntry 15 } ::= { diffServActionEntry 15 }
Draft Differentiated Services MIB October 1999
-- This object allows a configuring system to obtain a -- This object allows a configuring system to obtain a
-- unique value for diffServQueueNumber for purposes of -- unique value for diffServQueueNumber for purposes of
-- configuration -- configuration
diffServQueueUnique OBJECT-TYPE diffServQueueUnique OBJECT-TYPE
SYNTAX TestAndIncr SYNTAX TestAndIncr
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The diffServQueueUnique object yields a unique new "The diffServQueueUnique object yields a unique new
value for diffServQueueNumber when read and value for diffServQueueNumber when read and
subsequently set. This value must be tested for subsequently set. This value must be tested for
uniqueness." uniqueness."
::= { diffServObjects 4 } ::= { diffServObjects 5 }
-- The Queue Table allows us to describe queues -- The Queue Table allows us to describe queues
diffServQueueTable OBJECT-TYPE diffServQueueTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiffServQueueEntry SYNTAX SEQUENCE OF DiffServQueueEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Queue Table enumerates the queues on an interface. "The Queue Table enumerates the queues on an interface.
Queues are used to store traffic during intervals when Queues are used to store traffic during intervals when
skipping to change at page 24, line 50 skipping to change at page 32, line 53
rate. When a maximum rate is specified, the queue acts rate. When a maximum rate is specified, the queue acts
as a shaper if it has sufficient traffic and capacity as a shaper if it has sufficient traffic and capacity
is available. If it is a minimum rate, then the weight is available. If it is a minimum rate, then the weight
in the WRR is effectively set to this rate divided by in the WRR is effectively set to this rate divided by
the sum of the rates of queues on the interface, the sum of the rates of queues on the interface,
guaranteeing it at least that throughput rate. If it is guaranteeing it at least that throughput rate. If it is
a maximum rate, the queue operates as a shaper. A a maximum rate, the queue operates as a shaper. A
shaper potentially reduces the rate of traffic through shaper potentially reduces the rate of traffic through
it to the indicated rate, and minimizes variations in it to the indicated rate, and minimizes variations in
rate." rate."
::= { diffServTables 5 } ::= { diffServTables 6 }
Draft Differentiated Services MIB October 1999
diffServQueueEntry OBJECT-TYPE diffServQueueEntry OBJECT-TYPE
SYNTAX DiffServQueueEntry SYNTAX DiffServQueueEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Queue Table describes a single FIFO "An entry in the Queue Table describes a single FIFO
queue." queue."
INDEX { ifIndex, diffServInterfaceDirection, INDEX { ifIndex, diffServInterfaceDirection,
diffServQueueNumber } diffServQueueNumber }
::= { diffServQueueTable 1 } ::= { diffServQueueTable 1 }
DiffServQueueEntry ::= SEQUENCE { DiffServQueueEntry ::= SEQUENCE {
diffServQueueNumber INTEGER, diffServQueueNumber INTEGER,
diffServQueueMinimumRate Unsigned32, diffServQueueMinimumRate Unsigned32,
diffServQueueMaximumRate Unsigned32, diffServQueueMaximumRate Unsigned32,
diffServQueuePriority Unsigned32, diffServQueuePriority Unsigned32,
diffServQueueNextTCB RowPointer, diffServQueueNextTCB RowPointer,
diffServQueueOccupancyWeight Unsigned32,
diffServQueueStatus RowStatus diffServQueueStatus RowStatus
} }
diffServQueueNumber OBJECT-TYPE diffServQueueNumber OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of the queue." "The number of the queue."
::= { diffServQueueEntry 1 } ::= { diffServQueueEntry 1 }
skipping to change at page 25, line 50 skipping to change at page 34, line 4
time of this writing which exceed the number of bits time of this writing which exceed the number of bits
per second which may be represented in a 32 bit number. per second which may be represented in a 32 bit number.
If the value is zero, then there is effectively no If the value is zero, then there is effectively no
minimum rate. If the value is non-zero, the queue set minimum rate. If the value is non-zero, the queue set
will seek to assure this class of traffic at least this will seek to assure this class of traffic at least this
rate." rate."
::= { diffServQueueEntry 2 } ::= { diffServQueueEntry 2 }
diffServQueueMaximumRate OBJECT-TYPE diffServQueueMaximumRate OBJECT-TYPE
Draft Differentiated Services MIB October 1999
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "KBPS" UNITS "KBPS"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The rate of the queue, in kilobits per second (KBPS). "The rate of the queue, in kilobits per second (KBPS).
This unit is chosen because interfaces exist at the This unit is chosen because interfaces exist at the
time of this writing which exceed the number of bits time of this writing which exceed the number of bits
per second which may be represented in a 32 bit number. per second which may be represented in a 32 bit number.
skipping to change at page 26, line 49 skipping to change at page 34, line 53
interface. Incoming traffic may use the value interface. Incoming traffic may use the value
zeroDotZero in this variable to indicate that the zeroDotZero in this variable to indicate that the
packet is now to be routed; outbound traffic may use packet is now to be routed; outbound traffic may use
the same value to indicate that no subsequent queuing the same value to indicate that no subsequent queuing
applies. Ingress interfaces generally use queuing applies. Ingress interfaces generally use queuing
either to divert routing traffic for speedier either to divert routing traffic for speedier
processing during a flap, or for shaping purposes." processing during a flap, or for shaping purposes."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { diffServQueueEntry 5 } ::= { diffServQueueEntry 5 }
diffServQueueOccupancyWeight OBJECT-TYPE
Draft Differentiated Services MIB October 1999
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The amount, in the form of a factor, that the current,
actual queue occupancy should influence the averaged
queue occupancy. The averaged queue occupancy can be
used for comparison to configured drop thresholds in
RED or RED-like dropper implementations. Larger the
weight, the greater the instantaneous queue occupancy
influences the averaged queue occupancy. Usually,
dramatic changes in the instantaneous queue occupancy
is the result of bursty input streams. Notice this
numeric attribute is divided by 10,000 to get the
effective fractional factor used in the actual
calculations."
::= { diffServQueueEntry 6 }
diffServQueueStatus OBJECT-TYPE diffServQueueStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable controls the activation, "The RowStatus variable controls the activation,
deactivation, or deletion of a queue. Any writable deactivation, or deletion of a queue. Any writable
variable may be modified whether the row is active or variable may be modified whether the row is active or
notInService." notInService."
::= { diffServQueueEntry 6 } ::= { diffServQueueEntry 7 }
Draft Differentiated Services MIB October 1999
-- MIB Compliance statements. Three variations of -- MIB Compliance statements. Three variations of
-- compliance are described, for optical, LAN, and low speed -- compliance are described, for optical, LAN, and low speed
-- interfaces. The difference is the implementation of -- interfaces. The difference is the implementation of
-- diffServActionHCConformingOctets -- diffServActionHCConformingOctets
-- and diffServActionHCConformingPackets -- and diffServActionHCConformingPackets
diffServMIBCompliances OBJECT IDENTIFIER ::= { diffServMIBConformance 1 } diffServMIBCompliances OBJECT IDENTIFIER ::= { diffServMIBConformance 1 }
diffServMIBGroups OBJECT IDENTIFIER ::= { diffServMIBConformance 2 } diffServMIBGroups OBJECT IDENTIFIER ::= { diffServMIBConformance 2 }
diffServMIBCompliance MODULE-COMPLIANCE diffServMIBCompliance MODULE-COMPLIANCE
skipping to change at page 29, line 4 skipping to change at page 37, line 4
GROUP diffServMIBHCCounterGroup GROUP diffServMIBHCCounterGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those network interfaces "This group is mandatory for those network interfaces
for which the value of the corresponding instance of for which the value of the corresponding instance of
ifSpeed is greater than 20,000,000 bits/second." ifSpeed is greater than 20,000,000 bits/second."
GROUP diffServMIBVHCCounterGroup GROUP diffServMIBVHCCounterGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those network interfaces "This group is mandatory for those network interfaces
Draft Differentiated Services MIB October 1999
for which the value of the corresponding instance of for which the value of the corresponding instance of
ifSpeed is greater than 650,000,000 bits/second." ifSpeed is greater than 650,000,000 bits/second."
OBJECT diffServClassifierMatchObject OBJECT diffServClassifierMatchObject
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServClassifierNext OBJECT diffServClassifierNext
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 30, line 4 skipping to change at page 38, line 4
OBJECT diffServTBMeterSucceedNext OBJECT diffServTBMeterSucceedNext
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServTBMeterStatus OBJECT diffServTBMeterStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
Draft Differentiated Services MIB October 1999
OBJECT diffServActionNext OBJECT diffServActionNext
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServActionDSCP OBJECT diffServActionDSCP
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 31, line 4 skipping to change at page 39, line 4
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServQueuePriority OBJECT diffServQueuePriority
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServQueueNextTCB OBJECT diffServQueueNextTCB
MIN-ACCESS read-only MIN-ACCESS read-only
Draft Differentiated Services MIB October 1999
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServQueueStatus OBJECT diffServQueueStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { diffServMIBCompliances 1 } ::= { diffServMIBCompliances 1 }
Draft Differentiated Services MIB October 1999
diffServMIBVHCCompliance MODULE-COMPLIANCE diffServMIBVHCCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This MIB may be implemented as a read-only or as a "This MIB may be implemented as a read-only or as a
read-create MIB. As a result, it may be used for read-create MIB. As a result, it may be used for
monitoring or for configuration. monitoring or for configuration.
Very High Speed compliance implies that the Very High Speed compliance implies that the
implementation complies for interfaces for which an implementation complies for interfaces for which an
interface's packet or octet counters might wrap more interface's packet or octet counters might wrap more
skipping to change at page 33, line 4 skipping to change at page 41, line 4
"Write access is not required." "Write access is not required."
OBJECT diffServClassifierStatus OBJECT diffServClassifierStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServTBMeterInterval OBJECT diffServTBMeterInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
Draft Differentiated Services MIB October 1999
"Write access is not required." "Write access is not required."
OBJECT diffServTBMeterBurstSize OBJECT diffServTBMeterBurstSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServTBMeterFailNext OBJECT diffServTBMeterFailNext
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 34, line 4 skipping to change at page 42, line 4
OBJECT diffServActionMaxThreshold OBJECT diffServActionMaxThreshold
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServActionDropPolicy OBJECT diffServActionDropPolicy
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
Draft Differentiated Services MIB October 1999
OBJECT diffServActionStatus OBJECT diffServActionStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServQueueMinimumRate OBJECT diffServQueueMinimumRate
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 35, line 4 skipping to change at page 43, line 4
OBJECT diffServQueueNextTCB OBJECT diffServQueueNextTCB
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServQueueStatus OBJECT diffServQueueStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { diffServMIBCompliances 2 } ::= { diffServMIBCompliances 2 }
Draft Differentiated Services MIB October 1999
diffServMIBHCCompliance MODULE-COMPLIANCE diffServMIBHCCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This MIB may be implemented as a read-only or as a "This MIB may be implemented as a read-only or as a
read-create MIB. As a result, it may be used for read-create MIB. As a result, it may be used for
monitoring or for configuration. monitoring or for configuration.
High Speed compliance implies that the implementation High Speed compliance implies that the implementation
complies for interfaces for which an interface's octet complies for interfaces for which an interface's octet
counters might wrap more than once an hour, which by counters might wrap more than once an hour, which by
skipping to change at page 36, line 4 skipping to change at page 44, line 4
"Write access is not required." "Write access is not required."
OBJECT diffServClassifierNext OBJECT diffServClassifierNext
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServClassifierSequence OBJECT diffServClassifierSequence
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
Draft Differentiated Services MIB October 1999
"Write access is not required." "Write access is not required."
OBJECT diffServClassifierStatus OBJECT diffServClassifierStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServTBMeterInterval OBJECT diffServTBMeterInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 37, line 4 skipping to change at page 45, line 4
OBJECT diffServActionDSCP OBJECT diffServActionDSCP
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServActionMinThreshold OBJECT diffServActionMinThreshold
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
Draft Differentiated Services MIB October 1999
OBJECT diffServActionMaxThreshold OBJECT diffServActionMaxThreshold
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServActionDropPolicy OBJECT diffServActionDropPolicy
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 38, line 4 skipping to change at page 46, line 4
OBJECT diffServQueueNextTCB OBJECT diffServQueueNextTCB
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT diffServQueueStatus OBJECT diffServQueueStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { diffServMIBCompliances 3 } ::= { diffServMIBCompliances 3 }
Draft Differentiated Services MIB October 1999
diffServMIBClassifierGroup OBJECT-GROUP diffServMIBClassifierGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServAggregateDSCP, diffServAggregateDSCP,
diffServClassifierMatchObject, diffServClassifierMatchObject,
diffServClassifierNext, diffServClassifierNext,
diffServClassifierSequence, diffServClassifierSequence,
diffServClassifierStatus diffServClassifierStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 39, line 4 skipping to change at page 47, line 4
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Action Group defines the objects used in "The Action Group defines the objects used in
describing an action." describing an action."
::= { diffServMIBGroups 3 } ::= { diffServMIBGroups 3 }
diffServMIBHCCounterGroup OBJECT-GROUP diffServMIBHCCounterGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServActionHCConformingOctets diffServActionHCConformingOctets
Draft Differentiated Services MIB October 1999
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"At 20,000,000 bits per second or greater, the number "At 20,000,000 bits per second or greater, the number
of octets a given class may count can overflow a 32 bit of octets a given class may count can overflow a 32 bit
counter in under an hour. Therefore, by convention counter in under an hour. Therefore, by convention
established in the IFMIB, the 64 bit counter must be established in the IFMIB, the 64 bit counter must be
implemented as well." implemented as well."
::= { diffServMIBGroups 4 } ::= { diffServMIBGroups 4 }
skipping to change at page 40, line 4 skipping to change at page 48, line 4
diffServMIBStaticGroup OBJECT-GROUP diffServMIBStaticGroup OBJECT-GROUP
OBJECTS { OBJECTS {
diffServClassifierUnique, diffServTBMeterUnique, diffServClassifierUnique, diffServTBMeterUnique,
diffServQueueUnique, diffServActionUnique diffServQueueUnique, diffServActionUnique
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Static Group contains scalar objects used in "The Static Group contains scalar objects used in
creating unique enumerations for classifiers, meters, creating unique enumerations for classifiers, meters,
Draft Differentiated Services MIB October 1999
and queues." and queues."
::= { diffServMIBGroups 7 } ::= { diffServMIBGroups 7 }
END END
Draft Differentiated Services MIB October 1999
5. Acknowledgments 5. Acknowledgments
This MIB has been developed with active involvement from a This MIB has been developed with active involvement from a
number of sources, but most notably Yoram Bernet, Steve Blake, number of sources, but most notably Yoram Bernet, Steve Blake,
Brian Carpenter, Kwok Chan, Dave Durham, Jeremy Greene, Roch Brian Carpenter, Kwok Chan, Dave Durham, Jeremy Greene, Roch
Guerin, Scott Hahn, Keith McCloghrie, Kathleen Nichols, Ping Guerin, Scott Hahn, Keith McCloghrie, Kathleen Nichols, Ping
Pan, Andrew Smith, and Bert Wijnen. Pan, Andrew Smith, and Bert Wijnen.
6. Security Considerations 6. Security Considerations
skipping to change at page 42, line 5 skipping to change at page 50, line 5
apply to a customer's ingress or egress traffic. There are no apply to a customer's ingress or egress traffic. There are no
objects which are sensitive in their own right, such as objects which are sensitive in their own right, such as
passwords or monetary amounts. passwords or monetary amounts.
It may be important to control even GET access to these It may be important to control even GET access to these
objects and possibly to even encrypt the values of these objects and possibly to even encrypt the values of these
object when sending them over the network via SNMP. Not all object when sending them over the network via SNMP. Not all
versions of SNMP provide features for such a secure versions of SNMP provide features for such a secure
environment. environment.
Draft Differentiated Services MIB October 1999
7. References 7. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An [1] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks", Architecture for Describing SNMP Management Frameworks",
RFC 2571, Cabletron Systems, Inc., BMC Software, Inc., RFC 2571, Cabletron Systems, Inc., BMC Software, Inc.,
IBM T. J. Watson Research, April 1999 IBM T. J. Watson Research, April 1999
[2] Rose, M., and K. McCloghrie, "Structure and [2] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP-based Identification of Management Information for TCP/IP-based
Internets", RFC 1155, STD 16, Performance Systems Internets", RFC 1155, STD 16, Performance Systems
skipping to change at page 43, line 4 skipping to change at page 51, line 4
SMIv2", RFC 2580, STD 58, Cisco Systems, SNMPinfo, TU SMIv2", RFC 2580, STD 58, Cisco Systems, SNMPinfo, TU
Braunschweig, SNMP Research, First Virtual Holdings, Braunschweig, SNMP Research, First Virtual Holdings,
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", RFC 1157, STD 15, "Simple Network Management Protocol", RFC 1157, STD 15,
SNMP Research, Performance Systems International, SNMP Research, Performance Systems International,
Performance Systems International, MIT Laboratory for Performance Systems International, MIT Laboratory for
Computer Science, May 1990. Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, SNMP "Introduction to Community-based SNMPv2", RFC 1901, SNMP
Draft Differentiated Services MIB October 1999
Research, Inc., Cisco Systems, Inc., Dover Beach Research, Inc., Cisco Systems, Inc., Dover Beach
Consulting, Inc., International Network Services, January Consulting, Inc., International Network Services, January
1996. 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Management Protocol (SNMPv2)", RFC 1906, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996. International Network Services, January 1996.
skipping to change at page 44, line 5 skipping to change at page 52, line 5
[16] Case, J., Mundy, R., Partain, D., and B. Stewart, [16] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard "Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, SNMP Research, Network Management Framework", RFC 2570, SNMP Research,
Inc., TIS Labs at Network Associates, Inc., Ericsson, Inc., TIS Labs at Network Associates, Inc., Ericsson,
[DSCP] [DSCP]
K. Nichols, S. Blake, F. Baker, D. Black, "Definition of K. Nichols, S. Blake, F. Baker, D. Black, "Definition of
the Differentiated Services Field (DS Field) in the IPv4 the Differentiated Services Field (DS Field) in the IPv4
and IPv6 Headers." RFC 2474, December 1998. and IPv6 Headers." RFC 2474, December 1998.
Draft Differentiated Services MIB October 1999
[Architecture] [Architecture]
S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W. S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W.
Weiss, "An Architecture for Differentiated Service." RFC Weiss, "An Architecture for Differentiated Service." RFC
2475, December 1998. 2475, December 1998.
[AF] J. Heinanen, F. Baker, W. Weiss, J. Wroclawski, "Assured [AF] J. Heinanen, F. Baker, W. Weiss, J. Wroclawski, "Assured
Forwarding PHB Group." RFC 2597, June 1999. Forwarding PHB Group." RFC 2597, June 1999.
[EF] V. Jacobson, K. Nichols, K. Poduri. "An Expedited [EF] V. Jacobson, K. Nichols, K. Poduri. "An Expedited
Forwarding PHB." RFC 2598, June 1999. Forwarding PHB." RFC 2598, June 1999.
[Model] [Model]
Bernet et al, "A Conceptual Model for Diffserv Routers", Bernet et al, "A Conceptual Model for Diffserv Routers",
06/25/1999, draft-ietf-diffserv-model-00.txt 06/25/1999, draft-ietf-diffserv-model-00.txt
[IFMIB] [IFMIB]
K. McCloghrie, F. Kastenholz. "The Interfaces Group MIB K. McCloghrie, F. Kastenholz. "The Interfaces Group MIB
using SMIv2", Request for Comments 2233, November 1997. using SMIv2", Request for Comments 2233, November 1997.
8. Author's Address: 8. Authors' Addresses:
Fred Baker Fred Baker
519 Lado Drive 519 Lado Drive
Santa Barbara, California 93111 Santa Barbara, California 93111
fred@cisco.com fred@cisco.com
Kwok Ho Chan
Nortel Networks
600 Technology Park Drive
Billerica, MA 01821
khchan@nortelnetworks.com
Andrew Smith
Extreme Networks
3585 Monroe Street
Santa Clara, CA 95051
USA
andrew@extremenetworks.com
 End of changes. 73 change blocks. 
57 lines changed or deleted 515 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/