draft-ietf-diffserv-pib-02.txt   draft-ietf-diffserv-pib-03.txt 
Network Working Group M. Fine Network Working Group M. Fine
Internet Draft K. McCloghrie Internet Draft K. McCloghrie
Expires May 2001 Cisco Systems Expires September 2001 Cisco Systems
J. Seligson J. Seligson
K. Chan K. Chan
Nortel Networks Nortel Networks
S. Hahn S. Hahn
C. Bell
Intel Intel
A. Smith A. Smith
Allegro Networks Allegro Networks
Francis Reichmeyer Francis Reichmeyer
IPHighway PFN
November 24, 2000 March 2, 2001
Differentiated Services Quality of Service Policy Information Base Differentiated Services Quality of Service Policy Information Base
draft-ietf-diffserv-pib-02.txt draft-ietf-diffserv-pib-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. Internet-Drafts are working provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as ``work in progress.'' or to cite them other than as ``work in progress.''
To view the current status of any Internet-Draft, please check the DiffServ QoS Policy Information Base February 2001
DiffServ QoS Policy Information Base November 2000
To view the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in an Internet-Drafts Shadow ``1id-abstracts.txt'' listing contained in an Internet-Drafts Shadow
Directory, see http://www.ietf.org/shadow.html. Directory, see http://www.ietf.org/shadow.html.
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
1. Glossary 1. Glossary
PRC Provisioning Class. A type of policy data. PRC Provisioning Class. A type of policy data.
PRI Provisioning Instance. An instance of a PRC. PRI Provisioning Instance. An instance of a PRC.
PIB Policy Information Base. The database of policy information. PIB Policy Information Base. The database of policy information.
PDP Policy Decision Point. See [RAP-FRAMEWORK]. PDP Policy Decision Point. See [RAP-FRAMEWORK].
PEP Policy Enforcement Point. See [RAP-FRAMEWORK]. PEP Policy Enforcement Point. See [RAP-FRAMEWORK].
PRID Provisioning Instance Identifier. Uniquely identifies an PRID Provisioning Instance Identifier. Uniquely identifies an
instance of a a PRC. instance of a a PRC.
skipping to change at page 4, line 5 skipping to change at page 4, line 5
3. Relationship to the Diffserv Informal Management Model 3. Relationship to the Diffserv Informal Management Model
This PIB is designed according to the Differentiated Services Informal This PIB is designed according to the Differentiated Services Informal
Management Model documented in [MODEL]. The model describes the way that Management Model documented in [MODEL]. The model describes the way that
ingress and egress interfaces of an 'n'-port router are modelled. It ingress and egress interfaces of an 'n'-port router are modelled. It
describes the configuration and management of a Diffserv interface in describes the configuration and management of a Diffserv interface in
terms of a Transmission Control Block (TCB) which contains, by terms of a Transmission Control Block (TCB) which contains, by
definition, zero or more classifiers, meters, actions, algorithmic definition, zero or more classifiers, meters, actions, algorithmic
droppers, queues and schedulers. These elements are arranged according droppers, queues and schedulers. These elements are arranged according
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
to the QoS policy being expressed, always in that order. Traffic may be to the QoS policy being expressed, always in that order. Traffic may be
classified; classified traffic may be metered; each stream of traffic classified; classified traffic may be metered; each stream of traffic
identified by a combination of classifiers and meters may have some set identified by a combination of classifiers and meters may have some set
of actions performed on it; it may have dropping algorithms applied and of actions performed on it; it may have dropping algorithms applied and
it may ultimately be stored into a queue before being scheduled out to it may ultimately be stored into a queue before being scheduled out to
its next destination, either onto a link or to another TCB. When the its next destination, either onto a link or to another TCB. When the
treatment for a given packet must have any of those elements repeated in treatment for a given packet must have any of those elements repeated in
a way that breaks the permitted sequence {classifier, meter, action, a way that breaks the permitted sequence {classifier, meter, action,
algorithmic dropper, queue, scheduler}, this must be modelled by algorithmic dropper, queue, scheduler}, this must be modelled by
skipping to change at page 4, line 31 skipping to change at page 4, line 31
algorithmic dropper, queue, scheduler or a decision to now forward a algorithmic dropper, queue, scheduler or a decision to now forward a
packet. packet.
The PIB models the individual elements that make up the TCBs. The The PIB models the individual elements that make up the TCBs. The
higher level concept of a TCB is not required in the parameterization or higher level concept of a TCB is not required in the parameterization or
in the linking together of the individual elements, hence it is not used in the linking together of the individual elements, hence it is not used
in the PIB itself and only mentioned in the text for relating the PIB in the PIB itself and only mentioned in the text for relating the PIB
with the [MODEL]. The actual distinguishing of which TCB a specific with the [MODEL]. The actual distinguishing of which TCB a specific
element is a part of is not needed for the instructmentation of a device element is a part of is not needed for the instructmentation of a device
to support the functionalities of DiffServ, but it is useful for to support the functionalities of DiffServ, but it is useful for
conceptual reasons. By not including the TCB notion in its parameters, conceptual reasons. By not using the TCB concept, this PIB allow any ]
this PIB allow any grouping of elements to construct TCBs, using rules grouping of elements to construct TCBs, using rules indicated by the
indicated by the [MODEL]. This will minimize changes to this PIB if [MODEL]. This will minimize changes to this PIB if rules in [MODEL]
rules in [MODEL] changes. change.
The notion of a Data Path is used in this PIB to indicate the DiffServ The notion of a Data Path is used in this PIB to indicate the DiffServ
processing a packet may experience. This Data Path is distinguished processing a packet may experience. This Data Path is distinguished
based on the Role Combination and the Direction of the flow the packet based on the Role Combination and the Direction of the flow the packet
is part of. A Data Path Table Entry indicates the first of possibly is part of. A Data Path Table Entry indicates the first of possibly
multiple elements that will apply DiffServ treatment to the packet. multiple elements that will apply DiffServ treatment to the packet.
3.1. PIB Overview 3.1. PIB Overview
This PIB is structured based on the need to configure the sequential This PIB is structured based on the need to configure the sequential
DiffServ treatments being applied to a packet, and the parameterization DiffServ treatments being applied to a packet, and the parameterization
of these treatments. These two aspects of the configuration are kept of these treatments. These two aspects of the configuration are kept
separate throughout the design of the PIB, and are fulfilled using separate throughout the design of the PIB, and are fulfilled using
separate tables and data definitions. separate tables and data definitions.
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
In addition, the PIB includes tables describing the capabilities and In addition, the PIB includes tables describing the capabilities and
limitations of the device using a general extensible framework. These limitations of the device using a general extensible framework. These
tables are reported to the PDP and assist the PDP with the configuration tables are reported to the PDP and assist the PDP with the configuration
of functional elements that can be realized by the device. of functional elements that can be realized by the device.
In this PIB, the ingress and egress portions of a router are configured In this PIB, the ingress and egress portions of a router are configured
independently but in the same manner. The difference is distinguished by independently but in the same manner. The difference is distinguished by
an attribute in a table describing the start of the data path. Each an attribute in a table describing the start of the data path. Each
interface performs some or all of the following high-level functions: interface performs some or all of the following high-level functions:
skipping to change at page 5, line 33 skipping to change at page 5, line 33
appropriate drop policy and marking of the traffic with a appropriate drop policy and marking of the traffic with a
Differentiated Services Code Point (DSCP) as defined in [DSFIELD]. Differentiated Services Code Point (DSCP) as defined in [DSFIELD].
o Enqueue the traffic for output in the appropriate queue, whose o Enqueue the traffic for output in the appropriate queue, whose
scheduler may shape the traffic or simply forward it with some scheduler may shape the traffic or simply forward it with some
minimum rate or maximum latency. minimum rate or maximum latency.
The PIB therefore contains the following elements: The PIB therefore contains the following elements:
Data Path Table Data Path Table
A general extensible framework for describing the starting point of This describes the starting point of DiffServ data paths within a
DiffServ datapaths within a single DiffServ device. This table single DiffServ device. This table descibes interface role
descibes interface role combination and interface direction combination
specific data paths. and interface direction specific data paths.
Classifier Tables Classifier Tables
A general extensible framework for specifying a group of filters. A general extensible framework for specifying a group of filters.
Meter Tables Meter Tables
A general extensible framework and one example of a A general extensible framework and one example of a
parameterization table - TBMeter table, applicable for Simple Token parameterization table - TBParam table, applicable for Simple Token
Bucket Meter, Average Rate Meter, Single Rate Three Color Meter, Bucket Meter, Average Rate Meter, Single Rate Three Color Meter,
Two Rate Three Color Meter, and Sliding Window Three Color Meter. Two Rate Three Color Meter, and Sliding Window Three Color Meter.
Action Tables Action Tables
A general extensible framework and examples of parameterization A general extensible framework and examples of parameterization
tables for Absolute Drop, Mark and Count actions. The tables for Absolute Drop, Mark and Count actions. The
"multiplexer", "replicator" and "null" actions described in [MODEL] "multiplexer" and "null" actions described in [MODEL] are
are accomplished implicitly by means of the RowPointer structures accomplished implicitly by means of the Prid structures
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
of the other elements. of the other elements.
Queue, Scheduler and Algorithmic Dropper Tables Queue, Scheduler and Algorithmic Dropper Tables
A general extensible framework for parameterizing queuing and A general extensible framework for parameterizing queuing and
scheduler systems. The queue measurement dependent algorithmic scheduler systems. The queue measurement dependent algorithmic
droppers are also described here. droppers are also described here.
Capabilities Tables Capabilities Tables
A general extensible framework for defining the capabilities and A general extensible framework for defining the capabilities and
skipping to change at page 7, line 5 skipping to change at page 7, line 5
functional datapath element allows the elements to be ordered in any functional datapath element allows the elements to be ordered in any
way. way.
4.2. DiffServ Data Paths 4.2. DiffServ Data Paths
This part of the PIB provides instrumentation for connecting the This part of the PIB provides instrumentation for connecting the
DiffServ Functional Elements within a single DiffServ device. Please DiffServ Functional Elements within a single DiffServ device. Please
refer to the [MODEL] for discussions on the valid sequencing and refer to the [MODEL] for discussions on the valid sequencing and
grouping of DiffServ Functional Elements. Given some basic information, grouping of DiffServ Functional Elements. Given some basic information,
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
e.g. the interface role combination and direction, the first DiffServ e.g. the interface role combination and direction, the first DiffServ
Functional Element is determined. Subsequent DiffServ Functional Functional Element is determined. Subsequent DiffServ Functional
Elements are provided by the "Next" pointer attribute of each entry of Elements are provided by the "Next" pointer attribute of each entry of
data path tables. A description of how this "Next" pointer is used in data path tables. A description of how this "Next" pointer is used in
each table is provided in their respective sections. each table is provided in their respective DESCRIPTION clauses.
4.2.1. Data Path PRC 4.2.1. Data Path PRC
The Data Path PRC provides the DiffServ treatment starting points for The Data Path PRC provides the DiffServ treatment starting points for
all packets of this DiffServ device. Each instance of this PRC specifies all packets of this DiffServ device. Each instance of this PRC specifies
the interface role combination and direction for the packet flow. There the interface type, role combination and direction for the packet flow.
should be at most two entries for each role combination, one for ingress There should be at most two entries for each (interface type, role
and one for egress. Each instance provides the first DiffServ combination) pair, one for ingress and one for egress. Each instance
Functional Element each packet at a specific interface (identified by provides the first DiffServ Functional Element each packet at a specific
the roles assigned to the interface) traveling in a specific relative interface (identified by the roles assigned to the interface) traveling
direction should experience. Notice this table is interface specific, in a specific relative direction should experience. Notice this table
with the use of RoleCombination. To indicate explicitly that there are is interface specific, with the use of interface type and
no Diffserv treatments for a particular role combination and direction, RoleCombination. To indicate explicitly that there are no Diffserv
an instance of the Data Path PRC can be created with zeroDotZero in the treatments for a particular interface type, role combination and
qosDataPathStart attribute. This situation can also be indicated direction, an instance of the Data Path PRC can be created with
implicitly by not supplying an instance of a Data Path PRC for that zeroDotZero in the qosDataPathStart attribute. This situation can also
particular role combination and direction. The explicit/implicit be indicated implicitly by not supplying an instance of a Data Path PRC
selection is up to the implementation. This means that the PEP should for that particular interface type, role combination and direction. The
perform normal IP device processing when zeroDotZero is used in the explicit/implicit selection is up to the implementation. This means
qosDataPathStart attribute, or when the entry does not exist. Normal IP that the PEP should perform normal IP device processing when zeroDotZero
device processing will depend on the device, for example, this can be is used in the qosDataPathStart attribute, or when the entry does not
forwarding the packet. exist. Normal IP device processing will depend on the device, for
example, this can be forwarding the packet.
4.3. Classifiers 4.3. Classifiers
The classifier and classifier element tables determine how traffic is The classifier and classifier element tables determine how traffic is
sorted out. They identify separable classes of traffic, by reference to sorted out. They identify separable classes of traffic, by reference to
appropriate filters, which may select anything from an individual micro- appropriate filters, which may select anything from an individual micro-
flow to aggregates identified by DSCP. flow to aggregates identified by DSCP.
The classification is used to send these separate streams to appropriate The classification is used to send these separate streams to appropriate
Meter, Action, Queue, Scheduler and Algorithmic Dropper elements. For Meter, Action, Algorithmic Dropper, Queue and Scheduler elements. For
example, to indicate a multi-stage meter, sub-classes of traffic may be example, to indicate a multi-stage meter, sub-classes of traffic may be
sent to different meter stages: e.g. in an implementation of the Assured sent to different meter stages: e.g. in an implementation of the Assured
Forwarding (AF) PHB [AF-PHB], AF11 traffic might be sent to the first Forwarding (AF) PHB [AF-PHB], AF11 traffic might be sent to the first
meter, AF12 traffic might be sent to the second and AF13 traffic sent to
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
meter, AF12 traffic might be sent to the second and AF13 traffic sent to
the second meter stage's out-of-profile action. the second meter stage's out-of-profile action.
The concept of a classifier is the same as described in [MODEL]. The The concept of a classifier is the same as described in [MODEL]. The
structure of the classifier and classifier element tables, is the same structure of the classifier and classifier element tables, is the same
as the classifier described in [MODEL]. Classifier elements have an as the classifier described in [MODEL]. Classifier elements have an
associated precedence order solely for the purpose of resolving associated precedence order solely for the purpose of resolving
ambiguity between overlapping filters. Filter with higher values of ambiguity between overlapping filters. Filter with higher values of
order are compared first; the order of tests for entries of the same order are compared first; the order of tests for entries of the same
precedence is unimportant. precedence is unimportant.
skipping to change at page 8, line 36 skipping to change at page 8, line 37
necessarily deterministic - see [MODEL] section 4.1.2. necessarily deterministic - see [MODEL] section 4.1.2.
The definition of the actual filter to be used by the classifier is The definition of the actual filter to be used by the classifier is
referenced via a Prid: this enables the use of any sort of filter table referenced via a Prid: this enables the use of any sort of filter table
that one might wish to design, standard or proprietary. No filters are that one might wish to design, standard or proprietary. No filters are
defined in this PIB. However, standard filters for IP packets are defined in this PIB. However, standard filters for IP packets are
defined in the Framework PIB [FR-PIB]. defined in the Framework PIB [FR-PIB].
4.3.1. Classifier PRC 4.3.1. Classifier PRC
Classifiers are organized by instances of the Classifier PRC. Each Classifiers, used in various ingress and egress interfaces, are
instance corresponds to a single Classifier. Instances of the organized by the instances of the Classifier PRC. A data path entry
Classifier PRC get linked from the upstream diffserv functional datapath points to a classifier entry. A classifier entry identifies a list of
element, e.g., a qosDataPathentry instance. A data path may consist of classifier elements. A classifier element effectively includes the
more than one Classifier, and the order in which the classifiers are filter entry, and points to a "next" classifier entry or other data path
applied to the traffic is the same as the order the classifier table functional element.
entries are linked in the data path.
4.3.2. Classifier Element PRC 4.3.2. Classifier Element PRC
While the Classifier PRC specifies the input side of the Classifier, the Classifier elements point to the filters which identify various classes
Classifier Element PRC enumerates each branch of the fan-out of a of traffic. The separation between the "classifier element" and the
"filter" allows us to use many different kinds of filters with the same
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
Classifier, associating each fan-out branch with a Filter for essential semantics of "an identified set of traffic". The traffic
discriminating the traffic for that branch. Each Classifier Element PRI matching the filter corresponding to a classifier element is given to
is part of a Classifier, indicated by qosClfrElementClfrId. the "next" data path functional element identified in the classifier
element.
The definition of the actual filter to be used by the classifier is The definition of the actual filter to be used by the classifier is
referenced via a Prid: this enables the use of any sort of filter table referenced via a Prid: this enables the use of any sort of filter table
that one might wish to design, standard or proprietary. An example of a that one might wish to design, standard or proprietary. An example of a
filter that may be pointed to by a Classifier Element PRI is the filter that may be pointed to by a Classifier Element PRI is the
frwkIpFilter PRC, defined in [FR-PIB]. frwkIpFilter PRC, defined in [FR-PIB].
4.4. Meters 4.4. Meters
A meter, according to [MODEL] section 5, measures the rate at which A meter, according to [MODEL] section 5, measures the rate at which
packets making up a stream of traffic pass it, compares this rate to packets making up a stream of traffic pass it, compares this rate to
some set of thresholds and produces some number (two or more) of some set of thresholds and produces some number (two or more) of
potential results. A given packet is said to "conform" to the meter if, potential results. A given packet is said to "conform" to the meter if,
at the time that the packet is being looked at, the stream appears to be at the time that the packet is being looked at, the stream appears to be
within the meter's profile. PIB syntax makes it easiest to define this within the meter's profile. PIB syntax makes it easiest to define this
as a sequence of one or more cascaded pass/fail tests, modeled here as as a sequence of one or more cascaded pass/fail tests, modeled here as
if-then-else constructs. It is important to understand that this way of if-then-else constructs. It is important to understand that this way of
modelling does not imply anything about the implementation being modelling does not imply anything about the implementation being
"sequential": multi-rate/multi-profile meters e.g. those designed to "sequential": multi-rate/multi-profile meters e.g. those designed to
support [SRTCM] or [TRTCM], can still be modelled this way even if they, support [SRTCM], [TRTCM], or [TSWTCM] can still be modeled this way even
of necessity, share information between the stages: the stages are if they, of necessity, share information between the stages: the stages
introduced merely as a notational convenience in order to simplify the are introduced merely as a notational convenience in order to simplify
PIB structure. the PIB structure.
4.4.1. Meter PRC 4.4.1. Meter PRC
The generic meter PRC is used as a base for all more specific forms of The generic meter PRC is used as a base for all more specific forms of
meter. The definition of parameters specific to the type of meter used meter. The definition of parameters specific to the type of meter used
is referenced via a pointer to an instance of a PRC containing those is referenced via a pointer to an instance of a PRC containing those
specifics. This enables the use of any sort of specific meter table specifics. This enables the use of any sort of specific meter table
that one might wish to design, standard or proprietary. The specific that one might wish to design, standard or proprietary. The specific
meter table may be, but does not need to be, defined in this PIB module. meter table may be, but does not need to be, defined in this PIB module.
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
4.4.2. Token-Bucket Meter PRC 4.4.2. Token-Bucket Parameter PRC
This is included as an example of a common type of meter. Entries in This is included as an example of a common type of meter. Entries in
this table are referenced from the qosMeterSpecific attributes of meter this table are referenced from the qosMeterSpecific attributes of meter
PRC instances. The parameters are represented by a rate qosTBMeterRate, PRC instances. The parameters are represented by a rate qosTBParamRate,
a burst size qosTBMeterBurstSize, and an interval qosTBMeterInterval. a burst size qosTBParamBurstSize, and an interval qosTBparamInterval.
The type of meter being parameterized is indicated by the qosTBMeterType The type of meter being parameterized is indicated by the qosTBParamType
attribute. This is used to determine how the rate, burst and rate attribute. This is used to determine how the rate, burst and rate
interval parameters are used. Additional meter parameterization classes interval parameters are used. Additional meter parameterization classes
can be defined in this or another PIB when necessary. can be defined in this or another PIB when necessary.
4.5. Actions 4.5. Actions
Actions include "no action", "mark the traffic with a DSCP" or "drop the Actions include "no action", "mark the traffic with a DSCP" or "drop the
traffic". Other tasks such as "shape the traffic" or "drop based on some traffic". Other tasks such as "shape the traffic" or "drop based on some
algorithm" are handled elsewhere as queueing mechanisms, rather than algorithm" are handled elsewhere as queueing mechanisms, rather than
actions, consistent with [MODEL]. The "multiplexer", "replicator" and actions, consistent with [MODEL]. The "multiplexer", "replicator" and
skipping to change at page 11, line 5 skipping to change at page 11, line 5
allows for the use of proprietary Actions without impact on those allows for the use of proprietary Actions without impact on those
defined here. defined here.
There is one action - the absolute drop action - that does not require There is one action - the absolute drop action - that does not require
additional parameters. This action silently discards all traffic additional parameters. This action silently discards all traffic
presented to it. To accommodate this action, the qosAction PRC contains presented to it. To accommodate this action, the qosAction PRC contains
an attribute, qosActionType, that indicates whether the absolute drop an attribute, qosActionType, that indicates whether the absolute drop
action is to be used or if the action is described by a specific action action is to be used or if the action is described by a specific action
table. table.
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
4.5.1. DSCP Mark Action PRC 4.5.1. DSCP Mark Action PRC
This Action is applied to traffic in order to mark it with a Diffserv This Action is applied to traffic in order to mark it with a Diffserv
Codepoint (DSCP) value, specified in the qosDscpMarkActTable. Other Codepoint (DSCP) value, specified in the qosDscpMarkActTable. Other
marking actions might be specified elsewhere - these are outside the marking actions might be specified elsewhere - these are outside the
scope of this PIB. scope of this PIB.
4.5.2. Absolute Drop Action 4.5.2. Absolute Drop Action
This action just silently discards all traffic presented to it. This This action just silently discards all traffic presented to it. This
action has no additional parameters and so is represented only within action has no additional parameters and so is represented only within
diffServActionType without its specific table. qosActionType without its specific table.
4.6. Queueing Elements 4.6. Queueing Elements
These include Algorithmic Droppers, Queues and Schedulers which are all These include Algorithmic Droppers, Queues and Schedulers which are all
inter-related in their use of queueing techniques. inter-related in their use of queueing techniques.
4.6.1. Algorithmic Dropper PRC 4.6.1. Algorithmic Dropper PRC
Algorithmic Droppers have a close relationship with queueing: they are Algorithmic Droppers are represented in this PIB by instances of the
represented in this PIB by instances of an Algorithmic Dropper PRC. Algorithmic Dropper PRC. An Algorithmic Dropper is assumed to operate
Entries contain a qosAlgDropNext attribute which indicates to which indiscriminately on all packets that are presented at its input, all
queue they sink their traffic. traffic separation should be done by classifiers and meters preceding
it.
An Algorithmic Dropper is assumed to operate indiscriminately on all Algorithmic Droppers have a close relationship with queuing, each
packets that are presented at its input. If it is necessary to perform Algorithmic Dropper Table entry contains a qosAlgDropQMeasure attribute,
additional classification on the stream then a separate TCB must be indicating which queue's state affects the calculation of the
introduced at this point: Classifier elements here can then distinguish Algorithmic Dropper. Each entry also contains a qosAlgDropNext
the different types of traffic on which dropping is to act and the attribute which indicates to which queue the Algorithmic Dropper sinks
treatment for each type is described by a separate qosAlgDropEntry. its traffic.
Algorithmic Droppers may also contain a pointer to specific detail of Algorithmic Droppers may also contain a pointer to specific detail of
the drop algorithm. This PIB defines the detail for three drop the drop algorithm, qosAlgDropSpecific. This PIB defines the detail for
algorithms: Tail Drop, Head Drop and Random Drop; other algorithms are three drop algorithms: Tail Drop, Head Drop and Random Drop; other
outside the scope of this PIB modele but the general framework is algorithms are outside the scope of this PIB module but the general
intended to allow for their inclusion via other PIB modules. framework is intended to allow for their inclusion via other PIB
modules.
DiffServ QoS Policy Information Base February 2001
One generally-applicable parameter of a dropper is the specification of One generally-applicable parameter of a dropper is the specification of
a queue-depth threshold at which some drop action is to start. This is a queue-depth threshold at which some drop action is to start. This is
represented in this PIB, as a base attribute, qosAlgDropQThreshold, of
DiffServ QoS Policy Information Base November 2000 the Algorithmic Dropper entry. The attribute, qosAlgDropQMeasure,
specifies which queue's depth qosAlgDropQThreshold is to compare
represented in this PIB, as a base attribute of the Algorithmic Dropper against.
entry, by pointing to the queue for which depth is to be compared and
the depth threshold to compare against.
o A Tail Dropper requires the specification of a maximum queue depth o A Tail Dropper requires the specification of a maximum queue depth
threshold: when the queue pointed at by diffServAlgDropQMeasure threshold: when the queue pointed at by qosAlgDropQMeasure
reaches that depth threshold, qosAlgDropQThresh, any new reaches that depth threshold, qosAlgDropQThresh, any new
traffic arriving at the dropper is discarded. This algorithm uses traffic arriving at the dropper is discarded. This algorithm uses
only parameters that are part of the qosAlgDropEntry. only parameters that are part of the qosAlgDropEntry.
o A Head Dropper requires the specification of a maximum queue depth o A Head Dropper requires the specification of a maximum queue depth
threshold: when the queue pointed at by qosAlgDropQMeasure threshold: when the queue pointed at by qosAlgDropQMeasure
reaches that depth threshold, qosAlgDropQThresh, traffic reaches that depth threshold, qosAlgDropQThresh, traffic
currently at the head of the queue is discarded. This algorithm currently at the head of the queue is discarded. This algorithm
uses only parameters that are part of the qosAlgDropEntry. uses only parameters that are part of the qosAlgDropEntry.
skipping to change at page 12, line 36 skipping to change at page 12, line 39
communicate with TCP-like protocols about congestion avoidance, but communicate with TCP-like protocols about congestion avoidance, but
differ markedly on their specific parameters. This PIB attempts to differ markedly on their specific parameters. This PIB attempts to
offer a minimal set of controls for any random dropper, but expects offer a minimal set of controls for any random dropper, but expects
that vendors will augment the PRC with additional controls and that vendors will augment the PRC with additional controls and
status in accordance with their implementation. This algorithm status in accordance with their implementation. This algorithm
requires additional parameters on top of those in requires additional parameters on top of those in
qosAlgDropEntry; these are discussed below. qosAlgDropEntry; these are discussed below.
4.6.2. Random Dropper PRC 4.6.2. Random Dropper PRC
One example of a random dropper is a RED-like dropper. An example of One example of a random dropper is a RED-like dropper. An example of the
the representation chosen in this PIB for this element is shown in representation chosen in this PIB for this element is shown in Figure 1.
Figure 1.
Random droppers often have their drop probability function described as Random droppers often have their drop probability function described as
a plot of drop probability (P) against averaged queue length (Q). a plot of drop probability (P) against averaged queue length (Q).
(Qmin,Pmin) then defines the start of the characteristic plot. Normally (Qmin,Pmin) then defines the start of the characteristic plot. Normally
Pmin=0, meaning with average queue length below Qmin, there will be no Pmin=0, meaning with average queue length below Qmin, there will be no
drops. (Qmax,Pmax) defines a "knee" on the plot, after which point the drops. (Qmax,Pmax) defines a "knee" on the plot, after which point the
drop probability become more progressive (greater slope). (Qclip,1) drop probability become more progressive (greater slope). (Qclip,1)
defines the queue length at which all packets will be dropped. Notice defines the queue length at which all packets will be dropped. Notice
this is different from Tail Drop because this uses an averaged queue
length. although it is possible for Qclip = Qmax. In the PIB module,
DiffServ QoS Policy Information Base November 2000
qosRandomDropMinThreshBytes and qosRandomDropMinThreshPkts represent DiffServ QoS Policy Information Base February 2001
Qmin. qosRandomDropMaxThreshBytes and qosRandomDropMaxThreshPkts
represent Qmax.
+-------------+ +-----------+
--->| Next --------+-->| Next ---------> to Scheduler
| Thresh=100k | | | Min=none |
| Measure -------+ | Max=none |
| Type=random | | Pri=10 |
| Specif -------+ | Type=fifo |
+-------------+ | +-----------+
AlgDrop.3 | Queue.4
|
| +--------------+
+-->| Minthresh=10k|
| Maxthresh=80k|
| Weight=1/16 |
| ProbMax= 0.5 |
+--------------+
RandomDrop.3
Figure 1: Example Use of the RandomDropTable for Random Droppers this is different from Tail Drop because this uses an averaged queue
length. Although it is possible for Qclip = Qmax.
qosRandomDropProbMax represents Pmax. This PIB does not represent Pmin In the PIB module, qosRandomDropMinThreshBytes and
(assumed to be zero unless otherwise represented) or Qclip (assumed to qosRandomDropMinThreshPkts represent Qmin. qosRandomDropMaxThreshBytes
be Qmax unless otherwise represented). and qosRandomDropMaxThreshPkts represent Qmax. qosAlgDropQThreshold
represents Qclip. qosRandomDropProbMax represents Pmax. This PIB does
not represent Pmin (assumed to be zero unless otherwise represented).
In addition, since message memory is finite, queues generally have some
upper bound above which they are incapable of storing additional
traffic. Normally this number is equal to Qclip, specified by
qosAlgDropQThreshold.
Each random dropper specification is associated with a queue. This Each random dropper specification is associated with a queue. This
allows multiple drop processes (of same or different types) be allows multiple drop processes (of same or different types) to be
associated with the same queue, as different PHB implementations may associated with the same queue, as different PHB implementations may
require. This also allows for sequences of multiple droppers if require. This also allows for sequences of multiple droppers if
necessary. necessary.
AlgDrop Queue
+-----------------+ +-------+
--->| Next ---------+--+------------------->| Next -+--> ...
| QMeasure -------+--+ | ... |
| QThreshold | RandomDrop +-------+
| Type=randomDrop | +----------------+
| Specific -------+---->| MinThreshBytes |
+-----------------+ | MaxThreshBytes |
| ProbMax |
| InvWeight |
| SamplingRate |
+----------------+
Figure 1: Example Use of the RandomDropTable for Random Droppers
The calculation of a smoothed queue length may also have an important The calculation of a smoothed queue length may also have an important
bearing on the behaviour of the dropper: parameters may include the bearing on the behavior of the dropper: parameters may include the
sampling interval and the weight of each sample. The performance may be sampling interval or rate, and the weight of each sample. The
very sensitive to the values of these parameters and a wide range of performance may be very sensitive to the values of these parameters and
possible values may be required due to a wide range of link speeds. Most a wide range of possible values may be required due to a wide range of
algorithms include a sample weight, represented here by link speeds. Most algorithms include a sample weight, represented here
qosRandomDropInvWeight. Note however that there is ongoing research on by qosRandomDropInvWeight. The availability of
this topic, see e.g. [ACTQMGMT]. qosRandomDropSamplingRate as readable is important, the information
provided by Sampling Rate is essential to the configuration of
Additional parameters may be added in an enterprise PIB module, e.g. by DiffServ QoS Policy Information Base February 2001
DiffServ QoS Policy Information Base November 2000 qosRandomDropInvWeight. Having Sampling Rate be configurable is also
helpful, as line speed increases, the ability to have queue sampling be
less frequent than packet arrival is needed. Note however that there is
ongoing research on this topic, see e.g. [ACTQMGMT] and [AQMROUTER].
using AUGMENTS or EXTENDS on this table, to handle aspects of random Additional parameters may be added in an enterprise PIB module, e.g. by
drop algorithms that are not standardised here. using AUGMENTS on this table, to handle aspects of random drop
algorithms that are not standardized here.
NOTE: Deterministic Droppers can be viewed as a special case of Random NOTE: Deterministic Droppers can be viewed as a special case of Random
Droppers with the drop probability restricted to 0 and 1. Hence Droppers with the drop probability restricted to 0 and 1. Hence
Deterministic Droppers might be described by a Random Dropper with Pmin Deterministic Droppers might be described by a Random Dropper with Pmin
= 0, Pmax = 1, Qmin = Qmax = Qclip, the averaged queue length at which = 0, Pmax = 1, Qmin = Qmax = Qclip, the averaged queue length at which
dropping occurs. dropping occurs.
4.6.3. Queues and Schedulers 4.6.3. Queues and Schedulers
The Queue PRC models simple FIFO queues, as described in [MODEL] section The Queue PRC models simple FIFO queues, as described in [MODEL] section
skipping to change at page 14, line 32 skipping to change at page 14, line 38
more complex hierarchies can be constructed that way also. more complex hierarchies can be constructed that way also.
Queue PRC instances are pointed at by the "next" attributes of the Queue PRC instances are pointed at by the "next" attributes of the
upstream elements e.g. qosMeterSucceedNext. Note that multiple upstream upstream elements e.g. qosMeterSucceedNext. Note that multiple upstream
elements may direct their traffic to the same Queue PRI. For example, elements may direct their traffic to the same Queue PRI. For example,
the Assured Forwarding PHB suggests that all traffic marked AF11, AF12 the Assured Forwarding PHB suggests that all traffic marked AF11, AF12
or AF13 be placed in the same queue, after metering, without reordering. or AF13 be placed in the same queue, after metering, without reordering.
This would be represented by having the qosMeterSucceedNext of each This would be represented by having the qosMeterSucceedNext of each
upstream meter point at the same Queue PRI. upstream meter point at the same Queue PRI.
NOTE: Queue and Scheduler PRIs are for data path description, they both
use Scheduler Parameterization Table entries for diffserv treatment
parameterization.
Queue Table entries specify the scheduler it wants service from by use Queue Table entries specify the scheduler it wants service from by use
of its Next pointer. of its Next pointer.
Each Scheduler Table entry represents the algorithm in use for servicing Each Scheduler Table entry represents the algorithm in use for servicing
the one or more queues that feed it. The [MODEL] section 7.1.2 describes the one or more queues that feed it. The [MODEL] section 7.1.2 describes
a scheduler with multiple inputs: this is represented in the PIB by a scheduler with multiple inputs: this is represented in the PIB by
having the scheduling parameters be associated with each input. In this having the scheduling parameters be associated with each input. In this
way, sets of Queues can be grouped together as inputs to the same way, sets of Queues can be grouped together as inputs to the same
DiffServ QoS Policy Information Base February 2001
Scheduler. This table serves to represent the example scheduler Scheduler. This table serves to represent the example scheduler
described in the [MODEL]: other more complex representations might be described in the [MODEL]: other more complex representations might be
created outside of this PIB. created outside of this PIB.
Both the Queue PRC and the Scheduler PRC use instances of the Scheduler Both the Queue PRC and the Scheduler PRC use instances of the Scheduler
Parameterization PRC to specify diffserv treatment parameterization. Parameterization PRC to specify diffserv treatment parameterization.
Scheduler Parameter PRC instances are used to parameterize each input Scheduler Parameter PRC instances are used to parameterize each input
that feeds into a scheduler. The inputs can be a mixture of Queue PRI's that feeds into a scheduler. The inputs can be a mixture of Queue PRI's
and Scheduler PRI's. Scheduler Parameter PRI's can be used/reused by and Scheduler PRI's. Scheduler Parameter PRI's can be used/reused by
one or more Queue and/or Scheduler Table entries. one or more Queue and/or Scheduler Table entries.
DiffServ QoS Policy Information Base November 2000
For representing a Strict Priority scheduler, each scheduler input is For representing a Strict Priority scheduler, each scheduler input is
assigned a priority with respect to all the other inputs feeding the assigned a priority with respect to all the other inputs feeding the
same scheduler, with default values for the other parameters. A higher- same scheduler, with default values for the other parameters. A higher-
priority input will be serviced first over a lower-priority input, priority input which contains traffic that is not being delayed for
assuming that all guarantees have already been met. shaping will be serviced before a lower-priority input.
For Weighted Queueing algorithms e.g. WFQ, WRR, the "weight" of a given For Weighted Queuing methods e.g. WFQ, WRR, the "weight" of a given
scheduler input is represented with a Minimum Service Rate leaky-bucket scheduler input is represented with a Minimum Service Rate leaky-bucket
profile which provides guaranteed bandwidth to that input, if required. profile which provides guaranteed minimum bandwidth to that input, if
This is represented, as were token-bucket meters, by a rate required. This is represented by a rate qosAssuredRateAbs; the
qosSchdParamMinRateAbs. The rate may, alternatively, be represented by a classical weight is the ratio between that rate and the interface speed,
or perhaps the ratio between that rate and the sum of the configured
rates for classes. The rate may, alternatively, be represented by a
relative value, as a fraction of the interface's current line rate, relative value, as a fraction of the interface's current line rate,
qosSchdParamMinRateRel to assist in cases where line rates are variable qosAssuredRateRel to assist in cases where line rates are variable or
or where a higher-level policy might be expressed in terms of fractions where a higher-level policy might be expressed in terms of fractions of
of network resources. The two rate parameters are inter- related and network resources. The two rate parameters are inter-related and
changes in one may be reflected in the other. changes in one may be reflected in the other.
An input may also be capable of acting as a non-work-conserving [MODEL] For weighted scheduling methods, one can say loosely, that WRR focuses
traffic shaper: this is done by defining a Maximum Service Rate leaky- on meeting bandwidth sharing, without concern for relative delay amongst
bucket profile in order to limit the scheduler bandwidth available to the queues; where WFQ control both queue service order and amount of
that input. This is represented, similarly to the minimum rate, by a traffic serviced, providing meeting bandwidth sharing and relative delay
rate qosSchdParamMaxRateAbs. The rate may, alternatively, be represented ordering amongst the queues.
by a relative value, as a fraction of the interface's current line rate,
qosSchdParamMaxRateRel.
Notice hierarchical schedulers can be parameterized using these PRC's by A queue or scheduled set of queues (which is an input to a scheduler)
having Scheduler PRI's feed into other Scheduler PRI's. may also be capable of acting as a non-work-conserving [MODEL] traffic
shaper: this is done by defining a Maximum Service Rate leaky-bucket
profile in order to limit the scheduler bandwidth available to that
input. This is represented by a rate qosShapingRateAbs; the classical
weight is the ratio between that rate and the interface speed, or
perhaps the ratio between that rate and the sum of the configured rates
for classes. The rate may, alternatively, be represented by a relative
value, as a fraction of the interface's current line rate,
DiffServ QoS Policy Information Base February 2001
qosShapingRateRel. There was discussion in the working group about
alternative modeling approaches, such as defining a shaping action or a
shaping element. We did not take this approach because shaping is in
fact something a scheduler does to its inputs, (which we model as a
queue with a maximum rate or a scheduler whose output has a maximum
rate) and we felt it was simpler and more elegant to simply describe it
in that context.
Other types of priority and weighted scheduling methods can be defined
using existing parameters in qosAssuredRateEntry. NOTE:
qosSchedulerMethod uses OBJECT IDENTIFIER syntax, with the different
types of scheduling methods defined as OBJECT-IDENTITY. Future
scheduling methods may be defined in other MIBs. This requires an
OBJECT-IDENTITY definition, a description of how the existing objects
are reused, if they are, and any new objects they require.
NOTE: hierarchical schedulers can be parameterized using this PIB by
having Scheduler Table entries feeds into Scheduler Table entry.
4.7. Specifying Device Capabilities 4.7. Specifying Device Capabilities
The Diffserv PIB uses the Base PRC classes frwkPrcSupportTable and The Diffserv PIB uses the Base PRC classes frwkPrcSupportTable and
frwkCompLimitsTable defined in [FR-PIB] to specify what PRC's are frwkCompLimitsTable defined in [FR-PIB] to specify what PRC's are
supported by a PEP and to specify any limitations on that support. The supported by a PEP and to specify any limitations on that support. The
PIB also uses the capability PRC's frwkIfCapSetTable and PIB also uses the capability PRC's frwkIfCapSetTable and
frwkIfCapSetRoleComboTable defined in [FR-PIB] to specify the device's frwkIfCapSetRoleComboTable defined in [FR-PIB] to specify the device's
interface types and role combinations. Each instance of the capability interface types and role combinations. Each instance of the capability
PRC frwkIfCapSetTable contains an OID that points to an instance of a PRC frwkIfCapSetTable contains an OID that points to an instance of a
PRC that describes some capability of that interface type. The Diffserv PRC that describes some capability of that interface type. The Diffserv
PIB defines several of these capability PRC's, which assist the PDP with PIB defines several of these capability PRCs, which assist the PDP with
the configuration of Diffserv functional elements that can be the configuration of Diffserv functional elements that can be
implemented by the device. implemented by the device. Each of these capability PRCs contains a
direction attribute that specifies the direction for which the
capability applies. This attribute is defined in a base capability PRC,
which is extended by each specific capability PRC.
DiffServ QoS Policy Information Base November 2000 Classification capabilities, which specify the information elements the
device can use to classify traffic, are reported using the
qosIfClassificationCaps PRC. Metering capabilities, which indicate what
the device can do with out-of-profile packets, are specified using the
qosIfMeteringCaps PRC. Scheduling capabilities, such as the number of
inputs supported, are reported using the qosIfSchedulingCaps PRC.
Classification capabilities, such as which directions (ingress or egress DiffServ QoS Policy Information Base February 2001
support IP classification and whether the interface is capable of
classifying on layer 4 information, are reported using Algorithmic drop capabilities, such as the types of algorithms
qosIfClassificationCapsTable. Metering capabilities, such as which supported, are reported using the qosIfAlgDropCaps PRC. Queue
directions support metering, are specified using qosIfMeteringCapsTable. capabilities, such as the maximum number of queues, are reported using
Scheduling capabilities, such as the maximum number of queues and the qosIfQueueCaps PRC. Shaper capabilities, such as the number of
priorities supported, are reported using qosIfSchedulingCapsTable. rates supported, are reported using the qosIfShaperCaps table.
Two PRC's are defined to allow specification of the element linkage Two PRC's are defined to allow specification of the element linkage
capabilities of the PEP. The qosIfElmDepthCaps PRC indicates the capabilities of the PEP. The qosIfElmDepthCaps PRC indicates the
maximum number of functional datapath elements that can be linked maximum number of functional datapath elements that can be linked
consecutively in a datapath. The qosIfElmLinkCaps PRC indicates what consecutively in a datapath. The qosIfElmLinkCaps PRC indicates what
functional datapath elements are may follow a specific type of element functional datapath elements are may follow a specific type of element
in a datapath. in a datapath.
The capability reporting classes in the DiffServ and Framework PIB are
meant to allow the PEP to indicate some general guidelines about what
the device can do. They are intended to be an aid to the PDP when it
constructs policy for the PEP. These classes do not necessarily allow
the PEP to indicate every possible configuration that it can or cannot
support. If a PEP receives a policy that it cannot implement, it must
notify the PDP with a failure report.
5. PIB Usage Example 5. PIB Usage Example
This section provides some examples on how the different table entries This section provides some examples on how the different table entries
of this PIB may be used to parameterize a DiffServ Device. For the of this PIB may be used together for a Diffserv Device, with the usage
figures, all the PRC and attribute names are assumed to have the PRC of each individual attribute be defined within the PIB module itself.
(table entry) name as the common initial part of the name. For the figures, all the PIB table entry and attribute names are assumed
to have "qos" as their first common initial part of name, with the table
entry name assumed to be their second common initial part of name.
"0.0" is being used to mean zeroDotZero. And for Scheduler Method "= X"
means "using the OID of qoxSchedulerX".
5.1. Model's Example
As an example, when this PIB's structures are used for the hypothetical
configuration in [MODEL] section 8.1, the result is shown in Figure 2,
3, and 4. The parameterization table entries' values are not specified
in detail here, they can be obtained from [MODEL] section 8.1.
DiffServ QoS Policy Information Base February 2001
+---------------------+ +------------------------> Q_EF
|DataPath | |
| IfCapSet="If1" | |
| Roles = "A+B" | | +--------------+
| IfDirection=Ingress | +------+ | +--->|Action |
| Start --------------+--->|Clfr | | | | Id=EF2 |
+---------------------+ | Id=1 | | | | Next=0.0 |
+------+ | | | Specific=0.0 |
| | | Type=AbsDrop |
| | +--------------+
| |
| |
| |
+------------+ +--------------+ | |
|ClfrElement | +-->|Meter | | |
| Id=EF | | | Id=EF | | |
| ClfrId=1 | | | SucceedNext -+-+ |
| Order=NA | | | FailNext ----+----+
| Next ------+--+ | Specific -+ |
| Specific --+-+ +-----------+--+
+------------+ | |
| |
| |
| +--------+ | +---------+
+-->|FilterEF| +-->|TBMeterEF|
+--------+ +---------+
+------------+ +--------------+
|ClfrElement | +-------------------->|AlgDrop |
| Id=AF11 | | | Id=AF11 |
| ClfrId=1 | | | Type=tailDrop|
| Order=NA | | | Next --------+--+-> Q_AF1
| Next ------+--+ | QMeasure ----+--+
| Specific --+-+ | QThreshold |
+------------+ | | Specific=0.0 |
| +--------------+
|
| +----------+
+->|FilterAF11|
+----------+
Figure 2: Example from Model Section 8.1 part 1
DiffServ QoS Policy Information Base February 2001
+------------+ +--------------+
|ClfrElement | +-->|Meter |
| Id=AF21 | | | Id=AF21 |
| ClfrId=1 | | | SucceedNext -+----------> Q_AF2
| Order=NA | | | FailNext + |
| Next ------+--+ | Specific --+ |
| Specific --+-+ +----------+-+-+
+------------+ | | |
| | |
| | |
| +----------+ | | +-----------+
+->|FilterAF21| | +->|TBMeterAF21|
+----------+ | +-----------+
|
-----+
|
| +-----------+
+->|Action |
| Id=AF21F2 |
| Next -----+------> Q_AF2
| Specific -+-+
| Type=Spcf | |
+-----------+ |
|
| +---------------+
+->|DscpMarkActAF22|
+---------------+
+------------+
|ClfrElement | +-----------------------------------------> Q_BE
| Id=WildCard| |
| ClfrId=1 | |
| Order=NA | |
| Next ------+--+ +--------------+
| Specific --+------>|FilterMatchAll|
+------------+ +--------------+
Figure 3: Example from Model Section 8.1 part 2
+-------------+
Q_EF--->|Q |
| Id=EF +--+--------------------------+
| Next ----+ | +-----------+ |
DiffServ QoS Policy Information Base February 2001
| SchdParam --+-->|SchdParamEF| |
+-------------+ +-----------+ |
|
+-------------+ | +----------------+
Q_AF1-->|Q | +->|Scheduler |
| Id=AF1 +--+--------------------------+ | Id=Diffserv |
| Next ----+ | +------------+ | | Next=0.0 |
| SchdParam --+-->|SchdParamAF1| | | Method=Priority|
+-------------+ +------------+ | | SchdParam=0.0 |
| +----------------+
+-------------+ |
Q_AF2-->|Q | |
| Id=AF2 +--+--------------------------+
| Next ----+ | +------------+ |
| SchdParam --+-->|SchdParamAF2| |
+-------------+ +------------+ |
|
+-------------+ |
Q_BE--->|Q | |
| Id=BE +--+--------------------------+
| Next ----+ | +-----------+
| SchdParam --+-->|SchdParamBE|
+-------------+ +-----------+
Figure 4: Example from Model Section 8.1 part 3
5.2. Additional Data Path Example
5.2.1. Data Path and Classifier Example Discussion
The example in Figure 5 shows a single qosDataPathTable entry feeding
into a single Classifier entry, with three Classifier Element and Filter
Table entry pairs belonging to this Classifier 1. Notice the three
Filters used here must completely classify all the traffic presented to
this data path.
Another level of classification can be defined that follows the Action
functional DataPath elements in Figure 5. This multi-level
classification allow the construction of traffic separations and
specific actions at each level, like:
if (dept1) then take dept1-action
{
if (appl1) then take dept1-appl1-action.
DiffServ QoS Policy Information Base February 2001
if (appl2) then take dept1-appl2-action.
if (appl3) then take dept1-appl3-action.
}
if (dept2) then take dept2-action
{
if (appl1) then take dept2-appl1-action.
if (appl2) then take dept2-appl2-action.
if (appl3) then take dept2-appl3-action.
}
if (dept3) then take dept3-action
{
if (appl1) then take dept3-appl1-action.
if (appl2) then take dept3-appl2-action.
if (appl3) then take dept3-appl3-action.
}
Minimally, the filters for appl1, appl2, appl3 may be reused for the
above setup.
+---------------------+ +---------------------+
|DataPath | |DataPath |
| IfCapSet="If1" |
| Roles="A+B" | | Roles="A+B" |
| IfDirection=Ingress | +------+ | IfDirection=Ingress | +------+
| Start --------------+--->|Clfr | | Start --------------+--->|Clfr |
+---------------------+ | Id=1 | +---------------------+ | Id=1 |
+------+ +------+
+------------+ +--------------+ +-----------+ +------------+ +--------------+
|ClfrElement | +-->|Meter | +-->|Action | |ClfrElement | +-->|Meter |
| Id=101 | | | Id=101 | | | Id=101 | | Id=101 | | | Id=101 |
| ClfrId=1 | | | SucceedNext -+--+ | Next -----+---->... | ClfrId=1 | | | SucceedNext -+--->...
| Order=NA | | | FailNext ----+->... | Specific -+-+ | Order=NA | | | FailNext ----+--->...
| Next ------+--+ | Specific -+ | | Type=Spcf | | | Next ------+--+ | Specific -+ |
| Specific --+-+ +-----------+--+ +-----------+ | | Specific --+-+ +-----------+--+
+------------+ | | +-------+ +------------+ | |
| +-------+ | +--------+ | +------------+ | +-------+ | +--------+
+-->|Filter1| +-->|TBMeter1| +-->|DscpMarkAct1| +-->|Filter1| +-->|TBMeter1|
+-------+ +--------+ +------------+ +-------+ +--------+
DiffServ QoS Policy Information Base November 2000
+------------+ +--------------+ +-----------+ +------------+ +--------------+
|ClfrElement | +-->|Meter | +-->|Action | |ClfrElement | +-->|Meter |
| Id=102 | | | Id=102 | | | Id=102 | | Id=102 | | | Id=102 |
| ClfrId=1 | | | SucceedNext -+--+ | Next -----+---->...
| Order=NA | | | FailNext ----+->... | Specific -+-+
| Next ------+--+ | Specific -+ | | Type=Spcf | |
| Specific --+-+ +-----------+--+ +-----------+ |
+------------+ | | +-------+
| +-------+ | +--------+ | +------------+
+-->|Filter2| +-->|TBMeter2| +-->|DscpMarkAct2|
+-------+ +--------+ +------------+
+------------+ +--------------+ +-----------+ DiffServ QoS Policy Information Base February 2001
|ClfrElement | +-->|Meter | +-->|Action |
| Id=103 | | | Id=103 | | | Id=103 |
| ClfrId=1 | | | SucceedNext -+--+ | Next -----+---->...
| Order=NA | | | FailNext ----+->... | Specific -+-+
| Next ------+--+ | Specific -+ | | Type=Spcf | |
| Specific --+-+ +-----------+--+ +-----------+ |
+------------+ | | +-------+
| +-------+ | +--------+ | +------------+
+-->|Filter3| +-->|TBMeter3| +-->|DscpMarkAct3|
+-------+ +--------+ +------------+
Figure 3: Data Path Example Part 1 | ClfrId=1 | | | SucceedNext -+->...
| Order=NA | | | FailNext ----+->...
| Next ------+--+ | Specific -+ |
| Specific --+-+ +-----------+--+
+------------+ | |
| +-------+ | +--------+
+-->|Filter2| +-->|TBMeter2|
+-------+ +--------+
+-------------+ +------------------+ +----------------------+ +------------+ +--------------+
| Id=EF | | | Id=DiffServ | | | Id=Shaping | |ClfrElement | +-->|Meter |
| Next -------+---+ | Next ------------+--+ | Next=zeroDotZero | | Id=103 | | | Id=103 |
| SchdParam -+| | | Method=priorityq | | Method=priorityq | | ClfrId=1 | | | SucceedNext -+->...
+------------++ | | SchdParam -+ | | SchdParam=zeroDotZero| | Order=NA | | | FailNext ----+->...
| | +------------+-----+ +----------------------+ | Next ------+--+ | Specific -+ |
| Specific --+-+ +-----------+--+
+------------+ | | +------------+ | |
| | +------------+ | +-------+ | +--------+
| +-----------+ | | +-->|Filter3| +-->|TBMeter3|
+->|SchdParamEF| | | +----------------+ +-------+ +--------+
+-----------+ | +->|SchdParamShaping|
| +----------------+
|
|
+-----------------------------------------+
|
|
DiffServ QoS Policy Information Base November 2000 Figure 5: Additional Data Path Example Part 1
+-------------+ +-----------------+
---->|Q | +->|Scheduler |
| Id=EF | | | Id=Diffserv |
| Next -------+-----------------------+ | Next=0.0 |
| SchdParam -+| | | Method=Priority |
+------------++ | | SchdParam=0.0 |
| | +-----------------+
+------------+ |
| |
| +-----------+ |
+->|SchdParamEF| |
+-----------+ +---------------------+
|
+----------------+ +-------------+ | +----------------+ +-------------+ |
--->|AlgDrop | +->|Q | | --->|AlgDrop | +->|Q | |
| Id=AF11 | | | Id=AF1X | +-------------+ | | Id=AF11 | | | Id=AF1 | +-------------+ |
| Type=randomDrop| | | Next -------+--->|Scheduler | | | Type=randomDrop| | | Next -------+--->|Scheduler | |
| Next ----------+-+--+ | SchdParam -+| | Id=AF | | | Next ----------+-+--+ | SchdParam -+| | Id=AF | |
| QMeasure ------+-+ | +------------++ | Next -------+--+ | QMeasure ------+-+ | +------------++ | Next -------+--+
| QThreshold | | | | Method=wfq | | QThreshold | | | | Method=WFQ |
| Specific -+ | | +------------+ | SchdParam -+| | Specific -+ | | +------------+ | SchdParam --+--+
+-----------+----+ | | +------------++
| | | +-------------+ | DiffServ QoS Policy Information Base February 2001
+-----------+ | +->|SchdParamAF1X| +------------+
| +--------------+ | +-------------+ | +-----------+----+ | | +-------------+ |
| | | +------------+ |
+-----------+ | +->|SchdParamAF1| +----------------+
| +--------------+ | +------------+ |
+->|RandomDropAF11| | | +-----------+ +->|RandomDropAF11| | | +-----------+
+--------------+ | +->|SchdParamAF| +--------------+ | +->|SchdParamAF|
| +-----------+ | +-----------+
+----------------+ | +----------------+ |
--->|AlgDrop | | --->|AlgDrop | |
| Id=AF12 | | | Id=AF12 | |
| Type=randomDrop| | | Type=randomDrop| |
| Next ----------+-+--+ | Next ----------+-+--+
| QMeasure ------+-+ | QMeasure ------+-+
| QThreshold | | QThreshold |
| Specific -+ | | Specific -+ |
+-----------+----+ +-----------+----+
| |
+-----------+ +-----------+
| +--------------+ | +--------------+
+->|RandomDropAF12| +->|RandomDropAF12|
+--------------+ +--------------+
Figure 4: Data Path Example Part 2 Figure 6: Additional Data Path Example Part 2
5.1. Data Path and Classifier Example Discussion
The example in Figure 4 shows a single DataPathEntry PRI feeding into a
single Classifier PRI, with three ClfrElement and Filter PRI pairs
belonging to this Classifier 1. Notice the three Filters used here must
completely classify all the traffic presented to this data path.
Another level of classification can be defined that follows the Action
function datapath elements in Figure 3. This second level of
classifiers and their subsequent function datapath elements would be
considered as in another TCB.
DiffServ QoS Policy Information Base November 2000
This multi-level classification allow the construction of traffic
separations like:
if (dept1)
{
if (appl1) then take dept1-appl1-action.
if (appl2) then take dept1-appl2-action.
if (appl3) then take dept1-appl3-action.
}
if (dept2)
{
if (appl1) then take dept2-appl1-action.
if (appl2) then take dept2-appl2-action.
if (appl3) then take dept2-appl3-action.
}
if (dept3)
{
if (appl1) then take dept3-appl1-action.
if (appl2) then take dept3-appl2-action.
if (appl3) then take dept3-appl3-action.
}
The filters for appl1, appl2, appl3 may be reused for the above setup.
5.2. Meter and Action Example Discussion 5.2.2. Meter and Action Example Discussion
A simple Meter that can be parameterized by a single TBMeter entry is A simple Meter that can be parameterized by a single TBMeter entry is
shown here. For Metering types that require mutliple TBMeter entries shown here. For Metering types that require multiple TBMeter entries
for parameterization, a second level Meter and TBMeter table entries may for parameterization, a second level Meter and TBMeter table entries may
be used. For example, for trTCM, with the first level TBMeter entry be used. For example, for [TRTCM], with the first level TBMeter entry
used for Peak Information Token Bucket, the first level SucceedNext used for Peak Information Token Bucket, the first level SucceedNext
points to the second level Meter entry, with second level TBMeter entry points to the second level Meter entry, with second level TBMeter entry
used for Committed Information Token Bucket. used for Committed Information Token Bucket.
5.3. Queue and Scheduler Example Discussion 5.2.3. Queue and Scheduler Example Discussion
Example in Figure 4 shows three classified input traffic streams, EF, Example in Figure 6 shows three classified input traffic streams, EF,
AF11, and AF12, feeding into their respective queue and algorithmic AF11, and AF12, feeding into their respective queue and algorithmic
droppers. After their respective dropping process, the AF traffic droppers. After their respective dropping process, the AF traffic
streams feed into the same queue, QAF1X. streams feed into the same queue, QAF1X.
A Scheduler, AF, is shown in Figure 4, as the sink for AF1X queue A Scheduler, AF, is shown in Figure 6, as the sink for AF1X queue
traffic, servicing AF1X queue with scheduling parameters indicated by
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
traffic, servicing AF1X queue with scheduling parameters indicated by
SchdParamAF1X. This scheduler is used to service traffic from AF1X, SchdParamAF1X. This scheduler is used to service traffic from AF1X,
AF2X, AF3X queues using weighted fair queueing method. The AF2X and AF2X, AF3X queues using weighted fair queuing method. The AF2X and AF3X
AF3X queues are not shown in Figure 4, they can be very much like AF1X queues are not shown in Figure 6, they can be very much like AF1X queue
queue setup. setup.
Another traffic stream, EF, is handled by the EF queue. Scheduler Another traffic stream, EF, is handled by the EF queue. Scheduler
DiffServ services output of EF queue using SchdParamEF, and output of AF Diffserv services output of EF queue using SchdParamEF, and output of AF
scheduler using SchdParamAF, with Weighted Fair Queueing method. scheduler using SchdParamAF, with Priority Queue scheduling method.
Notice all the diffserv traffic may go out on a link with traffic Notice all the diffserv traffic may go out on a link with traffic
shaping. The traffic shaping can be parameterize using the Shaping shaping. The traffic shaping can be parameterize using the Shaping
Scheduler in Figure 4. For shaping, the qosSchdParamMaxRate attributes | Scheduler in Figure 6. For shaping, the qosShapingRate attributes
should be used. The output of the Shaping Scheduler is indicated using should be used. The Shaping Scheduler is indicated as the last diffserv
its Next pointer with value of zeroDotZero, the output port. functional element of this data path by using its Next pointer with
value of zeroDotZero.
6. Summary of the DiffServ PIB 6. Summary of the DiffServ PIB
The DiffServ PIB consists of one module containing the base PRCs for The DiffServ PIB consists of one module containing the base PRCs for
setting DiffServ policy, queues, classifiers, meters, etc., and also setting DiffServ policy, queues, classifiers, meters, etc., and also
contains capability PRC's that allow a PEP to specify its device contains capability PRC's that allow a PEP to specify its device
characteristics to the PDP. This module contains two groups, which are characteristics to the PDP. This module contains two groups, which are
summarized in this section. summarized in this section.
QoS Capabilities Group QoS Capabilities Group
skipping to change at page 21, line 5 skipping to change at page 25, line 5
with individual interfaces on the device. with individual interfaces on the device.
QoS Policy Group QoS Policy Group
This group contains configuration of the functonal elements that This group contains configuration of the functonal elements that
comprise the QoS policy that applies to an interface and the comprise the QoS policy that applies to an interface and the
specific parameters that describe those elements. This group specific parameters that describe those elements. This group
contains classifiers, meters, actions, droppers, queues and contains classifiers, meters, actions, droppers, queues and
schedulers. This group also contains the PRC that associates the schedulers. This group also contains the PRC that associates the
datapath elements with role combinations. datapath elements with role combinations.
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
7. PIB Operational Overview 7. PIB Operational Overview
This section provides an operation overview of configuring DiffServ QoS This section provides an operation overview of configuring DiffServ QoS
policy. policy.
After initial PEP to PDP communication setup, using [COPS-PR] for After initial PEP to PDP communication setup, using [COPS-PR] for
example, the PEP will provide to the PDP the PIB Provisioning Classes example, the PEP will provide to the PDP the PIB Provisioning Classes
(PRCs), interface types, and interface type capabilities it supports. (PRCs), interface types, and interface type capabilities it supports.
skipping to change at page 22, line 5 skipping to change at page 26, line 5
qosIfElmOutputCapsTable, or in a table defined in another PIB. qosIfElmOutputCapsTable, or in a table defined in another PIB.
The PDP, with knowledge of the PEP's capabilities, then provides the PEP The PDP, with knowledge of the PEP's capabilities, then provides the PEP
with administration domain and interface-specific policy information. with administration domain and interface-specific policy information.
Instances of the qosDataPathTable are used to specify the first element Instances of the qosDataPathTable are used to specify the first element
in the set of functional elements applied to an interface. Each in the set of functional elements applied to an interface. Each
instance of the qosDataPathTable applies to an interface type defined by instance of the qosDataPathTable applies to an interface type defined by
its roles and direction (ingress or egress). its roles and direction (ingress or egress).
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
8. PIB Definitions 8. PIB Definitions
8.1. The DiffServ Base PIB 8.1. The DiffServ Base PIB
DIFFSERV-PIB PIB-DEFINITIONS ::= BEGIN DIFFSERV-PIB PIB-DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Unsigned32, Integer32, Unsigned32, Integer32,
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM COPS-PR-SPPI FROM COPS-PR-SPPI
zeroDotZero zeroDotZero
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue, TEXTUAL-CONVENTION TruthValue, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
InstanceId, ReferenceId, TagId, TagReference InstanceId, ReferenceId, TagId, TagReference
FROM COPS-PR-SPPI FROM COPS-PR-SPPI
RoleCombination RoleCombination
FROM FRAMEWORK-PIB FROM FRAMEWORK-PIB
Dscp, IfDirection Dscp
FROM DIFFSERV-DSCP-TC;
IfDirection
FROM DIFF-SERV-MIB; FROM DIFF-SERV-MIB;
BurstSize
FROM INTEGRATED-SERVICES-MIB;
qosPolicyPib MODULE-IDENTITY qosPolicyPib MODULE-IDENTITY
CLIENT-TYPE { tbd -- QoS Client Type SUBJECT-CATEGORIES { tbd -- QoS Client Type
} }
LAST-UPDATED "200011241800Z" LAST-UPDATED "200103021800Z"
ORGANIZATION "IETF DIFFSERV WG" ORGANIZATION "IETF DIFFSERV WG"
CONTACT-INFO " CONTACT-INFO "
Michael Fine Michael Fine
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 USA San Jose, CA 95134-1706 USA
Phone: +1 408 527 8218 Phone: +1 408 527 8218
Email: mfine@cisco.com Email: mfine@cisco.com
Keith McCloghrie Keith McCloghrie
DiffServ QoS Policy Information Base February 2001
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive, 170 West Tasman Drive,
San Jose, CA 95134-1706 USA San Jose, CA 95134-1706 USA
Phone: +1 408 526 5260 Phone: +1 408 526 5260
DiffServ QoS Policy Information Base November 2000
Email: kzm@cisco.com Email: kzm@cisco.com
John Seligson John Seligson
Nortel Networks, Inc. Nortel Networks, Inc.
4401 Great America Parkway 4401 Great America Parkway
Santa Clara, CA 95054 USA Santa Clara, CA 95054 USA
Phone: +1 408 495 2992 Phone: +1 408 495 2992
Email: jseligso@nortelnetworks.com" Email: jseligso@nortelnetworks.com"
DESCRIPTION DESCRIPTION
"The PIB module containing a set of policy rule classes "The PIB module containing a set of provisioning classes
that describe quality of service (QoS) policies for that describe quality of service (QoS) policies for
DiffServ. It includes general classes that may be extended DiffServ. It includes general classes that may be extended
by other PIB specifications as well as a set of PIB by other PIB specifications as well as a set of PIB
classes related to IP processing." classes related to IP processing."
::= { tbd } ::= { tbd }
qosCapabilityClasses OBJECT IDENTIFIER ::= { qosPolicyPib 1 } qosCapabilityClasses OBJECT IDENTIFIER ::= { qosPolicyPib 1 }
qosPolicyClasses OBJECT IDENTIFIER ::= { qosPolicyPib 2 } qosPolicyClasses OBJECT IDENTIFIER ::= { qosPolicyPib 2 }
qosPolicyParameters OBJECT IDENTIFIER ::= { qosPolicyPib 3 }
-- --
-- Interface Capabilities Group -- Interface Capabilities Group
-- --
-- --
-- Interface Type Capability Tables -- Interface Type Capability Tables
-- --
-- The Interface type capability tables define capabilities that may -- The Interface type capability tables define capabilities that may
-- be associated with an interface of a specific type. This PIB -- be associated with an interface of a specific type. This PIB
-- defines three such tables: a classification capabilities table, a -- defines three such tables: a classification capabilities table, a
-- metering capabilities table and a scheduling capabilities table. -- metering capabilities table and a scheduling capabilities table.
-- Other PIBs may define other capability tables to augment the -- Other PIBs may define other capability tables to augment the
-- capability definitions of these tables or to introduce completely -- capability definitions of these tables or to introduce completely
-- new capabilities. -- new capabilities.
-- --
DiffServ QoS Policy Information Base February 2001
-- Classification Capabilities -- Classification Capabilities
-- --
DiffServ QoS Policy Information Base November 2000 --
-- The Base Capability Table
--
qosBaseIfCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosBaseIfCapsEntry
PIB-ACCESS notify, 3
STATUS current
DESCRIPTION
"The Base Interface Capability class. This class represents
a generic capability supported by a device in the ingress,
egress or both directions."
::= { qosCapabilityClasses 1 }
qosBaseIfCapsEntry OBJECT-TYPE
SYNTAX QosBaseIfCapsEntry
STATUS current
DESCRIPTION
"An instance of this class describes the qosBaseIfCaps class."
PIB-INDEX { qosBaseIfCapsPrid }
QosBaseIfCapsEntry ::= SEQUENCE {
qosBaseIfCapsPrid InstanceId,
qosBaseIfCapsDirection Integer32
}
qosBaseIfCapsPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { qosBaseIfCapsEntry 1 }
qosBaseIfCapsDirection OBJECT-TYPE
SYNTAX Integer32 {
inbound(1),
outbound(2),
DiffServ QoS Policy Information Base February 2001
inAndOut(3)
}
STATUS current
DESCRIPTION
"This object specifies the direction(s) for which the capability
applies. A value of 'inbound(1)' means the capability applies
only to the ingress direction. A value of 'outbound(2)' means
the capability applies only to the egress direction. A value of
'inAndOut(3)' means the capability applies to both directions."
::= { qosBaseIfCapsEntry 2 }
--
-- The Classification Capability Table
--
qosIfClassificationCapsTable OBJECT-TYPE qosIfClassificationCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfClassificationCapsEntry SYNTAX SEQUENCE OF QosIfClassificationCapsEntry
PIB-ACCESS notify, 3 PIB-ACCESS notify, 2
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the classification capabilities of an "This table specifies the classification capabilities of an
interface type" interface type"
::= { qosCapabilityClasses 1 } ::= { qosCapabilityClasses 2 }
qosIfClassificationCapsEntry OBJECT-TYPE qosIfClassificationCapsEntry OBJECT-TYPE
SYNTAX QosIfClassificationEntry SYNTAX QosIfClassificationEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of this class describes the classification "An instance of this class describes the classification
capabilities of an interface." capabilities of an interface."
PIB-INDEX { qosIfClassificationCapsPrid } EXTENDS { qosBaseIfCapsEntry }
UNIQUENESS { qosIfClassificationCapsSpec } UNIQUENESS { qosBaseIfCapsDirection,
qosIfClassificationCapsSpec }
::= { qosIfClassificationCapsTable 1 } ::= { qosIfClassificationCapsTable 1 }
QosIfClassificationCapsEntry ::= SEQUENCE { QosIfClassificationCapsEntry ::= SEQUENCE {
qosIfClassificationCapsPrid InstanceId,
qosIfClassificationCapsSpec BITS qosIfClassificationCapsSpec BITS
} }
qosIfClassificationCapsPrid OBJECT-TYPE DiffServ QoS Policy Information Base February 2001
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { qosIfClassificationCapsEntry 1 }
qosIfClassificationCapsSpec OBJECT-TYPE qosIfClassificationCapsSpec OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
inputIpClassification(1), ipSrcAddrClassification(1),
outputIpClassification(2),
-- Indicates the ability to classify IP
-- packets on ingress and on egress,
-- respectively.
DiffServ QoS Policy Information Base November 2000
ipSrcAddrClassification(3),
-- indicates the ability to classify based on -- indicates the ability to classify based on
-- IP source addresses -- IP source addresses
ipDstAddrClassification(4), ipDstAddrClassification(2),
-- indicates the ability to classify based on -- indicates the ability to classify based on
-- IP destination addresses -- IP destination addresses
ipProtoClassification(5), ipProtoClassification(3),
-- indicates the ability to classify based on -- indicates the ability to classify based on
-- IP protocol numbers -- IP protocol numbers
ipDscpClassification(6) ipDscpClassification(4)
-- indicates the ability to classify based on -- indicates the ability to classify based on
-- IP DSCP -- IP DSCP
ipL4Classification(7) ipL4Classification(5)
-- indicates the ability to classify based on -- indicates the ability to classify based on
-- IP layer 4 port numbers for UDP and TCP -- IP layer 4 port numbers for UDP and TCP
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Bit set of supported classification capabilities. In "Bit set of supported classification capabilities. In
addition to these capabilities, other PIBs may define other addition to these capabilities, other PIBs may define other
capabilities that can then be specified in addition to the capabilities that can then be specified in addition to the
ones specified here (or instead of the ones specified here if ones specified here (or instead of the ones specified here if
none of these are specified)." none of these are specified)."
::= { qosIfClassificationCapsEntry 2 } ::= { qosIfClassificationCapsEntry 1 }
-- --
-- Metering Capabilities -- Metering Capabilities
-- --
qosIfMeteringCapsTable OBJECT-TYPE qosIfMeteringCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfMeteringCapsEntry SYNTAX SEQUENCE OF QosIfMeteringCapsEntry
PIB-ACCESS notify, 3 PIB-ACCESS notify, 2
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the metering capabilities of an "This table specifies the metering capabilities of an
interface type" interface type"
::= { qosCapabilityClasses 2 } ::= { qosCapabilityClasses 3 }
qosIfMeteringCapsEntry OBJECT-TYPE qosIfMeteringCapsEntry OBJECT-TYPE
SYNTAX QosIfMeteringCapsEntry SYNTAX QosIfMeteringCapsEntry
STATUS current
DESCRIPTION
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
STATUS current
DESCRIPTION
"An instance of this class describes the classification "An instance of this class describes the classification
capabilities of an interface." capabilities of an interface."
PIB-INDEX { qosIfMeteringCapsPrid } EXTENDS { qosBaseIfCapsEntry }
UNIQUENESS { qosIfMeteringCapsSpec } UNIQUENESS { qosBaseIfCapsDirection,
qosIfMeteringCapsSpec }
::= { qosIfMeteringCapsTable 1 } ::= { qosIfMeteringCapsTable 1 }
QosIfMeteringCapsEntry ::= SEQUENCE { QosIfMeteringCapsEntry ::= SEQUENCE {
qosIfMeteringCapsPrid InstanceId,
qosIfMeteringCapsSpec BITS qosIfMeteringCapsSpec BITS
} }
qosIfMeteringCapsPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { qosIfMeteringCapsEntry 1 }
qosIfMeteringCapsSpec OBJECT-TYPE qosIfMeteringCapsSpec OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
meterByRemarking (1), meterByRemarking (1),
meterByDropping (2), meterByDropping (2),
-- These capabilities indicate if the interface -- These capabilities indicate if the interface
-- can remark out of profile packets or drop them, -- can remark out of profile packets or drop them,
-- respectively -- respectively
inputShaping (3),
outputShaping (4)
-- indicate if the interface can shape on ingress
-- or on egress, respectively.
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Bit set of supported metering capabilities. As with "Bit set of supported metering capabilities. As with
classification capabilities, these metering capabilities may classification capabilities, these metering capabilities may
be augmented by capabilities specified in other PRCs (in other be augmented by capabilities specified in other PRCs (in other
DiffServ QoS Policy Information Base November 2000
PIBs)." PIBs)."
::= { qosIfMeteringCapsEntry 2 } ::= { qosIfMeteringCapsEntry 1 }
-- --
-- Algorithmic Dropper Capabilities
--
-- This capability table indicates the types of algorithmic
-- drop supported by an interface type for a specific flow
-- direction.
-- Additional capabilities affecting the drop functionalities
-- are determined based on queue capabilities associated with
-- specific instance of a dropper, hence not specified by
-- this table.
-- --
qosIfSchedulingCapsTable OBJECT-TYPE DiffServ QoS Policy Information Base February 2001
SYNTAX SEQUENCE OF QosIfSchedulingCapsEntry
PIB-ACCESS notify, 10 qosIfAlgDropCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfAlgDropCapsEntry
PIB-ACCESS notify, 2
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the scheduling capabilities of an "This table specifies the algorithmic dropper
interface type" capabilities of an interface type"
::= { qosCapabilityClasses 3 } ::= { qosCapabilityClasses 4 }
qosIfSchedulingCapsEntry OBJECT-TYPE qosIfAlgDropCapsEntry OBJECT-TYPE
SYNTAX QosIfSchedulingCapsEntry SYNTAX QosIfAlgDropCapsEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of this class describes the classification "An instance of this class describes the algorithm dropper
capabilities of an interface." capabilities of an interface."
EXTENDS { qosBaseIfCapsEntry }
UNIQUENESS { qosBaseIfCapsDirection,
qosIfAlgDropCapsType }
::= { qosIfAlgDropCapsTable 1 }
PIB-INDEX { qosIfSchedulingCapsPrid } QosIfAlgDropCapsEntry ::= SEQUENCE {
UNIQUENESS { qosIfSchedulingCapsMaxQueues, qosIfAlgDropCapsType BITS
qosIfSchedulingCapsMaxThresholds, }
qosIfSchedulingCapsMaxPriorities,
qosIfSchedulingCapsServiceDisc,
qosIfSchedulingCapsMinQueueSize,
qosIfSchedulingCapsMaxQueueSize,
qosIfSchedulingCapsTotalQueueSize,
qosIfSchedulingCapsWredCapable }
::= { qosIfSchedulingCapsTable 1 }
QosIfSchedulingCapsEntry ::= SEQUENCE { qosIfAlgDropCapsType OBJECT-TYPE
qosIfSchedulingCapsPrid InstanceId, SYNTAX BITS {
qosIfSchedulingCapsMaxQueues INTEGER, tailDrop(2),
qosIfSchedulingCapsMaxThresholds INTEGER, headDrop(3),
qosIfSchedulingCapsMaxPriorities INTEGER, randomDrop(4) }
STATUS current
DESCRIPTION
"The type of algorithm that droppers associated with queues
may use.
DiffServ QoS Policy Information Base November 2000 The tailDrop(2) algorithm means that packets are dropped from
the tail of the queue when the associated queue's MaxQueueSize is
exceeded. The headDrop(3) algorithm means that packets are
dropped from the head of the queue when the associated queue's
MaxQueueSize is exceeded. The randomDrop(4) algorithm means that
an algorithm is executed which may randomly
drop the packet, or drop other packet(s) from the queue
in its place. The specifics of the algorithm may be
proprietary. However, parameters would be specified in the
qosRandomDropTable."
::= { qosIfAlgDropCapsEntry 1 }
qosIfSchedulingCapsServiceDisc BITS, DiffServ QoS Policy Information Base February 2001
qosIfSchedulingCapsMinQueueSize INTEGER,
qosIfSchedulingCapsMaxQueueSize INTEGER,
qosIfSchedulingCapsTotalQueueSize INTEGER,
qosIfSchedulingCapsAlgDropSupported BITS
}
qosIfSchedulingCapsPrid OBJECT-TYPE --
SYNTAX InstanceId -- Queue Capabilities
--
qosIfQueueCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfQueueCapsEntry
PIB-ACCESS notify, 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "This table specifies the scheduling capabilities of an
instance of the class." interface type"
::= { qosIfSchedulingCapsEntry 1 } ::= { qosCapabilityClasses 5 }
qosIfSchedulingCapsMaxQueues OBJECT-TYPE qosIfQueueCapsEntry OBJECT-TYPE
SYNTAX INTEGER SYNTAX QosIfSchedulerCapsEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of queues that this interface type can "An instance of this class describes the queue
support. A value of zero means that there is no maximum." capabilities of an interface type."
::= { qosIfSchedulingCapsEntry 2 } EXTENDS { qosBaseIfCapsEntry }
UNIQUENESS { qosBaseIfCapsDirection,
qosIfQueueCapsMinQueueSize,
qosIfQueueCapsMaxQueueSize,
qosIfQueueCapsTotalQueueSize }
::= { qosIfQueueCapsTable 1 }
qosIfSchedulingCapsMaxThresholds OBJECT-TYPE QosIfQueueCapsEntry ::= SEQUENCE {
SYNTAX INTEGER qosIfQueueCapsMinQueueSize Unsigned32,
qosIfQueueCapsMaxQueueSize Unsigned32,
qosIfQueueCapsTotalQueueSize Unsigned32
}
qosIfQueueCapsMinQueueSize OBJECT-TYPE
SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of drop thresholds that each queue "Some interfaces may allow the size of a queue to be
supports. If the interface has a different number of configured. This attribute specifies the minimum size that
thresholds for each of its queues, it must report the maximum can be configured for a queue, specified in bytes."
number of thresholds any of the queues supports. The value of ::= { qosIfQueueCapsEntry 1 }
this attribute must be one or more."
::= { qosIfSchedulingCapsEntry 3 }
qosIfSchedulingCapsMaxPriorities OBJECT-TYPE qosIfQueueCapsMaxQueueSize OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of priority levels that the the queues of
the interface may be grouped into. A value of zero means
there is no maximum."
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
::= { qosIfSchedulingCapsEntry 4 } "Some interfaces may allow the size of a queue to be
configured. This attribute specifies the maximum size that
can be configured for a queue, specified in bytes."
::= { qosIfQueueCapsEntry 2 }
qosIfSchedulingCapsServiceDisc OBJECT-TYPE qosIfQueueCapsTotalQueueSize OBJECT-TYPE
SYNTAX BITS { SYNTAX Unsigned32
other(1), -- Unspecified or specified in
-- another capability
priorityq(2), -- Priority Queueing
rr(3), -- Strict Round Robin
wrr(3), -- Weighted Round Robin
fq(4), -- Strict Fair Queuing
wfq(4), -- Weighted Fair Queuing
wirr(5), -- Weighted Interleaved Round Robin
bsp(6) -- Bounded Strict Priority
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The scheduling disciplines supported for servicing queues in "Some interfaces may have a limited buffer space to be share
the same priority group that the interface supports. Several amoungst all queues of that interface while also allowing the
general purpose and well-known queuing disciplines are size of each queue to be configurable. To prevent the
supported by this attribute. Other queueing disciplines may be situation where the PDP configures the sizes of the queues in
specified instead of, or in addition to, these disciplines by excess of the total buffer available to the interface, the PEP
setting and providing another capabilities PRC specifying the can report the total buffer space in bytes available with this
other scheduling discipline. capability."
::= { qosIfQueueCapsEntry 3 }
If none is specified then the service discipline is either --
unspecified or specified by another capabilities PRC." -- Scheduler Capabilities
::= { qosIfSchedulingCapsEntry 5 } --
qosIfSchedulingCapsMinQueueSize OBJECT-TYPE qosIfSchedulerCapsTable OBJECT-TYPE
SYNTAX INTEGER SYNTAX SEQUENCE OF QosIfSchedulerCapsEntry
PIB-ACCESS notify, 3
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Some interfaces may allow the size of a queue to be "This table specifies the scheduler capabilities of an
configured. This attribute specifies the minimum size the interface type"
queue can be configured to specified in bytes. ::= { qosCapabilityClasses 6 }
Some interfaces set queue size in terms of packets. These qosIfSchedulerCapsEntry OBJECT-TYPE
devices must report the minimum queue size in bytes by SYNTAX QosIfSchedulerCapsEntry
assuming an average packet size suitable for the particular STATUS current
interface." DESCRIPTION
::= { qosIfSchedulingCapsEntry 6 } "An instance of this class describes the scheduler
capabilities of an interface type."
EXTENDS { qosBaseIfCapsEntry }
UNIQUENESS { qosBaseIfCapsDirection,
qosIfSchedulerCapsServiceDisc,
qosIfSchedulerCapsMaxInputs }
::= { qosIfSchedulerCapsTable 1 }
DiffServ QoS Policy Information Base November 2000 QosIfSchedulerCapsEntry ::= SEQUENCE {
qosIfSchedulingCapsMaxQueueSize OBJECT-TYPE DiffServ QoS Policy Information Base February 2001
SYNTAX INTEGER
qosIfSchedulerCapsServiceDisc OBJECT IDENTIFIER,
qosIfSchedulerCapsMaxInputs Unsigned32
}
qosIfSchedulerCapsServiceDisc OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Some interfaces may allow the size of a queue to be "The scheduling discipline for which the set of capabilities
configured. This attribute specifies the maximum size the specified in this object apply. Obejct identifiers for several
queue can be configured to specified in bytes. As with general purpose and well-known queuing disciplines are defined
qosIfSchedulingCapsMinQueueSize, devices that set in this PIB. Queueing disciplines defined in another PIB may
queue size in terms of packets must report the maximum queue also be specified."
size in bytes by assuming an average packet size suitable for ::= { qosIfSchedulerCapsEntry 1 }
the particular interface."
::= { qosIfSchedulingCapsEntry 7 }
qosIfSchedulingCapsTotalQueueSize OBJECT-TYPE qosIfSchedulerCapsMaxInputs OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Some interfaces may have a limited buffer space to be share "The maximum number of queues that this interface type can
amoung all queues of that interface while also allowing the support for the scheduler type indicated by
size of each queue to be configurable. To prevent the qosIfSchedulerCapsServiceDisc. A value of zero means that there
situation where the PDP configures the sizes of the queues in is no maximum."
excess of the total buffer available to the interface, the PEP ::= { qosIfSchedulerCapsEntry 2 }
can report the total buffer space available with this
capability. The value is the total number of bytes."
::= { qosIfSchedulingCapsEntry 8 }
qosIfSchedulingCapsAlgDropSupported OBJECT-TYPE --
SYNTAX BITS { -- Shaper Capabilities
tailDrop(2), --
headDrop(3),
randomDrop(4) qosIfShaperCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfShaperCapsEntry
PIB-ACCESS notify, 3
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of algorithm that droppers associated with this queue "This table specifies the shaping capabilities of an
may use. interface type"
::= { qosCapabilityClasses 7 }
The tailDrop(2) algorithm means that packets are dropped from qosIfShaperCapsEntry OBJECT-TYPE
the tail of the queue when the associated threshold is SYNTAX QosIfShaperCapsEntry
exceeded. The headDrop(3) algorithm means that packets are STATUS current
dropped from the head of the queue when the associated DESCRIPTION
threshold is exceeded. The randomDrop(4) algorithm means that, "An instance of this class describes the shaping
on packet arrival, an algorithm is executed which may randomly capabilities of an interface type."
drop the packet, or drop other packet(s) from the queue
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
in its place. The specifics of the algorithm may be EXTENDS { qosBaseIfCapsEntry }
proprietary. However, parameters would be specified in the UNIQUENESS { qosBaseIfCapsDirection,
qosRandomDropTable." qosIfShaperCapsAlgorithm,
::= { qosIfSchedulingCapsEntry 9 } qosIfShaperCapsMaxNumberOfRates }
::= { qosIfShaperCapsTable 1 }
QosIfShaperCapsEntry ::= SEQUENCE {
qosIfShaperCapsAlgorithm OBJECT IDENTIFIER,
qosIfShaperCapsMaxNumberOfRates Unsigned32
}
qosIfShaperCapsAlgorithm OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
STATUS current
DESCRIPTION
"The shaping method for which the set of capabilities
specified in this object apply. Values that may be
used for this attribute are TBD."
::= { qosIfShaperCapsEntry 1 }
qosIfShaperCapsMaxNumberOfRates OBJECT-TYPE
SYNTAX Unsigned32
STATUS current
DESCRIPTION
"The maximum number of rates shapers of the type indicated
by qosIfShaperCapsAlgorithm may have for this interface type
and flow direction."
::= { qosIfShaperCapsEntry 2 }
-- --
-- Datapath Element Linkage Capabilities -- Datapath Element Linkage Capabilities
-- --
-- --
-- Datapath Element Cascade Depth -- Datapath Element Cascade Depth
-- --
qosIfElmDepthCapsTable OBJECT-TYPE qosIfElmDepthCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfElmDepthCapsEntry SYNTAX SEQUENCE OF QosIfElmDepthCapsEntry
PIB-ACCESS notify, 4 PIB-ACCESS notify, 3
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the number of elements of the same "This table specifies the number of elements of the same
DiffServ QoS Policy Information Base February 2001
type that can be cascaded together in a data path." type that can be cascaded together in a data path."
::= { qosCapabilityClasses 4 } ::= { qosCapabilityClasses 8 }
qosIfElmDepthCapsEntry OBJECT-TYPE qosIfElmDepthCapsEntry OBJECT-TYPE
SYNTAX QosIfElmDepthCapsEntry SYNTAX QosIfElmDepthCapsEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of this class describes the cascade depth "An instance of this class describes the cascade depth
for a particular datapath functional element PRC. A for a particular datapath functional element PRC. A
functional datapath element not represented in this functional datapath element not represented in this
table can be assumed to have no specific maximum table can be assumed to have no specific maximum
depth." depth."
PIB-INDEX { qosIfElmDepthCapsPrid } EXTENDS { qosBaseIfCapsEntry }
UNIQUENESS { qosIfElmDepthCapsPrc } UNIQUENESS { qosBaseIfCapsDirection,
qosIfElmDepthCapsPrc }
::= { qosIfElmDepthCapsTable 1 } ::= { qosIfElmDepthCapsTable 1 }
QosIfElmDepthCapsEntry ::= SEQUENCE { QosIfElmDepthCapsEntry ::= SEQUENCE {
qosIfElmDepthCapsPrid InstanceId,
qosIfElmDepthCapsPrc OBJECT IDENTIFIER, qosIfElmDepthCapsPrc OBJECT IDENTIFIER,
qosIfElmDepthCapsCascadeMax Unsigned32 qosIfElmDepthCapsCascadeMax Unsigned32
DiffServ QoS Policy Information Base November 2000
} }
qosIfElmDepthCapsPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { qosIfElmDepthCapsEntry 1 }
qosIfElmDepthCapsPrc OBJECT-TYPE qosIfElmDepthCapsPrc OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object identifier of a PRC that represents a datapath "The object identifier of a PRC that represents a datapath
functional element. This may be one of: qosClfrElementEntry, functional element. This may be one of: qosClfrElementEntry,
qosMeterEntry, qosActionEntry, qosAlgDropEntry, qosQEntry, or qosMeterEntry, qosActionEntry, qosAlgDropEntry, qosQEntry, or
qosSchedulerEntry. The value is the OID of the table entry. qosSchedulerEntry. The value is the OID of the table entry.
There may not be more than one instance of this class with There may not be more than one instance of this class with
the same value of qosIfElmDepthCapsPrc." the same value of qosIfElmDepthCapsPrc."
::= { qosIfElmDepthCapsEntry 2 } ::= { qosIfElmDepthCapsEntry 1 }
qosIfElmDepthCapsCascadeMax OBJECT-TYPE qosIfElmDepthCapsCascadeMax OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of elements of type qosIfElmDepthCapsPrc "The maximum number of elements of type qosIfElmDepthCapsPrc
DiffServ QoS Policy Information Base February 2001
that can be linked consecutively in a data path." A value of that can be linked consecutively in a data path." A value of
zero indicates there is no specific maximum." zero indicates there is no specific maximum."
::= { qosIfElmDepthCapsEntry 3 } ::= { qosIfElmDepthCapsEntry 2 }
-- --
-- Datapath Element Linkage Types -- Datapath Element Linkage Types
-- --
qosIfElmLinkCapsTable OBJECT-TYPE qosIfElmLinkCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfElmLinkCapsEntry SYNTAX SEQUENCE OF QosIfElmLinkCapsEntry
PIB-ACCESS notify, 5 PIB-ACCESS notify, 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
DiffServ QoS Policy Information Base November 2000
"This table specifies what types of datapath functional "This table specifies what types of datapath functional
elements may be used as the next downstream element for elements may be used as the next downstream element for
a specific type of functional element." a specific type of functional element."
::= { qosCapabilityClasses 5 } ::= { qosCapabilityClasses 9 }
qosIfElmLinkCapsEntry OBJECT-TYPE qosIfElmLinkCapsEntry OBJECT-TYPE
SYNTAX QosIfElmLinkCapsEntry SYNTAX QosIfElmLinkCapsEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of this class specifies a PRC that may "An instance of this class specifies a PRC that may
be used as the next functional element after a specific be used as the next functional element after a specific
type of element in a data path." type of element in a data path."
PIB-INDEX { qosIfElmLinkCapsPrid } EXTENDS { qosBaseIfCapsEntry }
UNIQUENESS { qosIfElmLinkCapsPrc, UNIQUENESS { qosBaseIfCapsDirection,
qosIfElmLinkCapsPrc,
qosIfElmLinkCapsAttr, qosIfElmLinkCapsAttr,
qosIfElmLinkCapsNextPrc } qosIfElmLinkCapsNextPrc }
::= { qosIfElmLinkCapsTable 1 } ::= { qosIfElmLinkCapsTable 1 }
QosIfElmLinkCapsEntry ::= SEQUENCE { QosIfElmLinkCapsEntry ::= SEQUENCE {
qosIfElmLinkCapsPrid InstanceId,
qosIfElmLinkCapsPrc OBJECT IDENTIFIER, qosIfElmLinkCapsPrc OBJECT IDENTIFIER,
qosIfElmLinkCapsAttr Unsigned32, qosIfElmLinkCapsAttr Unsigned32,
qosIfElmLinkCapsNextPrc OBJECT IDENTIFIER qosIfElmLinkCapsNextPrc OBJECT IDENTIFIER
} }
qosIfElmLinkCapsPrid OBJECT-TYPE DiffServ QoS Policy Information Base February 2001
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { qosIfElmLinkCapsEntry 1 }
qosIfElmLinkCapsPrc OBJECT-TYPE qosIfElmLinkCapsPrc OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value is the OID of a PRC that represents a "The value is the OID of a PRC that represents a
functional datapath element." functional datapath element."
::= { qosIfElmLinkCapsEntry 1 }
DiffServ QoS Policy Information Base November 2000
::= { qosIfElmLinkCapsEntry 2 }
qosIfElmLinkCapsAttr OBJECT-TYPE qosIfElmLinkCapsAttr OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value represents the attribute in the the PRC "The value represents the attribute in the the PRC
indicated by qosIfElmLinkCapsPrc that is used to indicated by qosIfElmLinkCapsPrc that is used to
specify the next functional element in the datapath. specify the next functional element in the datapath.
The attribute value corresponds to the order in which The attribute value corresponds to the order in which
the attribute appears in the definition of the PRC. the attribute appears in the definition of the PRC.
A value of 1 indicates the first attribute of the PRC, A value of 1 indicates the first attribute of the PRC,
a value of 2 indicates the second attribute of the a value of 2 indicates the second attribute of the
PRC, and so forth." PRC, and so forth."
::= { qosIfElmLinkCapsEntry 3 } ::= { qosIfElmLinkCapsEntry 2 }
qosIfElmLinkCapsNextPrc OBJECT-TYPE qosIfElmLinkCapsNextPrc OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value is the OID of a PRC table entry from which "The value is the OID of a PRC table entry from which
instances can be referenced by the attribute indicated instances can be referenced by the attribute indicated
by qosIfElmLinkCapsPrc and qosIfElmLinkAttr. by qosIfElmLinkCapsPrc and qosIfElmLinkAttr.
For example, suppose a meter's success output can be an For example, suppose a meter's success output can be an
action or another meter, and the fail output can only be action or another meter, and the fail output can only be
an action. This can be expressed as follows: an action. This can be expressed as follows:
Prid Prc Attr NextPrc Prid Prc Attr NextPrc
1 qosMeterEntry qosMeterSucceedNext qosActionEntry 1 qosMeterEntry qosMeterSucceedNext qosActionEntry
2 qosMeterEntry qosMeterSucceedNext qosMeterEntry 2 qosMeterEntry qosMeterSucceedNext qosMeterEntry
3 qosMeterEntry qosMeterFailNext qosActionEntry." 3 qosMeterEntry qosMeterFailNext qosActionEntry."
::= { qosIfElmLinkCapsEntry 4 } ::= { qosIfElmLinkCapsEntry 3 }
-- --
DiffServ QoS Policy Information Base February 2001
-- Policy Classes
-- --
-- --
-- Data Path Table -- Data Path Table
DiffServ QoS Policy Information Base November 2000
-- --
-- The Data Path Table enumerates the Differentiated Services -- The Data Path Table enumerates the Differentiated Services
-- Data Paths within this device. Each entry specifies -- Data Paths within this device. Each entry specifies
-- the first functional datapath element to process data flow -- the first functional datapath element to process data flow
-- for each specific datapath. Each datapath is defined by the -- for each specific datapath. Each datapath is defined by the
-- interface role combination and direction. This table can -- interface role combination and direction. This table can
-- therefore have up to two entries for each role combination, -- therefore have up to two entries for each role combination,
-- ingress and egress. -- ingress and egress.
qosDataPathTable OBJECT-TYPE qosDataPathTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosDataPathEntry SYNTAX SEQUENCE OF QosDataPathEntry
PIB-ACCESS install, 5 PIB-ACCESS install, 6
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The data path table defines the data paths in this "The data path table defines the data paths in this
device. Each data path is defined by the interface, device. Each data path is defined by the interface,
role combination and traffic direction. The first role combination and traffic direction. The first
functional datapath element to handle traffic for functional datapath element to handle traffic for
this data path is defined by a Prid in the entries this data path is defined by a Prid in the entries
of this table." of this table."
::= { qosPolicyClasses 1 } ::= { qosPolicyClasses 1 }
skipping to change at page 35, line 42 skipping to change at page 40, line 47
DESCRIPTION DESCRIPTION
"An entry in the data path table describes a single "An entry in the data path table describes a single
data path in this device." data path in this device."
PIB-INDEX { qosDataPathPrid } PIB-INDEX { qosDataPathPrid }
UNIQUENESS { qosDataPathRoles, UNIQUENESS { qosDataPathRoles,
qosDataPathIfDirection } qosDataPathIfDirection }
::= { qosDataPathTable 1 } ::= { qosDataPathTable 1 }
QosDataPathEntry ::= SEQUENCE { QosDataPathEntry ::= SEQUENCE {
qosDataPathPrid InstanceId, qosDataPathPrid InstanceId,
qosDataPathIfName SnmpAdminString,
DiffServ QoS Policy Information Base February 2001
qosDataPathRoles RoleCombination, qosDataPathRoles RoleCombination,
qosDataPathIfDirection IfDirection, qosDataPathIfDirection IfDirection,
qosDataPathStart Prid qosDataPathStart Prid
} }
qosDataPathPrid OBJECT-TYPE qosDataPathPrid OBJECT-TYPE
DiffServ QoS Policy Information Base November 2000
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { qosDataPathEntry 1 } ::= { qosDataPathEntry 1 }
qosDataPathIfName OBJECT-TYPE
SYNTAX SnmpAdminString
STATUS current
DESCRIPTION
"The interface capability set to which this data path entry
applies. The interface capability name specified by this
attribute must exist in the frwkIfCapSetTable [FR-PIB] prior
to association with an instance of this class."
::= { qosDataPathEntry 2 }
qosDataPathRoles OBJECT-TYPE qosDataPathRoles OBJECT-TYPE
SYNTAX RoleCombination SYNTAX RoleCombination
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interfaces to which this data path entry applies, "The interfaces to which this data path entry applies,
specified in terms of roles. The role combination specified in terms of roles. There must exist an entry
specified by this attribute must exist in the in the frwkIfCapSetRoleComboTable [FR-PIB] specifying
frwkIfCapSetRoleComboTable [FR-PIB] prior to association this role combination, together with the interface
with an instance of this class." capability set specified by qosDataPathIfName, prior to
::= { qosDataPathEntry 2 } association with an instance of this class."
::= { qosDataPathEntry 3 }
qosDataPathIfDirection OBJECT-TYPE qosDataPathIfDirection OBJECT-TYPE
SYNTAX IfDirection SYNTAX IfDirection
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the direction for which this data path "Specifies the direction for which this data path
entry applies on this interface." entry applies on this interface."
::= { qosDataPathEntry 3 }
DiffServ QoS Policy Information Base February 2001
::= { qosDataPathEntry 4 }
qosDataPathStart OBJECT-TYPE qosDataPathStart OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This selects the first functional datapath element "This selects the first functional datapath element
to handle traffic for this data path. This to handle traffic for this data path. This
Prid should point to an instance of one of: Prid should point to an instance of one of:
qosClfrEntry qosClfrEntry
qosMeterEntry qosMeterEntry
qosActionEntry qosActionEntry
qosAlgDropEntry qosAlgDropEntry
qosQEntry qosQEntry
The PRI to must exist prior to the installation of The PRI to must exist prior to the installation of
this datapath start element." this datapath start element."
::= { qosDataPathEntry 4 } ::= { qosDataPathEntry 5 }
DiffServ QoS Policy Information Base November 2000
-- --
-- Classifiers -- Classifiers
-- --
-- --
-- Classifier Table -- Classifier Table
-- --
-- Classifier allows multiple classifier elements, of same or different -- Classifier allows multiple classifier elements, of same or different
-- types, to be used together. -- types, to be used together.
skipping to change at page 37, line 31 skipping to change at page 43, line 5
qosClfrTable OBJECT-TYPE qosClfrTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosClfrEntry SYNTAX SEQUENCE OF QosClfrEntry
PIB-ACCESS install, 3 PIB-ACCESS install, 3
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
REFERENCE REFERENCE
"[MODEL] section 4.1" "[MODEL] section 4.1"
::= { qosPolicyClasses 2 } ::= { qosPolicyClasses 2 }
DiffServ QoS Policy Information Base February 2001
qosClfrEntry OBJECT-TYPE qosClfrEntry OBJECT-TYPE
SYNTAX QosClfrEntry SYNTAX QosClfrEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the classifier table describes a "An entry in the classifier table describes a
single classifier, all classifier elements belong- single classifier. Each classifier element belong-
ing to the same classifier must have its ing to the this classifier must have its
qosClfrElementClfrId attribute have the same qosClfrElementClfrId attribute equal to qosClfrId."
value, one of qosClfrId."
PIB-INDEX { qosClfrPrid } PIB-INDEX { qosClfrPrid }
UNIQUENESS { qosClfrId } UNIQUENESS { qosClfrId }
::= { qosClfrTable 1 } ::= { qosClfrTable 1 }
QosClfrEntry ::= SEQUENCE { QosClfrEntry ::= SEQUENCE {
qosClfrPrid InstanceId, qosClfrPrid InstanceId,
qosClfrId TagReference qosClfrId TagReference
} }
DiffServ QoS Policy Information Base November 2000
qosClfrPrid OBJECT-TYPE qosClfrPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { qosClfrEntry 1 } ::= { qosClfrEntry 1 }
qosClfrId OBJECT-TYPE qosClfrId OBJECT-TYPE
SYNTAX TagReference SYNTAX TagReference
PIB-TAG qosClfrElementClfrId PIB-TAG qosClfrElementClfrId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies a Classifier. A Classifier must be "Identifies a Classifier. A Classifier must be
complete, this means all traffic handled by a complete, this means all traffic handled by a
Classifier must match at least one Classifier Classifier must match at least one Classifier
Element within the Classifier, with the Classifier Element within the Classifier."
parameters specified by a Filter.
If there is ambiguity between Classifiers Elements of
different Classifiers, the precedence is indicated
by the order the Classifiers are linked, the
first Classifier in the link is applied to the
traffic first.
::= { qosClfrEntry 2 } ::= { qosClfrEntry 2 }
-- --
-- Classifier Element Table -- Classifier Element Table
-- --
-- Entries in the classifier element table serves as -- Entries in the classifier element table serves as
-- the anchor for each classification pattern, defined -- the anchor for each classification pattern, defined
DiffServ QoS Policy Information Base February 2001
-- in filter table entries. Each classifier element -- in filter table entries. Each classifier element
-- table entry also specifies the subsequent downstream -- table entry also specifies the subsequent downstream
-- diffserv functional datapath element when the -- diffserv functional datapath element when the
-- classification pattern is satisfied. -- classification pattern is satisfied.
-- Each entry in the classifier element table describes -- Each entry in the classifier element table describes
-- one branch of the fan-out characteristic of a classifier -- one branch of the fan-out characteristic of a classifier
-- indicated in [MODEL] section 4.1. A classifier is madeup -- indicated in [MODEL] section 4.1. A classifier is madeup
-- of one or more classifier elements. -- of one or more classifier elements.
-- --
qosClfrElementTable OBJECT-TYPE qosClfrElementTable OBJECT-TYPE
DiffServ QoS Policy Information Base November 2000
SYNTAX SEQUENCE OF QosClfrElementEntry SYNTAX SEQUENCE OF QosClfrElementEntry
PIB-ACCESS install, 6 PIB-ACCESS install, 6
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The classifier element table enumerates the rela- "The classifier element table enumerates the rela-
tionship between classification patterns and subse- tionship between classification patterns and subse-
quent downstream diffserv functional datapath ele- quent downstream diffserv functional datapath ele-
ments. Classification parameters are defined by ments. Classification parameters are defined by
entries of filter tables pointed to by entries of filter tables pointed to by
qosClfrElementSpecific. There can be filter qosClfrElementSpecific. There can be filter
skipping to change at page 39, line 39 skipping to change at page 45, line 5
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the classifier element table describes a "An entry in the classifier element table describes a
single element of the classifier." single element of the classifier."
PIB-INDEX { qosClfrElementPrid } PIB-INDEX { qosClfrElementPrid }
UNIQUENESS { qosClfrElementClfrId, UNIQUENESS { qosClfrElementClfrId,
qosClfrElementOrder, qosClfrElementOrder,
qosClfrElementSpecific } qosClfrElementSpecific }
::= { qosClfrElementTable 1 } ::= { qosClfrElementTable 1 }
DiffServ QoS Policy Information Base February 2001
QosClfrElementEntry ::= SEQUENCE { QosClfrElementEntry ::= SEQUENCE {
qosClfrElementPrid InstanceId, qosClfrElementPrid InstanceId,
qosClfrElementClfrId TagId, qosClfrElementClfrId TagId,
qosClfrElementOrder Unsigned32, qosClfrElementPrecedence Unsigned32,
qosClfrElementNext Prid, qosClfrElementNext Prid,
qosClfrElementSpecific Prid qosClfrElementSpecific Prid
} }
qosClfrPrid OBJECT-TYPE qosClfrPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
DiffServ QoS Policy Information Base November 2000
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { qosClfrElementEntry 1 } ::= { qosClfrElementEntry 1 }
qosClfrElementClfrId OBJECT-TYPE qosClfrElementClfrId OBJECT-TYPE
SYNTAX TagId SYNTAX TagId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A classifier Id identifies which classifier this "A classifier Id identifies which classifier this
classifier element is a part of. This needs to be classifier element is a part of. This needs to be
the value of qosClfrId attribute for an existing the value of qosClfrId attribute for an existing
instance of qosClfrEntry." instance of qosClfrEntry."
::= { qosClfrElementEntry 2 } ::= { qosClfrElementEntry 2 }
qosClfrElementOrder OBJECT-TYPE qosClfrElementPrecedence OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The relative order in which classifier elements are "The relative order in which classifier elements are
applied: higher numbers represent classifier elements applied: higher numbers represent classifier elements
with higher precedence. Classifier elements with the same with higher precedence. Classifier elements with the same
order must be unambiguous i.e. they must define order must be unambiguous i.e. they must define
non-overlapping patterns, and are considered to be non-overlapping patterns, and are considered to be
applied simultaneously to the traffic stream. Clas- applied simultaneously to the traffic stream. Clas-
sifier elements with different order may overlap in sifier elements with different order may overlap in
their filters: the classifier element with the highest their filters: the classifier element with the highest
order that matches is taken. order that matches is taken.
On a given interface, there must be a complete clas- On a given interface, there must be a complete clas-
sifier in place at all times in the sifier in place at all times in the
DiffServ QoS Policy Information Base February 2001
ingress direction. This means that there will always ingress direction. This means that there will always
be one or more filters that match every possible pat- be one or more filters that match every possible pat-
tern that could be presented in an incoming packet. tern that could be presented in an incoming packet.
There is no such requirement in the egress direction." There is no such requirement in the egress direction."
DEFVAL { 0 } DEFVAL { 0 }
::= { qosClfrElementEntry 3 } ::= { qosClfrElementEntry 3 }
qosClfrElementNext OBJECT-TYPE qosClfrElementNext OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DiffServ QoS Policy Information Base November 2000
DESCRIPTION DESCRIPTION
"This attribute provides one branch of the fan-out "This attribute provides one branch of the fan-out
functionality of a classifier described in [MODEL] functionality of a classifier described in [MODEL]
section 4.1. section 4.1.
This selects the next diffserv functional datapath This selects the next diffserv functional datapath
element to handle traffic for this data path. element to handle traffic for this data path.
A value of zeroDotZero marks the end of DiffServ processing A value of zeroDotZero marks the end of DiffServ processing
for this data path. Any other value must point to a for this data path. Any other value must point to a
skipping to change at page 41, line 40 skipping to change at page 47, line 4
"A pointer to a valid entry in another table that "A pointer to a valid entry in another table that
describes the applicable classification filter, e.g. describes the applicable classification filter, e.g.
an entry in frwkIpFilterTable [FR-PIB]. an entry in frwkIpFilterTable [FR-PIB].
The PRI pointed to must exist prior to the installation of The PRI pointed to must exist prior to the installation of
this classifier element. this classifier element.
The value zeroDotZero is interpreted to match any- The value zeroDotZero is interpreted to match any-
thing not matched by another classifier element - only one thing not matched by another classifier element - only one
such entry may exist for each classifier." such entry may exist for each classifier."
DiffServ QoS Policy Information Base February 2001
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { qosClfrElementEntry 5 } ::= { qosClfrElementEntry 5 }
-- --
-- Meters -- Meters
-- --
-- This PIB supports a variety of Meters. It includes a -- This PIB supports a variety of Meters. It includes a
-- specific definition for Meters whose parameter set can -- specific definition for Meters whose parameter set can
-- be modelled using Token Bucket parameters. -- be modelled using Token Bucket parameters.
-- Other metering parameter sets can be defined and used -- Other metering parameter sets can be defined and used
DiffServ QoS Policy Information Base November 2000
-- when necessary. -- when necessary.
-- --
-- Multiple meter elements may be logically cascaded -- Multiple meter elements may be logically cascaded
-- using their qosMeterSucceedNext pointers if -- using their qosMeterSucceedNext pointers if
-- a multi-rate Meter is required. -- a multi-rate Meter is required.
-- One example of this might be for an AF PHB implementation -- One example of this might be for an AF PHB implementation
-- that uses two-rate meters. -- that uses two-rate meters.
-- --
-- Cascading of individual meter elements in the PIB is intended -- Cascading of individual meter elements in the PIB is intended
-- to be functionally equivalent to determining the conformance -- to be functionally equivalent to determining the conformance
skipping to change at page 42, line 41 skipping to change at page 48, line 4
-- With the first set parameterizing the Peak Information Rate -- With the first set parameterizing the Peak Information Rate
-- and Peak Burst Size token-bucket, second set parameterizing -- and Peak Burst Size token-bucket, second set parameterizing
-- the Committed Information Rate and Committed Burst Size -- the Committed Information Rate and Committed Burst Size
-- token-bucket. -- token-bucket.
-- --
-- Conforming to RFC 2859, tswTCM can be parameterized using -- Conforming to RFC 2859, tswTCM can be parameterized using
-- two sets of qosMeterEntry and qosTBMeterEntry. -- two sets of qosMeterEntry and qosTBMeterEntry.
-- With the first set parameterizing the Committed Target Rate, -- With the first set parameterizing the Committed Target Rate,
-- second set parametering the Peak Target Rate. -- second set parametering the Peak Target Rate.
-- With both set's qosTBMeterInterval being used to -- With both set's qosTBMeterInterval being used to
DiffServ QoS Policy Information Base February 2001
-- reflect the Average Interval as specified by RFC 2859. -- reflect the Average Interval as specified by RFC 2859.
-- --
qosMeterTable OBJECT-TYPE qosMeterTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosMeterEntry SYNTAX SEQUENCE OF QosMeterEntry
PIB-ACCESS install, 5 PIB-ACCESS install, 5
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table enumerates specific meters that a system "This table enumerates specific meters that a system
may use to police a stream of traffic. The traffic may use to police a stream of traffic. The traffic
DiffServ QoS Policy Information Base November 2000
stream to be metered is determined by the element(s) stream to be metered is determined by the element(s)
upstream of the meter i.e. by the object(s) that upstream of the meter i.e. by the object(s) that
point to each entry in this table. This may include point to each entry in this table. This may include
all traffic on an interface. all traffic on an interface.
Specific meter details are to be found in Specific meter details are to be found in
qosMeterSpecific." qosMeterSpecific."
REFERENCE REFERENCE
"[MODEL] section 5.1" "[MODEL] section 5.1"
::= { qosPolicyClasses 4 } ::= { qosPolicyClasses 4 }
skipping to change at page 43, line 38 skipping to change at page 49, line 4
QosMeterEntry ::= SEQUENCE { QosMeterEntry ::= SEQUENCE {
qosMeterPrid InstanceId, qosMeterPrid InstanceId,
qosMeterSucceedNext Prid, qosMeterSucceedNext Prid,
qosMeterFailNext Prid, qosMeterFailNext Prid,
qosMeterSpecific Prid qosMeterSpecific Prid
} }
qosMeterPrid OBJECT-TYPE qosMeterPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DiffServ QoS Policy Information Base February 2001
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { qosMeterEntry 1 } ::= { qosMeterEntry 1 }
qosMeterSucceedNext OBJECT-TYPE qosMeterSucceedNext OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the traffic does conform, this selects the next "If the traffic does conform, this selects the next
DiffServ QoS Policy Information Base November 2000
diffserv functional datapath element to handle diffserv functional datapath element to handle
traffic for this data path. traffic for this data path.
The value zeroDotZero in this variable indicates no The value zeroDotZero in this variable indicates no
further Diffserv treatment is performed on traffic of further Diffserv treatment is performed on traffic of
this datapath. Any other value must point to a valid this datapath. Any other value must point to a valid
(pre-existing) instance of one of:" (pre-existing) instance of one of:"
qosClfrEntry qosClfrEntry
qosMeterEntry qosMeterEntry
qosActionEntry qosActionEntry
skipping to change at page 44, line 40 skipping to change at page 50, line 4
The value zeroDotZero in this variable indicates no The value zeroDotZero in this variable indicates no
further Diffserv treatment is performed on traffic of further Diffserv treatment is performed on traffic of
this datapath. Any other value must point to a valid this datapath. Any other value must point to a valid
(pre-existing) instance of one of:" (pre-existing) instance of one of:"
qosClfrEntry qosClfrEntry
qosMeterEntry qosMeterEntry
qosActionEntry qosActionEntry
qosAlgDropEntry qosAlgDropEntry
qosQEntry." qosQEntry."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
DiffServ QoS Policy Information Base February 2001
::= { qosMeterEntry 3 } ::= { qosMeterEntry 3 }
qosMeterSpecific OBJECT-TYPE qosMeterSpecific OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the behaviour of the meter by point- "This indicates the behaviour of the meter by point-
ing to an entry containing detailed parameters. Note ing to an entry containing detailed parameters. Note
that entries in that specific table must be managed that entries in that specific table must be managed
explicitly. explicitly.
DiffServ QoS Policy Information Base November 2000
For example, qosMeterSpecific may point to an For example, qosMeterSpecific may point to an
entry in qosTBMeterTable, which contains an entry in qosTBMeterTable, which contains an
instance of a single set of Token Bucket parameters. instance of a single set of Token Bucket parameters.
The PRI pointed to must exist prior to installing this The PRI pointed to must exist prior to installing this
Meter datapath element." Meter datapath element."
::= { qosMeterEntry 5 } ::= { qosMeterEntry 5 }
-- --
-- Token-Bucket Parameter Table
-- --
-- Each entry in the Token Bucket Parameter Table parameterizes
-- a single token bucket. Multiple token buckets can be -- a single token bucket. Multiple token buckets can be
-- used together to parameterize multiple levels of -- used together to parameterize multiple levels of
-- conformance. -- conformance.
-- --
-- Entries of this table are used for both policing, as token
-- bucket parameters, and shaping, as leaky bucket parameters.
--
-- Note that an entry in the Token Bucket Parameter Table can
-- be shared, pointed to, by multiple qosMeterTable
-- and qosSchedulerTable entries.
--
qosTBMeterTable OBJECT-TYPE qosTBParamTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosTBMeterEntry SYNTAX SEQUENCE OF QosTBParamEntry
PIB-ACCESS install, 6 PIB-ACCESS install, 6
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table enumerates specific token-bucket meters "This table enumerates specific token-bucket meters
DiffServ QoS Policy Information Base February 2001
that a system may use to police a stream of traffic. that a system may use to police a stream of traffic.
Such meters are modelled here as having a single rate Such meters are modelled here as having a single rate
and a single burst size." and a single burst size. Multiple entries are used
when multiple rates/burst sizes are needed."
REFERENCE REFERENCE
"[MODEL] section 5.1" "[MODEL] section 5.1"
::= { qosPolicyClasses 5 } ::= { qosPolicyClasses 5 }
qosTBMeterEntry OBJECT-TYPE qosTBParamEntry OBJECT-TYPE
SYNTAX QosTBMeterEntry SYNTAX QosTBParamEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry that describes a single token-bucket meter, "An entry that describes a single token-bucket meter."
indexed by the same variables as a qosMeterEn- PIB-INDEX { qosTBParamPrid }
try." UNIQUENESS { qosTBParamType,
PIB-INDEX { qosTBMeterPrid } qosTBParamRate,
UNIQUENESS { qosTBMeterType, qosTBParamBurstSize,
qosTBMeterRate, qosTBParamInterval }
qosTBMeterBurstSize, ::= { qosTBParamTable 1 }
qosTBMeterInterval }
DiffServ QoS Policy Information Base November 2000
::= { qosTBMeterTable 1 }
QosTBMeterEntry ::= SEQUENCE { QosTBParamEntry ::= SEQUENCE {
qosTBMeterPrid InstanceId, qosTBParamPrid InstanceId,
qosTBMeterType INTEGER, qosTBParamType OBJECT IDENTIFIER,
qosTBMeterRate Unsigned32, qosTBParamRate Unsigned32,
qosTBMeterBurstSize BurstSize, qosTBParamBurstSize BurstSize,
qosTBMeterInterval Unsigned32 qosTBParamInterval Unsigned32
} }
qosTBMeterPrid OBJECT-TYPE qosTBParamPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { qosTBMeterEntry 1 } ::= { qosTBParamEntry 1 }
qosTBMeterType OBJECT-TYPE qosTBParamType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX OBJECT IDENTIFIER
tokenBucket(2), -- Simple Token Bucket
avgRate(3), -- Average Rate
srTCMBlind(4), -- srTCM, Color-blind
srTCMAware(5), -- srTCM, Color-aware
trTCMBlind(6), -- trTCM, Color-blind
trTCMAware(7), -- trTCM, Color-aware
tswTCM(8) -- tswTCM
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of meter using parameters specified by this "The Metering/Shaping algorithm associated with the
TBMeter entry.
Value of tokenBucket(2) indicates the use of Two
Parameter Token Bucket Meter as described in [MODEL]
section 5.2.3.
Value of avgRate(3) indicates the use of Average Rate
Meter as described in [MODEL] section 5.2.1.
Value of srTCMBlind(4) and srTCMAware(5) indicates DiffServ QoS Policy Information Base February 2001
the use of Single Rate Three Color Marker Metering as
DiffServ QoS Policy Information Base November 2000 Token/Leaky Bucket parameters.
defined by RFC 2697, with `Color Blind' and `Color Standard values for generic algorithms are as follows:
Aware' mode as described by the RFC.
Value of trTCMBlind(6) and trTCMAware(7) indicates qosTBParamSimpleTokenBucket, qosTBParamAvgRate,
the use of Two Rate Three Color Marker Metering as qosTBParamSrTCMBlind, qosTBParamSrTCMAware,
defined by RFC 2698, with `Color Blind' and `Color qosTBParamTrTCMBlind, qosTBParamTrTCMAware,
Aware' mode as described by the RFC. qosTBParamTswTCM
Value of tswTCM(8) indicates the use of Time Sliding are specified in this PIB as OBJECT-IDENTITYs; additional values
Window Three Color Marker Metering as defined by RFC may be further specified in other PIBs."
2859."
REFERENCE REFERENCE
"[MODEL] section 5" "[MODEL] section 5"
::= { qosTBMeterEntry 2 } ::= { qosTBParamEntry 2 }
qosTBMeterRate OBJECT-TYPE qosTBParamRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "kilobits per second" UNITS "kilobits per second"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The token-bucket rate, in kilobits per second "The token-bucket rate, in kilobits per second
(kbps). This attribute is used for: 1. CIR in RFC (kbps). This attribute is used for: 1. CIR in RFC
2697 for srTCM 2. PIR and CIR in FRC 2698 for trTCM 2697 for srTCM 2. PIR and CIR in FRC 2698 for trTCM
3. CTR and PTR in RFC 2859 for TSWTCM 4. AverageRate 3. CTR and PTR in RFC 2859 for TSWTCM 4. AverageRate
used in [MODEL] section 5." used in [MODEL] section 5."
::= { qosTBMeterEntry 3 } ::= { qosTBParamEntry 3 }
qosTBMeterBurstSize OBJECT-TYPE qosTBParamBurstSize OBJECT-TYPE
SYNTAX BurstSize SYNTAX BurstSize
UNITS "Bytes" UNITS "Bytes"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of bytes in a single transmission "The maximum number of bytes in a single transmission
burst. This attribute is used for: 1. CBS and EBS in burst. This attribute is used for: 1. CBS and EBS in
RFC 2697 for srTCM 2. CBS and PBS in FRC 2698 for RFC 2697 for srTCM 2. CBS and PBS in FRC 2698 for
trTCM 3. Burst Size used in [MODEL] section 5." trTCM 3. Burst Size used in [MODEL] section 5."
::= { qosTBMeterEntry 4 } ::= { qosTBParamEntry 4 }
qosTBMeterInterval OBJECT-TYPE qosTBparamInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "microseconds" UNITS "microseconds"
STATUS current STATUS current
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
DESCRIPTION DESCRIPTION
"The time interval used with the token bucket. For: "The time interval used with the token bucket. For:
1. Average Rate Meter, [MODEL] section 5.2.1, - 1. Average Rate Meter, [MODEL] section 5.2.1, -
Delta. 2. Simple Token Bucket Meter, [MODEL] section Delta. 2. Simple Token Bucket Meter, [MODEL] section
5.1, - time interval t. 3. RFC 2859 TSWTCM, - 5.1, - time interval t. 3. RFC 2859 TSWTCM, -
AVG_INTERVAL. 4. RFC 2697 srTCM, RFC 2698 trTCM, - AVG_INTERVAL. 4. RFC 2697 srTCM, RFC 2698 trTCM, -
token bucket update time interval." token bucket update time interval."
::= { qosTBMeterEntry 5 } ::= { qosTBParamEntry 5 }
-- --
-- Actions -- Actions
-- --
-- --
-- The Action Table allows enumeration of the different -- The Action Table allows enumeration of the different
-- types of actions to be applied to a traffic flow. -- types of actions to be applied to a traffic flow.
-- --
skipping to change at page 49, line 5 skipping to change at page 54, line 5
Specific actions are indicated by qosAction- Specific actions are indicated by qosAction-
Specific which points to an entry of a specific Specific which points to an entry of a specific
action type parameterizing the action in detail." action type parameterizing the action in detail."
REFERENCE REFERENCE
"[MODEL] section 6." "[MODEL] section 6."
::= { qosPolicyClasses 6 } ::= { qosPolicyClasses 6 }
qosActionEntry OBJECT-TYPE qosActionEntry OBJECT-TYPE
SYNTAX QosActionEntry SYNTAX QosActionEntry
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry in the action table allows description of "Each entry in the action table allows description of
one specific action to be applied to traffic." one specific action to be applied to traffic."
PIB-INDEX { qosActionPrid } PIB-INDEX { qosActionPrid }
UNIQUENESS { } UNIQUENESS { }
::= { qosActionTable 1 } ::= { qosActionTable 1 }
QosActionEntry ::= SEQUENCE { QosActionEntry ::= SEQUENCE {
skipping to change at page 50, line 5 skipping to change at page 55, line 5
this datapath. Any other value must point to a valid this datapath. Any other value must point to a valid
(pre-existing) instance of one of:" (pre-existing) instance of one of:"
qosClfrEntry qosClfrEntry
qosMeterEntry qosMeterEntry
qosActionEntry qosActionEntry
qosAlgDropEntry qosAlgDropEntry
qosQEntry." qosQEntry."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { qosActionEntry 2 } ::= { qosActionEntry 2 }
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
qosActionSpecific OBJECT-TYPE qosActionSpecific OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer to an object instance providing additional "A pointer to an object instance providing additional
information for the type of action indicated by this information for the type of action indicated by this
action table entry. action table entry.
This attribute is meaningful only if qosActionType is This attribute is meaningful only if qosActionType is
specific(3). For other action types, this attribute specific(2). For other action types, this attribute
should be NULL. should be NULL.
For the standard actions defined by this PIB module, For the standard actions defined by this PIB module,
this should point to an instance of this should point to an instance of
qosDscpMarkActEntry. For other actions, it may point qosDscpMarkActEntry. For other actions, it may point
to an instance of a PRC defined in some other PIB. to an instance of a PRC defined in some other PIB.
The PRI pointed to must exist prior to installing this The PRI pointed to must exist prior to installing this
action datapath entry." action datapath entry."
::= { qosActionEntry 3 } ::= { qosActionEntry 3 }
skipping to change at page 51, line 5 skipping to change at page 56, line 5
A value of absoluteDrop(3) indicates that the absolute A value of absoluteDrop(3) indicates that the absolute
drop action to be taken, and that no additional drop action to be taken, and that no additional
parameters apply to this action. For this action parameters apply to this action. For this action
type, the value of qosActionSpecific should be type, the value of qosActionSpecific should be
zeroDotZero." zeroDotZero."
::= { qosActionEntry 4 } ::= { qosActionEntry 4 }
-- DSCP Mark Action Table -- DSCP Mark Action Table
-- --
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
-- Rows of this table are pointed to by qosActionSpecific -- Rows of this table are pointed to by qosActionSpecific
-- to provide detailed parameters specific to the DSCP -- to provide detailed parameters specific to the DSCP
-- Mark action. -- Mark action.
-- --
qosDscpMarkActTable OBJECT-TYPE qosDscpMarkActTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosDscpMarkActEntry SYNTAX SEQUENCE OF QosDscpMarkActEntry
PIB-ACCESS install, 3 PIB-ACCESS install, 3
STATUS current STATUS current
skipping to change at page 52, line 5 skipping to change at page 57, line 5
} }
qosDscpMarkActPrid OBJECT-TYPE qosDscpMarkActPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { qosDscpMarkActEntry 1 } ::= { qosDscpMarkActEntry 1 }
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
qosDscpMarkActDscp OBJECT-TYPE qosDscpMarkActDscp OBJECT-TYPE
SYNTAX Dscp SYNTAX Dscp
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DSCP that this Action uses for marking/remarking "The DSCP that this Action uses for marking/remarking
traffic. Note that a DSCP value of -1 is not permit- traffic. Note that a DSCP value of -1 is not permit-
ted in this table. It is quite possible that the ted in this table. It is quite possible that the
only packets subject to this Action are already only packets subject to this Action are already
marked with this DSCP. Note also that Diffserv may marked with this DSCP. Note also that Diffserv may
skipping to change at page 53, line 5 skipping to change at page 58, line 5
SYNTAX QosAlgDropEntry SYNTAX QosAlgDropEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes a process that drops packets "An entry describes a process that drops packets
according to some algorithm. Further details of the according to some algorithm. Further details of the
algorithm type are to be found in qosAlgDropType algorithm type are to be found in qosAlgDropType
and with more detail parameter entry pointed to by and with more detail parameter entry pointed to by
qosAlgDropSpecific when necessary." qosAlgDropSpecific when necessary."
PIB-INDEX { qosAlgDropPrid } PIB-INDEX { qosAlgDropPrid }
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
UNIQUENESS { } UNIQUENESS { }
::= { qosAlgDropTable 1 } ::= { qosAlgDropTable 1 }
QosAlgDropEntry ::= SEQUENCE { QosAlgDropEntry ::= SEQUENCE {
qosAlgDropPrid InstanceId, qosAlgDropPrid InstanceId,
qosAlgDropType INTEGER, qosAlgDropType INTEGER,
qosAlgDropNext Prid, qosAlgDropNext Prid,
qosAlgDropQMeasure Prid, qosAlgDropQMeasure Prid,
qosAlgDropQThreshold Unsigned32, qosAlgDropQThreshold Unsigned32,
skipping to change at page 54, line 5 skipping to change at page 59, line 5
A value of other(1) indicates that the specifics of A value of other(1) indicates that the specifics of
the drop algorithm are specified in some other PIB the drop algorithm are specified in some other PIB
module, and that the qosAlgDropSpecific attribute module, and that the qosAlgDropSpecific attribute
points to an instance of a PRC in that PIB that points to an instance of a PRC in that PIB that
specifies the information necessary to implement the specifies the information necessary to implement the
algorithm. algorithm.
The tailDrop(2) algorithm is described as follows: The tailDrop(2) algorithm is described as follows:
qosAlgDropQThreshold represents the depth of the qosAlgDropQThreshold represents the depth of the
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
queue, pointed to by qosAlgDropQMeasure, at queue, pointed to by qosAlgDropQMeasure, at
which all newly arriving packets will be dropped. which all newly arriving packets will be dropped.
The headDrop(3) algorithm is described as follows: if The headDrop(3) algorithm is described as follows: if
a packet arrives when the current depth of the queue, a packet arrives when the current depth of the queue,
pointed to by qosAlgDropQMeasure, is at pointed to by qosAlgDropQMeasure, is at
qosAlgDropQThreshold, packets currently at the head of qosAlgDropQThreshold, packets currently at the head of
the queue are dropped to make room for the new packet the queue are dropped to make room for the new packet
to be enqueued at the tail of the queue. to be enqueued at the tail of the queue.
skipping to change at page 55, line 5 skipping to change at page 60, line 5
qosMeterEntry qosMeterEntry
qosActionEntry qosActionEntry
qosAlgDropEntry qosAlgDropEntry
qosQEntry." qosQEntry."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { qosAlgDropEntry 3 } ::= { qosAlgDropEntry 3 }
qosAlgDropQMeasure OBJECT-TYPE qosAlgDropQMeasure OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Points to an entry in the qosQTable to indicate "Points to an entry in the qosQTable to indicate
the queue that a drop algorithm is to monitor when the queue that a drop algorithm is to monitor when
deciding whether to drop a packet. deciding whether to drop a packet.
The PRI pointed to must exist prior to installing The PRI pointed to must exist prior to installing
this dropper element." this dropper element."
::= { qosAlgDropEntry 4 } ::= { qosAlgDropEntry 4 }
skipping to change at page 56, line 5 skipping to change at page 61, line 5
Entries with qosAlgDropType equal to other(1) Entries with qosAlgDropType equal to other(1)
must have this point to an instance of a PRC must have this point to an instance of a PRC
defined in another PIB module. defined in another PIB module.
Entries with qosAlgDropType equal to random- Entries with qosAlgDropType equal to random-
Drop(4) must have this point to an entry in Drop(4) must have this point to an entry in
qosRandomDropTable. qosRandomDropTable.
For all other algorithms, this should take the value For all other algorithms, this should take the value
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
zeroDotzero." zeroDotzero."
::= { qosAlgDropEntry 6 } ::= { qosAlgDropEntry 6 }
-- --
-- Random Drop Table -- Random Drop Table
-- --
qosRandomDropTable OBJECT-TYPE qosRandomDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosRandomDropEntry SYNTAX SEQUENCE OF QosRandomDropEntry
skipping to change at page 56, line 38 skipping to change at page 61, line 38
SYNTAX QosRandomDropEntry SYNTAX QosRandomDropEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes a process that drops packets "An entry describes a process that drops packets
according to a random algorithm." according to a random algorithm."
PIB-INDEX { qosRandomDropPrid } PIB-INDEX { qosRandomDropPrid }
UNIQUENESS { qosRandomDropMinThreshBytes, UNIQUENESS { qosRandomDropMinThreshBytes,
qosRandomDropMinThreshPkts, qosRandomDropMinThreshPkts,
qosRandomDropMaxThreshBytes, qosRandomDropMaxThreshBytes,
qosRandomDropMaxThreshPkts, qosRandomDropMaxThreshPkts,
qosRandomDropInvProbMax, qosRandomDropProbMax,
qosRandomDropInvWeight, qosRandomDropInvWeight,
qosRandomDropSamplingRate qosRandomDropSamplingRate
::= { qosRandomDropTable 1 } ::= { qosRandomDropTable 1 }
QosRandomDropEntry ::= SEQUENCE { QosRandomDropEntry ::= SEQUENCE {
qosRandomDropPrid InstanceId, qosRandomDropPrid InstanceId,
qosRandomDropMinThreshBytes Unsigned32, qosRandomDropMinThreshBytes Unsigned32,
qosRandomDropMinThreshPkts Unsigned32, qosRandomDropMinThreshPkts Unsigned32,
qosRandomDropMaxThreshBytes Unsigned32, qosRandomDropMaxThreshBytes Unsigned32,
qosRandomDropMaxThreshPkts Unsigned32, qosRandomDropMaxThreshPkts Unsigned32,
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
qosRandomDropInvProbMax Unsigned32, qosRandomDropProbMax Unsigned32,
qosRandomDropInvWeight Unsigned32, qosRandomDropInvWeight Unsigned32,
qosRandomDropSamplingRate Unsigned32 qosRandomDropSamplingRate Unsigned32
} }
qosRandomDropPrid OBJECT-TYPE qosRandomDropPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { qosRandomDropEntry 1 } ::= { qosRandomDropEntry 1 }
qosRandomDropMinThreshBytes OBJECT-TYPE qosRandomDropMinThreshBytes OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bytes" UNITS "bytes"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The average queue depth in bytes, beyond which "The average queue depth in bytes, beyond which traffic has a
traffic has a non-zero probability of being dropped. non-zero probability of being dropped."
Changes in this variable may or may not be reflected
in the reported value of qosRandomDropMinThreshPkts."
::= { qosRandomDropEntry 2 } ::= { qosRandomDropEntry 2 }
qosRandomDropMinThreshPkts OBJECT-TYPE qosRandomDropMinThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "packets" UNITS "packets"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The average queue depth in packets, beyond which "The average queue depth in packets, beyond which traffic has a
traffic has a non-zero probability of being dropped. non-zero probability of being dropped."
Changes in this variable may or may not be reflected
in the reported value of qosRandomDropMinThreshBytes."
::= { qosRandomDropEntry 3 } ::= { qosRandomDropEntry 3 }
qosRandomDropMaxThreshBytes OBJECT-TYPE qosRandomDropMaxThreshBytes OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bytes" UNITS "bytes"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The average queue depth beyond which traffic has a "The average queue depth beyond which traffic has a probability
indicated by qosRandomDropProbMax of being dropped or
DiffServ QoS Policy Information Base November 2000 marked. Note that this differs from the physical queue limit,
which is stored in qosAlgDropQThreshold."
probability indicated by qosRandomDropInvProbMax
of being dropped or marked. Note that this differs
from the physical queue limit, which is stored in
qosAlgDropQThreshold. Changes in this variable
may or may not be reflected in the reported value of
qosRandomDropMaxThreshPkts."
::= { qosRandomDropEntry 4 } ::= { qosRandomDropEntry 4 }
DiffServ QoS Policy Information Base February 2001
qosRandomDropMaxThreshPkts OBJECT-TYPE qosRandomDropMaxThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "packets" UNITS "packets"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The average queue depth beyond which traffic has a "The average queue depth beyond which traffic has a probability
probability indicated by qosRandomDropInvProbMax indicated by qosRandomDropProbMax of being dropped or
of being dropped or marked. Note that this differs marked. Note that this differs from the physical queue limit,
from the physical queue limit, which is stored in which is stored in qosAlgDropQThreshold."
qosAlgDropQThreshold. Changes in this variable
may or may not be reflected in the reported value of
qosRandomDropMaxThreshBytes."
::= { qosRandomDropEntry 5 } ::= { qosRandomDropEntry 5 }
qosRandomDropInvProbMax OBJECT-TYPE qosRandomDropProbMax OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The worst case random drop probability, expressed as "The worst case random drop probability, expressed in drops per
the inverse of the drop probability. With special thousand packets.
case of the value zero meaning zero probability of
drop.
For example, if every packet may be dropped in the For example, if every packet may be dropped in the worst case
worst case (100%), this has the value of (100%), this has the value 1000. Alternatively, if in the worst
4,294,967,295." case one percent (1%) of traffic may be dropped, it has the value
10."
::= { qosRandomDropEntry 6 } ::= { qosRandomDropEntry 6 }
qosRandomDropInvWeight OBJECT-TYPE qosRandomDropInvWeight OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The weighting of past history in affecting the cal- "The weighting of past history in affecting the calculation of
culation of the current queue average. The moving the current queue average. The moving average of the queue depth
uses the inverse of this value as the factor for the new queue
DiffServ QoS Policy Information Base November 2000 depth, and one minus that inverse as the factor for the
historical average.
average of the queue depth uses the inverse of this
value as the factor for the new queue depth, and one
minus that inverse as the factor for the historical
average.
Implementations may choose to limit the acceptable Implementations may choose to limit the acceptable set of values
set of values to a specified set, such as powers of to a specified set, such as powers of 2."
2."
::= { qosRandomDropEntry 7 } ::= { qosRandomDropEntry 7 }
qosRandomDropSamplingRate OBJECT-TYPE qosRandomDropSamplingRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times per second the queue is sampled
for queue average calculation. A value of zero means DiffServ QoS Policy Information Base February 2001
the queue is sampled approximately each time a packet
is enqueued (or dequeued)." "The number of times per second the queue is sampled for queue
average calculation. A value of zero means the queue is sampled
approximately each time a packet is enqueued (or dequeued)."
::= { qosRandomDropEntry 8 } ::= { qosRandomDropEntry 8 }
-- --
-- Queue Table -- Queue Table
-- --
-- --
-- An entry of qosQTable represents a FIFO queue diffserv
-- functional datapath element as described in [MODEL] section -- functional datapath element as described in [MODEL] section
-- 7.1.1. -- 7.1.1.
-- Notice the specification of scheduling parameters for a queue -- Notice the specification of scheduling parameters for a queue
-- as part of the input to a scheduler functional datapath -- as part of the input to a scheduler functional datapath
-- element as described in [MODEL] section 7.1.2. This allows -- element as described in [MODEL] section 7.1.2. This allows
-- building of hierarchical queuing/scheduling.
-- A queue therefore is parameterized by: -- A queue therefore is parameterized by:
-- 1. Which scheduler will service this queue, qosQNext. -- 1. Which scheduler will service this queue, qosQNext.
-- 2. How the scheduler will service this queue, with respect -- 2. How the scheduler will service this queue, with respect
-- to all the other queues the same scheduler needs to service, -- to all the other queues the same scheduler needs to service,
-- qosQWeight. |
--
-- Notice one or more upstream diffserv data path element may share,
-- point to, a qosQTable entry as described in [MODEL] section
-- 7.1.1.
-- --
qosQTable OBJECT-TYPE qosQTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosQEntry SYNTAX SEQUENCE OF QosQEntry
PIB-ACCESS install, 4 PIB-ACCESS install, 5
DiffServ QoS Policy Information Base November 2000
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Queue Table enumerates the individual queues on "The Queue Table enumerates the individual queues on
an interface." an interface."
::= { qosPolicyClasses 11 } ::= { qosPolicyClasses 11 }
qosQEntry OBJECT-TYPE qosQEntry OBJECT-TYPE
SYNTAX QosQEntry SYNTAX QosQEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Queue Table describes a single queue "An entry in the Queue Table describes a single queue
DiffServ QoS Policy Information Base February 2001
in one direction on an interface." in one direction on an interface."
PIB-INDEX { qosQPrid } PIB-INDEX { qosQPrid }
UNIQUENESS { } UNIQUENESS { }
::= { qosQTable 1 } ::= { qosQTable 1 }
QosQEntry ::= SEQUENCE { QosQEntry ::= SEQUENCE {
qosQPrid InstanceId, qosQPrid InstanceId,
qosQNext Prid, qosQNext Prid,
qosQSchdParam Prid qosQWeight Prid,
qosQShaper Prid
} }
qosQPrid OBJECT-TYPE qosQPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { qosQEntry 1 } ::= { qosQEntry 1 }
skipping to change at page 61, line 5 skipping to change at page 65, line 38
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This selects the next diffserv functional datapath "This selects the next diffserv functional datapath
element to handle traffic for this data path. This element to handle traffic for this data path. This
value must point to a valid (pre-existing) instance value must point to a valid (pre-existing) instance
of one of: of one of:
qosSchedulerEntry" qosSchedulerEntry"
::= { qosQEntry 2 } ::= { qosQEntry 2 }
DiffServ QoS Policy Information Base November 2000 qosQWeight OBJECT-TYPE
qosQSchdParam OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This Prid indicates the entry in "This Prid indicates the entry in qosAssuredRateTable
qosSchdParamTable the scheduler, pointed to by the scheduler, pointed to by qosQNext, should use to service
qosQNext, should use to service this queue. The PRI this queue. If this value is zeroDotZero, then qosQShaper
pointed to must exist prior to installing this queue must not be zeroDotZero. If this value is not zeroDotZero
element." then the instance pointed to must exist prior to installing
this entry."
DiffServ QoS Policy Information Base February 2001
::= { qosQEntry 3 } ::= { qosQEntry 3 }
qosQShaper OBJECT-TYPE
SYNTAX Prid
STATUS current
DESCRIPTION
"This Prid indicates the entry in qosShapingRateTable
the scheduler, pointed to by qosQNext, should use to service
this queue. If this value is zeroDotZero, then qosQWeight
must not be zeroDotZero. If this value is not zeroDotZero
then the instance pointed to must exist prior to installing
this entry."
::= { qosQEntry 4 }
-- --
-- Scheduler Table -- Scheduler Table
-- --
--
-- The Scheduler Table is used for representing packet schedulers: -- The Scheduler Table is used for representing packet schedulers:
-- it provides flexibility for multiple scheduling algorithms, each -- it provides flexibility for multiple scheduling algorithms, each
-- servicing multiple queues, to be used on the same logical/physical -- servicing multiple queues, to be used on the same logical/physical
-- interface. -- interface.
-- Notice the servicing parameters the scheduler uses is -- Notice the servicing parameters the scheduler uses is
-- specified by each of its upstream functional datapath elements, -- specified by each of its upstream functional datapath elements,
-- most likely queues or schedulers. -- most likely queues or schedulers.
-- The coordination and coherency between the servicing parameters -- The coordination and coherency between the servicing parameters
-- of the scheduler's upstream functional datapath elements must -- of the scheduler's upstream functional datapath elements must
-- be maintained for the scheduler to function correctly. -- be maintained for the scheduler to function correctly.
-- --
-- The qosSchedulerShaper attribute is used for specifying |
-- the servicing parameters for output of a scheduler when its -- the servicing parameters for output of a scheduler when its
-- downstream functional datapath element is another scheduler. -- downstream functional datapath element is another scheduler.
-- This is used for building hierarchical queue/scheduler. -- This is used for building hierarchical queue/scheduler.
-- |
-- More discussion of the scheduler functional data path element
-- is in [MODEL] section 7.1.2.
-- --
qosSchedulerTable OBJECT-TYPE qosSchedulerTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosSchedulerEntry SYNTAX SEQUENCE OF QosSchedulerEntry
PIB-ACCESS install, 5 PIB-ACCESS install, 6
STATUS current STATUS current
DESCRIPTION DESCRIPTION
DiffServ QoS Policy Information Base February 2001
"The Scheduler Table enumerates packet schedulers. "The Scheduler Table enumerates packet schedulers.
Multiple scheduling algorithms can be used on a given Multiple scheduling algorithms can be used on a given
interface, with each algorithm described by one interface, with each algorithm described by one
qosSchedulerEntry." qosSchedulerEntry."
REFERENCE REFERENCE
"[MODEL] section 7.1.2" "[MODEL] section 7.1.2"
DiffServ QoS Policy Information Base November 2000
::= { qosPolicyClasses 12 } ::= { qosPolicyClasses 12 }
qosSchedulerEntry OBJECT-TYPE qosSchedulerEntry OBJECT-TYPE
SYNTAX QosSchedulerEntry SYNTAX QosSchedulerEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Scheduler Table describing a single "An entry in the Scheduler Table describing a single
instance of a scheduling algorithm." instance of a scheduling algorithm."
PIB-INDEX { qosSchedulerPrid } PIB-INDEX { qosSchedulerPrid }
UNIQUENESS { } UNIQUENESS { }
::= { qosSchedulerTable 1 } ::= { qosSchedulerTable 1 }
QosSchedulerEntry ::= SEQUENCE { QosSchedulerEntry ::= SEQUENCE {
qosSchedulerPrid InstanceId, qosSchedulerPrid InstanceId,
qosSchedulerNext Prid, qosSchedulerNext Prid,
qosSchedulerMethod INTEGER, qosSchedulerMethod OBJECT IDENTIFIER,
qosSchedulerSchdParam Prid qosSchedulerWeight Prid,
qosSchedulerShaper Prid
} }
qosSchedulerPrid OBJECT-TYPE qosSchedulerPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { qosSchedulerEntry 1 } ::= { qosSchedulerEntry 1 }
qosSchedulerNext OBJECT-TYPE qosSchedulerSucceedNext OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This selects the next diffserv functional datapath "This selects the next diffserv functional datapath
element to handle traffic for this data path. element to handle traffic for this data path.
DiffServ QoS Policy Information Base February 2001
A value of zeroDotZero in this attribute indicates no A value of zeroDotZero in this attribute indicates no
further Diffserv treatment is performed on traffic of further Diffserv treatment is performed on traffic of
this datapath. The use of zeroDotZero is the normal this datapath. The use of zeroDotZero is the normal
usage for the last functional datapath element. Any usage for the last functional datapath element. Any
value other than zeroDotZero must point to a valid value other than zeroDotZero must point to a valid
(pre-existing) instance of one of: (pre-existing) instance of one of:
qosSchedulerEntry qosSchedulerEntry
qosQEntry (as indicated by [MODEL] section
7.1.4),
DiffServ QoS Policy Information Base November 2000 or
qosQEntry (as indicated by [MODEL] section qosClfrEntry
7.1.4). qosMeterEntry
qosActionEntry
qosAlgDropEntry (for building multiple TCB's for the same
data path).
This can point to another qosSchedulerEntry This can point to another qosSchedulerEntry
for implementation of multiple scheduler methods for for implementation of multiple scheduler methods for
the same datapath, and for implementation of the same datapath, and for implementation of
hierarchical schedulers." hierarchical schedulers."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { qosSchedulerEntry 2 } ::= { qosSchedulerEntry 2 }
qosSchedulerMethod OBJECT-TYPE qosSchedulerMethod OBJECT-TYPE
SYNTAX INTEGER { SYNTAX OBJECT IDENTIFIER
priorityq(2), -- Priority Queueing
wrr(3), -- Weighted Round Robin
wfq(4), -- Weighted Fair Queuing
wirr(5), -- Weighted Interleaved Round Robin
bsp(6) -- Bounded Strict Priority
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The scheduling algorithm used by this Scheduler. "The scheduling algorithm used by this Scheduler. Standard values
for generic algorithms: qosSchedulerPriority, qosSchedulerWRR,
A value of priorityq(2) is used to indicate strict and qosSchedulerWFQ are specified in this PIB;
priority queueing: only the qosSchdParamPriority additional values may be further specified in other PIBs."
attributes of the queues feeding this scheduler are
used when determining the next packet to schedule.
A value of wrr(3) indicates weighted round-robin
scheduling. Packets are scheduled from each of the
queues feeding this scheduler according to all of the
parameters of the qosSchdParam entry.
A value of wfq(4) indicates weighted fair queueing
scheduling. Packets are scheduled from each of the
queues feeding this scheduler according to all the
parameters of the QosSchdParamEntry directed
from qosQueue entry.
A value of wirr(5) indicates weighted interleaved
roundrobin queueing scheduling. Packets are
scheduled from each of the queues feeding this
scheduler according to all the parameters of the
QosSchdParamEntry directed from qosQueue
entry.
DiffServ QoS Policy Information Base November 2000
A value of bsp(6) indicates bounded strict priority
scheduling. Packets are scheduled from each of the
queues feeding this scheduler according to all the
parameters of the QosSchdParamEntry directed
from qosQueue entry."
REFERENCE REFERENCE
"[MODEL] section 7.1.2" "[MODEL] section 7.1.2"
::= { qosSchedulerEntry 3 } ::= { qosSchedulerEntry 3 }
qosSchedulerSchdParam OBJECT-TYPE qosSchedulerWeight OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This Prid indicates the entry in "This Prid indicates the entry in qosAssuredRateTable
qosSchdParamTable the higher level scheduler, which indicates the priority or minimum output rate from this
pointed to by qosSchedulerNext, should use to
service the output of this scheduler. This attribute DiffServ QoS Policy Information Base February 2001
is only used when there is more than one level of
scheduler. A value of 0.0 should be sent to indicate scheduler. This attribute is only used when there is more than
that this attribute is not used." one level of scheduler. It should have the value of zeroDotZero
when not used."
DEFVAL { zeroDotZero }
::= { qosSchedulerEntry 4 } ::= { qosSchedulerEntry 4 }
qosSchedulerShaper OBJECT-TYPE
SYNTAX Prid
STATUS current
DESCRIPTION
"This Prid indicates the entry in qosShapingRateTable
which indicates the maximum output rate from this scheduler.
This attribute is only used when there is more than one level of
scheduler. It should have the value of zeroDotZero when not
used."
DEFVAL { zeroDotZero }
::= { qosSchedulerEntry 5 }
-- --
-- Assured Rate Parameters Table
--
-- This is used to specify parameters for the inputs to a
-- work-conserving scheduler.
-- --
-- The scheduling parameters are separate from the Queue Entries -- The scheduling parameters are separate from the Queue Entries
-- for reusability and for usage by both queues and schedulers, -- for reusability and for usage by both queues and schedulers,
-- and this follows the separation of datapath elements from -- and this follows the separation of datapath elements from
-- parameterization approach used through out this PIB.
-- Usage of scheduling parameter table entry by schedulers allow -- Usage of scheduling parameter table entry by schedulers allow
-- building of hierarchical scheduling. -- building of hierarchical scheduling.
-- --
qosSchdParamTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosSchdParamEntry
DiffServ QoS Policy Information Base November 2000 qosAssuredRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosAssuredRateEntry
PIB-ACCESS install, 7 PIB-ACCESS install, 5
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Scheduling Parameter Table enumerates individual "The Assured Rate Table enumerates individual
sets of scheduling parameter that can be used/reused sets of scheduling parameter that can be used/reused
by Queues and Schedulers." by Queues and Schedulers."
::= { qosPolicyClasses 13 } ::= { qosPolicyClasses 13 }
qosSchdParamEntry OBJECT-TYPE DiffServ QoS Policy Information Base February 2001
SYNTAX QosSchdParamEntry
qosAssuredRateEntry OBJECT-TYPE
SYNTAX QosAssuredRateEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Scheduling Parameter Table describes "An entry in the Assured Rate Table describes
a single set of scheduling parameter for use by a single set of scheduling parameter for use by
queues and schedulers. queues and schedulers."
PIB-INDEX { qosAssuredRatePrid }
Notice multiple inter-mixed Queue and Scheduler UNIQUENESS { qosAssuredRatePriority,
entries can use the same Scheduler Parameter entry." qosAssuredRateAbs,
PIB-INDEX { qosSchdParamPrid } qosAssuredRateRel }
UNIQUENESS { qosSchdParamPriority, ::= { qosAssuredRateTable 1 }
qosSchdParamMinRateAbs,
qosSchdParamMinRateRel,
qosSchdParamMaxRateAbs,
qosSchdParamMaxRateRel }
::= { qosSchdParamTable 1 }
QosSchdParamEntry ::= SEQUENCE { QosAssuredRateEntry ::= SEQUENCE {
qosSchdParamPrid InstanceId, qosAssuredRatePrid InstanceId,
qosSchdParamPriority Unsigned32, qosAssuredRatePriority Unsigned32,
qosSchdParamMinRateAbs Unsigned32, qosAssuredRateAbs Unsigned32,
qosSchdParamMinRateRel Unsigned32, qosAssuredRateRel Unsigned32
qosSchdParamMaxRateAbs Unsigned32,
qosSchdParamMaxRateRel Unsigned32
} }
qosSchdParamPrid OBJECT-TYPE qosAssuredRatePrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { qosSchdParamEntry 1 } ::= { qosAssuredRateEntry 1 }
DiffServ QoS Policy Information Base November 2000
qosSchdParamPriority OBJECT-TYPE qosAssuredRatePriority OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The priority of this queue, to be used as a parame- "The priority of this input to the associated scheduler, relative
ter to the next scheduler element downstream from to the scheduler's other inputs."
this one." ::= { qosAssuredRateEntry 2 }
::= { qosSchdParamEntry 2 }
qosSchdParamMinRateAbs OBJECT-TYPE qosAssuredRateAbs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "kilobits per second" UNITS "kilobits per second"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
DiffServ QoS Policy Information Base February 2001
"The minimum absolute rate, in kilobits/sec, that a "The minimum absolute rate, in kilobits/sec, that a
downstream scheduler element should allocate to this downstream scheduler element should allocate to this
queue. If the value is zero, then there is effec- queue. If the value is zero, then there is effec-
tively no minimum rate guarantee. If the value is tively no minimum rate guarantee. If the value is
non-zero, the scheduler will assure the servicing of non-zero, the scheduler will assure the servicing of
this queue to at least this rate. this queue to at least this rate.
Note that this attribute's value is coupled to that Note that this attribute's value is coupled to that
of qosSchdParamMinRateRel: changes to one will of qosAssuredRateRel: changes to one will
affect the value of the other. They are linked by the affect the value of the other. They are linked by the
following equation: following equation:
qosSchdParamMinRateRel = qosSchdParamMinRateAbs * 10,000,000/ifSpeed qosAssuredRateRel = qosAssuredRateAbs * 10000/ifSpeed
or, if appropriate: or, if appropriate:
qosSchdParamMinRateRel = qosSchdParamMinRateAbs * 10 / ifHighSpeed" qosAssuredRateRel = qosAssuredRateAbs * 10000 / ifHighSpeed"
REFERENCE REFERENCE
"ifSpeed, ifHighSpeed from [IFMIB]" "ifSpeed, ifHighSpeed from [IFMIB]"
::= { qosSchdParamEntry 3 } ::= { qosAssuredRateEntry 3 }
qosSchdParamMinRateRel OBJECT-TYPE qosAssuredRateRel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum rate that a downstream scheduler element "The minimum rate that a downstream scheduler element
should allocate to this queue, relative to the max- should allocate to this queue, relative to the max-
imum rate of the interface as reported by ifSpeed or imum rate of the interface as reported by ifSpeed or
ifHighSpeed, in units of 1/10,000 of 1. If the value ifHighSpeed, in units of 1/10,000 of 1. If the value
DiffServ QoS Policy Information Base November 2000
is zero, then there is effectively no minimum rate is zero, then there is effectively no minimum rate
guarantee. If the value is non-zero, the scheduler guarantee. If the value is non-zero, the scheduler
will assure the servicing of this queue to at least will assure the servicing of this queue to at least
this rate. this rate.
Note that this attribute's value is coupled to that Note that this attribute's value is coupled to that
of qosSchdParamMinRateAbs: changes to one will of qosAssuredRateAbs: changes to one will
affect the value of the other. They are linked by the affect the value of the other. They are linked by the
following equation: following equation:
qosSchdParamMinRateAbs = ifSpeed * qosSchdParamMinRateRel/10,000,000 qosAssuredRateAbs = ifSpeed * qosAssuredRateRel/10000
or, if appropriate: or, if appropriate:
qosSchdParamMinRateAbs = ifHighSpeed * qosSchdParamMinRateRel / 10" qosAssuredRateAbs = ifHighSpeed * qosAssuredRateRel/10000"
DiffServ QoS Policy Information Base February 2001
REFERENCE REFERENCE
"ifSpeed, ifHighSpeed from [IFMIB]" "ifSpeed, ifHighSpeed from [IFMIB]"
::= { qosSchdParamEntry 4 } ::= { qosAssuredRateEntry 4 }
qosSchdParamMaxRateAbs OBJECT-TYPE --
-- Shaping Rate Table
--
-- This contains attributes that are used to specify
-- non-work-conserving parameters to a scheduler for the purpose
-- of traffic shaping. These attributes limits the servicing of
-- the queue/scheduler, in affect, shaping the output of the
-- queue/scheduler, as described in [MODEL] section 7.2.
--
-- The scheduling parameters are separate from the Queue Entries
-- for reusability and for usage by both queues and schedulers,
-- and this follows the separation of data path elements from
-- parameterization approach used through out this PIB.
-- Usage of scheduling parameter table entry by schedulers allow
-- building of hierarchical scheduling.
--
qosShapingRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosShapingRateEntry
PIB-ACCESS install, 6
STATUS current
DESCRIPTION
"The Shaping Rate Table enumerates individual
sets of scheduling parameter that can be used/reused
by Queues and Schedulers."
::= { qosPolicyClasses 14 }
qosShapingRateEntry OBJECT-TYPE
SYNTAX QosShapingRateEntry
STATUS current
DESCRIPTION
"An entry in the Assured Rate Table describes
a single set of scheduling parameter for use by
queues and schedulers."
PIB-INDEX { qosShapingRatePrid }
UNIQUENESS { qosShapingRateLevel,
qosShapingRateAbs,
qosShapingRateRel,
qosShapingRateThreshold }
DiffServ QoS Policy Information Base February 2001
::= { qosShapingRateTable 1 }
QosShapingRateEntry ::= SEQUENCE {
qosShapingRatePrid InstanceId,
qosShapingRateLevel Unsigned32,
qosShapingRateAbs Unsigned32,
qosShapingRateRel Unsigned32,
qosShapingRateThreshold BurstSize
}
qosShapingRatePrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { qosShapingRateEntry 1 }
qosShapingRateLevel OBJECT-TYPE
SYNTAX Unsigned32
STATUS current
DESCRIPTION
"An index that indicates which level of a multi-rate shaper is
being given its parameters. By convention, increasing levels have
increasing rates."
::= { qosShapingRateEntry 2 }
qosShapingRateAbs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "kilobits per second" UNITS "kilobits per second"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum rate in kilobits/sec that a downstream "The maximum rate in kilobits/sec that a downstream
scheduler element should allocate to this queue. If scheduler element should allocate to this queue. If
the value is zero, then there is effectively no max- the value is zero, then there is effectively no max-
imum rate limit and that the scheduler should attempt imum rate limit and that the scheduler should attempt
to be work-conserving for this queue. If the value to be work-conserving for this queue. If the value
is non-zero, the scheduler will limit the servicing is non-zero, the scheduler will limit the servicing
of this queue to, at most, this rate in a non-work- of this queue to, at most, this rate in a non-work-
conserving manner. conserving manner.
DiffServ QoS Policy Information Base February 2001
Note that this attribute's value is coupled to that Note that this attribute's value is coupled to that
of qosSchdParamMaxRateRel: changes to one will of qosShapingRateRel: changes to one will
affect the value of the other. They are linked by the affect the value of the other. They are linked by the
following equation: following equation:
qosSchdParamMaxRateRel = qosSchdParamMaxRateAbs * 10,000,000/ifSpeed qosShapingRateRel = qosShapingRateAbs * 10000/ifSpeed
or, if appropriate: or, if appropriate:
qosSchdParamMaxRateRel = qosSchdParamMaxRateAbs * 10 / ifHighSpeed" qosShapingRateRel = qosShapingRateAbs * 10000/ifHighSpeed"
REFERENCE REFERENCE
DiffServ QoS Policy Information Base November 2000
"ifSpeed, ifHighSpeed from [IFMIB]" "ifSpeed, ifHighSpeed from [IFMIB]"
::= { qosSchdParamEntry 5 } ::= { qosShapingRateEntry 3 }
qosSchdParamMaxRateRel OBJECT-TYPE qosShapingRateRel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum rate that a downstream scheduler element "The maximum rate that a downstream scheduler element
should allocate to this queue, relative to the max- should allocate to this queue, relative to the max-
imum rate of the interface as reported by ifSpeed or imum rate of the interface as reported by ifSpeed or
ifHighSpeed, in units of 1/10,000 of 1. If the value ifHighSpeed, in units of 1/10,000 of 1. If the value
is zero, then there is effectively no maximum rate is zero, then there is effectively no maximum rate
limit and the scheduler should attempt to be work- limit and the scheduler should attempt to be work-
conserving for this queue. If the value is non-zero, conserving for this queue. If the value is non-zero,
the scheduler will limit the servicing of this queue the scheduler will limit the servicing of this queue
to, at most, this rate in a non-work-conserving to, at most, this rate in a non-work-conserving
manner. manner.
Note that this attribute's value is coupled to that Note that this attribute's value is coupled to that
of qosSchdParamMaxRateAbs: changes to one will of qosShapingRateAbs: changes to one will
affect the value of the other. They are linked by the affect the value of the other. They are linked by the
following equation: following equation:
qosSchdParamMaxRateAbs = ifSpeed * qosSchdParamMaxRateRel/10,000,000 qosShapingRateAbs = ifSpeed * qosShapingRateRel/10000
or, if appropriate: or, if appropriate:
qosSchdParamMaxRateAbs = ifHighSpeed * qosSchdParamMaxRateRel / 10" qosShapingRateAbs = ifHighSpeed * qosShapingRateRel/10000"
REFERENCE REFERENCE
"ifSpeed, ifHighSpeed from [IFMIB]" "ifSpeed, ifHighSpeed from [IFMIB]"
::= { qosSchdParamEntry 6 } ::= { qosShapingRateEntry 4 }
DiffServ QoS Policy Information Base February 2001
qosShapingRateThreshold OBJECT-TYPE
SYNTAX BurstSize
UNITS "Bytes"
STATUS current
DESCRIPTION
"The number of bytes of queue depth at which the rate of a
multi-rate scheduler will increase to the next output rate. In
the last conceptual row for such a shaper, this threshold is
ignored and by convention is zero."
REFERENCE
"RFC 2963"
::= { qosShapingRateEntry 5 }
--
-- Parameters Section
--
-- The Parameters Section defines parameter objects that can be used for
-- specific attributes defined in the PIB PRCs.
qosTBParameters OBJECT IDENTIFIER ::= { qosPolicyParameters 1 }
qosSchedulerParameters OBJECT IDENTIFIER ::= { qosPolicyParameters 2 }
--
-- Token Bucket Type Parameters
--
qosTBParamSimpleTokenBucket OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This value indicates the use of a Two Parameter Token Bucket
as described in [MODEL] section 5.2.3."
REFERENCE
"[MODEL] sections 5 and 7.1.2"
::= { qosTBParameters 1 }
qosTBParamAvgRate OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This value indicates the use of an Average Rate Meter as
described in [MODEL] section 5.2.1."
REFERENCE
DiffServ QoS Policy Information Base February 2001
"[MODEL] sections 5 and 7.1.2"
::= { qosTBParameters 4 }
qosTBParamSrTCMBlind OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This value indicates the use of Single Rate Three Color Marker
Metering as defined by RFC 2697, with `Color Blind' mode as
described by the RFC."
REFERENCE
"[MODEL] sections 5 and 7.1.2"
::= { qosTBParameters 5 }
qosTBParamSrTCMAware OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This value indicates the use of Single Rate Three Color Marker
Metering as defined by RFC 2697, with `Color Aware' mode as
described by the RFC."
REFERENCE
"[MODEL] sections 5 and 7.1.2"
::= { qosTBParameters 6 }
qosTBParamTrTCMBlind OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This value indicates the use of Two Rate Three Color Marker
Metering as defined by RFC 2698, with `Color Blind' mode as
described by the RFC."
REFERENCE
"[MODEL] sections 5 and 7.1.2"
::= { qosTBParameters 7 }
qosTBParamTrTCMAware OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This value indicates the use of Two Rate Three Color Marker
Metering as defined by RFC 2698, with `Color Aware' mode as
described by the RFC."
REFERENCE
"[MODEL] sections 5 and 7.1.2"
DiffServ QoS Policy Information Base February 2001
::= { qosTBParameters 8 }
qosTBParamTswTCM OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This value indicates the use of Time Sliding Window
Three Color Marker Metering as defined by RFC 2859."
REFERENCE
"[MODEL] sections 5 and 7.1.2"
::= { qosTBParameters 9 }
--
-- Scheduler Method Parameters
--
qosSchedulerPriority OBJECT-IDENTITY
STATUS current
DESCRIPTION
"For use with qosSchedulerMethod and qosIfSchedulingCapsServiceDisc
to indicate Priority scheduling method, defined as an algorithm in
which the presence of data in a queue or set of queues absolutely
precludes dequeue from another queue or set of queues. Notice
attributes from qosAssuredRateEntry of the queues/schedulers feeding
this scheduler are used when determining the next packet to
schedule."
REFERENCE
"[MODEL] section 7.1.2"
::= { qosSchedulerParameters 1 }
qosSchedulerWRR OBJECT-IDENTITY
STATUS current
DESCRIPTION
"For use with qosSchedulerMethod and qosIfSchedulingCapsServiceDisc
to indicate Weighted Round scheduling method, defined as any
algorithm
in which a set of queues are visited in a fixed order, and varying
amounts of traffic are removed from each queue in turn to implement
an
average output rate by class. Notice attributes from
qosAssuredRateEntry of the queues/schedulers feeding this scheduler
are
used when determining the next packet to schedule."
REFERENCE
"[MODEL] section 7.1.2"
::= { qosSchedulerParameters 2 }
DiffServ QoS Policy Information Base February 2001
qosSchedulerWFQ OBJECT-IDENTITY
STATUS current
DESCRIPTION
"For use with qosSchedulerMethod and qosIfSchedulingCapsServiceDisc
to indicate Weighted Fair Queueing scheduling method, defined as any
algorithm in which a set of queues are conceptually visited in some
order, to implement an average output rate by class. Notice
attributes from qosAssuredRateEntry of the queues/schedulers feeding
this scheduler are used when determining the next packet to
schedule."
REFERENCE
"[MODEL] section 7.1.2"
::= { qosSchedulerParameters 3 }
-- --
-- Conformance Section -- Conformance Section
-- --
qosPolicyPibConformance qosPolicyPibConformance
OBJECT IDENTIFIER ::= { qosPolicyPib 3 } OBJECT IDENTIFIER ::= { qosPolicyPib 3 }
qosPolicyPibCompliances qosPolicyPibCompliances
DiffServ QoS Policy Information Base November 2000
OBJECT IDENTIFIER ::= { qosPolicyPibConformance 1 } OBJECT IDENTIFIER ::= { qosPolicyPibConformance 1 }
qosPolicyPibGroups qosPolicyPibGroups
OBJECT IDENTIFIER ::= { qosPolicyPibConformance 2 } OBJECT IDENTIFIER ::= { qosPolicyPibConformance 2 }
qosPolicyPibCompliance MODULE-COMPLIANCE qosPolicyPibCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the "Describes the requirements for conformance to the
QoS Policy PIB." QoS Policy PIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
qosPibDataPathGroup, qosPibDataPathGroup,
qosPibClfrGroup, qosPibClfrGroup,
qosPibClfrElementGroup, qosPibClfrElementGroup,
qosPibActionGroup, qosPibActionGroup,
qosPibAlgDropGroup, qosPibAlgDropGroup,
qosPibQGroup, qosPibQGroup,
qosPibSchedulerGroup, qosPibSchedulerGroup,
qosPibSchdParamGroup } qosPibAssuredRateGroup,
DiffServ QoS Policy Information Base February 2001
qosPibShapingRateGroup }
GROUP qosPibMeterGroup GROUP qosPibMeterGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that implement "This group is mandatory for devices that implement
metering functions." metering functions."
GROUP qosPibTBMeterGroup GROUP qosPibTBParamGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that implement "This group is mandatory for devices that implement
token-bucket metering functions." token-bucket metering functions."
GROUP qosPibDscpMarkActGroup GROUP qosPibDscpMarkActGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that implement "This group is mandatory for devices that implement
DSCP-Marking functions." DSCP-Marking functions."
GROUP qosPibRandomDropGroup GROUP qosPibRandomDropGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that implement "This group is mandatory for devices that implement
Random Drop functions." Random Drop functions."
DiffServ QoS Policy Information Base November 2000
OBJECT qosClfrId OBJECT qosClfrId
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosClfrElementClfrId OBJECT qosClfrElementClfrId
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosClfrElementOrder OBJECT qosClfrElementPrecedence
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
DiffServ QoS Policy Information Base February 2001
OBJECT qosClfrElementNext OBJECT qosClfrElementNext
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosClfrElementSpecific OBJECT qosClfrElementSpecific
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
skipping to change at page 71, line 4 skipping to change at page 80, line 30
"Install support is not required." "Install support is not required."
OBJECT qosMeterFailNext OBJECT qosMeterFailNext
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosMeterSpecific OBJECT qosMeterSpecific
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
DiffServ QoS Policy Information Base November 2000
"Install support is not required." "Install support is not required."
OBJECT qosTBMeterType OBJECT qosTBParamType
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosTBMeterRate OBJECT qosTBParamRate
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosTBMeterBurstSize OBJECT qosTBParamBurstSize
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
DiffServ QoS Policy Information Base February 2001
"Install support is not required." "Install support is not required."
OBJECT qosTBMeterInterval OBJECT qosTBParamInterval
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosActionNext OBJECT qosActionNext
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosActionSpecific OBJECT qosActionSpecific
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosAlgDropType OBJECT qosAlgDropType
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
DiffServ QoS Policy Information Base November 2000
OBJECT qosAlgDropNext OBJECT qosAlgDropNext
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosAlgDropQMeasure OBJECT qosAlgDropQMeasure
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosAlgDropQThreshold OBJECT qosAlgDropQThreshold
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
DiffServ QoS Policy Information Base February 2001
OBJECT qosAlgDropSpecific OBJECT qosAlgDropSpecific
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosRandomDropMinThreshBytes OBJECT qosRandomDropMinThreshBytes
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
skipping to change at page 73, line 4 skipping to change at page 82, line 30
"Install support is not required." "Install support is not required."
OBJECT qosRandomDropMaxThreshBytes OBJECT qosRandomDropMaxThreshBytes
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosRandomDropMaxThreshPkts OBJECT qosRandomDropMaxThreshPkts
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
DiffServ QoS Policy Information Base November 2000
"Install support is not required." "Install support is not required."
OBJECT qosRandomDropInvWeight OBJECT qosRandomDropInvWeight
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosRandomDropSamplingRate OBJECT qosRandomDropSamplingRate
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosRandomDropInvProbMax OBJECT qosRandomDropProbMax
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
DiffServ QoS Policy Information Base February 2001
"Install support is not required." "Install support is not required."
OBJECT qosQNext OBJECT qosQNext
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosQSchdParam OBJECT qosQWeight
MIN-ACCESS notify
DESCRIPTION
"Install support is not required."
OBJECT qosQShaper
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosSchedulerMethod OBJECT qosSchedulerMethod
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosSchedulerSchdParam OBJECT qosSchedulerWeight
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
DiffServ QoS Policy Information Base November 2000 OBJECT qosSchedulerShaper
MIN-ACCESS notify
DESCRIPTION
"Install support is not required."
OBJECT qosSchedulerNext OBJECT qosSchedulerNext
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosSchdParamPriority DiffServ QoS Policy Information Base February 2001
OBJECT qosAssuredRatePriority
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosSchdParamMinRateAbs OBJECT qosAssuredRateAbs
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosSchdParamMinRateRel OBJECT qosAssuredRateRel
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosSchdParamMaxRateAbs OBJECT qosShapingRateAbs
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
OBJECT qosSchdParamMaxRateRel OBJECT qosShapingRateRel
MIN-ACCESS notify
DESCRIPTION
"Install support is not required."
OBJECT qosShapingRateThreshold
MIN-ACCESS notify MIN-ACCESS notify
DESCRIPTION DESCRIPTION
"Install support is not required." "Install support is not required."
::= { qosPibCompliances 1 } ::= { qosPibCompliances 1 }
qosPibDataPathGroup OBJECT-GROUP qosPibDataPathGroup OBJECT-GROUP
OBJECTS { OBJECTS {
qosDataPathStart qosDataPathStart
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
"The Data Path Group defines the PIB Objects that "The Data Path Group defines the PIB Objects that
describe a data path." describe a data path."
::= { qosPibGroups 1 } ::= { qosPibGroups 1 }
qosPibClfrGroup OBJECT-GROUP qosPibClfrGroup OBJECT-GROUP
OBJECTS { OBJECTS {
qosClfrId qosClfrId
} }
STATUS current STATUS current
skipping to change at page 75, line 43 skipping to change at page 85, line 43
OBJECTS { OBJECTS {
qosMeterSucceedNext, qosMeterFailNext, qosMeterSucceedNext, qosMeterFailNext,
qosMeterSpecific qosMeterSpecific
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Meter Group defines the objects used in describ- "The Meter Group defines the objects used in describ-
ing a generic meter element." ing a generic meter element."
::= { qosPibGroups 5 } ::= { qosPibGroups 5 }
qosPibTBMeterGroup OBJECT-GROUP qosPibTBParamGroup OBJECT-GROUP
OBJECTS { OBJECTS {
qosTBMeterType, qosTBMeterRate, qosTBParamType, qosTBParamRate,
qosTBMeterBurstSize, qosTBMeterInterval qosTBParamBurstSize, qosTBParamInterval
} }
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Token-Bucket Meter Group defines the objects "The Token-Bucket Parameter Group defines the objects
used in describing a single-rate token bucket meter used in describing a single-rate token bucket meter
element." element."
::= { qosPibGroups 6 } ::= { qosPibGroups 6 }
qosPibActionGroup OBJECT-GROUP qosPibActionGroup OBJECT-GROUP
OBJECTS { OBJECTS {
qosActionNext, qosActionSpecific qosActionNext, qosActionSpecific
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 77, line 5 skipping to change at page 87, line 5
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Algorithmic Drop Group contains the objects that "The Algorithmic Drop Group contains the objects that
describe algorithmic dropper operation and configura- describe algorithmic dropper operation and configura-
tion." tion."
::= { qosPibGroups 12 } ::= { qosPibGroups 12 }
qosPibRandomDropGroup OBJECT-GROUP qosPibRandomDropGroup OBJECT-GROUP
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
OBJECTS { OBJECTS {
qosRandomDropMinThreshBytes, qosRandomDropMinThreshBytes,
qosRandomDropMinThreshPkts, qosRandomDropMinThreshPkts,
qosRandomDropMaxThreshBytes, qosRandomDropMaxThreshBytes,
qosRandomDropMaxThreshPkts, qosRandomDropMaxThreshPkts,
qosRandomDropInvProbMax, qosRandomDropProbMax,
qosRandomDropInvWeight, qosRandomDropInvWeight,
qosRandomDropSamplingRate qosRandomDropSamplingRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Random Drop Group augments the Algorithmic Drop Group for "The Random Drop Group augments the Algorithmic Drop Group for
random dropper operation and configuration." random dropper operation and configuration."
::= { qosPibGroups 13 } ::= { qosPibGroups 13 }
qosPibQGroup OBJECT-GROUP qosPibQGroup OBJECT-GROUP
OBJECTS { OBJECTS {
qosQNext, qosQSchdParam qosQNext, qosQWeight, qosQShaper
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Queue Group contains the objects that describe "The Queue Group contains the objects that describe
an interface's queues." an interface's queues."
::= { qosPibGroups 14 } ::= { qosPibGroups 14 }
qosPibSchedulerGroup OBJECT-GROUP qosPibSchedulerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
qosSchedulerMethod, qosSchedulerSchdParam, qosSchedulerMethod, qosSchedulerWeight,
qosSchedulerNext qosSchedulerShaper, qosSchedulerNext
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Scheduler Group contains the objects that "The Scheduler Group contains the objects that
describe packet schedulers on interfaces." describe packet schedulers on interfaces."
::= { qosPibGroups 15 } ::= { qosPibGroups 15 }
qosPibSchdParamGroup OBJECT-GROUP qosPibAssuredRateGroup OBJECT-GROUP
OBJECTS { OBJECTS {
qosSchdParamPriority, qosAssuredRatePriority,
qosSchdParamMinRateAbs, qosSchdParamMinRateRel, qosAssuredRateAbs, qosAssuredRateRel
qosSchdParamMaxRateAbs, qosSchdParamMaxRateRel,
} }
STATUS current
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
STATUS current
DESCRIPTION DESCRIPTION
"The Scheduler Parameter Group contains the objects "The Assured Rate Group contains the objects
that describe packet schedulers' parameters on inter- that describe packet schedulers' parameters on inter-
faces." faces."
::= { qosPibGroups 16 } ::= { qosPibGroups 16 }
qosPibShapingRateGroup OBJECT-GROUP
OBJECTS {
qosShapingRateAbs, qosShapingRateRel,
qosShapingRateThreshold
}
STATUS current
DESCRIPTION
"The Shaping Rate Group contains the objects
that describe packet schedulers' parameters on inter-
faces."
::= { qosPibGroups 17 }
END END
DiffServ QoS Policy Information Base November 2000 DiffServ QoS Policy Information Base February 2001
9. Security Considerations 9. Subect Category Considerations
The numbering space used for the DiffServ PIB, as indicated by the
SUBJECT-CATEGORIES clause, will be assigned by the Internet Assigned
Numbers Authority (IANA). Notice the numbering space used by SUBJECT-
CATEGORIES maps to the Client Type numbering space in [COPS-PR]. This
relationship is detailed in section 7.1 of [SPPI]. Due to the fact that
Client Type value of 1 has already been used by [COPS-RSVP], the
numbering space for SUBJECT-CATEGORIES will need to start with the value
of 2.
Other PIB Modules may use the same SUBJECT-CATEGORIES as this DiffServ
PIB Module. In such situations, PRC numbering space under a specific
SUBJECT-CATEGORIES should be coordinated with existing PIB Modules using
the same SUBJECT-CATEGORIES.
10. Security Considerations
The information contained in a PIB when transported by the COPS protocol The information contained in a PIB when transported by the COPS protocol
[COPS-PR] may be sensitive, and its function of provisioning a PEP [COPS-PR] may be sensitive, and its function of provisioning a PEP
requires that only authorized communication take place. The use of requires that only authorized communication take place. The use of
IPSEC between PDP and PEP, as described in [COPS], provides the IPSEC between PDP and PEP, as described in [COPS], provides the
necessary protection against these threats. necessary protection against these threats.
10. Intellectual Property Considerations 11. Intellectual Property Considerations
The IETF is being notified of intellectual property rights claimed in The IETF is being notified of intellectual property rights claimed in
regard to some or all of the specification contained in this document. regard to some or all of the specification contained in this document.
For more information consult the online list of claimed rights. For more information consult the online list of claimed rights.
11. Authors' Addresses 12. Authors' Addresses
Michael Fine Michael Fine
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 USA San Jose, CA 95134-1706 USA
Phone: +1 408 527 8218 Phone: +1 408 527 8218
Email: mfine@cisco.com Email: mfine@cisco.com
Keith McCloghrie Keith McCloghrie
DiffServ QoS Policy Information Base February 2001
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 USA San Jose, CA 95134-1706 USA
Phone: +1 408 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com Email: kzm@cisco.com
John Seligson John Seligson
Nortel Networks, Inc. Nortel Networks, Inc.
4401 Great America Parkway 4401 Great America Parkway
Santa Clara, CA 95054 USA Santa Clara, CA 95054 USA
Phone: +1 408 495 2992 Phone: +1 408 495 2992
Email: jseligso@nortelnetworks.com Email: jseligso@nortelnetworks.com
Kwok Ho Chan Kwok Ho Chan
Nortel Networks, Inc. Nortel Networks, Inc.
600 Technology Park Drive 600 Technology Park Drive
DiffServ QoS Policy Information Base November 2000
Billerica, MA 01821 USA Billerica, MA 01821 USA
Phone: +1 978 288 8175 Phone: +1 978 288 8175
Email: khchan@nortelnetworks.com Email: khchan@nortelnetworks.com
Scott Hahn Scott Hahn
Intel Intel
2111 NE 25th Avenue 2111 NE 25th Avenue
Hillsboro, OR 97124 USA Hillsboro, OR 97124 USA
Phone: +1 503 264 8231 Phone: +1 503 264 8231
Email: scott.hahn@intel.com Email: scott.hahn@intel.com
Carol Bell
Intel
2111 NE 25th Avenue
Hillsboro, OR 97124 USA
Phone: +1 503 264 8491
Email: carol.a.bell@intel.com
Andrew Smith Andrew Smith
Allegro Networks Allegro Networks
6399 San Ignacio Ave 6399 San Ignacio Ave
San Jose, CA 95119 San Jose, CA 95119
andrew@allegronetworks.com andrew@allegronetworks.com
DiffServ QoS Policy Information Base February 2001
Francis Reichmeyer Francis Reichmeyer
PFN, Inc.
University Park at MIT University Park at MIT
26 Landsdowne Street 26 Landsdowne Street
Cambridge, MA 02139 Cambridge, MA 02139
Phone: +1 617 494 9980 Phone: +1 617 494 9980
Email: franr@pfn.com Email: franr@pfn.com
12. References 13. References
[COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., and [COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., and
A. Sastry, "The COPS (Common Open Policy Service) Protocol" A. Sastry, "The COPS (Common Open Policy Service) Protocol"
RFC 2748, January 2000. RFC 2748, January 2000.
[COPS-PR] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, [COPS-PR] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie,
F. Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, F. Reichmeyer, J. Seligson, A. Smith, R. Yavatkar,
"COPS Usage for Policy Provisioning," "COPS Usage for Policy Provisioning,"
draft-ietf-rap-cops-pr-05.txt, October 2000. draft-ietf-rap-cops-pr-05.txt, October 2000.
[SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning
Information," draft-ietf-rap-sppi-03.txt, November 2000. Information," draft-ietf-rap-sppi-03.txt, November 2000.
[DSARCH] M. Carlson, W. Weiss, S. Blake, Z. Wang, D. Black, and [DSARCH] M. Carlson, W. Weiss, S. Blake, Z. Wang, D. Black, and
E. Davies, "An Architecture for Differentiated Services", E. Davies, "An Architecture for Differentiated Services",
DiffServ QoS Policy Information Base November 2000
RFC 2475, December 1998 RFC 2475, December 1998
[DSFIELD] K. Nichols, S. Blake, F. Baker, D. Black, "Definition of the [DSFIELD] K. Nichols, S. Blake, F. Baker, D. Black, "Definition of the
Differentiated Services Field (DS Field) in the IPv4 and Differentiated Services Field (DS Field) in the IPv4 and
IPv6 Headers", RFC 2474, December 1998. IPv6 Headers", RFC 2474, December 1998.
[FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, [FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn,
A. Smith, F. Reichmeyer "Framework Policy Information Base", A. Smith, F. Reichmeyer "Framework Policy Information Base",
Internet Draft <draft-ietf-rap-frameworkpib-03.txt>, Internet Draft <draft-ietf-rap-frameworkpib-03.txt>,
November 2000 November 2000
[RAP-FRAMEWORK] R. Yavatkar, D. Pendarakis, "A Framework for [RAP-FRAMEWORK] R. Yavatkar, D. Pendarakis, "A Framework for
Policy-based Admission Control", Policy-based Admission Control",
RFC 2753, January 2000. RFC 2753, January 2000.
[SNMP-SMI] K. McCloghrie, D. Perkins, J. Schoenwaelder, J. Case, [SNMP-SMI] K. McCloghrie, D. Perkins, J. Schoenwaelder, J. Case,
M. Rose and S. Waldbusser, "Structure of Management Information M. Rose and S. Waldbusser, "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
DiffServ QoS Policy Information Base February 2001
[MODEL] Y. Bernet, A. Smith, S. Blake, D. Grossman "A Conceptual Model [MODEL] Y. Bernet, A. Smith, S. Blake, D. Grossman "A Conceptual Model
for DiffServ Routers", draft-ietf-diffserv-model-04.txt, for DiffServ Routers", draft-ietf-diffserv-model-04.txt,
July 2000. July 2000.
[IFMIB] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB using [IFMIB] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB using
SMIv2", RFC 2233, November 1997. SMIv2", RFC 2233, November 1997.
DiffServ QoS Policy Information Base November 2000 [DS-MIB] F. Baker, K. Chan, A. Smith, "Management Information Base for
the Differentiated Services Architecture",
draft-ietf-diffserv-mib-07.txt, February 2001
[ACTQMGMT] V. Firoiu, M. Borden "A Study of Active Queue Management for
Congestion Control", March 2000, In IEEE Infocom 2000,
http://www.ieee-infocom.org/2000/papers/405.pdf
[AQMROUTER]
V.Misra, W.Gong, D.Towsley "Fuid-based analysis of a network of AQM
routers supporting TCP flows with an application to RED", In
SIGCOMM 2000,
http://www.acm.org/sigcomm/sigcomm2000/conf/paper/sigcomm2000-4-
3.ps.gz
[AF-PHB] J. Heinanen, F. Baker, W. Weiss, J. Wroclawski, "Assured
Forwarding
PHB Group.", RFC 2597, June 1999.
[EF-PHB] V. Jacobson, K. Nichols, K. Poduri, "An Expedited Forwarding
PHB."
RFC 2598, June 1999.
[INETADDRESS] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder,
J.,
"Textual Conventions for Internet Network Addresses.", RFC 2851,
June 2000.
[INTSERVMIB] F. Baker, J. Krawczyk, A. Sastry, "Integrated Services
Management Information Base using SMIv2", RFC 2213, September 1997.
[QUEUEMGMT] B. Braden et al., "Recommendations on Queue Management and
Congestion Avoidance in the Internet", RFC 2309, April 1998.
[RED93] "Random Early Detection", 1993.
[SRTCM] J. Heinanen, R. Guerin, "A Single Rate Three Color Marker", RFC
2697, September 1999.
DiffServ QoS Policy Information Base February 2001
[TRTCM] J. Heinanen, R. Guerin, "A Two Rate Three Color Marker", RFC
2698,
September 1999.
[TSWTCM] W. Fang, N. Seddigh, B. Nandy "A Time Sliding Window Three
Colour
Marker", RFC 2859, June 2000.
DiffServ QoS Policy Information Base February 2001
Table of Contents Table of Contents
1 Glossary ........................................................ 3 1 Glossary ........................................................ 3
2 Introduction .................................................... 3 2 Introduction .................................................... 3
3 Relationship to the Diffserv Informal Management Model .......... 3 3 Relationship to the Diffserv Informal Management Model .......... 3
3.1 PIB Overview .................................................. 4 3.1 PIB Overview .................................................. 4
4 Structure of the PIB ............................................ 6 4 Structure of the PIB ............................................ 6
4.1 General Conventions ........................................... 6 4.1 General Conventions ........................................... 6
4.2 DiffServ Data Paths ........................................... 6 4.2 DiffServ Data Paths ........................................... 6
4.2.1 Data Path PRC ............................................... 7 4.2.1 Data Path PRC ............................................... 7
4.3 Classifiers ................................................... 7 4.3 Classifiers ................................................... 7
4.3.1 Classifier PRC .............................................. 8 4.3.1 Classifier PRC .............................................. 8
4.3.2 Classifier Element PRC ..................................... 8 4.3.2 Classifier Element PRC ..................................... 8
4.4 Meters ........................................................ 9 4.4 Meters ........................................................ 9
4.4.1 Meter PRC ................................................... 9 4.4.1 Meter PRC ................................................... 9
4.4.2 Token-Bucket Meter PRC ...................................... 10 4.4.2 Token-Bucket Parameter PRC .................................. 10
4.5 Actions ....................................................... 10 4.5 Actions ....................................................... 10
4.5.1 DSCP Mark Action PRC ........................................ 11 4.5.1 DSCP Mark Action PRC ........................................ 11
4.5.2 Absolute Drop Action ........................................ 11 4.5.2 Absolute Drop Action ........................................ 11
4.6 Queueing Elements ............................................. 11 4.6 Queueing Elements ............................................. 11
4.6.1 Algorithmic Dropper PRC ..................................... 11 4.6.1 Algorithmic Dropper PRC ..................................... 11
4.6.2 Random Dropper PRC .......................................... 12 4.6.2 Random Dropper PRC .......................................... 12
4.6.3 Queues and Schedulers ....................................... 14 4.6.3 Queues and Schedulers ....................................... 14
4.7 Specifying Device Capabilities ................................ 15 4.7 Specifying Device Capabilities ................................ 16
5 PIB Usage Example ............................................... 16 5 PIB Usage Example ............................................... 17
5.1 Data Path and Classifier Example Discussion ................... 18 5.1 Model's Example ............................................... 17
5.2 Meter and Action Example Discussion ........................... 19 5.2 Additional Data Path Example .................................. 20
5.3 Queue and Scheduler Example Discussion ........................ 19 5.2.1 Data Path and Classifier Example Discussion ................. 20
6 Summary of the DiffServ PIB ..................................... 20 5.2.2 Meter and Action Example Discussion ......................... 23
7 PIB Operational Overview ........................................ 21 5.2.3 Queue and Scheduler Example Discussion ...................... 23
8 PIB Definitions ................................................. 22 6 Summary of the DiffServ PIB ..................................... 24
8.1 The DiffServ Base PIB ......................................... 22 7 PIB Operational Overview ........................................ 25
9 Security Considerations ......................................... 79 8 PIB Definitions ................................................. 26
10 Intellectual Property Considerations ........................... 79 8.1 The DiffServ Base PIB ......................................... 26
11 Authors' Addresses ............................................. 79 9 Subect Category Considerations .................................. 89
12 References ..................................................... 80 10 Security Considerations ........................................ 89
11 Intellectual Property Considerations ........................... 89
12 Authors' Addresses ............................................. 89
13 References ..................................................... 91
 End of changes. 372 change blocks. 
877 lines changed or deleted 1451 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/