Network Working Group                             M. Fine
Internet Draft                                    K. McCloghrie
Expires December 2000 May 2001                                     Cisco Systems
                                                  J. Seligson
                                                  K. Chan
                                                      Nortel Networks
                                                  S. Hahn
                                                      Intel
                                                  A. Smith
                                                      No Affiliation
                                                      Allegro Networks
                                                  Francis Reichmeyer
                                                      IPHighway

                                                  July 14,

                                                  November 24, 2000

   Differentiated Services Quality of Service Policy Information Base

                     draft-ietf-diffserv-pib-01.txt

                     draft-ietf-diffserv-pib-02.txt

Status of this Memo

This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026.  Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups.  Note that other groups may also distribute working
documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet-Drafts as reference material
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                       November 2000

``1id-abstracts.txt'' listing contained in an Internet-Drafts Shadow
Directory, see http://www.ietf.org/shadow.html.

DiffServ QoS Policy Information Base                       November 2000

1.  Glossary

PRC     Policy Rule     Provisioning Class.  A type of policy data.
PRI     Policy Rule     Provisioning Instance.  An instance of a PRC.
PIB     Policy Information Base.  The database of policy information.
PDP     Policy Decision Point. See [RAP-FRAMEWORK].
PEP     Policy Enforcement Point. See [RAP-FRAMEWORK].
PRID    Policy Rule    Provisioning Instance Identifier.  Uniquely identifies an
        instance of a a PRC.

2.  Introduction

[SPPI] describes a structure for specifying policy information that can
then be transmitted to a network device for the purpose of configuring
policy at that device.  The model underlying this structure is one of
well defined policy rule classes and instances of these classes residing
in a virtual information store called the Policy Information Base (PIB).

This document specifies a set of policy rule classes specifically for
configuring QoS Policy for Differentiated Services [DSARCH].

One way to provision policy is by means of the COPS protocol [COPS] with
the extensions for provisioning [COPS-PR].  This protocol supports
multiple clients, each of which may provision policy for a specific
policy domain such as QoS.  The PRCs defined in this DiffServ QoS PIB
are intended for use by the COPS-PR QoS client type.  Furthemore, these
PRCs are in addition to any other PIBs that may be defined for the QoS
client type in the future, as well as the PRCs defined in the Framework
PIB [FR-PIB] [FR-PIB].

3.  DiffServ  Relationship to the Diffserv Informal Management Model

This PIB Concepts

3.1.  Filters, Filter Groups and Classifiers is designed according to the Differentiated Services Informal
Management Model documented in [MODEL]. The basis model describes the way that
ingress and egress interfaces of differential QoS treatment an 'n'-port router are modelled. It
describes the configuration and management of packets is a filter. This is
simply a general specification for matching a pattern to appear Diffserv interface in
packets belonging to flows, e.g. microflows or behavior aggregates.
Associated with each filter is a permit/deny flag which effectively
gives a negation operation.

Sets
terms of these filters are used to create classifiers. Classifiers are
applied to interfaces with a direction flag to indicate an ingress Transmission Control Block (TCB) which contains, by
definition, zero or
egress classifier. Filters are combined, in order, into filter groups;

filter groups more classifiers, meters, actions, algorithmic
droppers, queues and schedulers. These elements are then combined, in order, to build a classifier. This
allows a rudimentary classification grammar arranged according

DiffServ QoS Policy Information Base                       November 2000

to be defined. On input,
each packet is checked against the ingress classifier on the interface.
Similarly, on output QoS policy being expressed, always in that order. Traffic may be
classified; classified traffic may be metered; each packet is checked against the egress
classifier on the interface. The result stream of the classifier then feeds
into appropriate meters traffic
identified by a combination of classifiers and meters may have some set
of actions to be performed on it; it may have dropping algorithms applied and
it may ultimately be stored into a queue before being scheduled out to packets.

For each classifier,
its next destination, either onto a link or to another TCB. When the
treatment for a given packet is checked against the set must have any of filter
groups those elements repeated in
a way that breaks the appropriate order. The detailed operation of the permitted sequence {classifier, meter, action,
algorithmic dropper, queue, scheduler}, this must be modelled by
cascading multiple TCBs.

The PIB
syntax is as follows. If a packet matches a filter in represents this cascade by following the first filter
group "Next" attributes of a classifier and
the sense is "permit" then various elements. They indicate what the subsequent
meters and actions associated with that classifier are applied next step in Diffserv
processing will be, whether it be a classifier, meter, action,
algorithmic dropper, queue, scheduler or a decision to that
packet and no further filters are compared. If now forward a
packet.

The PIB models the sense is "deny" then individual elements that make up the rest TCBs.  The
higher level concept of the filters a TCB is not required in the current filter group are skipped and
operation proceeds with parameterization or
in the first filter linking together of the next filter group. If
the packet does individual elements, hence it is not match any of used
in the filters PIB itself and only mentioned in the filter group then text for relating the next filter group is tried. This process is continued until a
definitive match is obtained. Each classifier must cover all possible
matches i.e., it must be complete.

3.2.  Applying QoS Policy Using Targets PIB
with the [MODEL].  The task actual distinguishing of applying QoS policy within which TCB a network requires specific
element is a part of is not needed for the
specification instructmentation of several components. The flows a device
to which QoS policy
should be applied must be identified. The interfaces of support the device on
which functionalities of DiffServ, but it is useful for
conceptual reasons.  By not including the policy should be enforced must be known. A certain set TCB notion in its parameters,
this PIB allow any grouping of
parameters elements to support flow metering is also required. construct TCBs, using rules
indicated by the [MODEL].  This will minimize changes to this PIB if
rules in [MODEL] changes.

The combination notion of
these components provides the target against which QoS policy a Data Path is used in this PIB to be
applied. Within indicate the DiffServ
processing a packet may experience.  This Data Path is distinguished
based on the context Role Combination and the Direction of the QoS PIB, flow the association between
these components packet
is defined efficiently using part of.  A Data Path Table Entry indicates the Target class.

The Target class serves first of possibly
multiple elements that will apply DiffServ treatment to logically link several other QoS policy
classes. Flow classification rules, specifying behavior aggregate (BA)
or multi-field (MF) classification parameters, are indirectly identified
using the PRC for the appropriate classification class coupled with an
identifier for a specific -- classifier. Interface information packet.

3.1.  PIB Overview

This PIB is
specified using structured based on the role combination tag, defined in need to configure the Interface Type
class, sequential
DiffServ treatments being applied to identify a packet, and the group parameterization
of interfaces on which classification is to
be performed. The direction these treatments.  These two aspects of packet flow on the identified interfaces
is provided as well. A link to configuration are kept
separate throughout the metering component is provided design of the PIB, and are fulfilled using
separate tables and data definitions.

DiffServ QoS Policy Information Base                       November 2000

In addition, the PRC for PIB includes tables describing the appropriate metering class instance.

Once capabilities and
limitations of the device using a target has been defined, actions based on general extensible framework.  These
tables are reported to the classification PDP and
metering phases must be specified. Action class instances are linked
with assist the Target entry through PDP with the associated Meter class instance.  A

precedence component is also provided so that a definitive order configuration
of
evaluation may functional elements that can be defined for Target class instances being applied to realized by the same interface role device.

In this PIB, the ingress and flow direction targets. The Target class
thus functions as egress portions of a router are configured
independently but in the integration point for same manner. The difference is distinguished by
an attribute in a table describing the range start of components used
for the application data path.  Each
interface performs some or all of QoS policy.

3.3.  Interface Modeling with Queue Sets

The traffic processing capabilities the following high-level functions:

o    Classify each packet according to some set of an interface are determined by rules

o    Determine whether the queuing resources that are associated with data stream the interface.  These
capabilities are represented abstractly using queue sets.  A queue set packet is comprised part of one is within
     or more individual queues.  The PDP creates the
queue sets, configures the parameters outside its rate

o    Perform a set of resulting actions such as application of an
     appropriate drop policy and marking of the individual queues,
configures traffic with a
     Differentiated Services Code Point (DSCP) as defined in [DSFIELD].

o    Enqueue the scheduling discipline to be used to schedule traffic for output in the queues
and then assigns a queue set to each <interface type, role combination>
tuple.  In this way, appropriate queue, whose
     scheduler may shape the PDP sets traffic or simply forward it with some
     minimum rate or maximum latency.

The PIB therefore contains the scheduling policy following elements:

Data Path Table
     A general extensible framework for each
interface based on describing the starting point of
     DiffServ datapaths within a single DiffServ device.  This table
     descibes interface role combination of the and interface direction
     specific data paths.

Classifier Tables
     A general extensible framework for specifying a group of filters.

Meter Tables
     A general extensible framework and the type one example of
the interface.

In order for the PDP to configure a queue set that can be properly
realized
     parameterization table - TBMeter table, applicable for Simple Token
     Bucket Meter, Average Rate Meter, Single Rate Three Color Meter,
     Two Rate Three Color Meter, and Sliding Window Three Color Meter.

Action Tables
     A general extensible framework and examples of parameterization
     tables for Absolute Drop, Mark and Count actions.  The
     "multiplexer", "replicator" and "null" actions described in [MODEL]
     are accomplished implicitly by an interface, means of the PEP reports to RowPointer structures

DiffServ QoS Policy Information Base                       November 2000

     of the PDP other elements.

Queue, Scheduler and Algorithmic Dropper Tables
     A general extensible framework for parameterizing queuing and
     scheduler systems.  The queue measurement dependent algorithmic
     droppers are also described here.

Capabilities Tables
     A general extensible framework for defining the types of
interfaces it has together with various capabilities and configuration
limits (such as
     limitations of the maximum number elements listed above. The capability tables
     allow intelligent configuration of queues an interface could support) the elements by a PDP.

4.  Structure of the interface types.

It should be emphasized PIB

4.1.  General Conventions

The PIB consists of classes that represent functional elements in the PDP does not configure individual
interfaces directly.  Rather, it configures them indirectly by
specifying the configuration for each interface type
data path (e.g. classifiers, meters, actions), and role
combination pair.  It is the responsibility classes that specify
parameters that apply to a certain type of the PEP functional element (e.g. a
Token Bucket meter or a Mark action).  Parameters are typically
specified in a separate PRC to apply enable the
queue set characteristics, and hence use of parameter classes by
multiple policies.

Functional element PRC's use the interface scheduling
configuration, Prid TC (defined in [SPPI]) to the individual interfaces on the basis indicate
indirection.  A Prid is a object identifier that is used to specify an
instance of the type and
role combination information.

3.3.1.  Queue Scheduling

There are two basic scheduling disciplines supported by queue sets:
priority queueing and weighted fair queueing.  To support these, each
queue a PRC in another table.  A Prid is assigned used to point to
parameter PRC that applies to a priority functional element, such as which filter
should be used for a classifier element.   A Prid is then also used to determine
specify an instance of a strict
processing order between queues.  However, several queues may functional element PRC that describes what
treatment should be
assigned applied next for a packet in the data path.

Note that the use of Prid's to specify parameter PRC's allows the same priority.  In this case, these queues form a group,
called
funtional element PRC to be extended with a priority group, and are scheduled using WFQ. number of different types of
parameter PRC's.  In other words,
service is given addition, using Prids to indicate the priority group with next
functional datapath element allows the highest priority that
has elements to be ordered in any non-empty queue.  Within a priority group queues are serviced
using WFQ.

3.3.2.  Assigning Packets To Queues and Thresholds

In keeping with the
way.

4.2.  DiffServ model Data Paths

This part of classifying packets into behaviour
classes and then providing service suitable the PIB provides instrumentation for that behaviour, packets
are assigned connecting the
DiffServ Functional Elements within a single DiffServ device.  Please
refer to queues the [MODEL] for discussions on the basis valid sequencing and
grouping of their final DSCP values.
Furthermore, each queue is configured with a set of thresholds to
support multiple discard priorities for DiffServ Functional Elements.  Given some basic information,

DiffServ QoS Policy Information Base                       November 2000

e.g. the PHBs in a PHB group.
Packets interface role combination and direction, the first DiffServ
Functional Element is determined.  Subsequent DiffServ Functional
Elements are assigned to thresholds within a queue on provided by the basis "Next" pointer attribute of each entry of
data path tables.  A description of how this "Next" pointer is used in
each table is provided in their
DSCPs. respective sections.

4.2.1.  Data Path PRC

The PDP is responsible Data Path PRC provides the DiffServ treatment starting points for
all packets of this assignment DiffServ device. Each instance of DSCP values to
queues this PRC specifies
the interface role combination and direction for the associated thresholds.

3.3.3.  Hierarchies of Queues

Sometimes policy may require hierachies of queues.  For example, a
department might has some set of traffic classes with packet flow.  There
should be at most two entries for each role combination, one for ingress
and one for egress.  Each instance provides the first DiffServ
Functional Element each packet at a defined
scheduling policy between these classes.  Multiple departments might
then share specific interface (identified by
the roles assigned to the interface) traveling in a link specific relative
direction should experience.  Notice this table is interface specific,
with the use of RoleCombination.  To indicate explicitly that there being are
no Diffserv treatments for a defined scheduling policy between
traffic from particular role combination and direction,
an instance of the various depertments.

The PIB does not support hierarchical queueing at this time.  However,
we expect to add this support Data Path PRC can be created with zeroDotZero in the future
qosDataPathStart attribute.  This situation can also be indicated
implicitly by allowing the traffic from
one queue set to feed into the queues of another queue set.

4.  Summary not supplying an instance of the DiffServ PIB a Data Path PRC for that
particular role combination and direction.  The DiffServ PIB consists of one module containing explicit/implicit
selection is up to the base PRCs for
setting DiffServ policy, queues, classifiers, meters, etc.,  and also
contains filters for matching IP packets.  This module comprises several
groups which are summarized in this section.

QoS Interface Group implementation.  This group consists of PRCs to indicate to the PDP the types of
     interface supported on the PEP in terms of their QoS capabilities
     and PRCs means that the PDP can install PEP should
perform normal IP device processing when zeroDotZero is used in order to configure these
     interfaces (queues, scheduling parameters, buffer sizes, etc.) to
     affect the desired policy.  This group describes capabilities in
     terms of
qosDataPathStart attribute, or when the types of interfaces and takes configuration in terms
     of interface types and role combinations [FR-PIB]; it entry does not deal
     with individual interfaces exist.  Normal IP
device processing will depend on the device.

QoS Metering Group
     This group contains configuration of meters.  These meters device, for example, this can then be used
forwarding the packet.

4.3.  Classifiers

The classifier and classifier element tables determine how traffic is
sorted out. They identify separable classes of traffic, by reference to
appropriate filters, which may select anything from an individual micro-
flow to aggregates identified by target classes DSCP.

The classification is used to specify metering policy.

QoS Action Group
     This group contains the policies that define the action send these separate streams to appropriate
Meter, Action, Queue, Scheduler and Algorithmic Dropper elements.  For
example, to indicate a multi-stage meter, sub-classes of traffic may be taken
     after the result
sent to different meter stages: e.g. in an implementation of the classification and metering. This group
     also contains Assured
Forwarding (AF) PHB [AF-PHB], AF11 traffic might be sent to the policies that associate first
meter, AF12 traffic might be sent to the classifiers, meters second and actions.

5.  PIB Operational Overview

This section provides an operation overview of configuring AF13 traffic sent to

DiffServ QoS
policy.

After initial PEP to PDP communication setup, using [COPS-PR] for
example, the PEP will provide to the PDP the PIB Policy Rule Classes
(PRCs), interface types, and interface type capabilities it supports.

The PRCs supported by the PEP are reported to Information Base                       November 2000

the PDP in second meter stage's out-of-profile action.

The concept of a classifier is the PRC Support
Table, frwkPrcSupportTable defined same as described in the framework PIB [FR-PIB].  Each
instance [MODEL].  The
structure of the frwkPrcSupportTable indicates a PRC that the PEP
understands classifier and for which classifier element tables, is the PDP can send class instances same
as part of
the policy information.

The interface types the PEP supports are classifier described by rows in [MODEL].  Classifier elements have an
associated precedence order solely for the
interface type table, frwkIfCapsSetTable.  Each row, or instance purpose of this
class describes the characteristics resolving
ambiguity between overlapping filters.  Filter with higher values of an interface type.  The PEP
informs
order are compared first; the PDP order of tests for entries of these interface types and then the PDP configures the
interfaces, per role combination, by means same
precedence is unimportant.

A datapath may consist of installing queue sets. more than one classifier.  There may be
overlap of filter specification between filters of different
classifiers.  The PDP, with knowledge first classifier functional datapath element
encountered, as determined by the sequencing of diffserv functional
datapath elements, will be used first.

An important form of classifier is "everything else": the PEP's capabilities, then provides final stage of
the PEP classifier i.e. the one with administration domain and interface-specific policy information.

Instances of the qosTargetTable define how lowest precedence, must be
"complete" since the Traffic Conditioning
Elements are combined into Traffic Conditioning Blocks, as described in
[MODEL].  Each instance result of the qosTargetTable applies to an interface
type defined by its roles and direction (ingress or egress).  This incomplete classifier is
pictured in the following diagram where not
necessarily deterministic - see [MODEL] section 4.1.2.

The definition of the InterfaceRoles X, and Y
would actual filter to be used by the network device to associate the traffic
conditioning block with classifier is
referenced via a Prid: this enables the interfaces needing each use of thess policies.

                                       +----------------------------+
   +----------------------------+      | qosTargetEntry             |
   |                            |      |                            |
   |    PolicyFilterEntry       | <------- Ptr any sort of filter table
that one might wish to Policy Filter     |
   |                            |      |        InterfaceRoles = X  |
   +----------------------------+      |        Meter -----+        |
                                       +-------------------|--------+
                                                           |
                                                           v
                                                   +----------------+
                                                   | qosMeterEntry  |
                                                   +----------------+
                                                           |
                                                           v
                                                   +----------------+
                                                   | qosActionEntry |
                                                   +----------------+

              Figure 7.1  DiffServ design, standard or proprietary.  No filters are
defined in this PIB.  However, standard filters for IP packets are
defined in the Framework PIB Table Relationships

Notice that [FR-PIB].

4.3.1.  Classifier PRC

Classifiers are organized by instances of the qosTargetTable allows Classifier PRC. Each
instance corresponds to a single Classifier.  Instances of the use
Classifier PRC get linked from the upstream diffserv functional datapath
element, e.g., a qosDataPathentry instance.  A data path may consist of heterogeneous
more than one Classifier, and the order in which the classifiers with are
applied to the traffic is the same instance as the order the classifier table
entries are linked in the data path.

4.3.2.   Classifier Element PRC

While the Classifier PRC specifies the input side of qosMeterTable.  For example, if
classifiers operating on layer 2 addresses were the Classifier, the
Classifier Element PRC enumerates each branch of the fan-out of a

DiffServ QoS Policy Information Base                       November 2000

Classifier, associating each fan-out branch with a Filter for
discriminating the traffic for that branch. Each Classifier Element PRI
is part of a Classifier, indicated by qosClfrElementClfrId.

The definition of the actual filter to be defined, those
classifiers could be used together with by the IP ones.

After receiving classifier is
referenced via a Prid: this enables the PIB, use of any sort of filter table
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 PEP will associate
frwkIpFilter PRC, defined in [FR-PIB].

4.4.  Meters

A meter, according to [MODEL] section 5, measures the Classifier, Meter rate at which
packets making up a stream of traffic pass it, compares this rate to
some set of thresholds and Action with produces some number (two or more) of
potential results. A given packet is said to "conform" to the corresponding interfaces supporting meter if,
at the specific
interface type and roles.

6.  PIB Definitions

6.1.  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
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
modelling does not imply anything about the implementation being
"sequential": multi-rate/multi-profile meters e.g. those designed to
support [SRTCM] or [TRTCM], can still be modelled this way even if they,
of necessity, share information between the stages: the stages are
introduced merely as a notational convenience in order to simplify the
PIB structure.

4.4.1.  Meter PRC

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
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
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.

DiffServ QoS Policy Information Base                       November 2000

4.4.2.  Token-Bucket Meter PRC

This is included as an example of a common type of meter.  Entries in
this table are referenced from the qosMeterSpecific attributes of meter
PRC instances.  The parameters are represented by a rate qosTBMeterRate,
a burst size qosTBMeterBurstSize, and an interval qosTBMeterInterval.
The type of meter being parameterized is indicated by the qosTBMeterType
attribute.  This is used to determine how the rate, burst and rate
interval parameters are used.  Additional meter parameterization classes
can be defined in this or another PIB when necessary.

