draft-ietf-rap-frameworkpib-05.txt   draft-ietf-rap-frameworkpib-06.txt 
Internet Draft M. Fine Internet Draft M. Fine
Expires January 2002 K. McCloghrie Expires May 2002 K. McCloghrie
File: draft-ietf-rap-frameworkpib-05.txt Cisco Systems File: draft-ietf-rap-frameworkpib-06.txt Cisco Systems
J. Seligson J. Seligson
K. Chan K. Chan
Nortel Networks Nortel Networks
S. Hahn S. Hahn
R. Sahita R. Sahita
Intel Intel
A. Smith A. Smith
Allegro Networks Allegro Networks
F. Reichmeyer F. Reichmeyer
PFN PFN
July 20, 2001 November 13, 2001
Framework Policy Information Base Framework Policy Information Base
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are all provisions of Section 10 of RFC2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as ''work in reference material or to cite them other than as ''work in
progress''. progress''.
The list of current Internet-Drafts can be accessed at To view the current status of any Internet-Draft, please check the
http://www.ietf.org/1id-abstracts.html ''1id-abstracts.txt'' listing contained in an Internet-Drafts Shadow
Directory, see http://www.ietf.org/shadow.html.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Framework Policy Information Base July 2001
1. Glossary
PRC Provisioning Class. A type of policy data. Framework Policy Information Base November 2001
PRI 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 Provisioning Instance Identifier. Uniquely identifies an
instance of a PRC.
2. Introduction Abstract
[SPPI] describes a structure for specifying policy information that [SPPI] describes a structure for specifying policy information that
can then be transmitted to a network device for the purpose of can then be transmitted to a network device for the purpose of
configuring policy at that device. The model underlying this configuring policy at that device. The model underlying this
structure is one of well-defined provisioning classes and instances structure is one of well-defined provisioning classes and instances
of these classes residing in a virtual information store called the of these classes residing in a virtual information store called the
Policy Information Base (PIB). Policy Information Base (PIB).
One way to provision policy is by means of the COPS protocol [COPS] One way to provision policy is by means of the COPS protocol [COPS]
with the extensions for provisioning [COPS-PR]. This protocol with the extensions for provisioning [COPS-PR]. This protocol
supports multiple clients, each of which may provision policy for a supports multiple clients, each of which may provision policy for a
specific policy domain such as QoS, virtual private networks, or specific policy domain such as QoS, virtual private networks, or
security. security.
As described in [COPS-PR], each client supports a non-overlapping As described in [COPS-PR], each client supports a non-overlapping
and independent set of PIB modules. However, some provisioning and independent set of PIB modules. However, some provisioning
classes are common to all subject-categories (client-types) and need classes are common to all subject-categories (client-types) and need
to be present in each. This document presents a set of PRCs that to be present in each. This document defines a set of PRCs and
are common to all clients that provision policy using COPS for textual conventions that are common to all clients that provision
Provisioning. policy using COPS for Provisioning.
3. General PIB Concepts 1. Glossary
3.1. Roles PRC Provisioning Class. A type of policy data.
PRI 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 Provisioning Instance Identifier. Uniquely identifies an
instance of a PRC.
2. General PIB Concepts
2.1. Roles
The policy to apply to an interface may depend on many factors such The policy to apply to an interface may depend on many factors such
as immutable characteristics of the interface (e.g., ethernet or as immutable characteristics of the interface (e.g., ethernet or
frame relay), the status of the interface (e.g., half or full frame relay), the status of the interface (e.g., half or full
duplex), or user configuration (e.g., branch office or headquarters duplex), or user configuration (e.g., branch office or headquarters
interface). Rather than specifying policies explicitly for each interface). Rather than specifying policies explicitly for each
interface of all devices in the network, policies are specified in interface of all devices in the network, policies are specified in
terms of interface functionality. terms of interface functionality.
To describe these functionalities of an interface we use the concept To describe these functionalities of an interface we use the concept
of "Roles". A Role is simply a string that is associated with an of "Roles". A Role is simply a string that is associated with an
interface. A given interface may have any number of roles interface. A given interface may have any number of roles
simultaneously. Provisioning classes have an attribute called a simultaneously. Provisioning classes have an attribute called a
"RoleCombination÷ which is a lexicographically ordered set of roles. "RoleCombination÷ which is a lexicographically ordered set of roles.
Instances of a given provisioning class are applied to an interface Instances of a given provisioning class are applied to an interface
Framework Policy Information Base July 2001
if and only if the set of roles in the role combination matches the if and only if the set of roles in the role combination matches the
set of the roles of the interface. set of the roles of the interface.
Framework Policy Information Base November 2001
Thus, roles provide a way to bind policy to interfaces without Thus, roles provide a way to bind policy to interfaces without
having to explicitly identify interfaces in a consistent manner having to explicitly identify interfaces in a consistent manner
across all network devices. (The SNMP experience with ifIndex has across all network devices. (The SNMP experience with ifIndex has
proved this to be a difficult task.) That is, roles provide a level proved this to be a difficult task.) That is, roles provide a level
of indirection to the application of a set of policies to specific of indirection to the application of a set of policies to specific
interfaces. Furthermore, if the same policy is being applied to interfaces. Furthermore, if the same policy is being applied to
several interfaces, that policy need be pushed to the device only several interfaces, that policy need be pushed to the device only
once, rather than once per interface, as long as the interfaces are once, rather than once per interface, as long as the interfaces are
configured with the same role combination. configured with the same role combination.
We point out that, in the event that the administrator needs to have We point out that, in the event that the administrator needs to have
unique policy for each interface, this can be achieved by unique policy for each interface, this can be achieved by
configuring each interface with a unique role. configuring each interface with a unique role.
The PEP sends all its Capability Set Names, Role Combinations, The PEP sends all its Capability Set Names, Role Combinations,
Policy Controlled Interfaces, and their relationships to the PDP in Policy Controlled Interfaces, and their relationships to the PDP in
the initial COPS request (REQ) message. The PDP can install new the first COPS request (REQ) message for a handle and whenever any
instances or change existing instances of these PRIs. This updates or deletes occur. The PDP can install new instances or
operation can also occur in subsequent request messages generated in change existing instances of these PRIs. This operation can also
response to COPS state synchronization (SSQ) requests and local occur in subsequent request messages generated in response to COPS
configuration changes. state synchronization (SSQ) requests and local configuration
changes.
The comparing of roles (or role combinations) is case sensitive. The comparing of roles (or role combinations) is case sensitive.
By convention, when formatting the role-combination for exchange By convention, when formatting the role-combination for exchange
within a protocol message, within a PIB/MIB object's value, or as a within a protocol message, within a PIB/MIB object's value, or as a
printed value, the set is formatted in lexicographical order of the printed value, the set is formatted in lexicographical order of the
role's ASCII values; that is, the role that is first is formatted role's ASCII values; that is, the role that is first is formatted
first. For example, "a+b" and "b+a" are NOT different role- first. For example, "a+b" and "b+a" are NOT different role-
combinations; rather, they are different formatting of the same combinations; rather, they are different formatting of the same
role-combination, and hence for this example: role-combination, and hence for this example:
skipping to change at page 4, line 4 skipping to change at page 3, line 57
In an "install" or an "install-notify" class, the wildcard role- In an "install" or an "install-notify" class, the wildcard role-
combination "*" can be used. In addition to providing for interface- combination "*" can be used. In addition to providing for interface-
specific roles, it also allows for other optimizations in reducing specific roles, it also allows for other optimizations in reducing
the number of role-combinations for which a policy has to be the number of role-combinations for which a policy has to be
specified. For example: specified. For example:
Suppose we have three interfaces: Suppose we have three interfaces:
Roles A, B and R1 are assigned to interface I1 Roles A, B and R1 are assigned to interface I1
Roles A, B and R2 are assigned to interface I2
Framework Policy Information Base July 2001 Framework Policy Information Base November 2001
Roles A, B and R2 are assigned to interface I2
Roles A, B and R3 are assigned to interface I3 Roles A, B and R3 are assigned to interface I3
Then, a PRI of a fictional IfDscpAssignTable that has the following Then, a PRI of a fictional IfDscpAssignTable that has the following
values for its attributes: values for its attributes:
ifDscpAssignPrid = 1 ifDscpAssignPrid = 1
ifDscpAssignRoles = "*+A+B" ifDscpAssignRoles = "*+A+B"
ifDscpAssignName = "4queues" ifDscpAssignName = "4queues"
ifDscpAssignDscpMap = 1 ifDscpAssignDscpMap = 1
skipping to change at page 4, line 47 skipping to change at page 4, line 46
- Can include zero or more other roles. - Can include zero or more other roles.
- The wildcard character "*" is listed before the other roles as - The wildcard character "*" is listed before the other roles as
"*" is lexicographically before "a"; however, the wildcard matches "*" is lexicographically before "a"; however, the wildcard matches
any zero or more roles, irrespective of lexicographical order. any zero or more roles, irrespective of lexicographical order.
For example: "*+b+e+g" would match "a+b+c+e+f+g" For example: "*+b+e+g" would match "a+b+c+e+f+g"
Note that the characters "+" and "*" MUST not be used in an Note that the characters "+" and "*" MUST not be used in an
interface Role. The Framework Role PIB module in section 4 of this interface Role. The Framework Role PIB module in section 4 of this
document contains the Role and RoleCombination Textual Conventions. document contains the Role and RoleCombination Textual Conventions.
3.1.1. An Example 2.1.1. An Example
The functioning of roles might be best understood by an example. The functioning of roles might be best understood by an example.
Suppose I have a device with three interfaces, with roles as Suppose I have a device with three interfaces, with roles as
follows: follows:
IF1: "finance" IF1: "finance"
IF2: "finance" IF2: "finance"
IF3: "manager" IF3: "manager"
Suppose, I also have a PDP with two policies: Suppose, I also have a PDP with two policies:
P1: Packets from finance department (role "finance") get DSCP 5 P1: Packets from finance department (role "finance") get DSCP 5
Framework Policy Information Base July 2001
P2: Packets from managers (role "manager") get DSCP 6 P2: Packets from managers (role "manager") get DSCP 6
Framework Policy Information Base November 2001
To obtain policy, the PEP reports to the PDP that it has some To obtain policy, the PEP reports to the PDP that it has some
interfaces with role combination "finance" and some with role interfaces with role combination "finance" and some with role
combination "manager". In response, the PDP downloads policy P1 combination "manager". In response, the PDP downloads policy P1
associated with role combination "finance" and downloads a second associated with role combination "finance" and downloads a second
policy P2 associated with role combination "manager". policy P2 associated with role combination "manager".
Now suppose the finance person attached to IF2 is promoted to Now suppose the finance person attached to IF2 is promoted to
manager and so the system administrator adds the role "manager" to manager and so the system administrator adds the role "manager" to
IF2. The PEP now reports to the PDP that it has three role IF2. The PEP now reports to the PDP that it has three role
combinations: some interfaces with role combination "finance", some combinations: some interfaces with role combination "finance", some
skipping to change at page 5, line 41 skipping to change at page 5, line 39
P3: Packets from finance managers (role "finance" and role P3: Packets from finance managers (role "finance" and role
"manager") get DSCP 7 "manager") get DSCP 7
The point here is that the PDP is required to determine what policy The point here is that the PDP is required to determine what policy
applies to this new role combination and to download a third policy applies to this new role combination and to download a third policy
to the PEP for the role combination "finance+manager" even if that to the PEP for the role combination "finance+manager" even if that
policy is the same as one already downloaded. The PEP is not policy is the same as one already downloaded. The PEP is not
required (or allowed) to construct policy for new role combinations required (or allowed) to construct policy for new role combinations
from existing policy. from existing policy.
3.2. Multiple PIB Instances 2.2. Management of Role-Combinations from the PDP
The PEP notifies the PDP of the Role-Combination assigned to each
interface and ifCapSetName in a COPS configuration request
(instances of the frwkIfRoleComboTable).
Default ('null') Role-Combinations must be sent to the PDP for all
ifIndices active on the PEP in the first configuration request sent
for a request handle and updates must be sent every time the
IfIndices are updated. The PEP may notify the PDP of the Interface
Capability sets (if any) via the frwkIfCapSetTable. If the PEP does
not need to notify the PDP of capability sets, it must set the
ifCapSetName in the frwkIfRoleComboTable instances to a zero length
string.
In response to this configuration request, if applicable, the PDP
may send policies for the PEP in a solicited decision or must send a
null decision. The PEP must then send a solicited report message for
the decision.
At any later time, the PDP can update the Role-Combinations assigned
Framework Policy Information Base November 2001
to a specific interface, identified by IfIndex, or for an aggregate,
identified by IfCapSetName, via an unsolicited decision to the PEP
on any open request handle. The PDP does this by sending updated
PRIs for the frwkIfRoleComboTable.
When the Interface Role Combination associations are updated by the
PDP, the PEP is responsible to send updated requests for all open
contexts (request handles). This is true even if the PEP's request
state changes due to an internal event or if the state is changed by
the PDP. If the role-combination updates were sent by the PDP, the
PEP must send these updated requests only if it can process the
unsolicited decision containing the frwkIfRoleCombo PRIs
successfully and it must do so after sending the success report for
the unsolicited decision. If the PEP failed to process the decision
(i.e., the frwkIfRoleCombo PRIs) it must only send a failure report
to the PDP.
On the other hand, the PDP must not expect to receive the updated
requests with the revised role-combination information until after
it receives a success report for these updates from the PEP.
Note that, any unsolicited decisions received by the PEP in the time
period after it receives updates to its Role-Combination
associations and before receiving solicited decisions for the
updated requests it sent for all context handles, must be ignored
since they would contain outdated decisions sent by the PDP for the
old request information.
The PDP must respond to the updated requests by solicited decisions,
sending policies if applicable or null decisions. The PEP must
respond to these solicited decisions with solicited reports to
complete the transaction.
2.3. Updating a Request State
This section describes the messages exchanged between the PEP and
PDP when the PEP is updating a previously sent request for a
particular COPS handle. Note that a PEP can incrementally update a
request only if the frwkPibIncarnationFullState attribute is shown
to be supported via the supported PRC table. If this attribute is
not supported the PDP must treat all PEP requests as the full
request state.
2.3.1 Full Request State
When the PEP wants to send the entire request state to the PDP (for
example, in response to a Synchronize State Request from the PDP),
the PEP MUST send the incarnation instance with the
frwkPibIncarnationFullState attribute set to TRUE.
A PDP that receives an incarnation instance in the request message
with this attribute set to TRUE, must clear the request information
Framework Policy Information Base November 2001
it maintains for this request handle and re-install the information
received.
If this attribute is set to FALSE or if the incarnation instance is
missing in the request message, the request must be interpreted as
an incremental update to the previous request message.
2.3.2 Installing PRIs in a Request
If the PEP wants to install additional PRIs for a request handle,
the PEP MUST ensure that frwkPibIncarnationFullState attribute is
set to FALSE and the PEP MUST use new (unused in this context)
InstanceIds [SPPI] for these PRIs.
When a PDP receives instances with new InstanceIds for a request
with the frwkPibIncarnationFullState in the incarnation instance set
to FALSE or if the request has no incarnation information, it must
interpret these PRIs as an incremental update to the request state
and add them to the request state it maintains for this handle.
2.3.3 Updating PRIs in a Request
If the PEP wants to update previously installed PRIs for a request
handle, the PEP MUST ensure that frwkPibIncarnationFullState
attribute is set to FALSE for these PRIs. Note that the PEP must
send the same InstanceIds for the PRIs being updated. If the PEP
uses new InstanceIds, the PDP must interpret them as Install's
for this request state.
When a PDP receives a request with instances having InstanceIds that
exist in its state for that handle with the
frwkPibIncarnationFullState in the incarnation instance set to FALSE
or if the request has no incarnation information, it must interpret
these PRIs as an update to the PRIs in the request state it
maintains for this handle.
2.3.4 Removing PRIs from a Request
If the PEP wants to remove previously installed PRIs for a request
handle, the PEP MUST ensure that frwkPibIncarnationFullState
attribute is set to FALSE and MUST send the PRI bindings with the
PRID set to the InstanceId of the PRI to be removed and the length
field in the EPD object header set to the header length only,
effectively setting the data length to zero.
Note that the PEP must send the same InstanceIds for the PRIs being
removed. If the PEP sends new InstanceIds and the length field in
the EPD object header is set to the header length only (implying the
data length is zero), the PEP is attempting to remove an
unknown/non-existent PRI. This SHOULD result in the PDP sending
error PRIs in the solicited decision (see section 2.3.6 for a
description of the frwkErrorTable).
Framework Policy Information Base November 2001
If the PEP sends new InstanceIds and the length field in the EPD
object header is greater than the header length only (implying the
EPD object has some attributes encoded in it), the PDP will
interpret this as an install of the PRI if it can decode the EPD
successfully.
When a PDP receives a request with instances having InstanceIds that
exist in its state for that handle with the
frwkPibIncarnationFullState in the incarnation instance set to FALSE
or if the request has no incarnation information, and the length
field in the EPD object header is set to the header length only
(implying the data length is zero), it must remove these PRIs from
the request state it maintains for this handle.
2.3.5 Removing EXTENDED, AUGMENTED PRIs
The PEP should remove the extended/augmented PRIs when it removes
the base PRIs in the same COPS message. See [SPPI] for description
of EXTENDED/AUGMENTED PRCs. A PDP that receives removes for a base
PRI must implicitly remove the extensions.
2.3.6 Error Handling in Request updates
If the PDP cannot process all the request installs/updates/removes
in the COPS request message successfully, it MUST rollback to its
previous request state and it MUST send a solicited decision to the
PEP that contains frwkErrorTable instances. These instances contain
an error code and a sub-code as defined in the [COPS-PR] CPERR
object. For example if the PEP tries to remove an instance that does
not exist, the 'priInstanceInvalid' error code must be sent to the
PEP in a frwkError PRI. The frwkError PRIs also contain the PRC and
the instanceId of the error-causing PRI. The PEP may then examine
these error PRIs and resend the modified request. Note that, until
the PEP resends the request updates/removes it will have
configuration information for the last successful request state it
sent to the PDP.
2.4. Multiple PIB Instances
[COPS-PR] supports multiple, disjoint, independent instances of the [COPS-PR] supports multiple, disjoint, independent instances of the
PIB to represent multiple instances of configured policy. The PIB to represent multiple instances of configured policy. The
intent is to allow for the pre-provisioning of policy that can then intent is to allow for the pre-provisioning of policy that can then
be made active by a single, short decision from the PDP. be made active by a single, short decision from the PDP.
A COPS context can be defined as an independent COPS request state A COPS context can be defined as an independent COPS request state
for a particular subject category (client-type). for a particular subject category (client-type).
With the COPS-PR protocol, each of these states is identified by a With the COPS-PR protocol, each of these states is identified by a
unique client handle. The creation and deletion of these PIB unique client handle. The creation and deletion of these PIB
instances is controlled by the PDP as described in [COPS-PR]. A PEP instances can be controlled by the PDP as described in [COPS-PR] or
must open only a single "request-state" for configuration for a can be triggered by an event by the PEP. A PEP must open at least
given subject-category (client type). Any additional "request- one "request-state" for configuration for a given subject-category
states" at the PEP must be initiated by the PDP.
Framework Policy Information Base November 2001
(client type). Additional "request-states" at the PEP may be
initiated by the PDP or asynchronously generated by the PEP for
outsourcing due to local events, which will be fully specified by
the PRID/EPD data carried in the request.
The frwkPibIncarnationInCtxtSet flag defines a set of contexts out
of which only one context can be active at any given time. This set
is called the 'configuration contexts' set. At the most one context
may be active from this 'configuration context' set at any given
time. Contexts that have the frwkPibIncarnationInCtxtSet attribute
set to 'true' belong to this set. Contexts that do not belong to
this set have the frwkPibIncarnationInCtxtSet set to 'false' and
belong to the set of 'outsourcing contexts'. Note that a PEP can
have these two sets of contexts only if the
frwkPibIncarnationInCtxtSet attribute is shown to be supported via
the supported PRC table. If the frwkPibIncarnationInCtxtSet is not
supported a PEP must treat all contexts as belonging to the set of
'configuration contexts' i.e., at the most one context can be active
at any given time.
Note that in the event that a PEP has an interface capability change
such as a card hot swap or any other change in its notify
information that may warrant a policy refresh, a subsequent complete
or incremental request must be issued to the PDP containing the
new/updated capabilities for all the configuration contexts. A
request for re-configuration is issued for all request state
configuration contexts, both for the active configuration context as
well as any inactive configuration contexts. This is to ensure that
when an inactive configuration context is activated, it has been
pre-configured with policies compatible with the PEP's current
capabilities.
Although many PIB instances may be configured on a device (the Although many PIB instances may be configured on a device (the
maximum number of these instances being determined by the device maximum number of these instances being determined by the device
itself) only one of the contexts from the 'configuration contexts'
set can be active at any given time, the active one being selected
by the PDP. The Framework PIB supports the attribute
frwkPibIncarnationActive in the frwkPibIncarnationTable to allow the
PDP to denote the PIB instance as being active in a COPS decision
message, and similarly, to report the active state (active or not)
of the PIB instance to the PDP in a COPS request message.
Framework Policy Information Base July 2001 When the PEP installs an attribute frwkPibIncarnationActive that is
'true' in one PIB instance which belongs to the 'configuration
contexts' set, the PEP must ensure, re-setting the attribute if
necessary, that the frwkPibIncarnationActive attribute is 'false'
in all other installed contexts that belong to this set. To switch
contexts, the PDP should set the frwkPibIncarnationActive attribute
to 'true' in the context it wants to make the active context. The
PDP should set this attribute in a context to 'false' only if it
wants to send an inactive context to the PEP or deactivate the
active context on the PEP. If an active context is made inactive
itself) only one of them can be active at any given time, the active Framework Policy Information Base November 2001
one being selected by the PDP. To facilitate this selection, the
Framework PIB supports an attribute to make a PIB instance the
active one and, similarly, to report the active PIB instance to the
PDP in a COPS request message. This attribute is in the Incarnation
Table described below.
Setting the attribute frwkPibIncarnationActive to 'true' in one PIB without activating another context, the PEP must not have any
instance MUST ensure that the attribute is 'false' in all other policies enforced from any configuration contexts installed.
contexts.
3.3. Reporting and Configuring of Device Capabilities 2.5. Reporting and Configuring of Device Capabilities
Each network device providing policy-based services has its own Each network device providing policy-based services has its own
inherent capabilities. These capabilities can be hardware specific, inherent capabilities. These capabilities can be hardware specific,
e.g., an ethernet interface supporting input classification, or can e.g., an ethernet interface supporting input classification, or can
be statically configured, e.g., supported queuing disciplines. be statically configured, e.g., supported queuing disciplines.
These capabilities are organized into some PEP default Interface These capabilities are organized into Interface Capability Sets,
Capability Set, with each Capability Set associated with a set of with each Capability Set given a unique name (ifCapSetName) and
Role Combinations, each Role Combination associated with a set of associated with a set of Role Combinations. Each Role Combination
interfaces. After receiving the PEP default setting for the PEP may in that way be associated with a set of interfaces. . These
device capabilities, the PDP can change them. These capabilities capabilities are communicated to the PDP when policy is requested by
are communicated to the PDP when initial policy is requested by the the PEP. Knowing device capabilities, the PDP can send the
PEP. Knowing device capabilities, the PDP can send the provisioning provisioning instances (PRIs) relevant to the specific device,
instances (PRIs) relevant to the specific device, rather than rather than sending the entire PIB.
sending the entire PIB.
The PIB indicates which capabilities the PEP must report to the PDP Specific capability PRCs may be defined in other PIBs. These
by means of the PIB-ACCESS clause as described in [SPPI]. capability instances are grouped via the frwkIfCapSetTable. If the
PEP wishes to send capability information to the PDP, the PIB must
indicate which capabilities the PEP may send to the PDP by means of
the 'notify' PIB-ACCESS clause as described in [SPPI]. If a PIB does
not have any capabilities to communicate to the PDP, it must not
send any instances for the frwkIfCapSetTable. If in this case the
frwkIfRoleCombo table is used to communicate role combinations
assigned to interfaces (via IfIndex), the ifCapSetName attribute in
the frwkIfRoleComboTable instances must be set to a zero length
string.
3.4. Reporting of Device Limitations 2.6. Reporting of Device Limitations
To facilitate efficient policy installation, it is important to To facilitate efficient policy installation, it is important to
understand a device's limitations in relation to the advertised understand a device's limitations in relation to the advertised
device capabilities. Limitations may be class-based, e.g., an device capabilities. Limitations may be class-based, e.g., an
"install" class is supported as a "notify" or only a limited number "install" class is supported as a "notify" or only a limited number
of class instances may be created, or attribute-based. Attribute of class instances may be created, or attribute-based. Attribute
limitations, such as supporting a restricted set of enumerations or limitations, such as supporting a restricted set of enumerations or
requiring related attributes to have certain values, detail requiring related attributes to have certain values, detail
implementation limitations at a fine level of granularity. implementation limitations at a fine level of granularity.
A PDP can avoid certain installation issues in a proactive fashion A PDP can avoid certain installation issues in a proactive fashion
by taking into account a device's limitations prior to policy by taking into account a device's limitations prior to policy
installation rather than in a reactive mode during installation. As installation rather than in a reactive mode during installation. As
with device capabilities, device limitations are communicated to the with device capabilities, device limitations are communicated to the
PDP when initial policy is requested. PDP when policy is requested.
Reported device limitations may be accompanied by guidance values Reported device limitations may be accompanied by guidance values
that can be used by a PDP to determine acceptable values for the that can be used by a PDP to determine acceptable values for the
identified attributes. identified attributes.
Framework Policy Information Base July 2001 Framework Policy Information Base November 2001
4. The Framework Role PIB module 3. The Framework TC PIB module
FRAMEWORK-ROLE-PIB PIB-DEFINITIONS ::= BEGIN FRAMEWORK-TC-PIB PIB-DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, TEXTUAL-CONVENTION, pib FROM COPS-PR-SPPI IMPORTS MODULE-IDENTITY, TEXTUAL-CONVENTION, pib FROM COPS-PR-SPPI
SnmpAdminString FROM SNMP-FRAMEWORK-MIB; SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
frwkRolePib MODULE-IDENTITY frwkTcPib MODULE-IDENTITY
SUBJECT-CATEGORIES { all } SUBJECT-CATEGORIES { all }
LAST-UPDATED "200003010400Z" LAST-UPDATED "200111130400Z"
ORGANIZATION "IETF RAP WG" ORGANIZATION "IETF RAP WG"
CONTACT-INFO "Keith McCloghrie CONTACT-INFO "Keith McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive, 170 West Tasman Drive,
San Jose, CA 95134-1706 USA San Jose, CA 95134-1706 USA
Phone: +1 408 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com Email: kzm@cisco.com
John Seligson John Seligson
Nortel Networks, Inc. Nortel Networks, Inc.
4401 Great America Parkway 4401 Great America Parkway
Santa Clara, CA 95054 USA Santa Clara, CA 95054 USA
Phone: +1 408 495 2992 Phone: +1 408 495 2992
Email: jseligso@nortelnetworks.com" Email: jseligso@nortelnetworks.com"
DESCRIPTION DESCRIPTION
"The PIB module containing the Role and "The PIB module containing the Role and
RoleCombination Textual Conventions and other RoleCombination Textual Conventions and other
required TCs." generic TCs."
::= { pib tbd } -- tbd to be assigned by IANA ::= { pib tbd } -- tbd to be assigned by IANA
Role ::= TEXTUAL-CONVENTION Role ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A role represents a functionality characteristic or "A role represents a functionality characteristic or
capability of a resource to which policies are applied. capability of a resource to which policies are applied.
Examples of roles include Backbone_interface, Examples of roles include Backbone_interface,
Frame_Relay_interface, BGP-capable-router, web-server, Frame_Relay_interface, BGP-capable-router, web-server,
firewall, etc. firewall, etc.
skipping to change at page 7, line 59 skipping to change at page 12, line 5
RoleCombination ::= TEXTUAL-CONVENTION RoleCombination ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Display string consisting of a set of roles concatenated "A Display string consisting of a set of roles concatenated
with a '+' character where the roles are in lexicographic with a '+' character where the roles are in lexicographic
order from minimum to maximum. order from minimum to maximum.
For example, a+b and b+a are NOT different For example, a+b and b+a are NOT different
role-combinations; rather, they are different formatting of role-combinations; rather, they are different formatting of
the same (one) role-combination. the same (one) role-combination.
Notice the roles within a role-combination are in Framework Policy Information Base November 2001
Framework Policy Information Base July 2001
Notice the roles within a role-combination are in
Lexicographic order from minimum to maximum, hence, we Lexicographic order from minimum to maximum, hence, we
declare: declare:
a+b is the valid formatting of the role-combination, a+b is the valid formatting of the role-combination,
b+a is an invalid formatting of the role-combination. b+a is an invalid formatting of the role-combination.
Notice the need of zero-length role-combination as the role- Notice the need of zero-length role-combination as the role-
combination of interfaces to which no roles have been combination of interfaces to which no roles have been
assigned. This role-combination is also known as the null assigned. This role-combination is also known as the null
role-combination. (Note the deliberate use of lower case role-combination. (Note the deliberate use of lower case
letters to avoid confusion with the ASCII NULL character letters to avoid confusion with the ASCII NULL character
skipping to change at page 8, line 48 skipping to change at page 12, line 49
convention. convention.
An attribute with this syntax can have the value 0 to An attribute with this syntax can have the value 0 to
indicate that it currently does not identify a PRC indicate that it currently does not identify a PRC
attribute." attribute."
SYNTAX Unsigned32 SYNTAX Unsigned32
AttrIdentifierOid ::= TEXTUAL-CONVENTION AttrIdentifierOid ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
An OID that identifies an attribute in a PRC. The value MUST "An OID that identifies an attribute in a PRC. The value
be an OID assigned to a PRC's attribute definition. The last MUST be an OID assigned to a PRC's attribute definition. The
sub-id is the position of the attribute as it is defined in last sub-id is the position of the attribute as it is
the PRC entry definition. The prefix OID (after dropping the defined in the PRC entry definition. The prefix OID (after
last sub-id) is the OID assigned to a defined PRC. An dropping the last sub-id) is the OID assigned to a defined
attribute with this syntax can have the value 0.0 PRC. An attribute with this syntax can have the value 0.0
(zeroDotZero) to indicate that it currently does not (zeroDotZero) to indicate that it currently does not
identify a PRC's attribute." identify a PRC's attribute."
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
Framework Policy Information Base November 2001
ClientType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An Unsigned32 value that identifies a COPS Client-type
[COPS]. An attribute with this syntax must be set to zero if
it does not specify a COPS client-type."
SYNTAX Unsigned32 (0..65535)
ClientHandle ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An octet string that identifies a COPS Client handle
[COPS]."
SYNTAX OCTET STRING (SIZE(0..65535))
END END
Framework Policy Information Base July 2001 Framework Policy Information Base November 2001
5. Summary of the Framework PIB 4. Summary of the Framework PIB
The Framework PIB comprises of three groups: The Framework PIB comprises of three groups:
1. Base PIB classes Group 4.1. Base PIB classes Group
This contains PRCs intended to describe the PRCs supported This contains PRCs intended to describe the PRCs supported
by the PEP, PRC and/or attribute limitations and its current by the PEP, PRC and/or attribute limitations and its current
configuration. configuration.
PRC Support Table PRC Support Table
As the technology evolves, we expect devices to be enhanced As the technology evolves, we expect devices to be enhanced
with new PIBs, existing PIBs to add new PRCs and existing PRCs with new PIBs, existing PIBs to add new PRCs and existing PRCs
to be augmented or extended with new attributes. Also, it is to be augmented or extended with new attributes. Also, it is
skipping to change at page 9, line 50 skipping to change at page 14, line 50
PIB Incarnation Table PIB Incarnation Table
This table contains exactly one row (corresponding to one PRI) This table contains exactly one row (corresponding to one PRI)
per context. It identifies the PDP that was the last to per context. It identifies the PDP that was the last to
download policy into the device and also contains an identifier download policy into the device and also contains an identifier
to identify the version of the policy currently downloaded. to identify the version of the policy currently downloaded.
This identifier, both its syntax and value, is meaningful only This identifier, both its syntax and value, is meaningful only
to the PDPs. It is intended to be a mechanism whereby a PDP, to the PDPs. It is intended to be a mechanism whereby a PDP,
on connecting to a PEP, can easily identify a known incarnation on connecting to a PEP, can easily identify a known incarnation
of policy. The incarnation PRC also includes an attribute to of policy. This PRC defines a flag via which the installed
indicate which context is the active one at the present time. contexts are divided into a set of contexts out of which only
The incarnation instance is specific to the particular Subject one context is active ('configuration contexts') and a set of
Category (Client-Type). 'outsourcing contexts'. The incarnation PRC also
defines an attribute to indicate which context is the
active one at the present time in the 'configuration contexts'
set. The incarnation instance is specific to the particular
Subject Category (Client-Type).
Framework Policy Information Base November 2001
Component Limitations Table Component Limitations Table
Some devices may not be able to implement the full range of Some devices may not be able to implement the full range of
values for all attributes. In principle, each PRC supports a values for all attributes. In principle, each PRC supports a
set of errors that the PEP can report to the PDP in the event set of errors that the PEP can report to the PDP in the event
Framework Policy Information Base July 2001
that the specified policy is not implementable. It may be that the specified policy is not implementable. It may be
preferable for the PDP to be informed of the device limitations preferable for the PDP to be informed of the device limitations
before actually attempting to install policy, and while the before actually attempting to install policy, and while the
error can indicate that a particular attribute value is error can indicate that a particular attribute value is
unacceptable to the PEP, this does not help the PDP ascertain unacceptable to the PEP, this does not help the PDP ascertain
which values would be acceptable. To alleviate these which values would be acceptable. To alleviate these
limitations, the PEP can report some limitations of attribute limitations, the PEP can report some limitations of attribute
values and/or classes and possibly guidance values for the values and/or classes and possibly guidance values for the
attribute in the Component Limitations Table attribute in the Component Limitations Table
Device Identification Table Device Identification Table
This class contains a single provisioning instance that This class contains a single provisioning instance that
contains device-specific information that is used to facilitate contains device-specific information that is used to facilitate
efficient policy installation by a PDP. The instance of this efficient policy installation by a PDP. The instance of this
class is reported to the PDP in a COPS request message so that class is reported to the PDP in a COPS request message so that
the PDP can take into account certain device characteristics the PDP can take into account certain device characteristics
during policy installation. during policy installation.
2. Device Capabilities group 4.2. Device Capabilities group
This group contains the PRCs that describe the characteristics of This group contains the PRCs that describe the characteristics of
interfaces of the device and the Role Combinations assigned to interfaces of the device and the Role Combinations assigned to
them. them.
Interface Capabilities Set Table Interface Capabilities Set Table
The interfaces the PEP supports are described by rows in The interfaces the PEP supports are described by rows in
this table (frwkIfCapSetTable). Each row, or instance of this this table (frwkIfCapSetTable). Each row, or instance of this
class, associates a unique interface name with a set of class, associates a unique interface name with a set of
capabilities that the interface supports. The unique name is capabilities that the interface supports. The unique name is
used to form a set of capabilities that the name represents. used to form a set of capabilities that the name represents.
The capability references can specify instances in relevant The capability references can specify instances in relevant
capability tables in any PIB. The PEP notifies the PDP of these capability tables in any PIB. The PEP notifies the PDP of these
interface names and capabilities and then the PDP configures interface names and capabilities and then the PDP configures
the interfaces, per role combination. The unique name the interfaces, per role combination. The unique name
(IfCapSetName) is not to be confused with the IfType object in (IfCapSetName) is not to be confused with the IfType object in
MIB-II [STD17]. MIB-II [STD17].
Interface Capability and Role Combo Table Interface and Role Combination Table
The Interface Capabilities Set Table (explained above) The Interface Capabilities Set Table (explained above)
describes the interfaces the PEP supports by their describes the interfaces the PEP supports by their
capabilities, by assigning the capability sets a unique name. capabilities, by assigning the capability sets a unique name
It is possible to tailor the behavior of interfaces by (ifCapSetName). It is possible to tailor the behavior of
assigning specific roles to the capability sets. This allows interfaces by assigning specific role-combinations to the
interfaces with the same capability sets to be assigned capability sets. This allows interfaces with the same
different policies, based on the current roles assigned to capability sets to be assigned different policies, based on the
them. At the PDP, configuration is done in terms of these
interface capability set names (ifCapSetName) and the role
combinations assigned to them. Thus, each row of this
class is a <interface capability set name, Role Combo> two-
tuple, that indicates the roles that have been assigned to a
Framework Policy Information Base July 2001
particular capability set (as identified by IfCapSetName). The
ifCapSetName is the grouping attribute used to form a set of
role combinations that apply to this capability set.
Interface and Role Combination Table Framework Policy Information Base November 2001
The Interface and Role Combination Table describes the current roles assigned to them. At the PDP, configuration is
association between specific interfaces with each role done in terms of these interface capability set names and the
combination. It answers the questions of Šwhich interfaces role-combinations assigned to them. Thus, each row of this
have a specific role combination?Ă and Šwhat role combination class is a <Interface Index, interface capability set name,
a specific interface is a part of?Ă. The Interface and Role Role Combo> tuple, that indicates the roles that have been
Combination Table entries each contains a <ifIndex, Role Combo> assigned to a particular capability set (as identified by
two-tuple to accomplish this mapping. IfCapSetName) and to a particular ifCapSetName. Note that the
uniqueness criteria for this table has all the attributes, thus
a ifCapSetName may have multiple role-combinations that it is
associated with. Via the IfIndex, this table answers the
questions of Šwhich interfaces have a specific role
combination?Ă and Šwhat role combination a specific interface
is a part of?Ă.
3. Classifier group 4.3. Classifier group
This group contains the IP and IEEE 802 Classifier elements. The This group contains the IP, IEEE 802 and Internal Label
set of tables consist of a Base Filter table that contains the Classifier elements. The set of tables consist of a Base Filter
Index InstanceId and the Negation flag for the filter. This table that contains the Index InstanceId and the Negation flag
frwkBaseFilterTable is extended to form the IP Filter table and for the filter. This frwkBaseFilterTable is extended to form the
the 802 Filter table [802]. Filters may also be defined outside IP Filter table, the 802 Filter table [802] and the Internal
this document and used to extend the Base Filter table. Label table. Filters may also be defined outside this document
and used to extend the Base Filter table.
The Extended classes do not have a separate Index value. The Extended classes do not have a separate Index value.
Instances of the extended classes have the same indices as their Instances of the extended classes have the same indices as their
base class instance. Inheritance is achieved using the EXTENDS base class instance. Inheritance is achieved using the EXTENDS
keyword as defined in [SPPI]. keyword as defined in [SPPI].
Framework Policy Information Base July 2001 4.4. Marker group
6. The Framework PIB Module This group contains the 802 marker and internal label marker
PRCs. The 802 marker may be applied to mark 802 packets with the
required VLAN Id and/or priority value. The Internal Label marker
is applied to traffic in order to label it with a network device
specific label. Such a label is used to assist the
differentiation of an input flow after it has been aggregated
with other flows. The label is implementation specific and may
be used for other policy related functions like flow accounting
purposes and/or other data path treatments.
Framework Policy Information Base November 2001
5. The Framework PIB Module
FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Unsigned32, Integer32, MODULE-IDENTITY, Unsigned32, Integer32, MODULE-IDENTITY,
MODULE-COMPLIANCE, OBJECT-TYPE, OBJECT-GROUP, pib MODULE-COMPLIANCE, OBJECT-TYPE, OBJECT-GROUP, pib
FROM COPS-PR-SPPI FROM COPS-PR-SPPI
InstanceId, Prid InstanceId, Prid
FROM COPS-PR-SPPI-TC FROM COPS-PR-SPPI-TC
RoleCombination, PrcIdentifier RoleCombination, PrcIdentifier, AttrIdentifier,
FROM FRAMEWORK-ROLE-PIB ClientType, ClientHandle
InetAddress, InetAddressType FROM FRAMEWORK-TC-PIB
InetAddress, InetAddressType,
InetAddressPrefixLength, InetPortNumber
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
InterfaceIndex InterfaceIndex
FROM IF-MIB FROM IF-MIB
DscpOrAny
FROM DIFFSERV-DSCP-TC
TruthValue, PhysAddress TruthValue, PhysAddress
FROM SNMPv2-TC FROM SNMPv2-TC
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB; FROM SNMP-FRAMEWORK-MIB;
frameworkPib MODULE-IDENTITY frameworkPib MODULE-IDENTITY
SUBJECT-CATEGORIES { all } SUBJECT-CATEGORIES { all }
LAST-UPDATED "200003010400Z" LAST-UPDATED "200011130400Z"
ORGANIZATION "IETF RAP WG" ORGANIZATION "IETF RAP WG"
CONTACT-INFO " CONTACT-INFO "
Michael Fine Michael Fine
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 USA San Jose, CA 95134-1706 USA
Phone: +1 408 527 8218 Phone: +1 408 527 8218
Email: mfine@cisco.com Email: mfine@cisco.com
Keith McCloghrie Keith McCloghrie
skipping to change at page 12, line 53 skipping to change at page 17, line 57
San Jose, CA 95134-1706 USA San Jose, CA 95134-1706 USA
Phone: +1 408 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com Email: kzm@cisco.com
John Seligson John Seligson
Nortel Networks, Inc. Nortel Networks, Inc.
4401 Great America Parkway 4401 Great America Parkway
Santa Clara, CA 95054 USA Santa Clara, CA 95054 USA
Phone: +1 408 495 2992 Phone: +1 408 495 2992
Email: jseligso@nortelnetworks.com" Email: jseligso@nortelnetworks.com"
DESCRIPTION DESCRIPTION
"A PIB module containing the base set of provisioning "A PIB module containing the base set of provisioning
Framework Policy Information Base November 2001
classes that are required for support of policies for classes that are required for support of policies for
all subject-categories." all subject-categories."
::= { pib tbd } -- tbd to be assigned by IANA ::= { pib tbd } -- tbd to be assigned by IANA
Framework Policy Information Base July 2001
-- --
-- The root OID for PRCs in the Framework PIB -- The root OID for PRCs in the Framework PIB
-- --
frwkBasePibClasses frwkBasePibClasses
OBJECT IDENTIFIER ::= { frameworkPib 1 } OBJECT IDENTIFIER ::= { frameworkPib 1 }
-- --
-- Textual Conventions -- Textual Conventions
-- --
skipping to change at page 14, line 5 skipping to change at page 19, line 5
DESCRIPTION DESCRIPTION
"An instance of the frwkPrcSupport class that identifies a "An instance of the frwkPrcSupport class that identifies a
specific PRC and associated attributes as supported specific PRC and associated attributes as supported
by the device." by the device."
PIB-INDEX { frwkPrcSupportPrid } PIB-INDEX { frwkPrcSupportPrid }
UNIQUENESS { frwkPrcSupportSupportedPrc } UNIQUENESS { frwkPrcSupportSupportedPrc }
::= { frwkPrcSupportTable 1 } ::= { frwkPrcSupportTable 1 }
Framework Policy Information Base July 2001 Framework Policy Information Base November 2001
FrwkPrcSupportEntry ::= SEQUENCE { FrwkPrcSupportEntry ::= SEQUENCE {
frwkPrcSupportPrid InstanceId, frwkPrcSupportPrid InstanceId,
frwkPrcSupportSupportedPrc PrcIdentifier, frwkPrcSupportSupportedPrc PrcIdentifier,
frwkPrcSupportSupportedAttrs OCTET STRING frwkPrcSupportSupportedAttrs OCTET STRING
} }
frwkPrcSupportPrid OBJECT-TYPE frwkPrcSupportPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
skipping to change at page 15, line 5 skipping to change at page 20, line 5
corresponding to the (8*i)-th class attribute. Each bit corresponding to the (8*i)-th class attribute. Each bit
specifies whether or not the corresponding class attribute specifies whether or not the corresponding class attribute
is currently supported, with a '1' indicating support and a is currently supported, with a '1' indicating support and a
'0' indicating no support. If the value of this bit string '0' indicating no support. If the value of this bit string
is N bits long and there are more than N class attributes is N bits long and there are more than N class attributes
then the bit string is logically extended with 0's to the then the bit string is logically extended with 0's to the
required length." required length."
::= { frwkPrcSupportEntry 3 } ::= { frwkPrcSupportEntry 3 }
Framework Policy Information Base July 2001 Framework Policy Information Base November 2001
-- --
-- PIB Incarnation Table -- PIB Incarnation Table
-- --
frwkPibIncarnationTable OBJECT-TYPE frwkPibIncarnationTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkPibIncarnationEntry SYNTAX SEQUENCE OF FrwkPibIncarnationEntry
PIB-ACCESS install-notify PIB-ACCESS install-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class contains a single provisioning instance per "This class contains a single provisioning instance per
installed context that identifies the current incarnation installed context that identifies the current incarnation
of the PIB and the PDP or network manager that installed of the PIB and the PDP or network manager that installed
this incarnation. The instance of this class is reported to this incarnation. The instance of this class is reported to
the PDP in the REQ message so that the PDP can (attempt to) the PDP in the REQ message so that the PDP can (attempt to)
ascertain the current state of the PIB and the active ascertain the current state of the PIB. A network manager
context. A network manager may use the instance to may use the instance to determine the state of the device."
determine the state of the device."
::= { frwkBasePibClasses 2 } ::= { frwkBasePibClasses 2 }
frwkPibIncarnationEntry OBJECT-TYPE frwkPibIncarnationEntry OBJECT-TYPE
SYNTAX FrwkPibIncarnationEntry SYNTAX FrwkPibIncarnationEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of the frwkPibIncarnation class. Only "An instance of the frwkPibIncarnation class. Only
one instance of this provisioning class is ever one instance of this provisioning class is ever
instantiated per context" instantiated per context"
skipping to change at page 15, line 45 skipping to change at page 20, line 44
PIB-INDEX { frwkPibIncarnationPrid } PIB-INDEX { frwkPibIncarnationPrid }
::= { frwkPibIncarnationTable 1 } ::= { frwkPibIncarnationTable 1 }
FrwkPibIncarnationEntry ::= SEQUENCE { FrwkPibIncarnationEntry ::= SEQUENCE {
frwkPibIncarnationPrid InstanceId, frwkPibIncarnationPrid InstanceId,
frwkPibIncarnationName SnmpAdminString, frwkPibIncarnationName SnmpAdminString,
frwkPibIncarnationId OCTET STRING, frwkPibIncarnationId OCTET STRING,
frwkPibIncarnationLongevity Unsigned32, frwkPibIncarnationLongevity Unsigned32,
frwkPibIncarnationTtl Unsigned32, frwkPibIncarnationTtl Unsigned32,
frwkPibIncarnationActive TruthValue frwkPibIncarnationInCtxtSet TruthValue,
frwkPibIncarnationActive TruthValue,
frwkPibIncarnationFullState TruthValue
} }
frwkPibIncarnationPrid OBJECT-TYPE frwkPibIncarnationPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index to uniquely identify an instance of this "An index to uniquely identify an instance of this
provisioning class." provisioning class."
::= { frwkPibIncarnationEntry 1 } ::= { frwkPibIncarnationEntry 1 }
Framework Policy Information Base July 2001 Framework Policy Information Base November 2001
frwkPibIncarnationName OBJECT-TYPE frwkPibIncarnationName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of the PDP that installed the current incarnation "The name of the PDP that installed the current incarnation
of the PIB into the device. By default, it is the zero of the PIB into the device. By default, it is the zero
length string." length string."
::= { frwkPibIncarnationEntry 2 } ::= { frwkPibIncarnationEntry 2 }
skipping to change at page 17, line 5 skipping to change at page 22, line 5
the incarnation and download new policy, if necessary, on a the incarnation and download new policy, if necessary, on a
reconnect. On receiving a Remove-State [COPS-PR] for the reconnect. On receiving a Remove-State [COPS-PR] for the
active context, this attribute value MUST be ignored and the active context, this attribute value MUST be ignored and the
PEP should expire the policy in that active context PEP should expire the policy in that active context
immediately. immediately.
Policy enforcement timing only applies to policies that have Policy enforcement timing only applies to policies that have
been installed dynamically (e.g., by a PDP via COPS)." been installed dynamically (e.g., by a PDP via COPS)."
::= { frwkPibIncarnationEntry 4 } ::= { frwkPibIncarnationEntry 4 }
Framework Policy Information Base July 2001 Framework Policy Information Base November 2001
frwkPibIncarnationTtl OBJECT-TYPE frwkPibIncarnationTtl OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds after a Client Close or TCP timeout "The number of seconds after a Client Close or TCP timeout
for which the PEP continues to enforce the policy in the for which the PEP continues to enforce the policy in the
PIB. After this interval, the PIB is considered expired and PIB. After this interval, the PIB is considered expired and
the device no longer enforces the policy installed in the the device no longer enforces the policy installed in the
PIB. PIB.
This attribute is only meaningful if This attribute is only meaningful if
frwkPibIncarnationLongevity is set to expireOnTimeout." frwkPibIncarnationLongevity is set to expireOnTimeout."
::= { frwkPibIncarnationEntry 5 } ::= { frwkPibIncarnationEntry 5 }
frwkPibIncarnationInCtxtSet OBJECT-TYPE
SYNTAX TruthValue
STATUS current
DESCRIPTION
"When the PDP installs a PRI with this flag set to 'true' it
implies this context belongs to the set of contexts out of
which at the most one context can be active at a given time.
If this attribute is set to false this context is one of the
outsourcing (simultaneous active) contexts on the PEP."
::= { frwkPibIncarnationEntry 6 }
frwkPibIncarnationActive OBJECT-TYPE frwkPibIncarnationActive OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this attribute is set to TRUE, then the PIB instance "When the PDP installs a PRI on the PEP with this attribute
to which this PRI belongs becomes the active PIB instance. set to 'true', then the PIB instance to which this PRI
The previous active instance MUST become inactive and the belongs must become the active PIB instance if this context
frwkPibIncarnationActive attribute in that PIB instance belongs to the 'configuration contexts' set. In this case,
MUST be set to false. the previous active instance from this set MUST become
inactive and the frwkPibIncarnationActive attribute in that
PIB instance MUST be set to 'false'.
When the PEP installs an attribute frwkPibIncarnationActive When the PDP installs an attribute frwkPibIncarnationActive
that is 'true' in one PIB instance, the PEP must ensure, on the PEP that is 'true' in one PIB instance and if the
re-setting the attribute if necessary, that the context belongs to the 'configuration contexts' set, the PEP
must ensure, re-setting the attribute if necessary, that the
frwkPibIncarnationActive attribute is 'false' in all other frwkPibIncarnationActive attribute is 'false' in all other
contexts." contexts which belong to the 'configuration contexts' set."
::= { frwkPibIncarnationEntry 6 } ::= { frwkPibIncarnationEntry 7 }
Framework Policy Information Base November 2001
frwkPibIncarnationFullState OBJECT-TYPE
SYNTAX TruthValue
STATUS current
DESCRIPTION
"This attribute is interpreted only when sent in a COPS
request message from the PEP to the PDP. It does not have
any meaning when sent from the PDP to the PDP.
If this attribute is set to TRUE by the PEP, then the
request that the PEP sends to the PDP must be interpreted as
the complete configuration request for the PEP. The PDP must
in this case refresh the request information for that
handle. If this attribute is set to FALSE, then the request
PRIs sent in the request must be interpreted as updates to
the previous request PRIs sent for that handle. See section
3.3 for details on updating request state information."
::= { frwkPibIncarnationEntry 8 }
-- --
-- Device Identification Table -- Device Identification Table
-- --
-- This table supports the ability to export general -- This table supports the ability to export general
-- purpose device information to facilitate efficient -- purpose device information to facilitate efficient
-- communication between the device and a PDP -- communication between the device and a PDP
frwkDeviceIdTable OBJECT-TYPE frwkDeviceIdTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkDeviceIdEntry SYNTAX SEQUENCE OF FrwkDeviceIdEntry
PIB-ACCESS notify PIB-ACCESS notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class contains a single provisioning instance that "This class contains a single provisioning instance that
contains device-specific information that is used to contains device-specific information that is used to
facilitate efficient policy installation by a PDP. The facilitate efficient policy installation by a PDP. The
Framework Policy Information Base July 2001
instance of this class is reported to the PDP in a COPS instance of this class is reported to the PDP in a COPS
request message so that the PDP can take into account request message so that the PDP can take into account
certain device characteristics during policy installation." certain device characteristics during policy installation."
::= { frwkBasePibClasses 3 } ::= { frwkBasePibClasses 3 }
frwkDeviceIdEntry OBJECT-TYPE frwkDeviceIdEntry OBJECT-TYPE
SYNTAX FrwkDeviceIdEntry SYNTAX FrwkDeviceIdEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of the frwkDeviceId class. Only one instance of "An instance of the frwkDeviceId class. Only one instance of
this provisioning class is ever instantiated." this provisioning class is ever instantiated."
PIB-INDEX { frwkDeviceIdPrid } PIB-INDEX { frwkDeviceIdPrid }
::= { frwkDeviceIdTable 1 } ::= { frwkDeviceIdTable 1 }
Framework Policy Information Base November 2001
FrwkDeviceIdEntry ::= SEQUENCE { FrwkDeviceIdEntry ::= SEQUENCE {
frwkDeviceIdPrid InstanceId, frwkDeviceIdPrid InstanceId,
frwkDeviceIdDescr SnmpAdminString, frwkDeviceIdDescr SnmpAdminString,
frwkDeviceIdMaxMsg Unsigned32, frwkDeviceIdMaxMsg Unsigned32,
frwkDeviceIdMaxContexts Unsigned32 frwkDeviceIdMaxContexts Unsigned32
} }
frwkDeviceIdPrid OBJECT-TYPE frwkDeviceIdPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
skipping to change at page 19, line 4 skipping to change at page 24, line 37
"A textual description of the PEP. This value should include "A textual description of the PEP. This value should include
the name and version identification of the PEP's hardware the name and version identification of the PEP's hardware
and software." and software."
::= { frwkDeviceIdEntry 2 } ::= { frwkDeviceIdEntry 2 }
frwkDeviceIdMaxMsg OBJECT-TYPE frwkDeviceIdMaxMsg OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "octets" UNITS "octets"
STATUS current STATUS current
Framework Policy Information Base July 2001
DESCRIPTION DESCRIPTION
"The maximum message size, in octets, that the device "The maximum message size, in octets, that the device
is capable of processing. Received messages with a is capable of processing. Received messages with a
size in excess of this value must cause the PEP to return an size in excess of this value must cause the PEP to return an
error to the PDP containing the global error code error to the PDP containing the global error code
'maxMsgSizeExceeded'. This is an additional error-avoidance 'maxMsgSizeExceeded'. This is an additional error-avoidance
mechanism to allow the administrator to have the ability to mechanism to allow the administrator to have the ability to
control the message size of messages sent to the device. The control the message size of messages sent to the device. The
device should send NULL for this attributes if it not device should send the MAX value for Unsigned32 for
defined." this attribute if it not defined."
::= { frwkDeviceIdEntry 3 } ::= { frwkDeviceIdEntry 3 }
frwkDeviceIdMaxContexts OBJECT-TYPE frwkDeviceIdMaxContexts OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "contexts" UNITS "contexts"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Framework Policy Information Base November 2001
"The maximum number of unique contexts supported by "The maximum number of unique contexts supported by
the device. This is an additional error-avoidance mechanism the device. This is an additional error-avoidance mechanism
to allow the administrators to have the ability to control to allow the administrators to have the ability to control
the number of contexts installed on the device. The device the number of contexts installed on the device. The device
should send NULL for this attribute if it is not should send NULL for this attribute if it is not
specified." specified."
::= { frwkDeviceIdEntry 4 } ::= { frwkDeviceIdEntry 4 }
-- --
skipping to change at page 20, line 4 skipping to change at page 25, line 41
or attribute and a limitation related to the implementation or attribute and a limitation related to the implementation
of the class/attribute in the device. Additional information of the class/attribute in the device. Additional information
providing guidance related to the limitation may also be providing guidance related to the limitation may also be
present. These PRIs are sent to the PDP to indicate which present. These PRIs are sent to the PDP to indicate which
PRCs or PRC attributes the device supports in a restricted PRCs or PRC attributes the device supports in a restricted
manner." manner."
::= { frwkBasePibClasses 4 } ::= { frwkBasePibClasses 4 }
frwkCompLimitsEntry OBJECT-TYPE frwkCompLimitsEntry OBJECT-TYPE
Framework Policy Information Base July 2001
SYNTAX FrwkCompLimitsEntry SYNTAX FrwkCompLimitsEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of the frwkCompLimits class that identifies "An instance of the frwkCompLimits class that identifies
a PRC or PRC attribute and a limitation related to the PRC a PRC or PRC attribute and a limitation related to the PRC
or PRC attribute implementation supported by the device. or PRC attribute implementation supported by the device.
[COPS-PR] lists the error codes that MUST be returned (if [COPS-PR] lists the error codes that MUST be returned (if
applicable)for policy installation that don't abide by the applicable)for policy installation that don't abide by the
restrictions indicated by the limitations exported. [SPPI] restrictions indicated by the limitations exported. [SPPI]
defines an INSTALL-ERRORS clause that allows PIB designers defines an INSTALL-ERRORS clause that allows PIB designers
to define PRC specific error codes that can be returned for to define PRC specific error codes that can be returned for
policy installation. This allows efficient debugging of PIB policy installation. This allows efficient debugging of PIB
implementations." implementations."
PIB-INDEX { frwkCompLimitsPrid } PIB-INDEX { frwkCompLimitsPrid }
UNIQUENESS { frwkCompLimitsComponent, UNIQUENESS { frwkCompLimitsComponent,
frwkCompLimitsAttrPos, frwkCompLimitsAttrPos,
frwkCompLimitsNegation, frwkCompLimitsNegation,
frwkCompLimitsType, frwkCompLimitsType,
Framework Policy Information Base November 2001
frwkCompLimitsSubType, frwkCompLimitsSubType,
frwkCompLimitsGuidance } frwkCompLimitsGuidance }
::= { frwkCompLimitsTable 1 } ::= { frwkCompLimitsTable 1 }
FrwkCompLimitsEntry ::= SEQUENCE { FrwkCompLimitsEntry ::= SEQUENCE {
frwkCompLimitsPrid InstanceId, frwkCompLimitsPrid InstanceId,
frwkCompLimitsComponent PrcIdentifier, frwkCompLimitsComponent PrcIdentifier,
frwkCompLimitsAttrPos Unsigned32, frwkCompLimitsAttrPos AttrIdentifier,
frwkCompLimitsNegation TruthValue, frwkCompLimitsNegation TruthValue,
frwkCompLimitsType Unsigned32, frwkCompLimitsType Unsigned32,
frwkCompLimitsSubType Unsigned32, frwkCompLimitsSubType Unsigned32,
frwkCompLimitsGuidance OCTET STRING frwkCompLimitsGuidance OCTET STRING
} }
frwkCompLimitsPrid OBJECT-TYPE frwkCompLimitsPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 21, line 4 skipping to change at page 26, line 39
::= { frwkCompLimitsEntry 1 } ::= { frwkCompLimitsEntry 1 }
frwkCompLimitsComponent OBJECT-TYPE frwkCompLimitsComponent OBJECT-TYPE
SYNTAX PrcIdentifier SYNTAX PrcIdentifier
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value is the OID of a PRC (the table entry) which is "The value is the OID of a PRC (the table entry) which is
supported in some limited fashion or contains an attribute supported in some limited fashion or contains an attribute
that is supported in some limited fashion with regard to that is supported in some limited fashion with regard to
it's definition in the associated PIB module. The same OID it's definition in the associated PIB module. The same OID
Framework Policy Information Base July 2001
may appear in the table several times, once for each may appear in the table several times, once for each
implementation limitation acknowledged by the device." implementation limitation acknowledged by the device."
::= { frwkCompLimitsEntry 2 } ::= { frwkCompLimitsEntry 2 }
frwkCompLimitsAttrPos OBJECT-TYPE frwkCompLimitsAttrPos OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX AttrIdentifier
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The relative position of the attribute within the PRC "The relative position of the attribute within the PRC
specified by the frwkCompLimitsComponent. A value of 1 would specified by the frwkCompLimitsComponent. A value of 1 would
represent the first columnar object in the PRC and a value represent the first columnar object in the PRC and a value
of N would represent the Nth columnar object in the PRC. A of N would represent the Nth columnar object in the PRC. A
NULL value indicates that the limit applies to the PRC NULL value indicates that the limit applies to the PRC
itself and not to a specific attribute." itself and not to a specific attribute."
::= { frwkCompLimitsEntry 3 } ::= { frwkCompLimitsEntry 3 }
Framework Policy Information Base November 2001
frwkCompLimitsNegation OBJECT-TYPE frwkCompLimitsNegation OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A boolean value ,if TRUE, negates the component limit "A boolean value ,if TRUE, negates the component limit
exported." exported."
::= { frwkCompLimitsEntry 4 } ::= { frwkCompLimitsEntry 4 }
frwkCompLimitsType OBJECT-TYPE frwkCompLimitsType OBJECT-TYPE
skipping to change at page 22, line 4 skipping to change at page 27, line 39
attributes in this class instance. attributes in this class instance.
Values for this object are one of the following: Values for this object are one of the following:
priSpaceLimited(1) - No more instances than that specified priSpaceLimited(1) - No more instances than that specified
by the guidance value may be installed in the given class. by the guidance value may be installed in the given class.
The component identified MUST be a valid PRC. The SubType The component identified MUST be a valid PRC. The SubType
used MUST be valueOnly(9). used MUST be valueOnly(9).
attrValueSupLimited(2) - Limited values are acceptable for attrValueSupLimited(2) - Limited values are acceptable for
Framework Policy Information Base July 2001
the identified component. The component identified MUST be a the identified component. The component identified MUST be a
valid PRC attribute. The guidance OCTET STRING will be valid PRC attribute. The guidance OCTET STRING will be
decoded according to the attribute type. decoded according to the attribute type.
attrEnumSupLimited(3) - Limited enumeration values are legal attrEnumSupLimited(3) - Limited enumeration values are legal
for the identified component. The attribute identified MUST for the identified component. The attribute identified MUST
be a valid enum type. be a valid enum type.
attrLengthLimited(4) - The length of the specified attrLengthLimited(4) - The length of the specified
value for the identified component is limited. The component value for the identified component is limited. The component
identified MUST be a valid PRC attribute of base-type OCTET identified MUST be a valid PRC attribute of base-type OCTET
STRING. STRING.
prcLimitedNotify (5) - The component is currently limited prcLimitedNotify (5) - The component is currently limited
for use by request or report messages prohibiting decision for use by request or report messages prohibiting decision
installation. The component identified must be a valid PRC." installation. The component identified must be a valid PRC."
::= { frwkCompLimitsEntry 5 } ::= { frwkCompLimitsEntry 5 }
Framework Policy Information Base November 2001
frwkCompLimitsSubType OBJECT-TYPE frwkCompLimitsSubType OBJECT-TYPE
SYNTAX Unsigned32 { SYNTAX Unsigned32 {
none(1), none(1),
lengthMin(2), lengthMin(2),
lengthMax(3), lengthMax(3),
rangeMin(4), rangeMin(4),
rangeMax(5), rangeMax(5),
enumMin(6), enumMin(6),
enumMax(7), enumMax(7),
enumOnly(8), enumOnly(8),
skipping to change at page 23, line 4 skipping to change at page 28, line 41
attribute provides data related to the minimum attribute provides data related to the minimum
acceptable length for the value of the identified acceptable length for the value of the identified
component. A corresponding class instance component. A corresponding class instance
specifying the 'lengthMax(3)' value is required specifying the 'lengthMax(3)' value is required
in conjunction with this sub-type. in conjunction with this sub-type.
A value of 'lengthMax(3)' means that the guidance A value of 'lengthMax(3)' means that the guidance
attribute provides data related to the maximum attribute provides data related to the maximum
acceptable length for the value of the identified acceptable length for the value of the identified
component. A corresponding class instance component. A corresponding class instance
Framework Policy Information Base July 2001
specifying the 'lengthMin(2)' value is required specifying the 'lengthMin(2)' value is required
in conjunction with this sub-type. in conjunction with this sub-type.
A value of 'rangeMin(4)' means that the guidance A value of 'rangeMin(4)' means that the guidance
attribute provides data related to the lower bound attribute provides data related to the lower bound
of the range for the value of the identified of the range for the value of the identified
component. A corresponding class instance component. A corresponding class instance
specifying the 'rangeMax(5)' value is required specifying the 'rangeMax(5)' value is required
in conjunction with this sub-type. in conjunction with this sub-type.
A value of 'rangeMax(5)' means that the guidance A value of 'rangeMax(5)' means that the guidance
attribute provides data related to the upper bound attribute provides data related to the upper bound
of the range for the value of the identified of the range for the value of the identified
component. A corresponding class instance component. A corresponding class instance
specifying the 'rangeMin(4)' value is required specifying the 'rangeMin(4)' value is required
in conjunction with this sub-type. in conjunction with this sub-type.
A value of 'enumMin(6)' means that the guidance A value of 'enumMin(6)' means that the guidance
attribute provides data related to the lowest attribute provides data related to the lowest
Framework Policy Information Base November 2001
enumeration acceptable for the value of the enumeration acceptable for the value of the
identified component. A corresponding identified component. A corresponding
class instance specifying the 'enumMax(7)' class instance specifying the 'enumMax(7)'
value is required in conjunction with this sub-type. value is required in conjunction with this sub-type.
A value of 'enumMax(7)' means that the guidance A value of 'enumMax(7)' means that the guidance
attribute provides data related to the largest attribute provides data related to the largest
enumeration acceptable for the value of the enumeration acceptable for the value of the
identified component. A corresponding identified component. A corresponding
class instance specifying the 'enumMin(6)' class instance specifying the 'enumMin(6)'
skipping to change at page 23, line 59 skipping to change at page 29, line 40
attribute is a bit mask such that all the combinations of attribute is a bit mask such that all the combinations of
bits set in the bitmask are acceptable values for the bits set in the bitmask are acceptable values for the
identified component which should be an attribute of type identified component which should be an attribute of type
'BITS'. 'BITS'.
For example, an implementation of the frwkIpFilter class may For example, an implementation of the frwkIpFilter class may
be limited in several ways, such as address mask, protocol be limited in several ways, such as address mask, protocol
and Layer 4 port options. These limitations could be and Layer 4 port options. These limitations could be
exported using this table with the following instances: exported using this table with the following instances:
Component Type Sub Guidance Component Type Sub-Type Guidance
Framework Policy Information Base July 2001
Type
------------------------------------------------------------ ------------------------------------------------------------
frwkIpFilterDstAddrMask attrValueSupLimited valueOnly 24 DstPrefixLength attrValueSupLimited valueOnly 24
frwkIpFilterSrcAddrMask attrValueSupLimited valueOnly 24 SrcPrefixLength attrValueSupLimited valueOnly 24
frwkIpFilterProtocol attrValueSupLimited rangeMin 10 Protocol attrValueSupLimited rangeMin 10
frwkIpFilterProtocol attrValueSupLimited rangeMax 20 Protocol attrValueSupLimited rangeMax 20
The above entries describe a number of limitations that The above entries describe a number of limitations that
may be in effect for the frwkIpFilter class on a given may be in effect for the frwkIpFilter class on a given
device. The limitations include restrictions on acceptable device. The limitations include restrictions on acceptable
values for certain attributes. values for certain attributes.
Also, an implementation of a PRC may be limited in the ways Also, an implementation of a PRC may be limited in the ways
it can be accessed. For instance, for a fictitious PRC it can be accessed. For instance, for a fictitious PRC
dscpMapEntry, which has a PIB-ACCESS of 'install-notify': dscpMapEntry, which has a PIB-ACCESS of 'install-notify':
Component Type SubType Guidance Component Type SubType Guidance
------------------------------------------------------------ ------------------------------------------------------------
dscpMapEntry prcLimitedNotify none zero-length string." dscpMapEntry prcLimitedNotify none zero-length string."
Framework Policy Information Base November 2001
::= { frwkCompLimitsEntry 6 } ::= { frwkCompLimitsEntry 6 }
frwkCompLimitsGuidance OBJECT-TYPE frwkCompLimitsGuidance OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value used to convey additional information related "A value used to convey additional information related
to the implementation limitation. Note that a guidance to the implementation limitation. Note that a guidance
value will not necessarily be provided for all exported value will not necessarily be provided for all exported
limitations. If a guidance value is not provided, the limitations. If a guidance value is not provided, the
skipping to change at page 25, line 5 skipping to change at page 30, line 40
--------- ----- --------- -----
Unsigned32/Integer32 32-bit value. Unsigned32/Integer32 32-bit value.
Unsigned64/Integer64 64-bit Value. Unsigned64/Integer64 64-bit Value.
OCTET STRING octets of data. OCTET STRING octets of data.
OID 32-bit OID components. OID 32-bit OID components.
BITS Binary octets of length same as BITS Binary octets of length same as
Component specified." Component specified."
::= { frwkCompLimitsEntry 7 } ::= { frwkCompLimitsEntry 7 }
Framework Policy Information Base July 2001 --
-- Complete Reference specification table
--
frwkReferenceTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkReferenceEntry
PIB-ACCESS install-notify
STATUS current
DESCRIPTION
"Each instance of this class specifies a reference to a PRI
in a specific PIB context (handle) for a specific client-
type."
::= { frwkBasePibClasses 5 }
Framework Policy Information Base November 2001
frwkReferenceEntry OBJECT-TYPE
SYNTAX FrwkReferenceEntry
STATUS current
DESCRIPTION
"Entry specification for the frwkReferenceTable."
PIB-INDEX { frwkReferencePrid }
UNIQUENESS { }
::= { frwkReferenceTable 1 }
FrwkReferenceEntry ::= SEQUENCE {
frwkReferencePrid InstanceId,
frwkReferenceClientType ClientType,
frwkReferenceClientHandle ClientHandle,
frwkReferenceInstance Prid
}
frwkReferencePrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the frwkReference class."
::= { frwkReferenceEntry 1 }
frwkReferenceClientType OBJECT-TYPE
SYNTAX ClientType
STATUS current
DESCRIPTION
"Is unused if set to zero else specifies a client-type for
which the reference is to be interpreted. This non-zero
client-type must be activated explicitly via a separate
COPS client-open else this attribute is not valid."
::= { frwkReferenceEntry 2 }
frwkReferenceClientHandle OBJECT-TYPE
SYNTAX ClientHandle
STATUS current
DESCRIPTION
"Must be set to specify a valid client-handle in the scope
of the client-type specified."
::= { frwkReferenceEntry 3 }
Framework Policy Information Base November 2001
frwkReferenceInstance OBJECT-TYPE
SYNTAX Prid
STATUS current
DESCRIPTION
"References a PRI in the context identified by
frwkReferenceClientHandle for client-type identified by
frwkReferenceClientType."
::= { frwkReferenceEntry 4 }
--
-- Error specification table
--
frwkErrorTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkErrorEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"Each instance of this class specifies a class specific
error object. Instances of this table are transient."
::= { frwkBasePibClasses 6 }
frwkErrorEntry OBJECT-TYPE
SYNTAX FrwkErrorEntry
STATUS current
DESCRIPTION
"Entry specification for the frwkErrorTable."
PIB-INDEX { frwkErrorPrid }
UNIQUENESS { }
::= { frwkErrorTable 1 }
FrwkErrorEntry ::= SEQUENCE {
frwkErrorPrid InstanceId,
frwkErrorCode Unsigned32,
frwkErrorSubCode Unsigned32,
frwkErrorPrc PrcIdentifier,
frwkErrorInstance InstanceId
}
frwkErrorPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the frwkError class."
::= { frwkErrorEntry 1 }
Framework Policy Information Base November 2001
frwkErrorCode OBJECT-TYPE
SYNTAX Unsigned32 (0..65535)
STATUS current
DESCRIPTION
"Error code defined in [COPS-PR] CPERR object."
::= { frwkErrorEntry 2 }
frwkErrorSubCode OBJECT-TYPE
SYNTAX Unsigned32 (0..65535)
STATUS current
DESCRIPTION
"The class-specific error object is used to communicate
errors relating to specific PRCs."
::= { frwkErrorEntry 3 }
frwkErrorPrc OBJECT-TYPE
SYNTAX PrcIdentifier
STATUS current
DESCRIPTION
"The PRC due to which the error specified by codes
(frwkErrorCode , frwkErrorSubCode) occurred."
::= { frwkErrorEntry 4 }
frwkErrorInstance OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"The PRI of the identified PRC (frwkErrorPrc) due to which
the error specified by codes (frwkErrorCode ,
frwkErrorSubCode) occurred. Must be set to zero if unused."
::= { frwkErrorEntry 5 }
-- --
-- The device interface capabilities and role combo classes group -- The device interface capabilities and role combo classes group
-- --
frwkDeviceCapClasses frwkDeviceCapClasses
OBJECT IDENTIFIER ::= { frameworkPib 2 } OBJECT IDENTIFIER ::= { frameworkPib 2 }
Framework Policy Information Base November 2001
-- --
-- Interface Capability Set Table -- Interface Capability Set Table
-- --
frwkIfCapSetTable OBJECT-TYPE frwkIfCapSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkIfCapSetEntry SYNTAX SEQUENCE OF FrwkIfCapSetEntry
PIB-ACCESS install-notify PIB-ACCESS notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class describes the interfaces that exist on the "This class describes the interfaces that exist on the
device. Associated with each interface is a set of device. Associated with each interface is a set of
capabilities. The capability set is given a unique name that capabilities. The capability set is given a unique name that
identifies the interface type. These capabilities are used identifies the interface type. These capabilities are used
by the PDP to determine policy information to be associated by the PDP to determine policy information to be associated
with interfaces of this type." with interfaces of this type."
::= { frwkDeviceCapClasses 1 } ::= { frwkDeviceCapClasses 1 }
skipping to change at page 26, line 5 skipping to change at page 34, line 51
frwkIfCapSetCapability Prid frwkIfCapSetCapability Prid
} }
frwkIfCapSetPrid OBJECT-TYPE frwkIfCapSetPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies a "An arbitrary integer index that uniquely identifies a
instance of the class." instance of the class."
Framework Policy Information Base July 2001
::= { frwkIfCapSetEntry 1 } ::= { frwkIfCapSetEntry 1 }
frwkIfCapSetName OBJECT-TYPE frwkIfCapSetName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Framework Policy Information Base November 2001
"The name for the capability set. The capability set name "The name for the capability set. The capability set name
is the unique identifier of an interface type." is the unique identifier of an interface type."
::= { frwkIfCapSetEntry 2 } ::= { frwkIfCapSetEntry 2 }
frwkIfCapSetCapability OBJECT-TYPE frwkIfCapSetCapability OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The complete PRC OID and instance identifier specifying the "The complete PRC OID and instance identifier specifying the
capability PRC instance for the interface." capability PRC instance for the interface."
::= { frwkIfCapSetEntry 3 } ::= { frwkIfCapSetEntry 3 }
-- --
-- Interface Capabilities Set Name and Role Combination Table -- Interface and Role Combination Table
-- --
frwkIfCapSetRoleComboTable OBJECT-TYPE frwkIfRoleComboTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkIfCapSetRoleComboEntry SYNTAX SEQUENCE OF FrwkIfRoleComboEntry
PIB-ACCESS install-notify PIB-ACCESS install-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Policy for an interface depends not only on the "This table enumerates the interface to role combination and
IfCapSetName mapping for all policy managed interfaces of a
device. Policy for an interface depends not only on the
capability set of an interface but also on its roles. This capability set of an interface but also on its roles. This
table specifies all the <interface capability set name, role table specifies all the <interface index, interface
combination> tuples currently on the device." capability set name, role combination> tuples currently on
the device"
::= { frwkDeviceCapClasses 2 } ::= { frwkDeviceCapClasses 2 }
frwkIfCapSetRoleComboEntry OBJECT-TYPE frwkIfRoleComboEntry OBJECT-TYPE
SYNTAX FrwkIfCapSetRoleComboEntry SYNTAX FrwkIfRoleComboEntry
STATUS current
DESCRIPTION
"An instance of this class describes a combination of an
interface capability set name and a role combination."
PIB-INDEX { frwkIfCapSetRoleComboPrid }
UNIQUENESS { frwkIfCapSetRoleComboName,
frwkIfCapSetRoleComboRoles }
::= { frwkIfCapSetRoleComboTable 1 }
Framework Policy Information Base July 2001
FrwkIfCapSetRoleComboEntry ::= SEQUENCE {
frwkIfCapSetRoleComboPrid InstanceId,
frwkIfCapSetRoleComboName SnmpAdminString,
frwkIfCapSetRoleComboRoles RoleCombination
}
frwkIfCapSetRoleComboPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { frwkIfCapSetRoleComboEntry 1 }
frwkIfCapSetRoleComboName OBJECT-TYPE
SYNTAX SnmpAdminString
STATUS current
DESCRIPTION
"The name of the interface capability set. This name must
exist in frwkIfCapSetTable."
::= { frwkIfCapSetRoleComboEntry 2 }
frwkIfCapSetRoleComboRoles OBJECT-TYPE
SYNTAX RoleCombination
STATUS current
DESCRIPTION
"A role combination. The PEP requires policy for interfaces
with this role combination and of capability set name
specified by frwkIfCapSetRoleComboName."
::= { frwkIfCapSetRoleComboEntry 3 }
--
-- Interface and Role Combination Table
--
frwkIfCapSetInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkIfCapSetInterfaceEntry
PIB-ACCESS install-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of this class describes the association of
a interface to an IfCapSetName and a role combination.
Note that a IfCapSetName can have multiple role combinations
assigned to it, but an IfIndex can have only one role
combination associated."
Framework Policy Information Base July 2001 PIB-INDEX { frwkIfRoleComboPrid }
UNIQUENESS { frwkIfRoleComboIfIndex }
"This table enumerates the interface to role combination
mapping for all policy managed interfaces of a device."
::= { frwkDeviceCapClasses 3 }
frwkIfCapSetInterfaceEntry OBJECT-TYPE
SYNTAX FrwkIfCapSetInterfaceEntry
STATUS current
DESCRIPTION
"An instance of this class describes an association of an
interface and a role combination."
PIB-INDEX { frwkIfCapSetInterfacePrid } ::= { frwkIfRoleComboTable 1 }
UNIQUENESS { frwkIfCapSetInterfaceIfIndex,
frwkIfCapSetInterfaceRoles }
::= { frwkIfCapSetInterfaceTable 1 } Framework Policy Information Base November 2001
FrwkIfCapSetInterfaceEntry ::= SEQUENCE { FrwkIfRoleComboEntry ::= SEQUENCE {
frwkIfCapSetInterfacePrid InstanceId, frwkIfRoleComboPrid InstanceId,
frwkIfCapSetInterfaceIfIndex InterfaceIndex, frwkIfRoleComboIfIndex InterfaceIndex,
frwkIfCapSetInterfaceRoles RoleCombination frwkIfRoleComboRoles RoleCombination,
frwkIfRoleComboCapSetName SnmpAdminString
} }
frwkIfCapSetInterfacePrid OBJECT-TYPE frwkIfRoleComboPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer index that uniquely identifies an "An arbitrary integer index that uniquely identifies an
instance of the class." instance of the class."
::= { frwkIfCapSetInterfaceEntry 1 } ::= { frwkIfRoleComboEntry 1 }
frwkIfCapSetInterfaceIfIndex OBJECT-TYPE frwkIfRoleComboIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value for which this conceptual row provides "The ifIndex value for which this conceptual row provides
policy information via the use of role combination." policy information via the use of role combination."
::= { frwkIfCapSetInterfaceEntry 2 } ::= { frwkIfRoleComboEntry 2 }
frwkIfCapSetInterfaceRoles OBJECT-TYPE frwkIfRoleComboRoles OBJECT-TYPE
SYNTAX RoleCombination SYNTAX RoleCombination
STATUS current STATUS current
DESCRIPTION
"The role combination of a specific interface. "
Framework Policy Information Base July 2001 ::= { frwkIfRoleComboEntry 3 }
frwkIfRoleComboCapSetName OBJECT-TYPE
SYNTAX SnmpAdminString
STATUS current
DESCRIPTION DESCRIPTION
"The role combination of a specific interface. This "The name of the interface capability set associated with
role combination must exist in frwkIfCapSetRoleComboTable." the Role Combination specified in frwkIfRoleComboRoles.
This name must exist in frwkIfCapSetTable."
::= { frwkIfCapSetInterfaceEntry 3 } ::= { frwkIfRoleComboEntry 4 }
Framework Policy Information Base November 2001
-- --
-- The Classification classes group -- The Classification classes group
-- --
frwkClassifierClasses frwkClassifierClasses
OBJECT IDENTIFIER ::= { frameworkPib 3 } OBJECT IDENTIFIER ::= { frameworkPib 3 }
-- --
-- The Base Filter Table -- The Base Filter Table
-- --
skipping to change at page 30, line 5 skipping to change at page 37, line 50
frwkBaseFilterNegation TruthValue frwkBaseFilterNegation TruthValue
} }
frwkBaseFilterPrid OBJECT-TYPE frwkBaseFilterPrid OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An integer index to uniquely identify this Filter among all "An integer index to uniquely identify this Filter among all
the Filters." the Filters."
Framework Policy Information Base July 2001
::= { frwkBaseFilterEntry 1 } ::= { frwkBaseFilterEntry 1 }
frwkBaseFilterNegation OBJECT-TYPE frwkBaseFilterNegation OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute behaves like a logical NOT for the filter. "This attribute behaves like a logical NOT for the filter.
Framework Policy Information Base November 2001
If the packet matches this filter and the value of this If the packet matches this filter and the value of this
attribute is true, the action associated with this filter attribute is true, the action associated with this filter
is not applied to the packet. If the value of this is not applied to the packet. If the value of this
attribute is false, then the action is applied to the attribute is false, then the action is applied to the
packet." packet."
::= { frwkBaseFilterEntry 2 } ::= { frwkBaseFilterEntry 2 }
-- --
-- The IP Filter Table -- The IP Filter Table
skipping to change at page 30, line 49 skipping to change at page 38, line 42
::= { frwkClassifierClasses 2 } ::= { frwkClassifierClasses 2 }
frwkIpFilterEntry OBJECT-TYPE frwkIpFilterEntry OBJECT-TYPE
SYNTAX FrwkIpFilterEntry SYNTAX FrwkIpFilterEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of the frwkIpFilter class." "An instance of the frwkIpFilter class."
EXTENDS { frwkBaseFilterEntry } EXTENDS { frwkBaseFilterEntry }
UNIQUENESS { frwkBaseFilterNegation, UNIQUENESS { frwkBaseFilterNegation,
frwkIpFilterDstAddrType, frwkIpFilterAddrType,
frwkIpFilterDstAddr, frwkIpFilterDstAddr,
frwkIpFilterDstAddrMask, frwkIpFilterDstPrefixLength,
frwkIpFilterSrcAddrType,
frwkIpFilterSrcAddr, frwkIpFilterSrcAddr,
frwkIpFilterSrcAddrMask, frwkIpFilterSrcPrefixLength,
frwkIpFilterDscp, frwkIpFilterDscp,
frwkIpFilterFlowId,
frwkIpFilterProtocol, frwkIpFilterProtocol,
frwkIpFilterDstL4PortMin, frwkIpFilterDstL4PortMin,
Framework Policy Information Base July 2001
frwkIpFilterDstL4PortMax, frwkIpFilterDstL4PortMax,
frwkIpFilterSrcL4PortMin, frwkIpFilterSrcL4PortMin,
frwkIpFilterSrcL4PortMax } frwkIpFilterSrcL4PortMax }
::= { frwkIpFilterTable 1 } ::= { frwkIpFilterTable 1 }
Framework Policy Information Base November 2001
FrwkIpFilterEntry ::= SEQUENCE { FrwkIpFilterEntry ::= SEQUENCE {
frwkIpFilterDstAddrType InetAddressType, frwkIpFilterAddrType InetAddressType,
frwkIpFilterDstAddr InetAddress, frwkIpFilterDstAddr InetAddress,
frwkIpFilterDstAddrMask Unsigned32, frwkIpFilterDstPrefixLength InetAddressPrefixLength,
frwkIpFilterSrcAddrType InetAddressType,
frwkIpFilterSrcAddr InetAddress, frwkIpFilterSrcAddr InetAddress,
frwkIpFilterSrcAddrMask Unsigned32, frwkIpFilterSrcPrefixLength InetAddressPrefixLength,
frwkIpFilterDscp Integer32, frwkIpFilterDscp DscpOrAny,
frwkIpFilterFlowId Unsigned32,
frwkIpFilterProtocol Integer32, frwkIpFilterProtocol Integer32,
frwkIpFilterDstL4PortMin Unsigned32, frwkIpFilterDstL4PortMin InetPortNumber,
frwkIpFilterDstL4PortMax Unsigned32, frwkIpFilterDstL4PortMax InetPortNumber,
frwkIpFilterSrcL4PortMin Unsigned32, frwkIpFilterSrcL4PortMin InetPortNumber,
frwkIpFilterSrcL4PortMax Unsigned32 frwkIpFilterSrcL4PortMax InetPortNumber
} }
frwkIpFilterDstAddrType OBJECT-TYPE frwkIpFilterAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type enumeration value [INETADDR] to specify "The address type enumeration value [INETADDR] to specify
the type of the packet's destination IP address." the type of the packet's IP address."
::= { frwkIpFilterEntry 1 } ::= { frwkIpFilterEntry 1 }
frwkIpFilterDstAddr OBJECT-TYPE frwkIpFilterDstAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address [INETADDR] to match against the packet's "The IP address [INETADDR] to match against the packet's
destination IP address." destination IP address. frwkIpFilterDstPrefixLength
indicates the number of bits that are relevant. "
::= { frwkIpFilterEntry 2 } ::= { frwkIpFilterEntry 2 }
frwkIpFilterDstAddrMask OBJECT-TYPE frwkIpFilterDstPrefixLength OBJECT-TYPE
SYNTAX Unsigned32 (0..128) SYNTAX InetAddressPrefixLength
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of a mask for the matching of the destination "The length of a mask for the matching of the destination
IP address. Masks are constructed by setting bits in IP address. Masks are constructed by setting bits in
sequence from the most-significant bit downwards for sequence from the most-significant bit downwards for
frwkIpFilterDstAddrMask bits length. All other bits in the frwkIpFilterDstPrefixLength bits length. All other bits in
mask, up to the number needed to fill the length of the the mask, up to the number needed to fill the length of
address frwkIpFilterDstAddr are cleared to zero. A zero bit the address frwkIpFilterDstAddr are cleared to zero. A zero
in the mask then means that the corresponding bit in the bit in the mask then means that the corresponding bit in
the address always matches."
Framework Policy Information Base July 2001
address always matches."
::= { frwkIpFilterEntry 3 } ::= { frwkIpFilterEntry 3 }
frwkIpFilterSrcAddrType OBJECT-TYPE Framework Policy Information Base November 2001
SYNTAX InetAddressType
STATUS current
DESCRIPTION
"The address type enumeration value to specify the type of
the packet's source IP address."
::= { frwkIpFilterEntry 4 }
frwkIpFilterSrcAddr OBJECT-TYPE frwkIpFilterSrcAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address to match against the packet's source IP "The IP address to match against the packet's source IP
address." address. frwkIpFilterSrcPrefixLength indicates the
number of bits that are relevant. "
::= { frwkIpFilterEntry 5 } ::= { frwkIpFilterEntry 4 }
frwkIpFilterSrcAddrMask OBJECT-TYPE frwkIpFilterSrcPrefixLength OBJECT-TYPE
SYNTAX Unsigned32 (0..128) SYNTAX InetAddressPrefixLength
UNITS "bits"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of a mask for the matching of the source IP "The length of a mask for the matching of the source IP
address. Masks are constructed by setting bits in sequence address. Masks are constructed by setting bits in sequence
from the most-significant bit downwards for from the most-significant bit downwards for
frwkIpFilterSrcAddrMask bits length. All other bits in the frwkIpFilterSrcPrefixLength bits length. All other bits in
mask, up to the number needed to fill the length of the the mask, up to the number needed to fill the length of
address frwkIpFilterSrcAddr are cleared to zero. A zero bit the address frwkIpFilterSrcAddr are cleared to zero. A
in the mask then means that the corresponding bit in the zero bit in the mask then means that the corresponding bit
address always matches." in the address always matches."
::= { frwkIpFilterEntry 6 } ::= { frwkIpFilterEntry 5 }
frwkIpFilterDscp OBJECT-TYPE frwkIpFilterDscp OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..63) SYNTAX DscpOrAny
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value that the DSCP in the packet can have and "The value that the DSCP in the packet can have and
match this filter. A value of -1 indicates that a specific match this filter. A value of -1 indicates that a specific
DSCP value has not been defined and thus all DSCP values DSCP value has not been defined and thus all DSCP values
are considered a match." are considered a match."
::= { frwkIpFilterEntry 6 }
frwkIpFilterFlowId OBJECT-TYPE
SYNTAX Unsigned32 (0..1048575)
STATUS current
DESCRIPTION
"The flow identifier in an IPv6 header."
::= { frwkIpFilterEntry 7 } ::= { frwkIpFilterEntry 7 }
frwkIpFilterProtocol OBJECT-TYPE frwkIpFilterProtocol OBJECT-TYPE
Framework Policy Information Base July 2001
SYNTAX Integer32 (-1 | 0..255) SYNTAX Integer32 (-1 | 0..255)
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP protocol to match against the packet's protocol. "The IP protocol to match against the packet's protocol.
A value of -1 means match all." A value of -1 means match all."
::= { frwkIpFilterEntry 8 } ::= { frwkIpFilterEntry 8 }
Framework Policy Information Base November 2001
frwkIpFilterDstL4PortMin OBJECT-TYPE frwkIpFilterDstL4PortMin OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX InetPortNumber
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum value that the packet's layer 4 destination "The minimum value that the packet's layer 4 destination
port number can have and match this filter. This value must port number can have and match this filter. This value must
be equal to or lesser that the value specified for this be equal to or lesser that the value specified for this
filter in frwkIpFilterDstL4PortMax." filter in frwkIpFilterDstL4PortMax."
::= { frwkIpFilterEntry 9 } ::= { frwkIpFilterEntry 9 }
frwkIpFilterDstL4PortMax OBJECT-TYPE frwkIpFilterDstL4PortMax OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX InetPortNumber
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum value that the packet's layer 4 destination "The maximum value that the packet's layer 4 destination
port number can have and match this filter. This value must port number can have and match this filter. This value must
be equal to or greater that the value specified for this be equal to or greater that the value specified for this
filter in frwkIpFilterDstL4PortMin." filter in frwkIpFilterDstL4PortMin."
::= { frwkIpFilterEntry 10 } ::= { frwkIpFilterEntry 10 }
frwkIpFilterSrcL4PortMin OBJECT-TYPE frwkIpFilterSrcL4PortMin OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX InetPortNumber
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum value that the packet's layer 4 source port "The minimum value that the packet's layer 4 source port
number can have and match this filter. This value must number can have and match this filter. This value must
be equal to or lesser that the value specified for this be equal to or lesser that the value specified for this
filter in frwkIpFilterSrcL4PortMax." filter in frwkIpFilterSrcL4PortMax."
::= { frwkIpFilterEntry 11 } ::= { frwkIpFilterEntry 11 }
frwkIpFilterSrcL4PortMax OBJECT-TYPE frwkIpFilterSrcL4PortMax OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX InetPortNumber
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum value that the packet's layer 4 source port "The maximum value that the packet's layer 4 source port
number can have and match this filter. This value must be number can have and match this filter. This value must be
equal to or greater that the value specified for this filter equal to or greater that the value specified for this filter
in frwkIpFilterSrcL4PortMin." in frwkIpFilterSrcL4PortMin."
Framework Policy Information Base July 2001
::= { frwkIpFilterEntry 12 } ::= { frwkIpFilterEntry 12 }
Framework Policy Information Base November 2001
-- --
-- The IEEE 802 Filter Table -- The IEEE 802 Filter Table
-- --
-- The IEEE 802 Filter Table supports the specification of IEEE -- The IEEE 802 Filter Table supports the specification of IEEE
-- 802-based [802] (e.g., 802.3) information that is used to perform -- 802-based [802] (e.g., 802.3) information that is used to perform
-- traffic classification. -- traffic classification.
-- --
frwk802FilterTable OBJECT-TYPE frwk802FilterTable OBJECT-TYPE
skipping to change at page 35, line 5 skipping to change at page 43, line 5
frwk802FilterDstAddrMask, frwk802FilterDstAddrMask,
frwk802FilterSrcAddr, frwk802FilterSrcAddr,
frwk802FilterSrcAddrMask, frwk802FilterSrcAddrMask,
frwk802FilterVlanId, frwk802FilterVlanId,
frwk802FilterVlanTagRequired, frwk802FilterVlanTagRequired,
frwk802FilterEtherType, frwk802FilterEtherType,
frwk802FilterUserPriority } frwk802FilterUserPriority }
::= { frwk802FilterTable 1 } ::= { frwk802FilterTable 1 }
Framework Policy Information Base July 2001 Framework Policy Information Base November 2001
Frwk802FilterEntry ::= SEQUENCE { Frwk802FilterEntry ::= SEQUENCE {
frwk802FilterDstAddr PhysAddress, frwk802FilterDstAddr PhysAddress,
frwk802FilterDstAddrMask PhysAddress, frwk802FilterDstAddrMask PhysAddress,
frwk802FilterSrcAddr PhysAddress, frwk802FilterSrcAddr PhysAddress,
frwk802FilterSrcAddrMask PhysAddress, frwk802FilterSrcAddrMask PhysAddress,
frwk802FilterVlanId Integer32, frwk802FilterVlanId Integer32,
frwk802FilterVlanTagRequired Unsigned32, frwk802FilterVlanTagRequired Unsigned32,
frwk802FilterEtherType Integer32, frwk802FilterEtherType Integer32,
frwk802FilterUserPriority BITS frwk802FilterUserPriority BITS
skipping to change at page 36, line 5 skipping to change at page 44, line 5
frwk802FilterDstAddr value must also be masked using this frwk802FilterDstAddr value must also be masked using this
value prior to any comparisons. value prior to any comparisons.
The length of this object in octets must equal the length in The length of this object in octets must equal the length in
octets of the frwk802FilterDstAddr. Note that a mask with no octets of the frwk802FilterDstAddr. Note that a mask with no
bits set (i.e., all zeroes) effectively wildcards the bits set (i.e., all zeroes) effectively wildcards the
frwk802FilterDstAddr object." frwk802FilterDstAddr object."
::= { frwk802FilterEntry 2 } ::= { frwk802FilterEntry 2 }
Framework Policy Information Base July 2001 Framework Policy Information Base November 2001
frwk802FilterSrcAddr OBJECT-TYPE frwk802FilterSrcAddr OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The 802 MAC address against which the 802 MAC SA of "The 802 MAC address against which the 802 MAC SA of
incoming traffic streams will be compared. Frames whose 802 incoming traffic streams will be compared. Frames whose 802
MAC SA matches the physical address specified by this MAC SA matches the physical address specified by this
object, taking into account address wildcarding as specified object, taking into account address wildcarding as specified
by the frwk802FilterSrcAddrMask object, are potentially by the frwk802FilterSrcAddrMask object, are potentially
skipping to change at page 37, line 4 skipping to change at page 44, line 57
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VLAN ID (VID) that uniquely identifies a VLAN "The VLAN ID (VID) that uniquely identifies a VLAN
within the device. This VLAN may be known or unknown within the device. This VLAN may be known or unknown
(i.e., traffic associated with this VID has not yet (i.e., traffic associated with this VID has not yet
been seen by the device) at the time this entry been seen by the device) at the time this entry
is instantiated. is instantiated.
Setting the frwk802FilterVlanId object to -1 indicates that Setting the frwk802FilterVlanId object to -1 indicates that
VLAN data should not be considered during traffic VLAN data should not be considered during traffic
Framework Policy Information Base July 2001
classification." classification."
::= { frwk802FilterEntry 5 } ::= { frwk802FilterEntry 5 }
Framework Policy Information Base November 2001
frwk802FilterVlanTagRequired OBJECT-TYPE frwk802FilterVlanTagRequired OBJECT-TYPE
SYNTAX Unsigned32 { SYNTAX Unsigned32 {
taggedOnly(1), taggedOnly(1),
priorityTaggedPlus(2), priorityTaggedPlus(2),
untaggedOnly(3), untaggedOnly(3),
ignoreTag(4) ignoreTag(4)
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the presence of an "This object indicates whether the presence of an
skipping to change at page 38, line 4 skipping to change at page 45, line 54
IEEE 802 frame. Example settings would include 'IP' IEEE 802 frame. Example settings would include 'IP'
(0x0800), 'ARP' (0x0806) and 'IPX' (0x8137). (0x0800), 'ARP' (0x0806) and 'IPX' (0x8137).
Setting the frwk802FilterEtherTypeMin object to -1 indicates Setting the frwk802FilterEtherTypeMin object to -1 indicates
that EtherType data should not be considered during traffic that EtherType data should not be considered during traffic
classification. classification.
Note that the position of the EtherType field depends on Note that the position of the EtherType field depends on
the underlying frame format. For Ethernet-II encapsulation, the underlying frame format. For Ethernet-II encapsulation,
the EtherType field follows the 802 MAC source address. For the EtherType field follows the 802 MAC source address. For
Framework Policy Information Base July 2001
802.2 LLC/SNAP encapsulation, the EtherType value follows 802.2 LLC/SNAP encapsulation, the EtherType value follows
the Organization Code field in the 802.2 SNAP header. The the Organization Code field in the 802.2 SNAP header. The
value that is tested with regard to this filter component value that is tested with regard to this filter component
therefore depends on the data link layer frame format being therefore depends on the data link layer frame format being
Framework Policy Information Base November 2001
used. If this 802 filter component is active when there is used. If this 802 filter component is active when there is
no EtherType field in a frame (e.g., 802.2 LLC), a match is no EtherType field in a frame (e.g., 802.2 LLC), a match is
implied." implied."
::= { frwk802FilterEntry 7 } ::= { frwk802FilterEntry 7 }
frwk802FilterUserPriority OBJECT-TYPE frwk802FilterUserPriority OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
matchPriority0(0), matchPriority0(0),
matchPriority1(1), matchPriority1(1),
skipping to change at page 39, line 5 skipping to change at page 46, line 44
component. component.
Setting all of the bits that are associated with this Setting all of the bits that are associated with this
object causes all user priority values to match this object causes all user priority values to match this
attribute. This essentially makes any comparisons attribute. This essentially makes any comparisons
with regard to user priority values unnecessary. Untagged with regard to user priority values unnecessary. Untagged
frames are treated as an implicit match." frames are treated as an implicit match."
::= { frwk802FilterEntry 8 } ::= { frwk802FilterEntry 8 }
Framework Policy Information Base July 2001 --
-- The Internal label filter extension
--
frwkILabelFilterTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkILabelFilterEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"Internal label filter Table. This PRC is used to achieve
classification based on the internal flow label set by the
PEP possibly after ingress classification to avoid
re-classification at the egress interface on the same PEP."
::= { frwkClassifierClasses 4 }
Framework Policy Information Base November 2001
frwkILabelFilterEntry OBJECT-TYPE
SYNTAX FrwkILabelFilterEntry
STATUS current
DESCRIPTION
"Internal label filter entry definition."
EXTENDS { frwkBaseFilterEntry }
UNIQUENESS { frwkBaseFilterNegation,
frwkILabelFilterILabel }
::= { frwkILabelFilterTable 1 }
FrwkILabelFilterEntry ::= SEQUENCE {
frwkILabelFilterILabel OCTET STRING
}
frwkILabelFilterILabel OBJECT-TYPE
SYNTAX OCTET STRING
STATUS current
DESCRIPTION
"The Label that this flow uses for differentiating traffic
flows. The flow labeling is meant for network device
internal usage. A value of zero length string matches all
internal labels."
::= { frwkILabelFilterEntry 1 }
--
-- The Marker classes group
--
frwkMarkerClasses
OBJECT IDENTIFIER ::= { frameworkPib 4 }
--
-- The 802 Marker Table
--
frwk802MarkerTable OBJECT-TYPE
SYNTAX SEQUENCE OF Frwk802MarkerEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The 802 Marker class. An 802 packet can be marked with the
specified VLAN id, priority level."
::= { frwkMarkerClasses 1 }
Framework Policy Information Base November 2001
frwk802MarkerEntry OBJECT-TYPE
SYNTAX Frwk802MarkerEntry
STATUS current
DESCRIPTION
"frwk802Marker entry definition."
PIB-INDEX { frwk802MarkerPrid }
UNIQUENESS { frwk802MarkerVlanId,
frwk802MarkerPriority }
::= { frwk802MarkerTable 1 }
Frwk802MarkerEntry::= SEQUENCE {
frwk802MarkerPrid InstanceId,
frwk802MarkerVlanId Unsigned32,
frwk802MarkerPriority Unsigned32
}
frwk802MarkerPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An integer index to uniquely identify this 802 Marker."
::= { frwk802MarkerEntry 1 }
frwk802MarkerVlanId OBJECT-TYPE
SYNTAX Unsigned32 (1..4094)
STATUS current
DESCRIPTION
"The VLAN ID (VID) that uniquely identifies a VLAN within
the device."
::= { frwk802MarkerEntry 2 }
frwk802MarkerPriority OBJECT-TYPE
SYNTAX Unsigned32 (0..7)
STATUS current
DESCRIPTION
"The user priority field of a tagged 802.1 frame."
::= { frwk802MarkerEntry 3 }
Framework Policy Information Base November 2001
--
-- The Internal Label Marker Table
--
frwkILabelMarkerTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkILabelMarkerEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The Internal Label Marker class. A flow in a PEP can be
marked with an internal label using this PRC."
::= { frwkMarkerClasses 2 }
frwkILabelMarkerEntry OBJECT-TYPE
SYNTAX FrwkILabelMarkerEntry
STATUS current
DESCRIPTION
"frwkILabelkMarker entry definition."
PIB-INDEX { frwkILabelMarkerPrid }
UNIQUENESS { frwkILabelMarkerILabel }
::= { frwkILabelMarkerEntry 1 }
FrwkILabelMarkerEntry::= SEQUENCE {
frwkILabelMarkerPrid InstanceId,
frwkILabelMarkerILabel OCTET STRING
}
frwkILabelMarkerPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An integer index to uniquely identify this Label Marker."
::= { frwkILabelMarkerEntry 1 }
frwkILabelMarkerILabel OBJECT-TYPE
SYNTAX OCTET STRING
STATUS current
DESCRIPTION
"This internal label is implementation specific and may be
used for other policy related functions like flow
accounting purposes and/or other data path treatments."
::= { frwkILabelMarkerEntry 2 }
Framework Policy Information Base November 2001
-- --
-- Conformance Section -- Conformance Section
-- --
frwkBasePibConformance frwkBasePibConformance
OBJECT IDENTIFIER ::= { frameworkPib 4 } OBJECT IDENTIFIER ::= { frameworkPib 4 }
frwkBasePibCompliances frwkBasePibCompliances
OBJECT IDENTIFIER ::= { frwkBasePibConformance 1 } OBJECT IDENTIFIER ::= { frwkBasePibConformance 1 }
skipping to change at page 39, line 32 skipping to change at page 50, line 32
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the "Describes the requirements for conformance to the
Framework PIB." Framework PIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { frwkPrcSupportGroup, MANDATORY-GROUPS { frwkPrcSupportGroup,
frwkPibIncarnationGroup, frwkPibIncarnationGroup,
frwkDeviceIdGroup, frwkDeviceIdGroup,
frwkCompLimitsGroup, frwkCompLimitsGroup,
frwkIfCapSetGroup, frwkIfCapSetGroup,
frwkIfCapSetRoleComboGroup,
frwkIfCapSetInterfaceGroup } frwkIfRoleComboGroup }
OBJECT frwkPibIncarnationLongevity OBJECT frwkPibIncarnationLongevity
PIB-MIN-ACCESS notify PIB-MIN-ACCESS notify
DESCRIPTION "Install support is not required." DESCRIPTION "Install support is not required."
OBJECT frwkPibIncarnationTtl OBJECT frwkPibIncarnationTtl
PIB-MIN-ACCESS notify PIB-MIN-ACCESS notify
DESCRIPTION "Install support is not required." DESCRIPTION "Install support is not required."
OBJECT frwkPibIncarnationActive OBJECT frwkPibIncarnationInCtxtSet
PIB-MIN-ACCESS notify PIB-MIN-ACCESS notify
DESCRIPTION "Install support is not required." DESCRIPTION "Install support is not required."
OBJECT frwkPibIncarnationFullState
PIB-MIN-ACCESS notify
DESCRIPTION "Install support is not required."
GROUP frwkReferenceGroup
DESCRIPTION
"The frwkReferenceGroup is mandatory if referencing
across PIB contexts for specific client-types is
supported."
GROUP frwkErrorGroup
Framework Policy Information Base November 2001
DESCRIPTION
"The frwkErrorGroup is mandatory sending errors in
decisions is required."
GROUP frwkBaseFilterGroup GROUP frwkBaseFilterGroup
DESCRIPTION DESCRIPTION
"The frwkBaseFilterGroup is mandatory if filtering "The frwkBaseFilterGroup is mandatory if filtering
based on traffic components is supported." based on traffic components is supported."
GROUP frwkIpFilterGroup GROUP frwkIpFilterGroup
DESCRIPTION DESCRIPTION
"The frwkIpFilterGroup is mandatory if filtering "The frwkIpFilterGroup is mandatory if filtering
based on IP traffic components is supported." based on IP traffic components is supported."
GROUP frwk802FilterGroup GROUP frwk802FilterGroup
DESCRIPTION DESCRIPTION
Framework Policy Information Base July 2001
"The frwk802FilterGroup is mandatory if filtering "The frwk802FilterGroup is mandatory if filtering
based on 802 traffic criteria is supported." based on 802 traffic criteria is supported."
GROUP frwkILabelFilterGroup
DESCRIPTION
"The frwkILabelFilterGroup is mandatory if filtering
based on PEP internal label is supported."
GROUP frwk802MarkerGroup
DESCRIPTION
"The frwk802MarkerGroup is mandatory if marking a packet
with 802 traffic criteria is supported."
GROUP frwkILabelMarkerGroup
DESCRIPTION
"The frwkILabelMarkerGroup is mandatory if marking a
flow with internal labels is supported."
::= { frwkBasePibCompliances 1 } ::= { frwkBasePibCompliances 1 }
frwkPrcSupportGroup OBJECT-GROUP frwkPrcSupportGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkPrcSupportSupportedPrc, frwkPrcSupportSupportedPrc,
frwkPrcSupportSupportedAttrs } frwkPrcSupportSupportedAttrs }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkPrcSupportTable." "Objects from the frwkPrcSupportTable."
::= { frwkBasePibGroups 1 } ::= { frwkBasePibGroups 1 }
frwkPibIncarnationGroup OBJECT-GROUP frwkPibIncarnationGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkPibIncarnationName, frwkPibIncarnationName,
frwkPibIncarnationId, frwkPibIncarnationId,
frwkPibIncarnationLongevity, frwkPibIncarnationLongevity,
frwkPibIncarnationTtl, frwkPibIncarnationTtl,
frwkPibIncarnationActive }
Framework Policy Information Base November 2001
frwkPibIncarnationActive,
frwkPibIncarnationFullState
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkDevicePibIncarnationTable." "Objects from the frwkDevicePibIncarnationTable."
::= { frwkBasePibGroups 2 } ::= { frwkBasePibGroups 2 }
frwkDeviceIdGroup OBJECT-GROUP frwkDeviceIdGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkDeviceIdDescr, frwkDeviceIdDescr,
frwkDeviceIdMaxMsg, frwkDeviceIdMaxMsg,
skipping to change at page 41, line 5 skipping to change at page 52, line 39
frwkCompLimitsComponent, frwkCompLimitsComponent,
frwkCompLimitsAttrPos, frwkCompLimitsAttrPos,
frwkCompLimitsNegation, frwkCompLimitsNegation,
frwkCompLimitsType, frwkCompLimitsType,
frwkCompLimitsSubType, frwkCompLimitsSubType,
frwkCompLimitsGuidance } frwkCompLimitsGuidance }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkCompLimitsTable." "Objects from the frwkCompLimitsTable."
Framework Policy Information Base July 2001
::= { frwkBasePibGroups 4 } ::= { frwkBasePibGroups 4 }
frwkIfCapSetGroup OBJECT-GROUP frwkReferenceGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkIfCapSetName, frwkReferenceClientType,
frwkIfCapSetCapability } frwkReferenceClientHandle,
frwkReferencePrid, }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkIfCapSetTable." "Objects from the frwkReferenceTable."
::= { frwkBasePibGroups 5 } ::= { frwkBasePibGroups 5 }
frwkIfCapSetRoleComboGroup OBJECT-GROUP frwkErrorGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkIfCapSetRoleComboName, frwkErrorCode,
frwkIfCapSetRoleComboRoles } frwkErrorSubCode,
frwkErrorPrc,
frwkErrorInstance }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkIfCapSetRoleComboTable."
Framework Policy Information Base November 2001
"Objects from the frwkErrorTable."
::= { frwkBasePibGroups 6 } ::= { frwkBasePibGroups 6 }
frwkIfCapSetInterfaceGroup OBJECT-GROUP frwkIfCapSetGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkIfCapSetInterfaceIfIndex, frwkIfCapSetName,
frwkIfCapSetInterfaceRoles } frwkIfCapSetCapability }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkIfCapSetInterfaceTable." "Objects from the frwkIfCapSetTable."
::= { frwkBasePibGroups 7 } ::= { frwkBasePibGroups 7 }
frwkIfRoleComboGroup OBJECT-GROUP
OBJECTS {
frwkIfRoleComboIfIndex,
frwkIfRoleComboRoles,
frwkIfRoleComboCapSetName }
STATUS current
DESCRIPTION
"Objects from the frwkIfRoleComboTable."
::= { frwkBasePibGroups 8 }
frwkBaseFilterGroup OBJECT-GROUP frwkBaseFilterGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkBaseFilterNegation } frwkBaseFilterNegation }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkBaseFilterTable." "Objects from the frwkBaseFilterTable."
::= { frwkBasePibGroups 8 } ::= { frwkBasePibGroups 9 }
frwkIpFilterGroup OBJECT-GROUP frwkIpFilterGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkIpFilterDstAddrType, frwkIpFilterAddrType,
frwkIpFilterDstAddr, frwkIpFilterDstAddr,
frwkIpFilterDstAddrMask, frwkIpFilterDstPrefixLength,
frwkIpFilterSrcAddrType,
Framework Policy Information Base July 2001
frwkIpFilterSrcAddr, frwkIpFilterSrcAddr,
frwkIpFilterSrcAddrMask, frwkIpFilterSrcPrefixLength,
frwkIpFilterDscp, frwkIpFilterDscp,
frwkIpFilterFlowId
frwkIpFilterProtocol, frwkIpFilterProtocol,
frwkIpFilterDstL4PortMin, frwkIpFilterDstL4PortMin,
frwkIpFilterDstL4PortMax, frwkIpFilterDstL4PortMax,
frwkIpFilterSrcL4PortMin, frwkIpFilterSrcL4PortMin,
frwkIpFilterSrcL4PortMax } frwkIpFilterSrcL4PortMax }
STATUS current STATUS current
Framework Policy Information Base November 2001
DESCRIPTION DESCRIPTION
"Objects from the frwkIpFilterTable." "Objects from the frwkIpFilterTable."
::= { frwkBasePibGroups 9 } ::= { frwkBasePibGroups 10 }
frwk802FilterGroup OBJECT-GROUP frwk802FilterGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwk802FilterDstAddr, frwk802FilterDstAddr,
frwk802FilterDstAddrMask, frwk802FilterDstAddrMask,
frwk802FilterSrcAddr, frwk802FilterSrcAddr,
frwk802FilterSrcAddrMask, frwk802FilterSrcAddrMask,
frwk802FilterVlanId, frwk802FilterVlanId,
frwk802FilterVlanTagRequired, frwk802FilterVlanTagRequired,
frwk802FilterEtherType, frwk802FilterEtherType,
frwk802FilterUserPriority } frwk802FilterUserPriority }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwk802FilterTable." "Objects from the frwk802FilterTable."
::= { frwkBasePibGroups 10 } ::= { frwkBasePibGroups 11 }
frwkILabelFilterGroup OBJECT-GROUP
OBJECTS {
FrwkILabelFilterILabel }
STATUS current
DESCRIPTION
"Objects from the frwkILabelFilterTable."
::= { frwkBasePibGroups 12 }
frwk802MarkerGroup OBJECT-GROUP
OBJECTS {
frwk802MarkerVlanId,
frwk802MarkerPriority }
STATUS current
DESCRIPTION
"Objects from the frwk802MarkerTable."
::= { frwkBasePibGroups 13 }
frwkILabelMarkerGroup OBJECT-GROUP
OBJECTS {
FrwkILabelMarkerILabel }
STATUS current
DESCRIPTION
"Objects from the frwkILabelMarkerTable."
::= { frwkBasePibGroups 14 }
END END
Framework Policy Information Base July 2001 Framework Policy Information Base November 2001
7. Security Considerations 6. Security Considerations
It is clear that this PIB is used for configuration using [COPS-PR], It is clear that this PIB is used for configuration using [COPS-PR],
and anything that can be configured can be misconfigured, with and anything that can be configured can be misconfigured, with
potentially disastrous effect. At this writing, no security holes potentially disastrous effect. At this writing, no security holes
have been identified beyond those that the COPS base protocol have been identified beyond those that the COPS base protocol
security is itself intended to address. These relate primarily to security is itself intended to address. These relate primarily to
controlled access to sensitive information and the ability to controlled access to sensitive information and the ability to
configure a device - or which might result from operator error, configure a device - or which might result from operator error,
which is beyond the scope of any security architecture. which is beyond the scope of any security architecture.
There are a number of provisioning classes defined in this PIB that There are a number of provisioning classes defined in this PIB that
have a PIB-ACCESS clause of install (read-create). Such objects may have a PIB-ACCESS clause of install and install-notify (read-
be considered sensitive or vulnerable in some network environments. create). Such objects may be considered sensitive or vulnerable in
The support for "Install" decisions sent over [COPS-PR] in a non- some network environments. The support for "Install" or "Install-
secure environment without proper protection can have a negative Notify" decisions sent over [COPS-PR] in a non-secure environment
effect on network operations. There are a number of provisioning without proper protection can have a negative effect on network
classes in this PIB that may contain information that may be operations. There are a number of provisioning classes in this PIB
sensitive from a business perspective, in that they may represent a that may contain information that may be sensitive from a business
customer's service contract or the filters that the service provider perspective, in that they may represent a customer's service
chooses to apply to a customer's ingress or egress traffic. There contract or the filters that the service provider chooses to apply
are no PRCs that are sensitive in their own right, such as passwords to a customer's ingress or egress traffic. There are no PRCs that
or monetary amounts. It may be important to control even are sensitive in their own right, such as passwords or monetary
"Notify"(read-only) access to these PRCs and possibly to even amounts. It may be important to control even "Notify"(read-only)
encrypt the values of these PRIs when sending them over the network access to these PRCs and possibly to even encrypt the values of
via COPS-PR. The use of IPSEC between the PDP and the PEP, as these PRIs when sending them over the network via COPS-PR. The use
described in [COPS], provides the necessary protection against of IPSEC between the PDP and the PEP, as described in [COPS],
security threats. However, even if the network itself is secure, provides the necessary protection against security threats. However,
there is no control as to who on the secure network is allowed to even if the network itself is secure, there is no control as to who
"Install/Notify" (read/change/create/delete) the PRIs in this PIB. on the secure network is allowed to "Install/Notify"
(read/change/create/delete) the PRIs in this PIB.
It is then a customer/user responsibility to ensure that the PEP/PDP It is then a customer/user responsibility to ensure that the PEP/PDP
giving access to an instance of this PIB, is properly configured to giving access to an instance of this PIB, is properly configured to
give access to the PRIs only to those principals (users) that have give access to the PRIs only to those principals (users) that have
legitimate rights to indeed "Install" or "Notify" (change/create/ legitimate rights to indeed "Install" or "Notify" (change/create/
delete) them. delete) them.
8. Author Information and Acknowledgments 7. RFC Editor Considerations
This document references [INETADDR] which is in the IESG last call
stage. This document references it as an Internet Draft. Please use
the corresponding RFC number prior to publishing of this document as
a RFC.
8. IANA Considerations
This document describes the frameworkPib and frwkTcPib Policy
Information Base (PIB) modules for standardization. An IANA assigned
PIB number is requested for both [SPPI].
Framework Policy Information Base November 2001
9. Author Information and Acknowledgments
Michael Fine Michael Fine
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 USA San Jose, CA 95134-1706 USA
Phone: +1 408 527 8218 Phone: +1 408 527 8218
Email: mfine@cisco.com Email: mfine@cisco.com
Keith McCloghrie Keith McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 USA San Jose, CA 95134-1706 USA
Phone: +1 408 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com Email: kzm@cisco.com
Framework Policy Information Base July 2001
John Seligson John Seligson
Nortel Networks, Inc. Nortel Networks, Inc.
4401 Great America Parkway 4401 Great America Parkway
Santa Clara, CA 95054 USA Santa Clara, CA 95054 USA
Phone: +1 408 495 2992 Phone: +1 408 495 2992
Email: jseligso@nortelnetworks.com Email: jseligso@nortelnetworks.com
Kwok Ho Chan Kwok Ho Chan
Nortel Networks, Inc. Nortel Networks, Inc.
600 Technology Park Drive 600 Technology Park Drive
skipping to change at page 44, line 43 skipping to change at page 57, line 5
Email: ravi.sahita@intel.com Email: ravi.sahita@intel.com
Andrew Smith Andrew Smith
Allegro Networks Allegro Networks
6399 San Ignacio Ave. 6399 San Ignacio Ave.
San Jose San Jose
CA 95119 CA 95119
FAX: 415 345 1827 FAX: 415 345 1827
Email: andrew@allegronetworks.com Email: andrew@allegronetworks.com
Framework Policy Information Base November 2001
Francis Reichmeyer Francis Reichmeyer
PFN, Inc. PFN, Inc.
University Park at MIT University Park at MIT
26 Landsdowne Street 26 Landsdowne Street
Cambridge, MA 02139 Cambridge, MA 02139
Phone: +1 617 494 9980 Phone: +1 617 494 9980
Email: franr@pfn.com Email: franr@pfn.com
Special thanks to Carol Bell and David Durham for their many Special thanks to Carol Bell and David Durham for their many
significant comments. significant comments.
Framework Policy Information Base July 2001 10. References
9. References
[COPS] [COPS]
Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., and Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., and
A. Sastry, "The COPS (Common Open Policy Service) Protocol" A. Sastry, "The COPS (Common Open Policy Service) Protocol"
RFC 2748, January 2000. RFC 2748, January 2000.
[COPS-PR] [COPS-PR]
K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie,
F. Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage F. Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage
for Policy Provisioning," RFC 3084, March 2001. for Policy Provisioning," RFC 3084, March 2001.
[SPPI] [SPPI]
K. McCloghrie, M. Fine, J. Seligson, K. Chan, S. Hahn, K. McCloghrie, M. Fine, J. Seligson, K. Chan, S. Hahn,
R. Sahita, A. Smith, F. Reichmeyer, "Structure of Policy R. Sahita, A. Smith, F. Reichmeyer, "Structure of Policy
Provisioning Information," draft-ietf-rap-sppi-07.txt, Provisioning Information," RFC 3159, August 2001.
May 2001.
[RAP-FRAMEWORK] [RAP-FRAMEWORK]
R. Yavatkar, D. Pendarakis, "A Framework for Policy-based R. Yavatkar, D. Pendarakis, "A Framework for Policy-based
Admission Control", RFC 2753, January 2000. Admission Control", RFC 2753, January 2000.
[SNMP-SMI] [SNMP-SMI]
K. McCloghrie, D. Perkins, J. Schoenwaelder, J. Case, M. Rose K. McCloghrie, D. Perkins, J. Schoenwaelder, J. Case, M. Rose
and S. Waldbusser, "Structure of Management Information and S. Waldbusser, "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[INETADDR] [INETADDR]
M. Daniele, B. Haberman, S. Routhier and J. Schoenwaelder " M. Daniele, B. Haberman, S. Routhier and J. Schoenwaelder "
Textual Conventions for Internet Network Addresses" RFC 2851, Textual Conventions for Internet Network Addresses"
June 2000 draft-ietf-ops-rfc2851-update-05.txt, October 31, 2001
[IFMIB] [IFMIB]
K. McCloghrie, F. Kastenholz, "The Interface Group MIB using K. McCloghrie, F. Kastenholz, "The Interface Group MIB using
SMIv2" RFC 2233, November 1977. SMIv2" RFC 2233, November 1977.
[802] [802]
IEEE Standards for Local and Metropolitan Area Networks: IEEE Standards for Local and Metropolitan Area Networks:
Overview and Architecture, ANSI/IEEE Std 802, 1990. Overview and Architecture, ANSI/IEEE Std 802, 1990.
Framework Policy Information Base November 2001
[SNMPFRWK] [SNMPFRWK]
Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
for Describing SNMP Management Frameworks", RFC 2571, for Describing SNMP Management Frameworks", RFC 2571,
May 1999 May 1999
[STD17] [STD17]
K. McCloghrie, M. Rose "Management Information Base for Network K. McCloghrie, M. Rose "Management Information Base for Network
Management of TCP/IP-based internets: MIB-II" STD 17, RFC 1213, Management of TCP/IP-based internets: MIB-II" STD 17, RFC 1213,
March 1991 March 1991
Framework Policy Information Base July 2001 11. Full Copyright
10. Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved. This Copyright (C) The Internet Society (2001). All Rights Reserved. This
document and translations of it may be copied and furnished to document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
skipping to change at page 46, line 34 skipping to change at page 59, line 5
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Framework Policy Information Base November 2001
Table of Contents Table of Contents
Status of this Memo...............................................1 Status of this Memo...............................................1
Abstract..........................................................2
1. Glossary.......................................................2 1. Glossary.......................................................2
2. Introduction...................................................2 2. General PIB Concepts...........................................2
3. General PIB Concepts...........................................2 2.1. Roles........................................................2
3.1. Roles........................................................2 2.1.1. An Example.................................................4
3.1.1. An Example.................................................4 2.2. Management of Role-Combinations from the PDP.................5
3.2. Multiple PIB Instances.......................................5 2.3. Updating a Request State.....................................6
3.3. Reporting and Configuring of Device Capabilities.............6 2.3.1 Full Request State..........................................6
3.4. Reporting of Device Limitations..............................6 2.3.2 Installing PRIs in a Request................................7
4. The Framework Role PIB module..................................7 2.3.3 Updating PRIs in a Request..................................7
5. Summary of the Framework PIB...................................9 2.3.4 Removing PRIs from a Request................................7
6. The Framework PIB Module......................................12 2.3.5 Removing EXTENDED, AUGMENTED PRIs...........................8
7. Security Considerations.......................................43 2.3.6 Error Handling in Request updates...........................8
8. Author Information and Acknowledgments........................43 2.4. Multiple PIB Instances.......................................8
9. References....................................................45 2.5. Reporting and Configuring of Device Capabilities............10
10. Full Copyright...............................................46 2.6. Reporting of Device Limitations.............................10
3. The Framework TC PIB module...................................11
4. Summary of the Framework PIB..................................14
4.1. Base PIB classes Group......................................14
4.2. Device Capabilities group...................................15
4.3. Classifier group............................................16
4.4. Marker group................................................16
5. The Framework PIB Module......................................17
6. Security Considerations.......................................55
7. RFC Editor Considerations.....................................55
8. IANA Considerations...........................................55
9. Author Information and Acknowledgments........................56
10. References...................................................57
11. Full Copyright...............................................58
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/