4.5.  Actions

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
algorithm" are handled elsewhere as queueing mechanisms, rather than
actions, consistent with [MODEL].  The "multiplexer", "replicator" and
"null" actions described in [MODEL] are accomplished implicitly through
various combinations of the other elements.

This PIB uses the Action PRC qosActionTable to organize one Action's
relationship with the element(s) before and after it. It allows Actions
to be cascaded to enable multiple Actions be applied to a single traffic
stream by using each entry's qosActionNext attribute.  The qosActionNext
attribute of the last action entry in the chain points to the next
element in the TCB, if any, e.g.  a Queueing element.  It may also point
at a next TCB.

The parameters needed for the Action element will depend on the type of
Action to be taken. Hence the PIB allows for specific Action Tables for
the different Action types.  This flexibility allows additional Actions
be specified in future revisions of this PIB, or in other PIBs and also
allows for the use of proprietary Actions without impact on those
defined here.

There is one action - the absolute drop action - that does not require
additional parameters.  This action silently discards all traffic
presented to it.  To accommodate this action, the qosAction PRC contains
an attribute, qosActionType, that indicates whether the absolute drop
action is to be used or if the action is described by a specific action
table.

DiffServ QoS Policy Information Base                       November 2000

4.5.1.  DSCP Mark Action PRC

This Action is applied to traffic in order to mark it with a Diffserv
Codepoint (DSCP) value, specified in the qosDscpMarkActTable.  Other
marking actions might be specified elsewhere - these are outside the
scope of this PIB.

4.5.2.  Absolute Drop Action

This action just silently discards all traffic presented to it.  This
action has no additional parameters and so is represented only within
diffServActionType without its specific table.

4.6.  Queueing Elements

These include Algorithmic Droppers, Queues and Schedulers which are all
inter-related in their use of queueing techniques.

4.6.1.  Algorithmic Dropper PRC

Algorithmic Droppers have a close relationship with queueing: they are
represented in this PIB by instances of an Algorithmic Dropper PRC.
Entries contain a qosAlgDropNext attribute which indicates to which
queue they sink their traffic.

An Algorithmic Dropper is assumed to operate indiscriminately on all
packets that are presented at its input. If it is necessary to perform
additional classification on the stream then a separate TCB must be
introduced at this point: Classifier elements here can then distinguish
the different types of traffic on which dropping is to act and the
treatment for each type is described by a separate qosAlgDropEntry.

Algorithmic Droppers may also contain a pointer to specific detail of
the drop algorithm. This PIB defines the detail for three drop
algorithms: Tail Drop, Head Drop and Random Drop; other algorithms are
outside the scope of this PIB modele but the general framework is
intended to allow for their inclusion via other PIB modules.

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

DiffServ QoS Policy Information Base                       November 2000

represented in this PIB, as a base attribute of the Algorithmic Dropper
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
     threshold: when the queue pointed at by diffServAlgDropQMeasure
     reaches that depth threshold, qosAlgDropQThresh, any new
     traffic arriving at the dropper is discarded. This algorithm uses
     only parameters that are part of the qosAlgDropEntry.

o    A Head Dropper requires the specification of a maximum queue depth
     threshold: when the queue pointed at by qosAlgDropQMeasure
     reaches that depth threshold, qosAlgDropQThresh, traffic
     currently at the head of the queue is discarded. This algorithm
     uses only parameters that are part of the qosAlgDropEntry.

o    Random Droppers are recommended as a way to control congestion, in
     [QUEUEMGMT] and called for in the [AF-PHB]. Various implementations
     exist, which agree on marking or dropping just enough traffic to
     communicate with TCP-like protocols about congestion avoidance, but
     differ markedly on their specific parameters. This PIB attempts to
     offer a minimal set of controls for any random dropper, but expects
     that vendors will augment the PRC with additional controls and
     status in accordance with their implementation. This algorithm
     requires additional parameters on top of those in
     qosAlgDropEntry; these are discussed below.

4.6.2.  Random Dropper PRC

One example of a random dropper is a RED-like dropper.  An example of
the representation chosen in this PIB for this element is shown in
Figure 1.

Random droppers often have their drop probability function described as
a plot of drop probability (P) against averaged queue length (Q).
(Qmin,Pmin) then defines the start of the characteristic plot.  Normally
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
drop probability become more progressive (greater slope).  (Qclip,1)
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
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

qosRandomDropProbMax represents Pmax. This PIB does not represent Pmin
(assumed to be zero unless otherwise represented) or Qclip (assumed to
be Qmax unless otherwise represented).

Each random dropper specification is associated with a queue. This
allows multiple drop processes (of same or different types) be
associated with the same queue, as different PHB implementations may
require.  This also allows for sequences of multiple droppers if
necessary.

The calculation of a smoothed queue length may also have an important
bearing on the behaviour of the dropper: parameters may include the
sampling interval and the weight of each sample. The performance may be
very sensitive to the values of these parameters and a wide range of
possible values may be required due to a wide range of link speeds. Most
algorithms include a sample weight, represented here by
qosRandomDropInvWeight. Note however that there is ongoing research on
this topic, see e.g. [ACTQMGMT].

Additional parameters may be added in an enterprise PIB module, e.g. by

DiffServ QoS Policy Information Base                       November 2000

using AUGMENTS or EXTENDS on this table, to handle aspects of random
drop algorithms that are not standardised here.

NOTE: Deterministic Droppers can be viewed as a special case of Random
Droppers with the drop probability restricted to 0 and 1. Hence
Deterministic Droppers might be described by a Random Dropper with Pmin
= 0, Pmax = 1, Qmin = Qmax = Qclip, the averaged queue length at which
dropping occurs.

4.6.3.  Queues and Schedulers

The Queue PRC models simple FIFO queues, as described in [MODEL] section
7.1.1.  The Scheduler PRC allows flexibility in constructing both simple
and somewhat more complex queueing hierarchies from those queues.  Of
course, since TCBs can be cascaded multiple times on an interface, even
more complex hierarchies can be constructed that way also.

Queue PRC instances are pointed at by the "next" attributes of the
upstream elements e.g. qosMeterSucceedNext.  Note that multiple upstream
elements may direct their traffic to the same Queue PRI.  For example,
the Assured Forwarding PHB suggests that all traffic marked AF11, AF12
or AF13 be placed in the same queue, after metering, without reordering.
This would be represented by having the qosMeterSucceedNext of each
upstream meter point at the same Queue PRI.

Queue Table entries specify the scheduler it wants service from by use
of its Next pointer.

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
a scheduler with multiple inputs: this is represented in the PIB by
having the scheduling parameters be associated with each input.  In this
way, sets of Queues can be grouped together as inputs to the same
Scheduler.  This table serves to represent the example scheduler
described in the [MODEL]: other more complex representations might be
created outside of this PIB.

Both the Queue PRC and the Scheduler PRC use instances of the Scheduler
Parameterization PRC to specify diffserv treatment parameterization.
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
and Scheduler PRI's.  Scheduler Parameter PRI's can be used/reused by
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
assigned a priority with respect to all the other inputs feeding the
same scheduler, with default values for the other parameters.  A higher-
priority input will be serviced first over a lower-priority input,
assuming that all guarantees have already been met.

For Weighted Queueing algorithms e.g. WFQ, WRR, the "weight" of a given
scheduler input is represented with a Minimum Service Rate leaky-bucket
profile which provides guaranteed bandwidth to that input, if required.
This is represented, as were token-bucket meters, by a rate
qosSchdParamMinRateAbs. The rate may, alternatively, be represented by a
relative value, as a fraction of the interface's current line rate,
qosSchdParamMinRateRel to assist in cases where line rates are variable
or where a higher-level policy might be expressed in terms of fractions
of network resources. The two rate parameters are inter- related and
changes in one may be reflected in the other.

An input 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, similarly to the minimum rate, by a
rate qosSchdParamMaxRateAbs. The rate may, alternatively, be represented
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
having Scheduler PRI's feed into other Scheduler PRI's.

4.7.  Specifying Device Capabilities

The Diffserv PIB uses the Base PRC classes frwkPrcSupportTable and
frwkCompLimitsTable defined in [FR-PIB] to specify what PRC's are
supported by a PEP and to specify any limitations on that support.  The
PIB also uses the capability PRC's frwkIfCapSetTable and
frwkIfCapSetRoleComboTable defined in [FR-PIB] to specify the device's
interface types and role combinations.  Each instance of the capability
PRC frwkIfCapSetTable contains an OID that points to an instance of a
PRC that describes some capability of that interface type.  The Diffserv
PIB defines several of these capability PRC's, which assist the PDP with
the configuration of Diffserv functional elements that can be
implemented by the device.

DiffServ QoS Policy Information Base                       November 2000

Classification capabilities, such as which directions (ingress or egress
support IP classification and whether the interface is capable of
classifying on layer 4 information, are reported using
qosIfClassificationCapsTable.  Metering capabilities, such as which
directions support metering, are specified using qosIfMeteringCapsTable.
Scheduling capabilities, such as the maximum number of queues and
priorities supported, are reported using qosIfSchedulingCapsTable.

Two PRC's are defined to allow specification of the element linkage
capabilities of the PEP.  The qosIfElmDepthCaps PRC indicates the
maximum number of functional datapath elements that can be linked
consecutively in a datapath.  The qosIfElmLinkCaps PRC indicates what
functional datapath elements are may follow a specific type of element
in a datapath.

5.  PIB Usage Example

This section provides some examples on how the different table entries
of this PIB may be used to parameterize a DiffServ Device.  For the
figures, all the PRC and attribute names are assumed to have the PRC
(table entry) name as the common initial part of the name.

+---------------------+
|DataPath             |
| Roles="A+B"           |
| IfDirection=Ingress |    +------+
| Start --------------+--->|Clfr  |
+---------------------+    | Id=1 |
                           +------+

  +------------+      +--------------+      +-----------+
  |ClfrElement |  +-->|Meter         |  +-->|Action     |
  | Id=101     |  |   | Id=101       |  |   | Id=101    |
  | ClfrId=1   |  |   | SucceedNext -+--+   | Next -----+---->...
  | Order=NA   |  |   | FailNext ----+->... | Specific -+-+
  | Next ------+--+   | Specific -+  |      | Type=Spcf | |
  | Specific --+-+    +-----------+--+      +-----------+ |
  +------------+ |                |               +-------+
                 |   +-------+    |   +--------+  |   +------------+
                 +-->|Filter1|    +-->|TBMeter1|  +-->|DscpMarkAct1|
                     +-------+        +--------+      +------------+

DiffServ QoS Policy Information Base                       November 2000

  +------------+      +--------------+      +-----------+
  |ClfrElement |  +-->|Meter         |  +-->|Action     |
  | Id=102     |  |   | Id=102       |  |   | Id=102    |
  | ClfrId=1   |  |   | SucceedNext -+--+   | Next -----+---->...
  | Order=NA   |  |   | FailNext ----+->... | Specific -+-+
  | Next ------+--+   | Specific -+  |      | Type=Spcf | |
  | Specific --+-+    +-----------+--+      +-----------+ |
  +------------+ |                |               +-------+
                 |   +-------+    |   +--------+  |   +------------+
                 +-->|Filter2|    +-->|TBMeter2|  +-->|DscpMarkAct2|
                     +-------+        +--------+      +------------+

  +------------+      +--------------+      +-----------+
  |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

     +-------------+      +------------------+     +----------------------+
---->|Q            |   +->|Scheduler         |  +->|Scheduler             |
     | Id=EF       |   |  | Id=DiffServ      |  |  | Id=Shaping           |
     | Next -------+---+  | Next ------------+--+  | Next=zeroDotZero     |
     | SchdParam -+|   |  | Method=priorityq |     | Method=priorityq     |
     +------------++   |  | SchdParam -+     |     | SchdParam=zeroDotZero|
                  |    |  +------------+-----+     +----------------------+
     +------------+    |               |
     |                 |  +------------+
     |  +-----------+  |  |
     +->|SchdParamEF|  |  |  +----------------+
        +-----------+  |  +->|SchdParamShaping|
                       |     +----------------+
                       |
                       |
                       +-----------------------------------------+
                                                                 |
                                                                 |

DiffServ QoS Policy Information Base                       November 2000

    +----------------+       +-------------+                     |
--->|AlgDrop         |    +->|Q            |                     |
    | Id=AF11        |    |  | Id=AF1X     |    +-------------+  |
    | Type=randomDrop|    |  | Next -------+--->|Scheduler    |  |
    | Next ----------+-+--+  | SchdParam -+|    | Id=AF       |  |
    | QMeasure ------+-+  |  +------------++    | Next -------+--+
    | QThreshold     |    |               |     | Method=wfq  |
    | Specific -+    |    |  +------------+     | SchdParam -+|
    +-----------+----+    |  |                  +------------++
                |         |  |  +-------------+              |
    +-----------+         |  +->|SchdParamAF1X| +------------+
    |  +--------------+   |     +-------------+ |
    +->|RandomDropAF11|   |                     |  +-----------+
       +--------------+   |                     +->|SchdParamAF|
                          |                        +-----------+
    +----------------+    |
--->|AlgDrop         |    |
    | Id=AF12        |    |
    | Type=randomDrop|    |
    | Next ----------+-+--+
    | QMeasure ------+-+
    | QThreshold     |
    | Specific -+    |
    +-----------+----+
                |
    +-----------+
    |  +--------------+
    +->|RandomDropAF12|
       +--------------+

                   Figure 4: 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

A simple Meter that can be parameterized by a single TBMeter entry is
shown here.  For Metering types that require mutliple TBMeter entries
for parameterization, a second level Meter and TBMeter table entries may
be used.  For example, for trTCM, with the first level TBMeter entry
used for Peak Information Token Bucket, the first level SucceedNext
points to the second level Meter entry, with second level TBMeter entry
used for Committed Information Token Bucket.

5.3.  Queue and Scheduler Example Discussion

Example in Figure 4 shows three classified input traffic streams, EF,
AF11, and AF12, feeding into their respective queue and algorithmic
droppers.  After their respective dropping process, the AF traffic
streams feed into the same queue, QAF1X.

A Scheduler, AF, is shown in Figure 4, as the sink for AF1X queue

DiffServ QoS Policy Information Base                       November 2000

traffic, servicing AF1X queue with scheduling parameters indicated by
SchdParamAF1X.  This scheduler is used to service traffic from AF1X,
AF2X, AF3X queues using weighted fair queueing method.  The AF2X and
AF3X queues are not shown in Figure 4, they can be very much like AF1X
queue setup.

Another traffic stream, EF, is handled by the EF queue.  Scheduler
DiffServ services output of EF queue using SchdParamEF, and output of AF
scheduler using SchdParamAF, with Weighted Fair Queueing method.

Notice all the diffserv traffic may go out on a link with traffic
shaping.  The traffic shaping can be parameterize using the Shaping
Scheduler in Figure 4.  For shaping, the qosSchdParamMaxRate attributes
should be used.  The output of the Shaping Scheduler is indicated using
its Next pointer with value of zeroDotZero, the output port.

6.  Summary of the DiffServ PIB

The DiffServ PIB consists of one module containing the base PRCs for
setting DiffServ policy, queues, classifiers, meters, etc.,  and also
contains capability PRC's that allow a PEP to specify its device
characteristics to the PDP.  This module contains two groups, which are
summarized in this section.

QoS Capabilities Group
     This group consists of PRCs to indicate to the PDP the types of
     interface supported on the PEP in terms of their QoS capabilities
     and PRCs that the PDP can install in order to configure these
     interfaces (queues, scheduling parameters, buffer sizes, etc.) to
     affect the desired policy.  This group describes capabilities in
     terms of the types of interfaces and takes configuration in terms
     of interface types and role combinations [FR-PIB]; it does not deal
     with individual interfaces on the device.

QoS Policy Group
     This group contains configuration of the functonal elements that
     comprise the QoS policy that applies to an interface and the
     specific parameters that describe those elements.  This group
     contains classifiers, meters, actions, droppers, queues and
     schedulers. This group also contains the PRC that associates the
     datapath elements with role combinations.

DiffServ QoS Policy Information Base                       November 2000

7.  PIB Operational Overview

This section provides an operation overview of configuring DiffServ QoS
policy.

After initial PEP to PDP communication setup, using [COPS-PR] for
example, the PEP will provide to the PDP the PIB Provisioning Classes
(PRCs), interface types, and interface type capabilities it supports.

The PRCs supported by the PEP are reported to the PDP in the PRC Support
Table, frwkPrcSupportTable defined in the framework PIB [FR-PIB].  Each
instance of the frwkPrcSupportTable indicates a PRC that the PEP
understands and for which the PDP can send class instances as part of
the policy information.

The interface types the PEP supports are described by rows in the
interface type table, frwkIfCapsSetTable.  Each row, or instance of this
class contains a pointer to a instance of a PRC that describes the
capabilities of the interface type.  The capability objects may reside
in the qosIfClassifierCapsTable, the qosIfMeterCapsTable, the
qosIfSchedulerCapsTable, the qosIfElmDepthCapsTable, the
qosIfElmOutputCapsTable, or in a table defined in another PIB.

The PDP, with knowledge of the PEP's capabilities, then provides the PEP
with administration domain and interface-specific policy information.

Instances of the qosDataPathTable are used to specify the first element
in the set of functional elements applied to an interface.  Each
instance of the qosDataPathTable applies to an interface type defined by
its roles and direction (ingress or egress).

DiffServ QoS Policy Information Base                       November 2000

8.  PIB Definitions

8.1.  The DiffServ Base PIB

DIFFSERV-PIB PIB-DEFINITIONS ::= BEGIN

IMPORTS
    Unsigned32, Integer32,
    MODULE-IDENTITY, OBJECT-TYPE
            FROM COPS-PR-SPPI
    zeroDotZero
         FROM SNMPv2-SMI
    TruthValue, TEXTUAL-CONVENTION
            FROM SNMPv2-TC
    InstanceId, ReferenceId, TagId, TagReference
            FROM COPS-PR-SPPI
    RoleCombination
            FROM FRAMEWORK-PIB
    Dscp, IfDirection
            FROM DIFF-SERV-MIB;

qosPolicyPib  MODULE-IDENTITY
    CLIENT-TYPE { tbd   -- QoS Client Type
                }
    LAST-UPDATED "200011241800Z"
    ORGANIZATION "IETF DIFFSERV WG"
    CONTACT-INFO "
                  Michael Fine
                  Cisco Systems, Inc.
                  170 West Tasman Drive
                  San Jose, CA  95134-1706 USA
                  Phone: +1 408 527 8218
                  Email: mfine@cisco.com

                  Keith McCloghrie
                  Cisco Systems, Inc.
                  170 West Tasman Drive,
                  San Jose, CA 95134-1706 USA
                  Phone: +1 408 526 5260

DiffServ QoS Policy Information Base                       November 2000

                  Email: kzm@cisco.com

                  John Seligson
                  Nortel Networks, Inc.
                  4401 Great America Parkway
                  Santa Clara, CA 95054 USA
                  Phone: +1 408 495 2992
                  Email: jseligso@nortelnetworks.com"
    DESCRIPTION
            "The PIB module containing a set of policy rule classes
            that describe quality of service (QoS) policies for
            DiffServ. It includes general classes that may be extended
            by other PIB specifications as well as a set of PIB
            classes related to IP processing."

    ::= { tbd }

qosCapabilityClasses  OBJECT IDENTIFIER ::= { qosPolicyPib 1 }
qosPolicyClasses   OBJECT IDENTIFIER ::= { qosPolicyPib 2 }

--
-- Interface Capabilities Group
--

--
-- Interface Type Capability Tables
--
-- The Interface type capability tables define capabilities that may
-- be associated with an interface of a specific type.  This PIB
-- defines three such tables: a classification capabilities table, a
-- metering capabilities table and a scheduling capabilities table.
-- Other PIBs may define other capability tables to augment the
-- capability definitions of these tables or to introduce completely
-- new capabilities.

--
-- Classification Capabilities
--

DiffServ QoS Policy Information Base                       November 2000

qosIfClassificationCapsTable OBJECT-TYPE
    SYNTAX         SEQUENCE OF QosIfClassificationCapsEntry
    PIB-ACCESS     notify, 3
    STATUS         current
    DESCRIPTION
        "This table specifies the classification capabilities of an
        interface type"
    ::= { qosCapabilityClasses 1 }

qosIfClassificationCapsEntry OBJECT-TYPE
    SYNTAX         QosIfClassificationEntry
    STATUS         current
    DESCRIPTION
        "An instance of this class describes the classification
        capabilities of an interface."

    PIB-INDEX { qosIfClassificationCapsPrid }
    UNIQUENESS { qosIfClassificationCapsSpec }
    ::= { qosIfClassificationCapsTable 1 }

QosIfClassificationCapsEntry ::= SEQUENCE {
        qosIfClassificationCapsPrid InstanceId,
        qosIfClassificationCapsSpec BITS
}

qosIfClassificationCapsPrid OBJECT-TYPE
    SYNTAX         InstanceId
    STATUS         current
    DESCRIPTION
        "An arbitrary integer index that uniquely identifies an
        instance of the class."
    ::= { qosIfClassificationCapsEntry 1 }

qosIfClassificationCapsSpec OBJECT-TYPE
    SYNTAX         BITS {
                        inputIpClassification(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
                        -- IP source addresses
                        ipDstAddrClassification(4),
                        -- indicates the ability to classify based on
                        -- IP destination addresses
                        ipProtoClassification(5),
                        -- indicates the ability to classify based on
                        -- IP protocol numbers
                        ipDscpClassification(6)
                        -- indicates the ability to classify based on
                        -- IP DSCP
                        ipL4Classification(7)
                        -- indicates the ability to classify based on
                        -- IP layer 4 port numbers for UDP and TCP
                   }
    STATUS         current
    DESCRIPTION
        "Bit set of supported classification capabilities.  In
        addition to these capabilities, other PIBs may define other
        capabilities that can then be specified in addition to the
        ones specified here (or instead of the ones specified here if
        none of these are specified)."
    ::= { qosIfClassificationCapsEntry 2 }

--
-- Metering Capabilities
--

qosIfMeteringCapsTable OBJECT-TYPE
    SYNTAX         SEQUENCE OF QosIfMeteringCapsEntry
    PIB-ACCESS     notify, 3
    STATUS         current
    DESCRIPTION
        "This table specifies the metering capabilities of an
        interface type"
    ::= { qosCapabilityClasses 2 }

qosIfMeteringCapsEntry OBJECT-TYPE
    SYNTAX         QosIfMeteringCapsEntry
    STATUS         current
    DESCRIPTION

DiffServ QoS Policy Information Base                       November 2000

        "An instance of this class describes the classification
        capabilities of an interface."

    PIB-INDEX { qosIfMeteringCapsPrid }
    UNIQUENESS { qosIfMeteringCapsSpec }
    ::= { qosIfMeteringCapsTable 1 }

QosIfMeteringCapsEntry ::= SEQUENCE {
        qosIfMeteringCapsPrid       InstanceId,
        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
    SYNTAX      BITS {
                    meterByRemarking (1),
                    meterByDropping (2),
                    -- These capabilities indicate if the interface
                    -- can remark out of profile packets or drop them,
                    -- respectively

                    inputShaping (3),
                    outputShaping (4)
                    -- indicate if the interface can shape on ingress
                    -- or on egress, respectively.

                   }
    STATUS         current
    DESCRIPTION
        "Bit set of supported metering capabilities.  As with
        classification capabilities, these metering capabilities may
        be augmented by capabilities specified in other PRCs (in other

DiffServ QoS Policy Information Base                       November 2000

        PIBs)."
    ::= { qosIfMeteringCapsEntry 2 }

--
-- Scheduling Capabilities
--

qosIfSchedulingCapsTable OBJECT-TYPE
    SYNTAX         SEQUENCE OF QosIfSchedulingCapsEntry
    PIB-ACCESS     notify, 10
    STATUS         current
    DESCRIPTION
        "This table specifies the scheduling capabilities of an
        interface type"
    ::= { qosCapabilityClasses 3 }

qosIfSchedulingCapsEntry OBJECT-TYPE
    SYNTAX         QosIfSchedulingCapsEntry
    STATUS         current
    DESCRIPTION
        "An instance of this class describes the classification
        capabilities of an interface."

    PIB-INDEX { qosIfSchedulingCapsPrid }
    UNIQUENESS { qosIfSchedulingCapsMaxQueues,
                 qosIfSchedulingCapsMaxThresholds,
                 qosIfSchedulingCapsMaxPriorities,
                 qosIfSchedulingCapsServiceDisc,
                 qosIfSchedulingCapsMinQueueSize,
                 qosIfSchedulingCapsMaxQueueSize,
                 qosIfSchedulingCapsTotalQueueSize,
                 qosIfSchedulingCapsWredCapable }
    ::= { qosIfSchedulingCapsTable 1 }

QosIfSchedulingCapsEntry ::= SEQUENCE {
        qosIfSchedulingCapsPrid             InstanceId,
        qosIfSchedulingCapsMaxQueues        INTEGER,
        qosIfSchedulingCapsMaxThresholds    INTEGER,
        qosIfSchedulingCapsMaxPriorities    INTEGER,

DiffServ QoS Policy Information Base                       November 2000

        qosIfSchedulingCapsServiceDisc      BITS,
        qosIfSchedulingCapsMinQueueSize     INTEGER,
        qosIfSchedulingCapsMaxQueueSize     INTEGER,
        qosIfSchedulingCapsTotalQueueSize   INTEGER,
        qosIfSchedulingCapsAlgDropSupported BITS
}

qosIfSchedulingCapsPrid OBJECT-TYPE
    SYNTAX         InstanceId
    STATUS         current
    DESCRIPTION
        "An arbitrary integer index that uniquely identifies an
        instance of the class."
    ::= { qosIfSchedulingCapsEntry 1 }

qosIfSchedulingCapsMaxQueues OBJECT-TYPE
    SYNTAX      INTEGER
    STATUS      current
    DESCRIPTION
        "The maximum number of queues that this interface type can
        support.  A value of zero means that there is no maximum."
    ::= { qosIfSchedulingCapsEntry 2 }

qosIfSchedulingCapsMaxThresholds OBJECT-TYPE
    SYNTAX      INTEGER
    STATUS      current
    DESCRIPTION
        "The maximum number of drop thresholds that each queue
        supports.  If the interface has a different number of
        thresholds for each of its queues, it must report the maximum
        number of thresholds any of the queues supports.  The value of
        this attribute must be one or more."
    ::= { qosIfSchedulingCapsEntry 3 }

qosIfSchedulingCapsMaxPriorities OBJECT-TYPE
    SYNTAX      INTEGER
    STATUS      current
    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

    ::= { qosIfSchedulingCapsEntry 4 }

qosIfSchedulingCapsServiceDisc OBJECT-TYPE
    SYNTAX      BITS {
                    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
    DESCRIPTION
        "The scheduling disciplines supported for servicing queues in
        the same priority group that the interface supports.  Several
        general purpose and well-known queuing disciplines are
        supported by this attribute. Other queueing disciplines may be
        specified instead of, or in addition to, these disciplines by
        setting and providing another capabilities PRC specifying the
        other scheduling discipline.

        If none is specified then the service discipline is either
        unspecified or specified by another capabilities PRC."
    ::= { qosIfSchedulingCapsEntry 5 }

qosIfSchedulingCapsMinQueueSize OBJECT-TYPE
    SYNTAX      INTEGER
    STATUS      current
    DESCRIPTION
        "Some interfaces may allow the size of a queue to be
        configured.  This attribute specifies the minimum size the
        queue can be configured to specified in bytes.

        Some interfaces set queue size in terms of packets.  These
        devices must report the minimum queue size in bytes by
        assuming an average packet size suitable for the particular
        interface."
    ::= { qosIfSchedulingCapsEntry 6 }

DiffServ QoS Policy Information Base                       November 2000

qosIfSchedulingCapsMaxQueueSize OBJECT-TYPE
    SYNTAX      INTEGER
    STATUS      current
    DESCRIPTION
        "Some interfaces may allow the size of a queue to be
        configured.  This attribute specifies the maximum size the
        queue can be configured to specified in bytes.  As with
        qosIfSchedulingCapsMinQueueSize, devices that set
        queue size in terms of packets must report the maximum queue
        size in bytes by assuming an average packet size suitable for
        the particular interface."
    ::= { qosIfSchedulingCapsEntry 7 }

qosIfSchedulingCapsTotalQueueSize OBJECT-TYPE
    SYNTAX      INTEGER
    STATUS      current
    DESCRIPTION
        "Some interfaces may have a limited buffer space to be share
        amoung all queues of that interface while also allowing the
        size of each queue to be configurable.  To prevent the
        situation where the PDP configures the sizes of the queues in
        excess of the total buffer available to the interface, the PEP
        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 {
                     tailDrop(2),
                     headDrop(3),
                     randomDrop(4)
    STATUS      current
    DESCRIPTION
       "The type of algorithm that droppers associated with this queue
       may use.

       The tailDrop(2) algorithm means that packets are dropped from
       the tail of the queue when the associated threshold is
       exceeded.  The headDrop(3) algorithm means that packets are
       dropped from the head of the queue when the associated
       threshold is exceeded. The randomDrop(4) algorithm means that,
       on packet arrival, an algorithm is executed which may randomly
       drop the packet, or  drop  other  packet(s) from  the  queue

DiffServ QoS Policy Information Base PIB

DIFFSERV-PIB PIB-DEFINITIONS                       November 2000

       in  its place.  The specifics of the algorithm may be
       proprietary.  However, parameters would be specified in the
       qosRandomDropTable."
    ::= BEGIN

IMPORTS
    Unsigned32, Integer32,
    MODULE-IDENTITY, OBJECT-TYPE
            FROM COPS-PR-SPPI
    TruthValue, TEXTUAL-CONVENTION
            FROM SNMPv2-TC
    PolicyInstanceId, PolicyReferenceId, PolicyTagId, PolicyTagReference
            FROM COPS-PR-SPPI;
    RoleCombination
            FROM FRAMEWORK-PIB;

qosPolicyIpPib  MODULE-IDENTITY
    CLIENT-TYPE { tbd qosIfSchedulingCapsEntry 9 }

--
-- Datapath Element Linkage Capabilities
--

--
-- Datapath Element Cascade Depth
--

qosIfElmDepthCapsTable OBJECT-TYPE
    SYNTAX         SEQUENCE OF QosIfElmDepthCapsEntry
    PIB-ACCESS     notify, 4
    STATUS         current
    DESCRIPTION
        "This table specifies the number of elements of the same
        type that can be cascaded together in a data path."
    ::= { qosCapabilityClasses 4 }

qosIfElmDepthCapsEntry OBJECT-TYPE
    SYNTAX         QosIfElmDepthCapsEntry
    STATUS         current
    DESCRIPTION
        "An instance of this class describes the cascade depth
        for a particular datapath functional element PRC.  A
        functional datapath element not represented in this
        table can be assumed to have no specific maximum
        depth."

    PIB-INDEX { qosIfElmDepthCapsPrid }
    UNIQUENESS { qosIfElmDepthCapsPrc }
    ::= { qosIfElmDepthCapsTable 1 }

QosIfElmDepthCapsEntry ::= SEQUENCE {
        qosIfElmDepthCapsPrid               InstanceId,
        qosIfElmDepthCapsPrc                OBJECT IDENTIFIER,
        qosIfElmDepthCapsCascadeMax         Unsigned32

DiffServ QoS Client Type Policy Information Base                       November 2000

}
    LAST-UPDATED "200007141800Z"
    ORGANIZATION "IETF DIFFSERV WG"
    CONTACT-INFO "
                  Michael Fine
                  Cisco Systems, Inc.
                  170 West Tasman Drive
                  San Jose, CA  95134-1706 USA
                  Phone: +1 408 527 8218
                  Email: mfine@cisco.com

                  Keith McCloghrie
                  Cisco Systems, Inc.
                  170 West Tasman Drive,
                  San Jose, CA 95134-1706 USA
                  Phone: +1 408 526 5260
                  Email: kzm@cisco.com

                  John Seligson
                  Nortel Networks, Inc.
                  4401 Great America Parkway
                  Santa Clara, CA 95054 USA
                  Phone: +1 408 495 2992
                  Email: jseligso@nortelnetworks.com"

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
    SYNTAX         OBJECT IDENTIFIER
    STATUS         current
    DESCRIPTION
        "The object identifier of a PRC that represents a datapath
        functional element.  This may be one of:  qosClfrElementEntry,
        qosMeterEntry, qosActionEntry, qosAlgDropEntry, qosQEntry, or
        qosSchedulerEntry.  The value is the OID of the table entry.
        There may not be more than one instance of this class with
        the same value of qosIfElmDepthCapsPrc."
    ::= { qosIfElmDepthCapsEntry 2 }

qosIfElmDepthCapsCascadeMax OBJECT-TYPE
    SYNTAX         Unsigned32
    STATUS         current
    DESCRIPTION
        "The PIB module containing a set maximum number of policy rule classes elements of type qosIfElmDepthCapsPrc
        that describe quality can be linked consecutively in a data path."  A value of service (QoS) policies
        zero indicates there is no specific maximum."
    ::= { qosIfElmDepthCapsEntry 3 }

--
-- Datapath Element Linkage Types
--

qosIfElmLinkCapsTable OBJECT-TYPE
    SYNTAX         SEQUENCE OF QosIfElmLinkCapsEntry
    PIB-ACCESS     notify, 5
    STATUS         current
    DESCRIPTION

DiffServ QoS Policy Information Base                       November 2000

        "This table specifies what types of datapath functional
        elements may be used as the next downstream element for
            DiffServ. It includes general classes
        a specific type of functional element."
    ::= { qosCapabilityClasses 5 }

qosIfElmLinkCapsEntry OBJECT-TYPE
    SYNTAX         QosIfElmLinkCapsEntry
    STATUS         current
    DESCRIPTION
        "An instance of this class specifies a PRC that may
         be extended
            by other PIB specifications as well used as the next functional element after a set specific
         type of PIB
            classes related to IP processing."

    ::= element in a data path."

    PIB-INDEX { tbd qosIfElmLinkCapsPrid }
    UNIQUENESS { qosIfElmLinkCapsPrc,
                 qosIfElmLinkCapsAttr,
                 qosIfElmLinkCapsNextPrc }

qosPolicyGenPibClasses  OBJECT IDENTIFIER
    ::= { qosPolicyIpPib qosIfElmLinkCapsTable 1 }
qosPolicyIpPibClasses   OBJECT IDENTIFIER

QosIfElmLinkCapsEntry ::= SEQUENCE { qosPolicyIpPib 2
        qosIfElmLinkCapsPrid              InstanceId,
        qosIfElmLinkCapsPrc               OBJECT IDENTIFIER,
        qosIfElmLinkCapsAttr              Unsigned32,
        qosIfElmLinkCapsNextPrc           OBJECT IDENTIFIER
}

--
-- Textual Conventions
--

--
-- DiffServ Codepoint
--

Dscp ::= TEXTUAL-CONVENTION

qosIfElmLinkCapsPrid OBJECT-TYPE
    SYNTAX         InstanceId
    STATUS         current
    DESCRIPTION
        "An arbitrary integer index that uniquely identifies an
        instance of the class."
    ::= { qosIfElmLinkCapsEntry 1 }

qosIfElmLinkCapsPrc OBJECT-TYPE
    SYNTAX         OBJECT IDENTIFIER
    STATUS         current
    DESCRIPTION
        "The value is in the range OID of the a PRC that represents a
        functional datapath element."

DiffServ codepoint
        values."

    SYNTAX INTEGER (0..63)

--
-- Interface types
--

QosInterfaceQueueCount QoS Policy Information Base                       November 2000

    ::= TEXTUAL-CONVENTION { qosIfElmLinkCapsEntry 2 }

qosIfElmLinkCapsAttr OBJECT-TYPE
    SYNTAX         Unsigned32
    STATUS         current
    DESCRIPTION
        "An integer that describes
        "The value represents the number of queues an interface
        supports.  It attribute in the the PRC
         indicated by qosIfElmLinkCapsPrc that is limited used to
         specify the number of DSCP values."

    SYNTAX INTEGER (1..64)

--
-- QoS Interface Group
--

--
-- This group specifies next functional element in the configuration datapath.

         The attribute value corresponds to the order in which
         the attribute appears in the definition of the various interface
-- types including PRC.
         A value of 1 indicates the configuration first attribute of queue sets, setting the PRC,
         a value of
-- queueing parameters and 2 indicates the mapping second attribute of DSCPs to thresholds in
-- queues.

qosIfParameters the
         PRC, and so forth."
    ::= { qosIfElmLinkCapsEntry 3 }

qosIfElmLinkCapsNextPrc OBJECT-TYPE
    SYNTAX         OBJECT IDENTIFIER
    STATUS         current
    DESCRIPTION
        "The value is the OID of a PRC table entry from which
        instances can be referenced by the attribute indicated
        by qosIfElmLinkCapsPrc and qosIfElmLinkAttr.

        For example, suppose a meter's success output can be an
        action or another meter, and the fail output can only be
        an action.  This can be expressed as follows:

        Prid Prc             Attr                  NextPrc
        1    qosMeterEntry   qosMeterSucceedNext   qosActionEntry
        2    qosMeterEntry   qosMeterSucceedNext   qosMeterEntry
        3    qosMeterEntry   qosMeterFailNext      qosActionEntry."
    ::= { qosPolicyGenPibClasses 1 qosIfElmLinkCapsEntry 4 }

--
-- Interface Type Capability Tables
-- Data Path
-- The Interface type capability tables define capabilities that may

-- be associated with an interface of a specific type.  This PIB
-- defines three such tables: a classification capabilities table, a Data Path Table

DiffServ QoS Policy Information Base                       November 2000

-- metering capabilities table and a scheduling capabilities table.
-- Other PIBs may define other capability tables to augment The Data Path Table enumerates the Differentiated Services
-- capability definitions of these tables or Data Paths within this device.  Each entry specifies
-- the first functional datapath element to introduce completely process data flow
-- new capabilities. for each specific datapath.  Each datapath is defined by the
-- interface role combination and direction. This table can
-- Classification Capabilities therefore have up to two entries for each role combination,
--

qosIfClassificationCapsTable ingress and egress.

qosDataPathTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF QosIfClassificationCapsEntry QosDataPathEntry
    PIB-ACCESS     notify, 3   install, 5
    STATUS       current
    DESCRIPTION
        "This
       "The data path table specifies defines the data paths  in  this
       device.   Each  data path is defined by the classification capabilities interface,
       role combination and traffic direction.  The first
       functional datapath element  to  handle  traffic  for
       this  data path is defined by  a  Prid in the entries
       of an
        interface type" this table."
    ::= { qosIfParameters qosPolicyClasses 1 }

qosIfClassificationCapsEntry

qosDataPathEntry OBJECT-TYPE
    SYNTAX         QosIfClassificationEntry       QosDataPathEntry
    STATUS       current
    DESCRIPTION
       "An instance of this class describes entry in the classification
        capabilities of an interface."

    INDEX data path table describes  a  single
       data path in this device."
    PIB-INDEX { qosIfClassificationCapsPrid qosDataPathPrid }
    UNIQUENESS { qosIfClassificationCaps qosDataPathRoles,
                 qosDataPathIfDirection }
    ::= { qosIfClassificationCapsTable qosDataPathTable 1 }

QosIfClassificationCapsEntry

QosDataPathEntry ::= SEQUENCE  {
        qosIfClassificationCapsPrid PolicyInstanceId,
        qosIfClassificationCaps     BITS
    qosDataPathPrid           InstanceId,
    qosDataPathRoles          RoleCombination,
    qosDataPathIfDirection    IfDirection,
    qosDataPathStart          Prid
}

qosIfClassificationCapsPrid

qosDataPathPrid OBJECT-TYPE

DiffServ QoS Policy Information Base                       November 2000

    SYNTAX         PolicyInstanceId       InstanceId
    STATUS       current
    DESCRIPTION
       "An arbitrary integer index that uniquely identifies a an
        instance of the class."
    ::= { qosIfClassificationCapsEntry qosDataPathEntry 1 }

qosIfClassificationCaps

qosDataPathRoles OBJECT-TYPE
    SYNTAX         BITS {
                        inputIpClassification(1),
                        outputIpClassification(2),
                        -- Indicates the ability to classify IP
                        -- packets on ingress and on egress,
                        -- respectively.

                        ipAddrClassification(3),
                        -- indicates the ability to classify based on
                        -- IP addresses
                        ipProtoClassification(4),
                        -- indicates the ability to classify based on
                        -- IP protocol numbers
                        ipDscpClassification(5)
                        -- indicates the ability to classify based on
                        -- IP DSCP
                        ipL4Classification(6)
                        -- indicates the ability to classify based on
                        -- IP layer 4 port numbers for UDP and TCP
                   }       RoleCombination
    STATUS       current
    DESCRIPTION
        "Bit set of supported classification capabilities.  In
        addition
       "The interfaces to these capabilities, other PIBs may define other
        capabilities that can then be which this data path entry applies,
        specified in addition to the
        ones specified here (or instead terms of the ones roles.  The role combination
        specified here if
        none of these are specified)."
    ::= { qosIfClassificationCapsEntry 2 }

--
-- Metering Capabilities
--

qosIfMeteringCapsTable OBJECT-TYPE
    SYNTAX         SEQUENCE OF QosIfMeteringCapsEntry
    PIB-ACCESS     notify, 3
    STATUS         current
    DESCRIPTION
        "This table specifies by this attribute must exist in the metering capabilities of
        frwkIfCapSetRoleComboTable [FR-PIB] prior to association
        with an
        interface type" instance of this class."
    ::= { qosIfParameters qosDataPathEntry 2 }

qosIfMeteringCapsEntry

qosDataPathIfDirection OBJECT-TYPE
    SYNTAX         QosIfMeteringCapsEntry       IfDirection
    STATUS       current
    DESCRIPTION
        "An instance of
       "Specifies the direction for  which  this  data  path
       entry applies on this class describes the classification
        capabilities of an interface."

    INDEX { qosIfMeteringCapsPrid }
    UNIQUENESS { qosIfMeteringCaps }

    ::= { qosIfMeteringCapsTable 1 }

QosIfMeteringCapsEntry
    ::= SEQUENCE {
        qosIfMeteringCapsPrid       PolicyInstanceId,
        qosIfMeteringCaps           BITS qosDataPathEntry 3 }

qosIfMeteringCapsPrid

qosDataPathStart OBJECT-TYPE
    SYNTAX         PolicyInstanceId       Prid
    STATUS       current
    DESCRIPTION
        "An arbitrary integer index that uniquely identifies a
       "This selects the first functional  datapath  element
       to   handle   traffic   for  this  data  path.   This
       Prid should point to an instance of one of:
         qosClfrEntry
         qosMeterEntry
         qosActionEntry
         qosAlgDropEntry
         qosQEntry

       The PRI to must exist prior to the class." installation of
       this datapath start element."
    ::= { qosIfMeteringCapsEntry 1 qosDataPathEntry 4 }

qosIfMeteringCaps OBJECT-TYPE
    SYNTAX      BITS {
                    meterByRemarking (1),
                    meterByDropping (2),

DiffServ QoS Policy Information Base                       November 2000

-- These capabilities indicate if the interface
-- can remark out of profile packets or drop them, Classifiers
-- respectively

                    inputShaping (3),
                    outputShaping (4)

-- indicate if the interface can shape on ingress
-- or on egress, respectively.

                   }
    STATUS         current
    DESCRIPTION
        "Bit set Classifier Table
--
-- Classifier allows multiple classifier elements, of supported classification capabilities.  As with
        classification capabilities, these metering capabilities may same or different
-- types, to be augmented by capabilities specified in other PRCs (in other
        PIBs)."

    ::= { qosIfMeteringCapsEntry 2 } used together.
-- A classifier must completely classify all packets presented to it.
-- This means all traffic handled by a classifier must match
-- Scheduling Capabilities at least one classifier element within the classifier,
--

qosIfSchedulingCapsTable with the classifier element parameters specified by a filter.

qosClfrTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF QosIfSchedulingCapsEntry QosClfrEntry
    PIB-ACCESS     notify, 10   install, 3
    STATUS       current
    DESCRIPTION
        "This table specifies the scheduling capabilities of an
        interface type"
       ""
    REFERENCE
        "[MODEL] section 4.1"
    ::= { qosIfParameters 3 qosPolicyClasses 2 }

qosIfSchedulingCapsEntry

qosClfrEntry OBJECT-TYPE
    SYNTAX         QosIfSchedulingCapsEntry       QosClfrEntry
    STATUS       current
    DESCRIPTION
       "An instance of this class entry in the classifier table  describes  a
       single classifier, all classifier elements belong-
       ing  to  the classification
        capabilities of an interface."

    INDEX { qosIfSchedulingCapsPrid }
    UNIQUENESS { qosIfSchedulingCapsMaxQueues,
                 qosIfSchedulingCapsMaxThresholds,
                 qosIfSchedulingCapsMaxPriorities,
                 qosIfSchedulingCapsServiceDisc,
                 qosIfSchedulingCapsMinQueueSize,
                 qosIfSchedulingCapsMaxQueueSize,
                 qosIfSchedulingCapsTotalQueueSize,
                 qosIfSchedulingCapsWredCapable same classifier must have its
       qosClfrElementClfrId attribute have the same
       value, one of qosClfrId."
    PIB-INDEX { qosClfrPrid }
    UNIQUENESS { qosClfrId }
    ::= { qosIfSchedulingCapsTable qosClfrTable 1 }

QosIfSchedulingCapsEntry

QosClfrEntry ::= SEQUENCE  {
        qosIfSchedulingCapsPrid             PolicyInstanceId,
        qosIfSchedulingCapsMaxQueues        INTEGER
        qosIfSchedulingCapsMaxThresholds    INTEGER
        qosIfSchedulingCapsMaxPriorities    INTEGER
        qosIfSchedulingCapsServiceDisc      BITS
        qosIfSchedulingCapsMinQueueSize     INTEGER
        qosIfSchedulingCapsMaxQueueSize     INTEGER
        qosIfSchedulingCapsTotalQueueSize   INTEGER
        qosIfSchedulingCapsWredCapable      TruthValue
    qosClfrPrid            InstanceId,
    qosClfrId              TagReference
}

qosIfSchedulingCapsPrid

DiffServ QoS Policy Information Base                       November 2000

qosClfrPrid OBJECT-TYPE
    SYNTAX         PolicyInstanceId       InstanceId
    STATUS       current
    DESCRIPTION
       "An arbitrary integer index that uniquely identifies a an
        instance of the class."
    ::= { qosIfSchedulingCapsEntry qosClfrEntry 1 }

qosIfSchedulingCapsMaxQueues

qosClfrId OBJECT-TYPE
    SYNTAX      INTEGER       TagReference
    PIB-TAG      qosClfrElementClfrId
    STATUS       current
    DESCRIPTION
        "The maximum number of queues that this interface type can
        support.  The queues set assigned to this interface type may
        not have more queues than this maximum.
       "Identifies a Classifier.  A value of zero  Classifier must be
       complete, this means
        that all traffic handled by a
       Classifier must match at least  one  Classifier
       Element within  the  Classifier,  with  the Classifier
       parameters specified by a Filter.

       If there is no maximum." 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.
    ::= { qosIfSchedulingCapsEntry qosClfrEntry 2 }

qosIfSchedulingCapsMaxThresholds OBJECT-TYPE
    SYNTAX      INTEGER
    STATUS      current
    DESCRIPTION
        "The maximum number of drop thresholds that each queue
        supports.  If

--
-- Classifier Element Table
--
-- Entries in the interface has a different number of
        thresholds classifier element table serves as
-- the anchor for each of its queues, it must report classification pattern, defined
-- in filter table entries.  Each classifier element
-- table entry also specifies the maximum
        number of thresholds any of subsequent downstream
-- diffserv functional datapath element when the queues supports.  The value of
        this attribute must be
-- classification pattern is satisfied.
-- Each entry in the classifier element table describes
-- one or more."

    ::= { qosIfSchedulingCapsEntry 3 }

qosIfSchedulingCapsMaxPriorities OBJECT-TYPE
    SYNTAX      INTEGER
    STATUS      current
    DESCRIPTION
        "The maximum number branch of priority groups that the the queues fan-out characteristic of
        the interface may be grouped into. a classifier
-- indicated in [MODEL] section 4.1.  A value of zero means
        there is no maximum."

    ::= { qosIfSchedulingCapsEntry 4 }

qosIfSchedulingCapsServiceDisc OBJECT-TYPE
    SYNTAX      BITS {
                    fq(1), classifier is madeup
-- fair queueing (a.k.a. round robin)
                    wfq(2) of one or more classifier elements.
-- weighted fq (a.k.a. wrr)

qosClfrElementTable OBJECT-TYPE

DiffServ QoS Policy Information Base                       November 2000

    SYNTAX       SEQUENCE OF QosClfrElementEntry
    PIB-ACCESS   install, 6
    STATUS       current
    DESCRIPTION
       "The scheduling disciplines supported for servicing queues in
        the same priority group that classifier element table  enumerates  the interface supports.  Several
        general purpose  rela-
       tionship  between  classification patterns and well-known queuing disciplines subse-
       quent downstream diffserv  functional  datapath  ele-
       ments.   Classification  parameters  are
        supported  defined  by this attribute. Other queueing disciplines may be
        specified instead of, or in addition to, these disciplines
       entries   of   filter   tables    pointed    to    by
        setting and providing another capabilities PRC specifying the
        other scheduling discipline.

        A value
       qosClfrElementSpecific.   There  can  be  filter
       tables of fq indicates that the interface supports fair
        queuing, i.e., each queue is treated equally different types, and is serviced
        in  they  can  be  inter-
       mixed  and used within a round-robin fashion.

        A value classifier.  An example of wfq indicates that the queue is serviced
        using a weighted fair queuing discipline. Queues are serviced
        in a round robin fashion but each queue is given bandwidth in
        proportion to its weight.

        If none
       filter table is specified then the service discipline is either
        unspecified or specified by another capabilities PRC." frwkIpFilterTable, defined in
       [FR-PIB],  for IP Multi-Field Classifiers (MFCs).
       Filter tables for other filter types may  be  defined
       elsewhere."
    REFERENCE
        "[MODEL] section 4.1"
    ::= { qosIfSchedulingCapsEntry 5 qosPolicyClasses 3 }

qosIfSchedulingCapsMinQueueSize

qosClfrElementEntry OBJECT-TYPE
    SYNTAX      INTEGER       QosClfrElementEntry
    STATUS       current
    DESCRIPTION
        "Some interfaces may allow
       "An entry in the size of classifier element table describes a queue to be
        configured.  This attribute specifies the minimum size the
        queue can be configured to specified in bytes.

        Some interfaces set queue size in terms
       single element of packets.  These
        devices must report the minimum queue size in bytes by
        assuming classifier."
    PIB-INDEX { qosClfrElementPrid }
    UNIQUENESS { qosClfrElementClfrId,
                 qosClfrElementOrder,
                 qosClfrElementSpecific }
    ::= { qosClfrElementTable 1 }

QosClfrElementEntry ::= SEQUENCE  {
    qosClfrElementPrid        InstanceId,
    qosClfrElementClfrId      TagId,
    qosClfrElementOrder       Unsigned32,
    qosClfrElementNext        Prid,
    qosClfrElementSpecific    Prid
}

qosClfrPrid OBJECT-TYPE
    SYNTAX       InstanceId

DiffServ QoS Policy Information Base                       November 2000

    STATUS       current
    DESCRIPTION
       "An arbitrary integer index that uniquely identifies an average packet size suitable for
        instance of the particular
        interface." class."
    ::= { qosIfSchedulingCapsEntry 6 qosClfrElementEntry 1 }

qosIfSchedulingCapsMaxQueueSize

qosClfrElementClfrId OBJECT-TYPE
    SYNTAX      INTEGER       TagId
    STATUS       current
    DESCRIPTION
        "Some interfaces may allow the size of
       "A classifier Id  identifies  which  classifier  this
       classifier  element  is  a queue part of.  This needs to be
        configured.  This attribute specifies the maximum size
       the
        queue can be configured to specified in bytes.  As with
        qosIfSchedulingCapsMinQueueSize, devices that set
        queue size in terms value of packets must report the maximum queue
        size in bytes by assuming an average packet size suitable qosClfrId attribute for
        the particular interface." an existing
       instance of qosClfrEntry."
    ::= { qosIfSchedulingCapsEntry 7 qosClfrElementEntry 2 }

qosIfSchedulingCapsTotalQueueSize

qosClfrElementOrder OBJECT-TYPE
    SYNTAX      INTEGER       Unsigned32
    STATUS       current
    DESCRIPTION
        "Some interfaces may have a limited buffer space to be share
        amoung all queues of that interface while also allowing
       "The relative order in which classifier elements are
       applied:  higher  numbers  represent classifier elements
       with higher precedence.  Classifier elements with the
        size of each queue same
       order  must  be  unambiguous  i.e. they must define
       non-overlapping patterns, and are  considered  to  be configurable.  To prevent the
        situation where the PDP configures the sizes of the queues in
        excess of the total buffer available
       applied  simultaneously  to the interface, the PEP
        can report traffic stream. Clas-
       sifier elements with different order  may  overlap in
       their  filters:  the total buffer space available classifier element with this
        capability.  The value the highest
       order that matches is taken.

       On a given interface, there must be a complete  clas-
       sifier  in  place  at  all  times in   the total number of bytes."

    ::= { qosIfSchedulingCapsEntry 8 }

qosIfSchedulingCapsWredCapable OBJECT-TYPE
    SYNTAX      TruthValue
    STATUS      current
    DESCRIPTION
        "If true, then this interface supports WRED on (at least
       ingress direction.  This means that there will always
       be one
        of) its queues.  Otherwise it supports only taildrop." or more filters that match every possible pat-
       tern  that  could be presented in an incoming packet.
       There is no such requirement in the egress direction."
    DEFVAL { 0 }
    ::= { qosIfSchedulingCapsEntry 9 qosClfrElementEntry 3 }

--
--  Queue Set Assignment Table
--

qosIfQueueSetAssignTable

qosClfrElementNext OBJECT-TYPE
    SYNTAX         SEQUENCE OF QosIfQueueSetAssignEntry
    PIB-ACCESS     install, 6       Prid
    STATUS       current

DiffServ QoS Policy Information Base                       November 2000

    DESCRIPTION
        "Contains the assignment
       "This attribute provides one branch  of queue sets to interface types per
        role combination.

        Contains  the assignment  fan-out
       functionality  of DSCPs to queues and thresholds for
        each interface type.  So, after classification and metering,
        when the packet has  a final DSCP mark, the packet is enqueued
        on the apprpriate queue at the appropriated threshold based on  classifier described in [MODEL]
       section 4.1.

       This selects the mapping next  diffserv  functional  datapath
       element  to  handle traffic for this data path.

       A value of zeroDotZero marks the DSCP end of DiffServ processing
       for this data path.  Any other value must point to threshollds in queues." a
       valid (pre-existing) instance of one of:"
         qosClfrEntry
         qosMeterEntry
         qosActionEntry
         qosAlgDropEntry
         qosQEntry."
    DEFVAL      { zeroDotZero }
    ::= { qosIfParameters qosClfrElementEntry 4 }

qosIfQueueSetAssignEntry

qosClfrElementSpecific OBJECT-TYPE
    SYNTAX         QosIfQueueSetAssignEntry       Prid
    STATUS       current
    DESCRIPTION
       "A conceptual row pointer to a valid entry  in the qosIfQueueSetAssignTable.

    INDEX { qosIfQueueSetAssignPrid }
    UNIQUENESS { qosIfQueueSetAssignIfName,
                 qosIfQueueSetAssignRoles }

    ::= { qosIfQueueSetAssignTable 1 }

QosIfQueueSetAssignEntry ::= SEQUENCE {
        qosIfQueueSetAssignPrid              PolicyInstanceId,
        qosIfQueueSetAssignName              SnmpAdminString,
        qosIfQueueSetAssignRoles             RoleCombination,
        qosIfQueueSetAssignQueueSetId        PolicyTagReference,
        qosIfQueueSetAssignDscpMap           PolicyTagReference
}

qosIfQueueSetAssignPrid OBJECT-TYPE
    SYNTAX         PolicyInstanceId
    STATUS         current
    DESCRIPTION
        "The index  another  table  that uniquely identifies this row
       describes  the applicable classification filter, e.g.
       an entry in frwkIpFilterTable [FR-PIB].

       The PRI pointed to must exist prior to the table,
        i.e., installation of
       this PRI." classifier element.

       The value zeroDotZero is interpreted  to  match  any-
       thing  not  matched  by another classifier element - only one
       such entry may exist for each classifier."
    DEFVAL { zeroDotZero }
    ::= { qosIfQueueSetAssignEntry 1 qosClfrElementEntry 5 }

qosIfQueueSetAssignName OBJECT-TYPE
    SYNTAX         SnmpAdminString
    STATUS         current
    DESCRIPTION
        "The name

--
-- Meters
--
-- This PIB supports a variety of Meters.  It includes a
-- specific definition for Meters whose parameter set can
-- be modelled using Token Bucket parameters.
-- Other metering parameter sets can be defined and used

DiffServ QoS Policy Information Base                       November 2000

-- when necessary.
--
-- Multiple meter elements may be logically cascaded
-- using their qosMeterSucceedNext pointers if
-- a multi-rate Meter is required.
-- One example of this might be for an AF PHB implementation
-- that uses two-rate meters.
--
-- Cascading of an interface type.  This name must exist individual meter elements in
        frwkIfCapSetTable."

    ::= { qosIfQueueSetAssignEntry 2 }

qosIfQueueSetAssignRoles OBJECT-TYPE
    SYNTAX         RoleCombination
    STATUS         current
    DESCRIPTION
        "The role combination associated with the interface type.

    ::= { qosIfQueueSetAssignEntry 3 }

qosIfQueueSetAssignQueueSet OBJECT-TYPE
    SYNTAX         PolicyTagReference
    PIB-TAG       qosIfQueueSetId
    STATUS         current
    DESCRIPTION
        "The integer ID PIB is intended
-- to be functionally equivalent to determining the conformance
-- level of a packet using a multi-rate meter.  The sequential
-- nature of the queue set representation is merely a notational
-- convenience for this PIB.
--
-- For example:
-- Conforming to RFC 2697, srTCM can be assigned to all interfaces parameterized using
-- two sets of type specified by qosIfQueueSetAssignName qosMeterEntry and with role
        combination specified by qosIfQueueSetAssignRoles.
        This queue qosTBMeterEntry.
-- With the first set must exist in qosIfQueueTable."

    ::= { qosIfQueueSetAssignEntry 4 }

qosIfQueueSetAssignDscpMap OBJECT-TYPE
    SYNTAX         PolicyTagReference
    PIB-TAG        qosIfDscpMapMapId
    STATUS         current
    DESCRIPTION
        "The DSCP map parameterizing the Committed Burst Size
-- token-bucket, second set parameterizing the Excess Burst Size
-- token-bucket.  With both set's qosTBMeterRate parameters
-- being used to apply reflect the Committed Information Rate value.
--
-- Conforming to interfaces RFC 2698, trTCM can be parameterized using
-- two sets of type
        qosIfQueueSetAssignName qosMeterEntry and role combo
        qosIfQueueSetAssignRoles."

    ::= { qosIfQueueSetAssignEntry 5 } qosTBMeterEntry.
-- With the first set parameterizing the Peak Information Rate
-- Interface Queue Table
-- and Peak Burst Size token-bucket, second set parameterizing
-- The Interface Queue Table enumerates the individual queues Committed Information Rate and Committed Burst Size
-- groups  them into queue sets.  Configuration token-bucket.
--
-- Conforming to RFC 2859, tswTCM can be parameterized using
-- two sets of each queue, qosMeterEntry and qosTBMeterEntry.
-- hence an entire queue With the first set is parameterizing the Committed Target Rate,
-- second set parametering the Peak Target Rate.
-- With both set's qosTBMeterInterval being used to
-- reflect the Average Interval as specified by this table. RFC 2859.
--

qosIfQueueTable

qosMeterTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF QosIfQueueEntry QosMeterEntry
    PIB-ACCESS   install, 10 5
    STATUS       current
    DESCRIPTION
        "Contains configuration information for
       "This table enumerates specific meters that a  system
       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 individual queues  element(s)
       upstream  of  the queue sets."  meter  i.e.  by the object(s) that
       point to each entry in this table. This  may  include
       all traffic on an interface.

       Specific meter details are to be found  in
       qosMeterSpecific."
           REFERENCE
               "[MODEL] section 5.1"
    ::= { qosIfParameters 5 qosPolicyClasses 4 }

qosIfQueueEntry

qosMeterEntry OBJECT-TYPE
    SYNTAX         QosIfQueueEntry       QosMeterEntry
    STATUS       current
    DESCRIPTION
        "A conceptual row
       "An entry in the qosIfQueueTable.

        Each row identifies a specific queue within a given queue
        set and contains detailed information about the queue. Queues
        are associated with a given set through this  meter  table and  describing  a queue set is associated with an interface set through
        the qosIfQsetAssignTable."

    INDEX  single
       meter."
    PIB-INDEX { qosIfQueuePrid qosMeterPrid }
    UNIQUENESS {} { }
    ::= { qosIfQueueTable qosMeterTable 1 }

QosIfQueueEntry

QosMeterEntry ::= SEQUENCE  {
        qosIfQueuePrid                  PolicyInstanceId,
        qosIfQueueSetId                 PolicyTagId,
        qosIfQueueQueueSize             Unsigned32,
        qosIfQueueSetThreshSet          PolicyTagReference,
        qosIfQueuePriorityGroup         INTEGER,
        qosIfQueueServiceDisc           INTEGER,
        qosIfQueueDrainSize             Unsigned32,
        qosIfQueueMinAbsBandwidth       Unsigned64,
        qosIfQueueBandwidthAllocation   INTEGER
    qosMeterPrid              InstanceId,
    qosMeterSucceedNext       Prid,
    qosMeterFailNext          Prid,
    qosMeterSpecific          Prid
}

qosIfQueuePrid

qosMeterPrid OBJECT-TYPE
    SYNTAX         PolicyInstanceId       InstanceId
    STATUS       current
    DESCRIPTION
        "The
       "An arbitrary integer index that uniquely identifies this row in an
        instance of the table,
        i.e., this PRI." class."
    ::= { qosIfQueueEntry qosMeterEntry 1 }

qosIfQueueSetId

qosMeterSucceedNext OBJECT-TYPE
    SYNTAX         PolicyTagId       Prid
    STATUS       current
    DESCRIPTION
        "An index that uniquely identifies a specific queue set. The
        queue set identified by this value is associated
        with an interface set through
       "If the
        qosIfQueueSetAssignQueueSetId object in traffic does conform, this selects  the
        qosIfQueueSetAssignTable.  next

DiffServ QoS Policy Information Base                       November 2000

       diffserv   functional   datapath  element  to  handle
       traffic for this data path.

       The individual queues that are
        members value zeroDotZero in this variable  indicates  no
       further Diffserv treatment is performed on traffic of
       this set all have the same datapath.  Any other value for this attribute
        (i.e., they have the same set ID)." must point to a valid
       (pre-existing) instance of one of:"
         qosClfrEntry
         qosMeterEntry
         qosActionEntry
         qosAlgDropEntry
         qosQEntry."
    DEFVAL      { zeroDotZero }
    ::= { qosIfQueueEntry qosMeterEntry 2 }

qosIfQueueQueueSize

qosMeterFailNext OBJECT-TYPE
    SYNTAX         Unsigned32       Prid
    STATUS       current
    DESCRIPTION
       "The size of the queue in bytes.  Some devices set queue size
        in terms of packets.  These devices must calculate the queue
        size in packets by assuming an average packet size suitable
        for
       "If the particular interface.

        Some devices have a fixed size buffer to be shared among all
        queues.  These devices must allocate a fraction of traffic does not conform,  this  selects  the
        total buffer space
       next  diffserv  functional datapath element to handle
       traffic for this queue calculated as the the ratio data path.

       The value zeroDotZero in this variable  indicates  no
       further Diffserv treatment is performed on traffic of the queue size
       this datapath.  Any other value must point to the sum a valid
       (pre-existing) instance of the queue sizes for the
        interface." one of:"
         qosClfrEntry
         qosMeterEntry
         qosActionEntry
         qosAlgDropEntry
         qosQEntry."
    DEFVAL      { zeroDotZero }
    ::= { qosIfQueueEntry qosMeterEntry 3 }

qosIfQueueThreshSet

qosMeterSpecific OBJECT-TYPE
    SYNTAX         PolicyTagReference
    PIB-TAG        qosIfThresholdSetId       Prid
     STATUS       current
    DESCRIPTION
       "The threshold set in the threshold set table that is to be
        used to configure
       "This indicates the thresholds behaviour of this queue.  The threshold
        set specifies how to configure the taildrop or RED thresholds
        for this queue.

        "The threshold set may contain less thresholds than the queue
        actually supports.  In this case the queue is free meter by  point-
       ing  to
        configure the extra thresholds any way it likes since no
        packets will ever an entry containing detailed parameters. Note
       that entries in that specific table must  be assigned  managed
       explicitly.

DiffServ QoS Policy Information Base                       November 2000

       For example, qosMeterSpecific may  point  to those thresholds.

        A value  an
       entry  in  qosTBMeterTable,  which  contains  an
       instance of zero indicates no threshold set is associated with
        the queue.  In this case the queue is configured with a single
        threshold at 100% qosIfThresholdDropMethod set of tailDrop." Token Bucket parameters.

       The PRI pointed to must exist prior to installing this
       Meter datapath element."
    ::= { qosIfQueueEntry 4 qosMeterEntry 5 }

qosIfQueuePriorityGroup

--
-- Token-Bucket Meter Table
--
-- Each entry in the Token Bucket Meter Table parameterize
-- a single token bucket.  Multiple token buckets can be
-- used together to parameterize multiple levels of
-- conformance.
--

qosTBMeterTable OBJECT-TYPE
    SYNTAX         INTEGER       SEQUENCE OF QosTBMeterEntry
    PIB-ACCESS   install, 6
    STATUS       current
    DESCRIPTION
       "This attribute specifies the priority group table enumerates specific  token-bucket  meters
       that the queue
        belongs to.  Queues with a larger priority group number are
        given  a higher priority than those with system may use to police a smaller group
        number. For example, stream of traffic.
       Such meters are modelled here as having a queue in priority group 2 will be
        serviced (i.e., drained) before some other queue with single rate
       and a group
        number of 1.

        Queues with the same priority group number have single burst size."
    REFERENCE
        "[MODEL] section 5.1"
    ::= { qosPolicyClasses 5 }

qosTBMeterEntry OBJECT-TYPE
    SYNTAX       QosTBMeterEntry
    STATUS       current
    DESCRIPTION
       "An entry that describes a single token-bucket meter,
       indexed  by  the same
        priority.  For these another scheduling discipline (other than
        priority scheduling) must be specified.  This is done with variables as a qosMeterEn-
       try."
    PIB-INDEX { qosTBMeterPrid }
    UNIQUENESS { qosTBMeterType,
                 qosTBMeterRate,
                 qosTBMeterBurstSize,
                 qosTBMeterInterval }

DiffServ QoS Policy Information Base                       November 2000

    ::= { qosTBMeterTable 1 }

QosTBMeterEntry ::= SEQUENCE  {
    qosTBMeterPrid            InstanceId,
    qosTBMeterType            INTEGER,
    qosTBMeterRate            Unsigned32,
    qosTBMeterBurstSize       BurstSize,
    qosTBMeterInterval        Unsigned32
}

qosTBMeterPrid OBJECT-TYPE
    SYNTAX       InstanceId
    STATUS       current
    DESCRIPTION
       "An arbitrary integer index that uniquely identifies an
        instance of the
        qosIfQueueServiceDisc attribute." class."
    ::= { qosIfQueueEntry 5 qosTBMeterEntry 1 }

qosIfQueueServiceDisc

qosTBMeterType OBJECT-TYPE
    SYNTAX       INTEGER {
                       na(1),     -- only one queue in group
                       other(2),  -- specified by augmented attributes
                       fq(3),
                     tokenBucket(2),  -- Fair Queuing
                       wfq(4) 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)        -- Weighted Fair Queuing tswTCM
                 }
    STATUS       current
    DESCRIPTION
        "This attribute identifies the service discipline used to
        service the queues in the same priority group.  It must have
        the same value for all queues in the priority group.  Several
        general purpose and well-known queuing disciplines are
        supported by this attribute. Queuing disciplines that differ
        from those that are supported by this attribute are
       "The type of meter using parameters specified by setting this attribute to other(1) and augmenting this PRC
        with additional attributes to specify
       TBMeter entry.

       Value of tokenBucket(2)  indicates  the desired service
        discipline.

        As an example, an interface that is associated with a queue
        set supporting two priority queues and three queues that are
        serviced using WFQ would be modeled  use  of  Two
       Parameter  Token Bucket Meter as follows:

             Id    Q Discipline  Q Drain Size  Priority Group
             22         na(1)         -              3
             23         na(1)         -              2
             24        wfq(3)        500             1
             25        wfq(3)        350             1
             26        wfq(3)        150             1

        The queue set presented in this example would service
        all queued traffic described in queue 22 first, followed by all [MODEL]
       section 5.2.3.

       Value of avgRate(3) indicates the queued traffic use of Average Rate
       Meter as described in queue 23. Next [MODEL] section 5.2.1.

       Value of srTCMBlind(4)  and  srTCMAware(5)  indicates
       the queued traffic
        in queues 24 through 26 would be serviced in a round
        robin fashion use of Single Rate Three Color Marker Metering as

DiffServ QoS Policy Information Base                       November 2000

       defined by RFC 2697, with queue 24 receiving 50% of `Color  Blind'  and  `Color
       Aware' mode as described by the available
        bandwidth, queue 25 receiving 35% RFC.

       Value of trTCMBlind(6)  and  trTCMAware(7)  indicates
       the available
        bandwidth  use  of  Two Rate Three Color Marker Metering as
       defined by RFC 2698, with `Color  Blind'  and queue 26 receiving 15%  `Color
       Aware' mode as described by the RFC.

       Value of tswTCM(8) indicates the available
        bandwidth. use of Time  Sliding
       Window  Three Color Marker Metering as defined by RFC
       2859."
    REFERENCE
        "[MODEL] section 5"
    ::= { qosTBMeterEntry 2 }

qosTBMeterRate OBJECT-TYPE
    SYNTAX       Unsigned32
    UNITS        "kilobits per second"
    STATUS       current
    DESCRIPTION
       "The  token-bucket  rate,  in  kilobits  per   second
       (kbps).   This example  attribute  is presented used for: 1. CIR in RFC
       2697 for expository
        purposes srTCM 2. PIR and has been simplified accordingly.

        Note that, CIR in this example, queues 24, 25 FRC 2698  for  trTCM
       3.  CTR and 26 form PTR in RFC 2859 for TSWTCM 4. AverageRate
       used in [MODEL] section 5."
    ::= { qosTBMeterEntry 3 }

qosTBMeterBurstSize OBJECT-TYPE
    SYNTAX       BurstSize
    UNITS        "Bytes"
    STATUS       current
    DESCRIPTION
       "The maximum number of bytes in a
        priority group.  The qosIfQueueDrainSize single transmission
       burst.  This attribute is used for: 1. CBS and EBS in
       RFC 2697 for srTCM 2. CBS and PBS  in  FRC  2698  for
       trTCM 3. Burst Size used in [MODEL] section 5."
    ::= { qosTBMeterEntry 4 }

qosTBMeterInterval OBJECT-TYPE
    SYNTAX       Unsigned32
    UNITS        "microseconds"
    STATUS       current

DiffServ QoS Policy Information Base                       November 2000

    DESCRIPTION
       "The time interval used with the token bucket.   For:
       1.  Average  Rate  Meter,  [MODEL]  section  5.2.1, -
       Delta.  2. Simple Token Bucket Meter, [MODEL] section
       5.1, -  time  interval  t. 3.  RFC  2859  TSWTCM, -
       AVG_INTERVAL.   4.  RFC 2697 srTCM, RFC 2698 trTCM, -
       token bucket update time interval."
    ::= { qosTBMeterEntry 5 }

--
-- Actions
--

--
-- The Action Table allows enumeration of the different
-- types of actions to determine be applied to a traffic flow.
--

qosActionTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF QosActionEntry
    PIB-ACCESS   install, 5
    STATUS       current
    DESCRIPTION
       "The Action Table enumerates actions that can be per-
       formed  to  a stream of traffic. Multiple actions can
       be concatenated.  For example, after marking a stream
       of  traffic  exiting  from a meter, a device can then
       perform a mark  action  of  the additional processing characteristics  conforming  or  non-
       conforming traffic.

       Specific actions  are  indicated  by  qosAction-
       Specific  which  points  to  an  entry  of a specific
       action type parameterizing the
        individual queues action in a this priority group." detail."
    REFERENCE
        "[MODEL] section 6."
    ::= { qosIfQueueEntry qosPolicyClasses 6 }

qosIfQueueDrainSize

qosActionEntry OBJECT-TYPE
    SYNTAX         Unsigned32       QosActionEntry

DiffServ QoS Policy Information Base                       November 2000

    STATUS       current
    DESCRIPTION
        "The maximum number of bytes that may be drained from the
        queue
       "Each entry in one cycle.  The percentage of the interface
        bandwidth allocated action table allows description of
       one specific action to this queue can be calculated from
        this attribute and the sum of the drain sizes applied to traffic."
    PIB-INDEX { qosActionPrid }
    UNIQUENESS { }
    ::= { qosActionTable 1 }

QosActionEntry ::= SEQUENCE  {
    qosActionPrid              InstanceId,
    qosActionNext              Prid,
    qosActionSpecific          Prid,
    qosActionType              INTEGER
}

qosActionPrid OBJECT-TYPE
    SYNTAX       InstanceId
    STATUS       current
    DESCRIPTION
       "An arbitrary integer index that uniquely identifies an
        instance of all the
        queues in a specific priority group in a queue set.

        This attribute when compared with the drain size of other
        queues, represents class."
    ::= { qosActionEntry 1 }

qosActionNext OBJECT-TYPE
    SYNTAX       Prid
    STATUS       current
    DESCRIPTION
       "This selects the minimum bandwidth available next diffserv  functional  datapath
       element  to  handle traffic for this
        queue. data path.

       The minimum bandwidth specified value zeroDotZero in absolute terms this variable  indicates  no
       further Diffserv treatment is
        specified by the attribute qosIfQueueMinAbsBandwidth.  Which performed on traffic of
        these two applies is specified by the attribute
        qosIfQueueBandwidthAllocation."
       this datapath.  Any other value must point to a valid
       (pre-existing) instance of one of:"
         qosClfrEntry
         qosMeterEntry
         qosActionEntry
         qosAlgDropEntry
         qosQEntry."
    DEFVAL      { zeroDotZero }
    ::= { qosIfQueueEntry 7 qosActionEntry 2 }

qosIfQueueMinAbsBandwidth

DiffServ QoS Policy Information Base                       November 2000

qosActionSpecific OBJECT-TYPE
    SYNTAX         Unsigned64       Prid
    STATUS       current
    DESCRIPTION
        "The maximum interface bandwidth that is available
       "A pointer to an object instance providing additional
       information  for
        consumption when servicing the type of action indicated by this queue.
       action table entry.

       This bandwidth attribute is
        specified in terms of bits per second.

        This meaningful only if qosActionType is
       specific(3).  For other action types, this attribute represents
       should be NULL.

       For the absolute bandwidth that is
        available standard actions defined by this PIB  module,
       this should  point  to  an instance of
       qosDscpMarkActEntry.  For  other actions, it may point
       to an instance of a given queue. The relative bandwidth that is
        available PRC defined in some other PIB.
       The PRI pointed to a given queue, with respect must exist prior to other queues with
        which it is associated, is specified by the attribute
        qosIfQueueDrainSize.  Which of these two applies is specified
        by the attribute qosIfQueueBandwidthAllocation. installing this
       action datapath entry."
    ::= { qosIfQueueEntry 8 qosActionEntry 3 }

qosIfQueueBandwidthAllocation

qosActionType OBJECT-TYPE
    SYNTAX         INTEGER       INGEGER {
                        absolute(1),  --use qosIfQueueMinAbsBandwidth
                        relative(2)   --use qosIfQueueDrainSize
                   specific(2),
                   absoluteDrop(3)
                 }
    STATUS       current
    DESCRIPTION
       "This attribute specifies whether to configure indicates how the queue for
        an absolute bandwidth limit or one that is relative to other
        queues parameters of the priority group. i.e., whether
        action are to configure be specified.

        A value of specific(2) indicates that the
        queue using qosIfQueueMinAbsBandwidth or
        qosIfQueueDrainSize."

        If some queues have their bandwidth requirement specified in
        absolute terms and others action
        paramters are described in relative terms then the
        requirements instance of the absolute specification is met first.  That
        is, the drain sizes PRC
        pointed to by qosActionSpecific.

        A value of absoluteDrop(3) indicates that the absolute queues must
        drop action to be calculated
        based on the interface speed so as taken, and that no additional
        parameters apply to ensure this action.  For this action
        type, the absolute
        bandwidth requirement. value of qosActionSpecific should be
        zeroDotZero."
    ::= { qosIfQueueEntry 9 qosActionEntry 4 }

--
-- Interface Threshold DSCP Mark Action Table
--

DiffServ QoS Policy Information Base                       November 2000

-- The Interface Threshold Table enumerates the individual thresholds
-- and groups them into sets that can be applied Rows of this table are pointed to queues. by qosActionSpecific
-- Configuration of individual thresholds and hence to provide detailed parameters specific to the threshold sets DSCP
-- of individual queues, id done through this table. Mark action.
--

qosIfThresholdTable

qosDscpMarkActTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF QosIfThresholdEntry QosDscpMarkActEntry
    PIB-ACCESS   install, 6 3
    STATUS       current
    DESCRIPTION
        "Contains configuration information
       "This table enumerates specific DSCPs used for  mark-
       ing  or  remarking  the individual thresholds DSCP field of the threshold sets." IP packets. The
       entries of this table may be referenced by a
       qosActionSpecific attribute."
    REFERENCE
        "[MODEL] section 6.1"
    ::= { qosIfParameters 6 qosPolicyClasses 7 }

qosIfThresholdEntry

qosDscpMarkActEntry OBJECT-TYPE
    SYNTAX         QosIfThresholdEntry       QosDscpMarkActEntry
    STATUS       current
    DESCRIPTION
        "A conceptual row in the qosIfThresholdTable.

        Each row identifies a specific threshold within a given
        set and contains detailed information about the
        threshold. Threshold sets are associated with a queue set through
        the qosIfQueueThreshSet attribute of
    DESCRIPTION
       "An  entry  in  the qosIfQueueTable."  DSCP  mark  action  table   that
       describes a single DSCP used for marking."
    PIB-INDEX { qosDscpMarkActPrid }
    INDEX { qosIfThresholdPrid qosDscpMarkActDscp }
    UNIQUENESS { qosIfThresholdSetId,
                 qosIfThresholdDropMethod,
                 qosIfThresholdMinThresh,
                 qosIfThresholdMaxThresh qosDscpMarkActDscp }
    ::= { qosIfThresholdSetTable qosDscpMarkActTable 1 }

QosIfThresholdSetEntry

QosDscpMarkActEntry ::= SEQUENCE  {
        qosIfThresholdPrid          PolicyInstanceId,
        qosIfThresholdSetId         PolicyTagId,
        qosIfThresholdDropMethod    INTEGER,
        qosIfThresholdMinThresh     INTEGER,
        qosIfThresholdMaxThresh     INTEGER
    qosDscpMarkActPrid          InstanceId,
    qosDscpMarkActDscp          Dscp
}

qosIfThresholdPrid

qosDscpMarkActPrid OBJECT-TYPE
    SYNTAX         PolicyInstanceId       InstanceId
    STATUS       current
    DESCRIPTION
        "The
       "An arbitrary integer index that uniquely identifies this row in an
        instance of the table,
        i.e., this PRI." class."
    ::= { qosIfThresholdEntry qosDscpMarkActEntry 1 }

qosIfThresholdSetId

DiffServ QoS Policy Information Base                       November 2000

qosDscpMarkActDscp OBJECT-TYPE
    SYNTAX         PolicyTagId       Dscp
    STATUS       current
    DESCRIPTION
        "An index that uniquely identifies a specific threshold set.
        The individual thresholds
       "The DSCP that are members of this set all
        have the same value Action uses for this attribute (i.e., they have the
        same set ID)."

    ::= { qosIfThresholdEntry 2 }

qosIfThresholdDropMethod OBJECT-TYPE
    SYNTAX         INTEGER {
                       other(1),
                       tailDrop(2),
                       randomDrop(3)
                   }
    STATUS         current
    DESCRIPTION
        "The drop method to apply to packets exceeding the threshold.
        If the mechanism marking/remarking
       traffic.  Note that a DSCP value of -1 is other then another policy may be specified
        by an additional attribute augmenting this table."

    ::= { qosIfThresholdEntry 3 }

qosIfThresholdMinThresh OBJECT-TYPE
    SYNTAX         INTEGER
    STATUS         current
    DESCRIPTION
        "The queue depth, not permit-
       ted in bytes, below which no packets are
        dropped.  If the queue depth is above this value and below table.  It is  quite  possible  that  the
        value of qosIfThresholdMaxThresh then
       only  packets assigned  subject  to  this
        threshold  Action  are dropped randomly by the random drop process if
        random drop is in effect.  If tail drop is in effect, already
       marked with this
        attribute has no relevance."

    ::= { qosIfThresholdEntry 4 }

qosIfThresholdMaxThresh OBJECT-TYPE
    SYNTAX         INTEGER
    STATUS         current
    DESCRIPTION
        "The queue depth, DSCP. Note also  that  Diffserv  may
       result  in bytes, above which all packets assigned packet remarking both on ingress to this threshold are dropped." a net-
       work and on egress from it and it is  quite  possible
       that  ingress  and  egress  would  occur  in the same
       router."
    ::= { qosIfThresholdEntry 5 qosDscpMarkActEntry 2 }

--
-- DSCP to Queue and Threshold Mapping Algorithmic Drop Table
--
-- Supports the assignment of DSCPs to queues and thresholds for each
-- interface type
--

qosIfDscpMapTable

qosAlgDropTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF QosIfDscpMapEntry
    PIB-ACCESS     install, 6
    STATUS         current
    DESCRIPTION
        "Assigns DSCP values to queues and thresholds for QosAlgDropEntry
    PIB-ACCESS   install, 7
    STATUS       current
    DESCRIPTION
       "The algorithmic drop table contains entries describ-
       ing  an arbitrary
        DSCP map.  This map can then be assigned  element that drops packets according to various interface
        and role combination pairs." some
       algorithm."
    REFERENCE
        "[MODEL] section 7.1.3"
    ::= { qosIfParameters 7 qosPolicyClasses 9 }

qosIfDscpMapEntry

qosAlgDropEntry OBJECT-TYPE
    SYNTAX         QosIfDscpMapEntry       QosAlgDropEntry
    STATUS       current
    DESCRIPTION
       "An instance entry describes  a  process  that  drops  packets
       according  to some algorithm.  Further details of the qosIfDscpMap class."

    INDEX
       algorithm type are to be found in qosAlgDropType
       and  with  more  detail parameter entry pointed to by
       qosAlgDropSpecific when necessary."
    PIB-INDEX { qosIfDscpMapPrid qosAlgDropPrid }

DiffServ QoS Policy Information Base                       November 2000

    UNIQUENESS { qosIfDscpMapMapId,
                 qosIfDscpMapDscp }
    ::= { qosIfDscpMapTable qosAlgDropTable 1 }

QosIfDscpMapEntry

QosAlgDropEntry ::= SEQUENCE  {
        qosIfDscpMapPrid       PolicyInstanceId,
        qosIfDscpMapMapId      PolicyTagId,
        qosIfDscpMapDscp       Dscp,
        qosIfDscpMapQueue      PolicyReferenceId,
        qosIfDscpMapThresh     PolicyReferenceId
    qosAlgDropPrid             InstanceId,
    qosAlgDropType             INTEGER,
    qosAlgDropNext             Prid,
    qosAlgDropQMeasure         Prid,
    qosAlgDropQThreshold       Unsigned32,
    qosAlgDropSpecific         Prid
}

qosIfDscpMapPrid

qosAlgDropPrid OBJECT-TYPE
    SYNTAX         PolicyInstanceId       InstanceId
    STATUS       current
    DESCRIPTION
       "An arbitrary integer index that is used to uniquely identify the identifies an
        instance of the qosIfDscpMap class."
    ::= { qosIfDscpMapEntry 1 qosAlgDropEntry 1 }

qosAlgDropType OBJECT-TYPE
    SYNTAX       INTEGER {
                     other(1),
                     tailDrop(2),
                     headDrop(3),
                     randomDrop(4)
                 }
    STATUS       current
    DESCRIPTION
       "The type of algorithm used by this dropper. A  value
       of tailDrop(2) or headDrop(3) represents an algorithm
       that is completely specified by this PIB.

       A value of other(1) indicates that the specifics of
       the drop algorithm are specified in some other PIB
       module, and that the qosAlgDropSpecific attribute
       points to an instance of a PRC in that PIB that
       specifies the information necessary to implement the
       algorithm.

       The tailDrop(2) algorithm is  described  as  follows:
       qosAlgDropQThreshold represents the depth of the

DiffServ QoS Policy Information Base                       November 2000

       queue,  pointed  to  by  qosAlgDropQMeasure,  at
       which all newly arriving packets will be dropped.

       The headDrop(3) algorithm is described as follows: if
       a packet arrives when the current depth of the queue,
       pointed to by qosAlgDropQMeasure, is at
       qosAlgDropQThreshold,  packets currently at the head of
       the queue are dropped to make room for the new packet
       to be enqueued at the tail of the queue.

       The randomDrop(4) algorithm is described as  follows:
       on packet arrival, 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.  For  this  algorithm,
       qosAlgDropSpecific  points  to a qosRandomDropEntry
       that describes  the  algorithm.   For  this
       algorithm,  qosAlgQThreshold is understood to be
       the absolute maximum size of the queue and additional
       parameters are described in qosRandomDropTable."
    ::= { qosAlgDropEntry 2 }

qosIfDscpMapMapId

qosAlgDropNext OBJECT-TYPE
    SYNTAX         PolicyTagId       Prid
    STATUS       current
    DESCRIPTION
        "An integer that identifies
       "This selects the DSCP map next diffserv  functional  datapath
       element  to which  handle traffic for this PRI
        belongs." data path.

       The value zeroDotZero in this variable  indicates  no
       further Diffserv treatment is performed on traffic of
       this datapath.  Any other value must point to a valid
       (pre-existing) instance of one of:"
         qosClfrEntry
         qosMeterEntry
         qosActionEntry
         qosAlgDropEntry
         qosQEntry."
    DEFVAL      { zeroDotZero }
    ::= { qosIfDscpMapEntry 2 qosAlgDropEntry 3 }

qosIfDscpMapDscp

qosAlgDropQMeasure OBJECT-TYPE
    SYNTAX         Dscp       Prid

DiffServ QoS Policy Information Base                       November 2000

    STATUS       current
    DESCRIPTION
        "The DSCP
       "Points to an entry in the qosQTable to indicate
       the  queue  that  a drop algorithm is being assigned to monitor when
       deciding whether  to  drop  a queue and threshold by  packet.

       The PRI pointed to must exist prior to installing
       this PRI." dropper element."
    ::= { qosIfDscpMapEntry 3 qosAlgDropEntry 4 }

qosIfDscpMapQueue

qosAlgDropQThreshold OBJECT-TYPE
    SYNTAX         PolicyReferenceId
    PIB-REFERENCE  qosIfQueueTable       Unsigned32
    UNITS        "Bytes"
    STATUS       current
    DESCRIPTION
        "This attribute maps
       "A threshold on the DSCP specified by qosIfDscpMapDscp to depth in bytes of the queue identified by qosIfQueuePrid in qosIfQueueTable.
        For being
       measured at which a given DSCP map, all trigger is generated to the queues must belong drop-
       ping algorithm.

       For the tailDrop(2) or headDrop(3)  algorithms,  this
       represents  the  depth  of  the  queue, pointed to a single
        queue set." by
       qosAlgDropQMeasure, at  which  the  drop  action
       will take place. Other algorithms will need to define
       their own semantics for this threshold."
    ::= { qosIfDscpMapEntry 4 qosAlgDropEntry 5 }

qosIfDscpMapThresh

qosAlgDropSpecific OBJECT-TYPE
    SYNTAX         PolicyReferenceId
    PIB-REFERENCE  qosIfThresholdTable       Prid
    STATUS       current
    DESCRIPTION
        "This attribute maps the DSCP specified by qosIfDscpMapDscp
       "Points to
        the threshold identified by qosIfThresholdId in
        qosIfThresholdTable." a table entry that provides further detail
       regarding a drop algorithm.  The threshold set PRI pointed to which this
        threshold belongs
       must be assigned exist prior to the queue specified by
        qosIfDscpMapQueue."

    ::= { qosIfDscpMapEntry 5 }

--
-- QoS Meter Table
--
-- The QoS Meter Table contains metering specifications that
-- can be used installing this dropper element.

       Entries with qosAlgDropType  equal  to  other(1)
       must have this point to provide an acceptable flow bandwidth
-- dimension instance of a PRC
       defined in another PIB module.

       Entries with  qosAlgDropType  equal  to  random-
       Drop(4)   must   have  this  point  to  an  entry  in
       qosRandomDropTable.

       For all other algorithms, this should take the Target table.
--

qosMeter OBJECT IDENTIFIER  value

DiffServ QoS Policy Information Base                       November 2000

       zeroDotzero."
    ::= { qosPolicyGenPibClasses 2 qosAlgDropEntry 6 }

qosMeterTable

--
-- Random Drop Table
--

qosRandomDropTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF QosMeterEntry QosRandomDropEntry
    PIB-ACCESS   install, 10 9
    STATUS       current
    DESCRIPTION
        "Contains the current set of configured meters. The
        meters are associated with
       "The random drop table contains entries describing  a classifier during
        operation through the QoS Target Table."

    INSTALL-ERRORS {
        invalidCommittedData(1),
        invalidPeakData(2)
        }
       process  that drops packets randomly. Entries in this
       table is  intended  to  be  pointed  to  by
       qosAlgDropSpecific."
    REFERENCE
        "[MODEL] section 7.1.3"
    ::= { qosMeter 1 qosPolicyClasses 10 }

qosMeterEntry

qosRandomDropEntry OBJECT-TYPE
    SYNTAX         QosMeterEntry       QosRandomDropEntry
    STATUS       current
    DESCRIPTION
        "General metering definitions. Each entry specifies
        an instance of the qosMeter class which specifies
        metering information in terms of traffic stream
        bandwidth parameters. An
       "An entry can thus be used describes  a  process  that  drops  packets
       according to
        support traffic metering based on the specified
        service level specification."

    INDEX a random algorithm."
    PIB-INDEX { qosMeterPrid qosRandomDropPrid }
    UNIQUENESS { qosMeterDataSpecification,
                 qosMeterCommittedRate,
                 qosMeterCommittedBurst,
                 qosMeterPeakRate,
                 qosMeterPeakBurst,
                 qosMeterHighConfAction,
                 qosMeterMedConfAction,
                 qosMeterLowConfAction } qosRandomDropMinThreshBytes,
                 qosRandomDropMinThreshPkts,
                 qosRandomDropMaxThreshBytes,
                 qosRandomDropMaxThreshPkts,
                 qosRandomDropInvProbMax,
                 qosRandomDropInvWeight,
                 qosRandomDropSamplingRate
    ::= { qosMeterTable qosRandomDropTable 1 }

QosMeterEntry

QosRandomDropEntry ::= SEQUENCE  {
        qosMeterPrid              PolicyInstanceId,
        qosMeterDataSpecification INTEGER,
        qosMeterCommittedRate
    qosRandomDropPrid             InstanceId,
    qosRandomDropMinThreshBytes   Unsigned32,
    qosRandomDropMinThreshPkts    Unsigned32,
        qosMeterCommittedBurst
    qosRandomDropMaxThreshBytes   Unsigned32,
        qosMeterPeakRate
    qosRandomDropMaxThreshPkts    Unsigned32,

DiffServ QoS Policy Information Base                       November 2000

    qosRandomDropInvProbMax       Unsigned32,
        qosMeterPeakBurst
    qosRandomDropInvWeight        Unsigned32,
        qosMeterHighConfAction    PolicyReferenceId,
        qosMeterMedConfAction     PolicyReferenceId,
        qosMeterLowConfAction     PolicyReferenceId
    qosRandomDropSamplingRate     Unsigned32
}

qosMeterPrid

qosRandomDropPrid OBJECT-TYPE
    SYNTAX         PolicyInstanceId       InstanceId
    STATUS       current
    DESCRIPTION
       "An arbitrary integer index that uniquely identifies
        the an
        instance of the qosMeter class. Meters are
        associated with specific flows using class."
    ::= { qosRandomDropEntry 1 }

qosRandomDropMinThreshBytes OBJECT-TYPE
    SYNTAX       Unsigned32
    UNITS        "bytes"
    STATUS       current
    DESCRIPTION
       "The average  queue  depth  in  bytes,  beyond  which
       traffic  has a non-zero probability of being dropped.
       Changes in this variable may or may not be  reflected
       in the reported value of qosRandomDropMinThreshPkts."
    ::= { qosRandomDropEntry 2 }

qosRandomDropMinThreshPkts OBJECT-TYPE
    SYNTAX       Unsigned32
    UNITS        "packets"
    STATUS       current
    DESCRIPTION
       "The average queue depth  in  packets,  beyond  which
       traffic  has a non-zero probability of being dropped.
       Changes in this variable may or may not be  reflected
       in the reported value of qosRandomDropMinThreshBytes."
    ::= { qosRandomDropEntry 3 }

qosRandomDropMaxThreshBytes OBJECT-TYPE
    SYNTAX       Unsigned32
    UNITS        "bytes"
    STATUS       current
    DESCRIPTION
       "The average queue depth beyond which traffic  has  a

DiffServ QoS Policy Information Base                       November 2000

       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 }

qosRandomDropMaxThreshPkts OBJECT-TYPE
    SYNTAX       Unsigned32
    UNITS        "packets"
    STATUS       current
    DESCRIPTION
       "The average queue depth beyond which traffic  has  a
       probability indicated by qosRandomDropInvProbMax
       of being dropped or marked. Note  that  this attribute
        through  differs
       from  the qosTargetMeter attribute  physical  queue  limit, which is stored in
       qosAlgDropQThreshold.  Changes in this  variable
       may  or may not be reflected in the QoS
        Target class." reported value of
       qosRandomDropMaxThreshBytes."
    ::= { qosMeterEntry 1 qosRandomDropEntry 5 }

qosMeterDataSpecification

qosRandomDropInvProbMax OBJECT-TYPE
    SYNTAX         INTEGER {
                        noMeterData(1),   -- no metering reqd
                        committedData(2), -- committed rate only
                        peakData(3)       -- committed and peak
                   }       Unsigned32
    STATUS       current
    DESCRIPTION
        "Specifies the metering data, and thus
       "The worst case random drop probability, expressed as
       the actions, that
        are defined in a given entry.

        A value  inverse  of noMeterData(1) indicates that no flow metering
        is necessary. All flows associated with this meter entry
        are considered to be at a high level  the drop probability.  With special
       case of conformance.

        A the value of committedData(2) indicates that committed rate
        and committed burst information has been specified and will
        be applied to associated flows. No peak rate and burst
        information has been specified zero meaning that two levels
        of conformance (high, medium) are supported.

        A value  zero  probability  of peakData(3) indicates that peak rate and peak
        burst information has been provided
       drop.

       For example, if every packet may be  dropped  in addition to  the
        committed rate and committed burst information. All provided
        information will be applied to associated flows meaning that
        three levels
       worst   case   (100%),   this   has   the   value  of conformance (high, medium, low) are
        supported."
       4,294,967,295."
    ::= { qosMeterEntry 2 qosRandomDropEntry 6 }

qosMeterCommittedRate

qosRandomDropInvWeight OBJECT-TYPE
    SYNTAX       Unsigned32 (0..'ffffffff'h)
    STATUS       current
    DESCRIPTION
        "This object represents
       "The weighting of past history in affecting the committed information rate
        (CIR) against which associated traffic streams will be
        metered.  cal-
       culation  of  the  current queue average.  The CIR specifies moving

DiffServ QoS Policy Information Base                       November 2000

       average of the rate at which incoming
        traffic can arrive to be considered to be at a high
        level queue depth uses the inverse  of conformance. Typically,  this
       value specifies  as the rate at which tokens are added to a token bucket
        used to meter received flows.

        This object specifies a rate in bytes per second units
        such that, factor for example, a value the new queue depth, and one
       minus that inverse as the factor for  the  historical
       average.

       Implementations may choose to  limit  the  acceptable
       set  of 100 equates  values to a
        committed information rate specified set, such as powers of 100 bytes per second.

        Committed rate (and burst) information must be present
        if the qosMeterDataSpecification object has the value
        committedData(2) or peakRate(3). This, in turn, requires
        that at least both high and medium conformance actions
        be specified."
       2."
    ::= { qosMeterEntry 3 qosRandomDropEntry 7 }

qosMeterCommittedBurst

qosRandomDropSamplingRate OBJECT-TYPE
    SYNTAX       Unsigned32 (0..'ffffffff'h)
    STATUS       current
    DESCRIPTION
        "This object represents
       "The number of times per second the committed burst size
        (CBS) against which associated traffic streams will
        be metered. The CBS specifies queue is  sampled
       for queue average calculation.  A value of zero means
       the maximum burst size
        that queue is supported sampled approximately each time a packet
       is enqueued (or dequeued)."
    ::= { qosRandomDropEntry 8 }

--
-- Queue Table
--

--
-- An entry in qosQTable represents a FIFO queue diffserv
-- functional datapath element as described in [MODEL] section
-- 7.1.1.
-- Notice the specification of scheduling parameters for flows to be considered a queue
-- as part of the input to be at a high level scheduler functional datapath
-- element as described in [MODEL] section 7.1.2.  This allows
-- building of conformance. Typically, hierarchical queueing/scheduling.
-- A queue therefore is parameterized by:
-- 1. Which scheduler will service this value
        represents queue, qosQNext.
-- 2. How the maximum number of tokens scheduler will service this queue, with respect
--    to all the other queues the same scheduler needs to service,
--    qosQSchdParam.
--

qosQTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF QosQEntry
    PIB-ACCESS   install, 4

DiffServ QoS Policy Information Base                       November 2000

    STATUS       current
    DESCRIPTION
       "The Queue Table enumerates the individual queues  on
       an interface."
    ::= { qosPolicyClasses 11 }

qosQEntry OBJECT-TYPE
    SYNTAX       QosQEntry
    STATUS       current
    DESCRIPTION
       "An entry in the Queue Table describes a token
        bucket.

        This object specifies flow data single queue
       in bytes per second
        units such that, one direction on an interface."
    PIB-INDEX { qosQPrid }
    UNIQUENESS { }
    ::= { qosQTable 1 }

QosQEntry ::= SEQUENCE  {
    qosQPrid                    InstanceId,
    qosQNext                    Prid,
    qosQSchdParam               Prid
}

qosQPrid OBJECT-TYPE
    SYNTAX       InstanceId
    STATUS       current
    DESCRIPTION
        "An arbitrary integer index that uniquely identifies an
        instance of the class."
    ::= { qosQEntry 1 }

qosQNext OBJECT-TYPE
    SYNTAX       Prid
    STATUS       current
    DESCRIPTION
       "This selects the next diffserv  functional  datapath
       element  to  handle traffic for example, a this data path.  This
       value of 100 equates must point to a committed information rate valid (pre-existing) instance
       of 100 bytes per
        second.

        Committed burst (and rate) information must be present
        if the qosMeterDataSpecification object has the value
        committedData(2) or peakRate(3). This, in turn, requires
        that at least both high and medium conformance actions
        be specified." one of:
         qosSchedulerEntry"
    ::= { qosMeterEntry 4 qosQEntry 2 }

qosMeterPeakRate

DiffServ QoS Policy Information Base                       November 2000

qosQSchdParam OBJECT-TYPE
    SYNTAX         Unsigned32 (0..'ffffffff'h)       Prid
    STATUS       current
    DESCRIPTION
       "This object represents   Prid    indicates    the peak information rate (PIR)
        against which associated traffic streams will be
        metered. The PIR specifies    entry    in
       qosSchdParamTable  the rate at which incoming
        traffic can arrive  scheduler, pointed to be considered by
       qosQNext, should use to be at a medium
        level of conformance. Typically, service this value specifies
        the rate at which tokens are added queue.  The PRI
       pointed to a token bucket
        used must exist prior to meter received flows.

        This object specifies a rate in bytes per second units
        such that, installing this queue
       element."
    ::= { qosQEntry 3 }

--
-- Scheduler Table
--
-- The Scheduler Table is used for example, a value of 100 equates representing packet schedulers:
-- it provides flexibility for multiple scheduling algorithms, each
-- servicing multiple queues, to a
        committed information rate be used on the same logical/physical
-- interface.
-- Notice the servicing parameters the scheduler uses is
-- specified by each of 100 bytes per second.

        Peak rate (and burst) information its upstream functional datapath elements,
-- most likely queues or schedulers.
-- The coordination and coherency between the servicing parameters
-- of the scheduler's upstream functional datapath elements must
-- be present
        if maintained for the qosMeterDataSpecification object has scheduler to function correctly.
--
-- The qosSchedulerSchdParam attribute is used for specifying
-- the value
        peakData(3). This, in turn, requires that high, medium
        and low conformance actions servicing parameters for output of a scheduler when its
-- downstream functional datapath element is another scheduler.
-- This is used for building hierarchical queue/scheduler.
--

qosSchedulerTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF QosSchedulerEntry
    PIB-ACCESS   install, 5
    STATUS       current
    DESCRIPTION
       "The Scheduler Table  enumerates  packet  schedulers.
       Multiple scheduling algorithms can be specified." used on a given
       interface,  with  each  algorithm  described  by  one
       qosSchedulerEntry."
    REFERENCE
        "[MODEL] section 7.1.2"

DiffServ QoS Policy Information Base                       November 2000

    ::= { qosMeterEntry 5 qosPolicyClasses 12 }

qosMeterPeakBurst

qosSchedulerEntry OBJECT-TYPE
    SYNTAX         Unsigned32 (0..'ffffffff'h)       QosSchedulerEntry
    STATUS       current
    DESCRIPTION
        "This object represents the peak burst size (PBS)
        against which associated traffic streams will
        be metered. The CBS specifies the maximum burst size
        that is supported for flows to be considered to be at
        a medium level of conformance. Typically, this value
        represents the maximum number of tokens in a token
        bucket.

        This object specifies flow data
       "An entry in bytes per second
        units such that, for example, the Scheduler Table describing a value  single
       instance of 100 equates
        to a committed information rate of 100 bytes per
        second.

        Peak burst (and rate) information must be present
        if the qosMeterDataSpecification object has the value
        peakData(3). This, in turn, requires that high, medium
        and low conformance actions be specified." scheduling algorithm."
    PIB-INDEX { qosSchedulerPrid }
    UNIQUENESS { }
    ::= { qosMeterEntry 6 qosSchedulerTable 1 }

QosSchedulerEntry ::= SEQUENCE  {
    qosSchedulerPrid                 InstanceId,
    qosSchedulerNext                 Prid,
    qosSchedulerMethod               INTEGER,
    qosSchedulerSchdParam            Prid
}

qosMeterHighConfAction

qosSchedulerPrid OBJECT-TYPE
    SYNTAX         PolicyReferenceId
    PIB-REFERENCE  qosActionTable       InstanceId
    STATUS       current
    DESCRIPTION
        "This attribute identifies the action that is to be
        initiated for flows
        "An arbitrary integer index that are determined to have a high
        level uniquely identifies an
        instance of conformance with regard to metering criteria
        being applied to the flow.

        Actions must be defined in the qosActionTable prior to
        being referenced by this attribute. A valid value for
        this attribute must always be provided." class."
    ::= { qosMeterEntry 7 qosSchedulerEntry 1 }

qosMeterMedConfAction

qosSchedulerNext OBJECT-TYPE
    SYNTAX         PolicyReferenceId
    PIB-REFERENCE  qosActionTable       Prid
    STATUS       current
    DESCRIPTION
       "This attribute identifies selects the action that is next diffserv  functional  datapath
       element  to be
        initiated  handle traffic for flows that are determined to have a medium
        level this data path.

       A value of conformance with regard to metering criteria
        being applied to the flow.

        Actions must be defined zeroDotZero in this attribute indicates no
       further Diffserv treatment is performed on traffic of
       this datapath.  The use of zeroDotZero is the qosActionTable prior  normal
       usage for the last functional datapath element.  Any
       value other than zeroDotZero must point to
        being referenced a valid
       (pre-existing) instance of one of:
        qosSchedulerEntry

DiffServ QoS Policy Information Base                       November 2000

         qosQEntry  (as  indicated  by this attribute. A valid value  [MODEL]  section
       7.1.4).

       This can point to  another  qosSchedulerEntry
       for
        this attribute must be provided if the value  implementation of multiple scheduler methods for
       the
        associated qosMeterDataSpecification object is
        committedRate(2) or peakRate(3)."  same  datapath,  and   for   implementation   of
       hierarchical schedulers."
    DEFVAL       { zeroDotZero }
    ::= { qosMeterEntry 8 qosSchedulerEntry 2 }

qosMeterLowConfAction

qosSchedulerMethod OBJECT-TYPE
    SYNTAX         PolicyReferenceId
    PIB-REFERENCE  qosActionTable       INTEGER {
                     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
    DESCRIPTION
        "This attribute identifies the action that
       "The scheduling algorithm used by this Scheduler.

       A value of priorityq(2) is used  to be
        initiated for flows that are determined to have a low
        level  indicate  strict
       priority queueing: only the qosSchdParamPriority
       attributes of conformance with regard to metering criteria
        being applied to the flow.

        Actions must be defined in queues feeding this  scheduler  are
       used when determining the qosActionTable prior next packet to
        being referenced by this attribute. schedule.

       A valid value for  of  wrr(3)  indicates  weighted  round-robin
       scheduling.  Packets  are  scheduled from each of the
       queues feeding this attribute must be provided if scheduler according to all of the value
       parameters of the
        associated qosMeterDataSpecification object is
        peakRate(3)."

    ::= { qosMeterEntry 9 }

--
-- The Generic QoS Action Group
--

qosAction OBJECT IDENTIFIER ::= { qosPolicyGenPibClasses 3 }

--
-- The QoS Action Table
--
-- The QoS Action Table describes actions that qosSchdParam entry.

       A value of wfq(4) indicates  weighted  fair  queueing
       scheduling.   Packets  are associated with
-- specific meters through scheduled from each of the QoS Target Table.  An action specifies
-- whether
       queues feeding this scheduler according  to mark, drop, or leave  all  the packet unchaged.

qosActionTable OBJECT-TYPE
    SYNTAX         SEQUENCE OF QosActionEntry
    PIB-ACCESS     install, 4
    STATUS         current
    DESCRIPTION
        "Contains
       parameters  of  the current set  QosSchdParamEntry  directed
       from qosQueue entry.

       A value of configured actions. The actions
        are associated with meters and interfaces during operation."

    ::= { qosAction 1 }

qosActionEntry OBJECT-TYPE
    SYNTAX         QosActionEntry
    STATUS         current
    DESCRIPTION
        "General action definitions. Each entry specifies an instance  wirr(5)  indicates  weighted  interleaved
       roundrobin    queueing   scheduling.    Packets   are
       scheduled  from  each  of  the qosAction class which describes (potentially)
        several distinct action attributes.

        An instance of  queues  feeding  this class can not be deleted while it is being
        referenced in a target instance in another class. This
        class may be extended with actions that apply
       scheduler  according  to specific QoS
        policies using augmentation."

    INDEX { qosActionPrid }
    UNIQUENESS { qosActionDrop,
                 qosActionUpdateDSCP }

    ::= { qosActionTable 1 }

QosActionEntry ::= SEQUENCE {
        qosActionPrid       PolicyInstanceId,
        qosActionAction     INTEGER,
        qosActionUpdateDSCP Dscp,
}

qosActionPrid OBJECT-TYPE
    SYNTAX         PolicyInstanceId
    STATUS         current
    DESCRIPTION
        "An arbitrary integer index that uniquely identifies  all  the instance  parameters of the
       QosSchdParamEntry  directed  from  qosQueue
       entry.

DiffServ QoS Action class. Class instances
        may not be contiguous. Actions Policy Information Base                       November 2000

       A value of bsp(6) indicates bounded  strict  priority
       scheduling.   Packets  are associated with
        Target instances in other classes (e.g., scheduled from each of the QoS
        Meter class) using
       queues feeding this attribute." scheduler according  to  all  the
       parameters  of  the  QosSchdParamEntry  directed
       from qosQueue entry."
    REFERENCE
        "[MODEL] section 7.1.2"
    ::= { qosActionEntry 1 qosSchedulerEntry 3 }

qosActionAction

qosSchedulerSchdParam OBJECT-TYPE
    SYNTAX         INTEGER {
               drop(1),
               mark(2),
               unchange(3)    -- don't alter the DSCP
              }       Prid
    STATUS       current
    DESCRIPTION
       "This action attribute specifies   Prid    indicates    the action to be taken on    entry    in
       qosSchdParamTable  the
        packet.

        Prior  higher  level scheduler,
       pointed to discarding a packet, other actions that have
        been specified should be performed if they make protocol
        sense. For example, requests for traffic mirroring (if
        such an action is supported by a device) qosSchedulerNext,  should be
        honored. However, updating protocol header values will
        typically not be necessary."

    ::= { qosActionEntry 2 }

qosActionUpdateDSCP OBJECT-TYPE
    SYNTAX         Dscp
    STATUS         current
    DESCRIPTION
        "This attribute specifies the value  use  to write into
       service the DSCP
        field output of the packet if the action to be taken this scheduler.  This attribute
       is only used when there is more  than  one  level  of
       scheduler.   A value of 0.0 should be sent to mark the
        packet. indicate
       that this attribute is not used."
    ::= { qosActionEntry 3 qosSchedulerEntry 4 }

--
-- The QoS Target Scheduling Parameter Table
--
-- The QoS Target Table supports The scheduling parameters are separate from the Queue Entries
-- for reusability and for usage by both queues and schedulers,
-- and this follows the association separation of filters, datapath elements from
-- interfaces, meters and actions. It allows filter instances, as parameterization approach used throught out this PIB.
-- defined in various filter classes, to be associated with specific Usage of scheduling parameter table entry by schedulers allow
-- interfaces/flow direction (based on interface role combination and building of hierarchical scheduling.
-- traffic direction) and actions
-- The qosSchdParamMaxRateAbs/Rel attributes are used to be performed based on traffic
-- classification and metering.  Furthermore, it allows heterogeneous construct non-work-conserving scheduler for the purpose of
-- filter definition class instances to be applied to traffic shaping.  These attributes limits the same servicing of
-- interface group the queue/scheduler, in a prescribed order affect, shaping the output of precedence. the
-- queue/scheduler, as described in [MODEL] section 7.2.
--

qosTargetTable

qosSchdParamTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF QosTargetEntry QosSchdParamEntry

DiffServ QoS Policy Information Base                       November 2000

    PIB-ACCESS   install, 7
    STATUS       current
    DESCRIPTION
        "A class that applies a set of filters to interfaces specifying,
        for each interface, the precedence order of the filters with
        respect to other filters applied to the same interface and, for
        each filter, the meter to apply to packets accepted by the
        filter.  Interfaces are specified abstractly
        in terms
       "The Scheduling Parameter Table enumerates individual
       sets  of interface roles.

        This class may contain filters scheduling parameter that specify different types
        of traffic classification."
    INSTALL-ERRORS {
        priPrecedenceConflict(1) -- precedence conflict detected
        } can be used/reused
       by Queues and Schedulers."
    ::= { qosAction 2 qosPolicyClasses 13 }

qosTargetEntry

qosSchdParamEntry OBJECT-TYPE
    SYNTAX         QosTargetEntry       QosSchdParamEntry
    STATUS       current
    DESCRIPTION
       "An instance of the qosTarget class. Instance creation
        may be prohibited based on entry in the status Scheduling Parameter Table describes
       a  single  set  of certain class
        attributes which must exist prior to class instantiation."

    INDEX  scheduling  parameter  for use by
       queues and schedulers.

       Notice multiple inter-mixed Queue  and  Scheduler
       entries can use the same Scheduler Parameter entry."
    PIB-INDEX { qosTargetPrid qosSchdParamPrid }
    UNIQUENESS { qosTargetFilterId,
                 qosTargetInterfaceRoles,
                 qosTargetInterfaceDirection,
                 qosTargetOrder qosSchdParamPriority,
                 qosSchdParamMinRateAbs,
                 qosSchdParamMinRateRel,
                 qosSchdParamMaxRateAbs,
                 qosSchdParamMaxRateRel }
    ::= { qosTargetTable qosSchdParamTable 1 }

QosTargetEntry

QosSchdParamEntry ::= SEQUENCE  {
        qosTargetPrid               PolicyInstanceId,
        qosTargetFilterId           PolicyTagReference,
        qosTargetInterfaceRoles     RoleCombination,
        qosTargetInterfaceDirection INTEGER,
        qosTargetOrder
    qosSchdParamPrid            InstanceId,
    qosSchdParamPriority        Unsigned32,
    qosSchdParamMinRateAbs      Unsigned32,
    qosSchdParamMinRateRel      Unsigned32,
    qosSchdParamMaxRateAbs      Unsigned32,
        qosTargetMeter              PolicyReferenceId
    qosSchdParamMaxRateRel      Unsigned32
}

qosSchdParamPrid OBJECT-TYPE
    SYNTAX       InstanceId
    STATUS       current
    DESCRIPTION
        "An arbitrary integer index that uniquely identifies an
        instance of the class."
    ::= { qosSchdParamEntry 1 }

qosTargetPrid

DiffServ QoS Policy Information Base                       November 2000

qosSchdParamPriority OBJECT-TYPE
    SYNTAX         PolicyInstanceId       Unsigned32
     STATUS       current
    DESCRIPTION
        "An arbitrary integer index that uniquely identifies
        the instance
       "The priority of this queue, to be used as a  parame-
       ter  to  the QoS Target class."  next  scheduler element downstream from
       this one."
    ::= { qosTargetEntry 1 qosSchdParamEntry 2 }

qosTargetFilterId

qosSchdParamMinRateAbs OBJECT-TYPE
    SYNTAX         PolicyTagReference
    PIB-TAG        frwkFilterGroupDefinitionId       Unsigned32
    UNITS        "kilobits per second"
    STATUS       current
    DESCRIPTION
        "This attribute identifies the filter group
       "The minimum absolute rate, in kilobits/sec,  that is associated with  a
       downstream  scheduler element should allocate to this target.  This filter group must be specified in
        frwkFilterGroupDefinitionTable and
       queue.  If the specific group value is
        identified by zero, then  there  is  effec-
       tively  no  minimum  rate guarantee.  If the value is
       non-zero, the scheduler will assure the servicing  of
       this attribute." queue to at least this rate.

       Note that this attribute's value is coupled  to  that
       of  qosSchdParamMinRateRel:  changes to one will
       affect the value of the other. They are linked by the
       following equation:

         qosSchdParamMinRateRel = qosSchdParamMinRateAbs * 10,000,000/ifSpeed

       or, if appropriate:

         qosSchdParamMinRateRel = qosSchdParamMinRateAbs * 10 / ifHighSpeed"
    REFERENCE
        "ifSpeed, ifHighSpeed from [IFMIB]"
    ::= { qosTargetEntry 2 qosSchdParamEntry 3 }

qosTargetInterfaceRoles

qosSchdParamMinRateRel OBJECT-TYPE
    SYNTAX         RoleCombination       Unsigned32
     STATUS       current
    DESCRIPTION
       "The interfaces minimum rate that a downstream scheduler element
       should  allocate  to which this target applies specified
        in terms of a set queue, relative to the max-
       imum rate of roles. The role combination
        specified the interface as reported by this attribute must exist ifSpeed  or
       ifHighSpeed, in units of 1/10,000 of 1.  If the
        frwkIfCapSetRoleComboTable prior to being association
        with an instance value

DiffServ QoS Policy Information Base                       November 2000

       is zero, then there is effectively  no  minimum  rate
       guarantee.   If  the value is non-zero, the scheduler
       will assure the servicing of this class." queue to  at  least
       this rate.

       Note that this attribute's value is coupled  to  that
       of  qosSchdParamMinRateAbs:  changes to one will
       affect the value of the other. They are linked by the
       following equation:

         qosSchdParamMinRateAbs = ifSpeed * qosSchdParamMinRateRel/10,000,000

       or, if appropriate:

         qosSchdParamMinRateAbs = ifHighSpeed * qosSchdParamMinRateRel / 10"
    REFERENCE
        "ifSpeed, ifHighSpeed from [IFMIB]"
    ::= { qosTargetEntry 3 qosSchdParamEntry 4 }

qosTargetInterfaceDirection

qosSchdParamMaxRateAbs OBJECT-TYPE
    SYNTAX         INTEGER {
                       in(1),
                       out(2)
                   }       Unsigned32
    UNITS        "kilobits per second"
    STATUS       current
    DESCRIPTION
       "The direction maximum rate in kilobits/sec that  a  downstream
       scheduler  element  should allocate to this queue. If
       the value is zero, then there is effectively no  max-
       imum rate limit and that the scheduler should attempt
       to be work-conserving for this queue.  If  the  value
       is  non-zero,  the scheduler will limit the servicing
       of packet flow this queue to, at the interface most, this rate in
        question to which  a  non-work-
       conserving manner.

       Note that this filter applies." attribute's value is coupled  to  that
       of  qosSchdParamMaxRateRel:  changes to one will
       affect the value of the other. They are linked by the
       following equation:

         qosSchdParamMaxRateRel = qosSchdParamMaxRateAbs * 10,000,000/ifSpeed

       or, if appropriate:

         qosSchdParamMaxRateRel = qosSchdParamMaxRateAbs * 10 / ifHighSpeed"
    REFERENCE

DiffServ QoS Policy Information Base                       November 2000

        "ifSpeed, ifHighSpeed from [IFMIB]"
    ::= { qosTargetEntry 4 qosSchdParamEntry 5 }

qosTargetOrder

qosSchdParamMaxRateRel OBJECT-TYPE
    SYNTAX       Unsigned32
    STATUS       current
    DESCRIPTION
        "An integer
       "The maximum rate that determines a downstream scheduler element
       should  allocate  to this queue, relative to the precedence order max-
       imum rate of
        this filter in the list interface as reported by ifSpeed  or
       ifHighSpeed, in units of filters applied to interfaces 1/10,000 of 1.  If the specified role combination. A filter with a given
        precedence order value
       is positioned in the list before one
        with a higher-valued precedence order.

        As an example, consider the following Target association:

          Index   IfRoleCombo  IfDirection FilterId Order
            14  'eth1000+L2+L3'   'in'         8      1
            15  'eth1000+L2+L3'   'in'         3      2
            16  'eth1000+L2+L3'   'in'        12      3
            17  'eth1000+L2+L3'   'in'         6      4
            18  'eth1000+L2+L3'   'in'        21      5

        Five distinct filter specifications form a Target association
        (e.g., based on the specified interface role combination zero, then there is effectively  no  maximum  rate
       limit  and
        direction attributes) with a prescribed order of
        evaluation. The FilterId attributes identify  the filter
        definition instances.

        Precedence values within an association must be unique
        otherwise instance installation will  scheduler should attempt to be prohibited and an
        error work-
       conserving for this queue.  If the value is non-zero,
       the  scheduler will be returned."

    ::= { qosTargetEntry 5 }

qosTargetMeter OBJECT-TYPE
    SYNTAX         PolicyReferenceId
    PIB-REFERENCE  qosMeterTable
    STATUS         current
    DESCRIPTION
        "This attribute identifies limit the meter that is associated
        with servicing of this QoS Target instance. Meters are defined
        in the qosMeterTable. The corresponding instance queue
       to, at  most,  this  rate  in
        the qosMeter class (i.e., the class instance where
        the qosMeterPrid  a  non-work-conserving
       manner.

       Note that this attribute's value is equal coupled  to  that
       of  qosSchdParamMaxRateAbs:  changes to one will
       affect the value of this object)
        must exist prior to being associated with a Target
        entry." the other. They are linked by the
       following equation:

         qosSchdParamMaxRateAbs = ifSpeed * qosSchdParamMaxRateRel/10,000,000

       or, if appropriate:

         qosSchdParamMaxRateAbs = ifHighSpeed * qosSchdParamMaxRateRel / 10"
    REFERENCE
        "ifSpeed, ifHighSpeed from [IFMIB]"
    ::= { qosTargetEntry qosSchdParamEntry 6 }

--
-- Conformance Section
--

qosPolicyIpPibConformance

qosPolicyPibConformance
                OBJECT IDENTIFIER ::= { qosPolicyIpPib qosPolicyPib 3 }

qosPolicyIpPibCompliances

qosPolicyPibCompliances

DiffServ QoS Policy Information Base                       November 2000

                OBJECT IDENTIFIER ::= { qosPolicyIpPibConformance qosPolicyPibConformance 1 }
qosPolicyIpPibGroups
qosPolicyPibGroups
                OBJECT IDENTIFIER ::= { qosPolicyIpPibConformance qosPolicyPibConformance 2 }

qosPolicyIpPibCompliance

qosPolicyPibCompliance MODULE-COMPLIANCE
    STATUS  current
    DESCRIPTION
            "Describes the requirements for conformance to the
            QoS Policy IP PIB."

    MODULE  -- this module
        MANDATORY-GROUPS { qosIfSchedulingCapsGroup,
                           qosIfQueueSetAssignGroup,
                           qosIfQueueGroup,
                           qosMeterGroup,
                           qosActionGroup,
                           qosTargetGroup
            qosPibDataPathGroup,
            qosPibClfrGroup,
            qosPibClfrElementGroup,
            qosPibActionGroup,
            qosPibAlgDropGroup,
            qosPibQGroup,
            qosPibSchedulerGroup,
            qosPibSchdParamGroup }

    GROUP qosPibMeterGroup
    DESCRIPTION
       "This group is mandatory for devices  that  implement
       metering functions."

    GROUP qosPibTBMeterGroup
    DESCRIPTION
       "This group is mandatory for devices  that  implement
       token-bucket metering functions."

    GROUP qosPibDscpMarkActGroup
    DESCRIPTION
       "This group is mandatory for devices  that  implement
       DSCP-Marking functions."

    GROUP qosPibRandomDropGroup
    DESCRIPTION
       "This group is mandatory for devices  that  implement
       Random Drop functions."

DiffServ QoS Policy Information Base                       November 2000

    OBJECT        qosIfQueueSetAssignName qosClfrId
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfQueueSetAssignRoles qosClfrElementClfrId
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfQueueSetAssignQueueSetId qosClfrElementOrder
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfQueueSetId qosClfrElementNext
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfQueueQueueSize qosClfrElementSpecific
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfQueueSetThreshSet qosMeterSucceedNext
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfQueuePriorityGroup qosMeterFailNext
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfQueueServiceDisc qosMeterSpecific
    MIN-ACCESS notify
    DESCRIPTION

DiffServ QoS Policy Information Base                       November 2000

       "Install support is not required."

    OBJECT        qosIfQueueDrainSize qosTBMeterType
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfQueueMinAbsBandwidth qosTBMeterRate
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfQueueBandwidthAllocation qosTBMeterBurstSize
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosMeterDataSpecification qosTBMeterInterval
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosMeterCommittedRate qosActionNext
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosMeterCommittedBurst qosActionSpecific
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosMeterPeakRate qosAlgDropType
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

DiffServ QoS Policy Information Base                       November 2000

    OBJECT        qosMeterPeakBurst qosAlgDropNext
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosMeterHighConfAction qosAlgDropQMeasure
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosMeterMedConfAction qosAlgDropQThreshold
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosMeterLowConfAction qosAlgDropSpecific
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosActionDrop qosRandomDropMinThreshBytes
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosActionUpdateDSCP qosRandomDropMinThreshPkts
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

        GROUP   qosIfClassificationCapsGroup
        DESCRIPTION
            "The qosIfClassificationCapsGroup is mandatory
            if IP datagram classification is supported."

        GROUP   qosIfMeteringCapsGroup

    OBJECT qosRandomDropMaxThreshBytes
    MIN-ACCESS notify
    DESCRIPTION
            "The qosIfMeteringCapsGroup
       "Install support is mandatory if
            metering and shaping capabilities are supported."

        GROUP   qosIfThresholdGroup not required."

    OBJECT qosRandomDropMaxThreshPkts
    MIN-ACCESS notify
    DESCRIPTION
            "The qosIfThresholdGroup is mandatory if
            queue-based thresholds are supported and if
            the qosIfDscpMapGroup

DiffServ QoS Policy Information Base                       November 2000

       "Install support is supported." not required."

    OBJECT        qosIfThresholdSetId qosRandomDropInvWeight
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfThresholdDropMethod qosRandomDropSamplingRate
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfThresholdMinThresh qosRandomDropInvProbMax
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfThresholdMaxThresh qosQNext
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

        GROUP   qosIfDscpAssignGroup

    OBJECT qosQSchdParam
    MIN-ACCESS notify
    DESCRIPTION
            "The qosIfDscpAssignGroup is mandatory if traffic
            queue assignment based on DSCP
       "Install support is supported." not required."

    OBJECT        qosIfDscpAssignName qosSchedulerMethod
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfDscpAssignRoles qosSchedulerSchdParam
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

DiffServ QoS Policy Information Base                       November 2000

    OBJECT        qosIfDscpAssignDscpMap qosSchedulerNext
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

        GROUP   qosIfDscpMapGroup

    OBJECT qosSchdParamPriority
    MIN-ACCESS notify
    DESCRIPTION
            "The qosIfDscpMapGroup is mandatory if the
            qosIfDscpAssignGroup
       "Install support is supported." not required."

    OBJECT        qosIfDscpMapMapId qosSchdParamMinRateAbs
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfDscpMapDscp qosSchdParamMinRateRel
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfDscpMapQueue qosSchdParamMaxRateAbs
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    OBJECT        qosIfDscpMapThresh qosSchdParamMaxRateRel
    MIN-ACCESS notify
    DESCRIPTION
       "Install support is not required."

    ::= { qosPolicyIpPibCompliances qosPibCompliances 1 }

qosIfClassificationCapsGroup

qosPibDataPathGroup OBJECT-GROUP
    OBJECTS {
             qosIfClassificationCaps
        qosDataPathStart
    }
    STATUS current
    DESCRIPTION
            "Objects from

DiffServ QoS Policy Information Base                       November 2000

       "The Data Path Group defines  the qosIfClassificationCapsTable."  PIB  Objects  that
       describe a data path."
    ::= { qosPolicyIpPibGroups 3 qosPibGroups 1 }

qosIfMeteringCapsGroup

qosPibClfrGroup OBJECT-GROUP
    OBJECTS {
             qosIfMeteringCaps
        qosClfrId
    }
    STATUS current
    DESCRIPTION
            "Objects from
       "The Classifier Group defines the qosIfMeteringCapsTable."  PIB  Objects  that
       describe a generic classifier."
    ::= { qosPolicyIpPibGroups 4 qosPibGroups 2 }

qosIfSchedulingCapsGroup

qosPibClfrElementGroup OBJECT-GROUP
    OBJECTS {
             qosIfSchedulingCapsMaxQueues,
             qosIfSchedulingCapsMaxThresholds,
             qosIfSchedulingCapsMaxPriorities,
             qosIfSchedulingCapsServiceDisc,
             qosIfSchedulingCapsMinQueueSize,
             qosIfSchedulingCapsMaxQueueSize,
             qosIfSchedulingCapsTotalQueueSize,
             qosIfSchedulingCapsWredCapable
        qosClfrElementClfrId,  qosClfrElementOrder,
        qosClfrElementNext, qosClfrElementSpecific
    }
    STATUS current
    DESCRIPTION
            "Objects from
       "The Classifier Group defines the  PIB  Objects  that
       describe a generic classifier."
    ::= { qosPibGroups 3 }

qosPibMeterGroup OBJECT-GROUP
    OBJECTS {
        qosMeterSucceedNext, qosMeterFailNext,
        qosMeterSpecific
    }
    STATUS current
    DESCRIPTION
       "The Meter Group defines the qosIfSchedulingCapsTable." objects used in describ-
       ing a generic meter element."
    ::= { qosPolicyIpPibGroups qosPibGroups 5 }

qosIfQueueSetAssignGroup

qosPibTBMeterGroup OBJECT-GROUP
    OBJECTS {
             qosIfQueueSetAssignName,
             qosIfQueueSetAssignRoles,
             qosIfQueueSetAssignQueueSetId,
        qosTBMeterType, qosTBMeterRate,
        qosTBMeterBurstSize, qosTBMeterInterval
    }

DiffServ QoS Policy Information Base                       November 2000

    STATUS current
    DESCRIPTION
            "Objects from
       "The Token-Bucket Meter  Group  defines  the qosIfQueueSetAssignTable."  objects
       used  in  describing a single-rate token bucket meter
       element."
    ::= { qosPolicyIpPibGroups qosPibGroups 6 }

qosIfQueueGroup

qosPibActionGroup OBJECT-GROUP
    OBJECTS {
             qosIfQueueSetId,
             qosIfQueueQueueSize,
             qosIfQueueSetThreshSet,
             qosIfQueuePriorityGroup,
             qosIfQueueServiceDisc,
             qosIfQueueDrainSize,
             qosIfQueueMinAbsBandwidth,
             qosIfQueueBandwidthAllocation
        qosActionNext, qosActionSpecific
    }
    STATUS current
    DESCRIPTION
            "Objects from
       "The  Action  Group  defines  the qosIfQueueTable."  objects  used   in
       describing a generic action element."
    ::= { qosPolicyIpPibGroups qosPibGroups 7 }

qosIfThresholdGroup

qosPibDscpMarkActGroup OBJECT-GROUP
    OBJECTS {
             qosIfThresholdSetId,
             qosIfThresholdDropMethod,
             qosIfThresholdMinThresh,
             qosIfThresholdMaxThresh
        qosDscpMarkActDscp
    }
    STATUS current
    DESCRIPTION
            "Objects from
       "The DSCP Mark Action Group defines the qosIfThresholdTable." objects  used
       in describing a DSCP Marking Action element."
    ::= { qosPolicyIpPibGroups qosPibGroups 8 }

qosIfDscpAssignGroup

qosPibAlgDropGroup OBJECT-GROUP
    OBJECTS {
             qosIfDscpAssignName,
             qosIfDscpAssignRoles,
             qosIfDscpAssignDscpMap
        qosAlgDropType, qosAlgDropNext,
        qosAlgDropQMeasure, qosAlgDropQThreshold,
        qosAlgDropSpecific
    }
    STATUS current
    DESCRIPTION
            "Objects from
       "The Algorithmic Drop Group contains the qosIfDscpAssignTable." objects that
       describe algorithmic dropper operation and configura-
       tion."
    ::= { qosPolicyIpPibGroups 9 qosPibGroups 12 }

qosIfDscpMapGroup

qosPibRandomDropGroup OBJECT-GROUP

DiffServ QoS Policy Information Base                       November 2000

    OBJECTS {
             qosIfDscpMapMapId,
             qosIfDscpMapDscp,
             qosIfDscpMapQueue,
             qosIfDscpMapThresh
        qosRandomDropMinThreshBytes,
        qosRandomDropMinThreshPkts,
        qosRandomDropMaxThreshBytes,
        qosRandomDropMaxThreshPkts,
        qosRandomDropInvProbMax,
        qosRandomDropInvWeight,
        qosRandomDropSamplingRate
    }
    STATUS current
    DESCRIPTION
            "Objects from
       "The Random Drop Group augments the qosIfDscpMapTable." Algorithmic Drop Group for
       random dropper operation and configuration."
    ::= { qosPolicyIpPibGroups 10 qosPibGroups 13 }

qosMeterGroup

qosPibQGroup OBJECT-GROUP
    OBJECTS {
             qosMeterDataSpecification,
             qosMeterCommittedRate,
             qosMeterCommittedBurst,
             qosMeterPeakRate,
             qosMeterPeakBurst,
             qosMeterHighConfAction,
             qosMeterMedConfAction,
             qosMeterLowConfAction
        qosQNext, qosQSchdParam
    }
    STATUS current
    DESCRIPTION
            "Objects from
       "The Queue Group contains the qosMeterTable." objects  that  describe
       an interface's queues."
    ::= { qosPolicyIpPibGroups 11 qosPibGroups 14 }

qosActionGroup

qosPibSchedulerGroup OBJECT-GROUP
    OBJECTS {
             qosActionDrop,
             qosActionUpdateDSCP
        qosSchedulerMethod, qosSchedulerSchdParam,
        qosSchedulerNext
    }
    STATUS current
    DESCRIPTION
            "Objects from
       "The  Scheduler  Group  contains  the qosActionTable."  objects   that
       describe packet schedulers on interfaces."
    ::= { qosPolicyIpPibGroups 12 qosPibGroups 15 }

qosTargetGroup

qosPibSchdParamGroup OBJECT-GROUP
    OBJECTS {
             qosTargetFilterId,
             qosTargetFilterType,
             qosTargetInterfaceRoles,
             qosTargetInterfaceDirection,
             qosTargetOrder,
             qosTargetMeter
        qosSchdParamPriority,
        qosSchdParamMinRateAbs, qosSchdParamMinRateRel,
        qosSchdParamMaxRateAbs, qosSchdParamMaxRateRel,
    }

DiffServ QoS Policy Information Base                       November 2000

    STATUS current
    DESCRIPTION
            "Objects from
       "The Scheduler Parameter Group contains  the qosTargetTable."  objects
       that describe packet schedulers' parameters on inter-
       faces."
    ::= { qosPolicyIpPibGroups 13 qosPibGroups 16 }

END

7.

DiffServ QoS Policy Information Base                       November 2000

9.  Security Considerations

The information contained in a PIB when transported by the COPS protocol
[COPS-PR] may be sensitive, and its function of provisioning a PEP
requires that only authorized communication take place.  The use of
IPSEC between PDP and PEP, as described in [COPS], provides the
necessary protection against these threats.

8.

10.  Intellectual Property Considerations

The IETF is being notified of intellectual property rights claimed in
regard to some or all of the specification contained in this document.
For more information consult the online list of claimed rights.

9.

11.  Authors' Addresses

     Michael Fine
     Cisco Systems, Inc.
     170 West Tasman Drive
     San Jose, CA  95134-1706 USA
     Phone: +1 408 527 8218
     Email: mfine@cisco.com

     Keith McCloghrie
     Cisco Systems, Inc.
     170 West Tasman Drive
     San Jose, CA  95134-1706 USA
     Phone: +1 408 526 5260
     Email: kzm@cisco.com

     John Seligson
     Nortel Networks, Inc.
     4401 Great America Parkway
     Santa Clara, CA 95054 USA
     Phone: +1 408 495 2992
     Email: jseligso@nortelnetworks.com

     Kwok Ho Chan
     Nortel Networks, Inc.
     600 Technology Park Drive

DiffServ QoS Policy Information Base                       November 2000

     Billerica, MA 01821 USA
     Phone: +1 978 288 8175
     Email: khchan@nortelnetworks.com

     Scott Hahn
     Intel
     2111 NE 25th Avenue
     Hillsboro, OR 97124 USA
     Phone: +1 503 264 8231
     Email: scott.hahn@intel.com

     Andrew Smith
     Fax: +1 415 345 1827
     Email: ah_smith@pacbell.net
     Allegro Networks
     6399 San Ignacio Ave
     San Jose, CA 95119
     andrew@allegronetworks.com

     Francis Reichmeyer
     IPHighway Inc.
     Parker Plaza, 16th Floor
     400 Kelby St.
     Fort-Lee, NJ 07024
     University Park at MIT
     26 Landsdowne Street
     Cambridge, MA  02139
     Phone: (201) 585-0800 +1 617 494 9980
     Email: FranR@iphighway.com

10.  franr@pfn.com

12.  References

[COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., and
       A. Sastry, "The COPS (Common Open Policy Service) Protocol"
       RFC 2748, January 2000.

[COPS-PR] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie,
        F. Reichmeyer, J. Seligson, A. Smith, R. Yavatkar,
        "COPS Usage for Policy Provisioning,"
        draft-ietf-rap-cops-pr-03.txt, July
        draft-ietf-rap-cops-pr-05.txt, October 2000.

[SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning
        Information," draft-ietf-rap-sppi-01.txt, July draft-ietf-rap-sppi-03.txt, November 2000.

[DSARCH] M. Carlson, W. Weiss, S. Blake, Z. Wang, D. Black, and
         E. Davies, "An Architecture for Differentiated Services",

DiffServ QoS Policy Information Base                       November 2000

         RFC 2475, December 1998

[DSFIELD] K. Nichols, S. Blake, F. Baker, D. Black, "Definition of the
          Differentiated Services Field (DS Field) in the IPv4 and
          IPv6 Headers", RFC 2474, December 1998.

[FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn,
         A. Smith, F. Reichmeyer "Framework Policy Information Base",
         Internet Draft <draft-ietf-rap-frameworkpib-01.txt>,

[POLICY] M. Stevens, W. Weiss H. Mahon, B. Moore, J. Strassner,
        G. Waters, A. Westerinen, J. Wheeler, "Policy Framework",
        draft-ietf-policy-framework-00.txt, September 1999. <draft-ietf-rap-frameworkpib-03.txt>,
         November 2000

[RAP-FRAMEWORK] R. Yavatkar, D. Pendarakis, "A Framework for
        Policy-based Admission Control",
        draft-ietf-rap-framework-03.txt, April 1999.
        RFC 2753, January 2000.

[SNMP-SMI]  K. McCloghrie, D. Perkins, J. Schoenwaelder, J. Case,
        M. Rose and S. Waldbusser, "Structure of Management Information
        Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

[MODEL] Y. Bernet, A. Smith, S. Blake, D. Grossman "A Conceptual Model
        for DiffServ Routers", draft-ietf-diffserv-model-03.txt,
        May draft-ietf-diffserv-model-04.txt,
        July 2000.

[IFMIB] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB using
        SMIv2", RFC 2233, November 1997.

DiffServ QoS Policy Information Base                       November 2000

Table of Contents

1 Glossary ........................................................    2    3
2 Introduction ....................................................    2    3 DiffServ PIB Concepts ...........................................    2
3.1 Filters, Filter Groups and Classifiers ........................    2
3.2 Applying QoS Policy Using Targets .............................
3
3.3 Interface Modeling with Queue Sets ............................ Relationship to the Diffserv Informal Management Model ..........    3
3.1 PIB Overview ..................................................    4
3.3.1 Queue Scheduling ............................................
4
3.3.2 Assigning Packets To Queues and Thresholds ..................    5
3.3.3 Hierarchies Structure of the PIB ............................................    6
4.1 General Conventions ...........................................    6
4.2 DiffServ Data Paths ...........................................    6
4.2.1 Data Path PRC ...............................................    7
4.3 Classifiers ...................................................    7
4.3.1 Classifier PRC ..............................................    8
4.3.2  Classifier Element PRC .....................................    8
4.4 Meters ........................................................    9
4.4.1 Meter PRC ...................................................    9
4.4.2 Token-Bucket Meter PRC ......................................   10
4.5 Actions .......................................................   10
4.5.1 DSCP Mark Action PRC ........................................   11
4.5.2 Absolute Drop Action ........................................   11
4.6 Queueing Elements .............................................   11
4.6.1 Algorithmic Dropper PRC .....................................   11
4.6.2 Random Dropper PRC ..........................................   12
4.6.3 Queues and Schedulers .......................................   14
4.7 Specifying Device Capabilities ................................   15
5
4 PIB Usage Example ...............................................   16
5.1 Data Path and Classifier Example Discussion ...................   18
5.2 Meter and Action Example Discussion ...........................   19
5.3 Queue and Scheduler Example Discussion ........................   19
6 Summary of the DiffServ PIB .....................................    5
5   20
7 PIB Operational Overview ........................................    6
6   21
8 PIB Definitions .................................................    8
6.1   22
8.1 The DiffServ Base PIB .........................................    8
7   22
9 Security Considerations .........................................   48
8   79
10 Intellectual Property Considerations ............................   48
9 ...........................   79
11 Authors' Addresses ..............................................   48
10 .............................................   79
12 References .....................................................   49   80