draft-ietf-rap-frameworkpib-04.txt   draft-ietf-rap-frameworkpib-05.txt 
Internet Draft M. Fine Internet Draft M. Fine
Expires September 2001 K. McCloghrie Expires January 2002 K. McCloghrie
File: draft-ietf-rap-frameworkpib-04.txt Cisco Systems File: draft-ietf-rap-frameworkpib-05.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
March 1, 2001 July 20, 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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Framework Policy Information Base March 2001 Framework Policy Information Base July 2001
1. Glossary 1. Glossary
PRC Provisioning Class. A type of policy data. PRC Provisioning Class. A type of policy data.
PRI Provisioning Instance. An instance of a PRC. PRI Provisioning Instance. An instance of a PRC.
PIB Policy Information Base. The database of policy information. PIB Policy Information Base. The database of policy information.
PDP Policy Decision Point. See [RAP-FRAMEWORK]. PDP Policy Decision Point. See [RAP-FRAMEWORK].
PEP Policy Enforcement Point. See [RAP-FRAMEWORK]. PEP Policy Enforcement Point. See [RAP-FRAMEWORK].
PRID Provisioning Instance Identifier. Uniquely identifies an PRID Provisioning Instance Identifier. Uniquely identifies an
instance of a PRC. instance of a PRC.
skipping to change at page 3, line 5 skipping to change at page 3, line 5
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 March 2001 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.
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 reports all its role combinations to the PDP in the initial The PEP sends all its Capability Set Names, Role Combinations,
COPS request (REQ) message and in subsequent request messages Policy Controlled Interfaces, and their relationships to the PDP in
generated in response to COPS state synchronization (SSQ) requests the initial COPS request (REQ) message. The PDP can install new
and local configuration changes. instances or change existing instances of these PRIs. This
operation can also occur in subsequent request messages generated in
response to COPS 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 3, line 56 skipping to change at page 4, line 4
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
Framework Policy Information Base July 2001
Roles A, B and R2 are assigned to interface I2 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
Framework Policy Information Base March 2001
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
will apply to all three interfaces, because "*" matches with R1, R2 will apply to all three interfaces, because "*" matches with R1, R2
and R3. The policies can be assigned to an interface due to more and R3. The policies can be assigned to an interface due to more
skipping to change at page 4, line 57 skipping to change at page 5, line 4
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
P2: Packets from managers (role "manager") get DSCP 6
Framework Policy Information Base March 2001 Framework Policy Information Base July 2001
P2: Packets from managers (role "manager") get DSCP 6
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
skipping to change at page 5, line 51 skipping to change at page 5, line 53
[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]. instances is controlled by the PDP as described in [COPS-PR]. A PEP
must open only a single "request-state" for configuration for a
given subject-category (client type). Any additional "request-
states" at the PEP must be initiated by the PDP.
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
Framework Policy Information Base July 2001
itself) only one of them can be active at any given time, the active itself) only one of them can be active at any given time, the active
one being selected by the PDP. To facilitate this selection, the one being selected by the PDP. To facilitate this selection, the
Framework PIB supports an attribute to make a PIB instance the Framework PIB supports an attribute to make a PIB instance the
active one and, similarly, to report the active PIB instance to the active one and, similarly, to report the active PIB instance to the
Framework Policy Information Base March 2001
PDP in a COPS request message. This attribute is in the Incarnation PDP in a COPS request message. This attribute is in the Incarnation
Table described below. Table described below.
Setting the attribute frwkPibIncarnationActive to 'true' in one PIB Setting the attribute frwkPibIncarnationActive to 'true' in one PIB
instance MUST ensure that the attribute is 'false' in all other instance MUST ensure that the attribute is 'false' in all other
contexts. contexts.
3.3. Reporting of Device Capabilities 3.3. 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 communicated to the PDP when initial policy These capabilities are organized into some PEP default Interface
is requested by the PEP. Knowing device capabilities, the PDP can Capability Set, with each Capability Set associated with a set of
send the provisioning instances (PRIs) relevant to the specific Role Combinations, each Role Combination associated with a set of
device, rather than sending the entire PIB. interfaces. After receiving the PEP default setting for the PEP
device capabilities, the PDP can change them. These capabilities
are communicated to the PDP when initial policy is requested by the
PEP. Knowing device capabilities, the PDP can send the provisioning
instances (PRIs) relevant to the specific device, rather than
sending the entire PIB.
The PIB indicates which capabilities the PEP must report to the PDP The PIB indicates which capabilities the PEP must report to the PDP
by means of the PIB-ACCESS clause as described in [SPPI]. by means of the PIB-ACCESS clause as described in [SPPI].
3.4. Reporting of Device Limitations 3.4. 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
skipping to change at page 7, line 5 skipping to change at page 7, line 5
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 initial 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 March 2001 Framework Policy Information Base July 2001
4. The Framework Role PIB module 4. The Framework Role PIB module
FRAMEWORK-ROLE-PIB PIB-DEFINITIONS ::= BEGIN FRAMEWORK-ROLE-PIB PIB-DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, TEXTUAL-CONVENTION 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 frwkRolePib MODULE-IDENTITY
SUBJECT-CATEGORIES { all } SUBJECT-CATEGORIES { all }
LAST-UPDATED "200003010400Z" LAST-UPDATED "200003010400Z"
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
skipping to change at page 7, line 35 skipping to change at page 7, line 35
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." required TCs."
::= { tbd } ::= { 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.
Valid characters are a-z, A-Z, 0-9, period, hyphen and Valid characters are a-z, A-Z, 0-9, period, hyphen and
skipping to change at page 8, line 5 skipping to change at page 8, line 5
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 Notice the roles within a role-combination are in
Framework Policy Information Base March 2001 Framework Policy Information Base July 2001
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
which has a value of zero but length of one.)" which has a value of zero but length of one.)"
SYNTAX SnmpAdminString (SIZE (0..255)) SYNTAX SnmpAdminString (SIZE (0..255))
PrcIdentifier ::= TEXTUAL-CONVENTION PrcIdentifier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An OID that identifies a PRC. The value MUST be an OID "An OID that identifies a PRC. The value MUST be an OID
assigned to a PRC's row definition. An attribute with this assigned to a PRC's row definition. An attribute with this
syntax can have the value 0.0 to indicate that it currently syntax can have the value 0.0 (zeroDotZero) to indicate that
does not identify a PRC." it currently does not identify a PRC."
SYNTAX OBJECT IDENTIFIER
AttrIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A Unsigned32 value that identifies an attribute in a PRC.
A AttrIdentifier value is always interpreted within the
context of a PrcIdentifier value. The PrcIdentifier object
which defines the context must be registered immediately
before the object which uses the AttrIdentifier textual
convention.
An attribute with this syntax can have the value 0 to
indicate that it currently does not identify a PRC
attribute."
SYNTAX Unsigned32
AttrIdentifierOid ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
An OID that identifies an attribute in a PRC. The value MUST
be an OID assigned to a PRC's attribute definition. The last
sub-id is the position of the attribute as it is defined in
the PRC entry definition. The prefix OID (after dropping the
last sub-id) is the OID assigned to a defined PRC. An
attribute with this syntax can have the value 0.0
(zeroDotZero) to indicate that it currently does not
identify a PRC's attribute."
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
END END
Framework Policy Information Base July 2001
5. Summary of the Framework PIB 5. Summary of the Framework PIB
The Framework PIB comprises of three groups: The Framework PIB comprises of three groups:
1. Base PIB classes Group 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.
skipping to change at page 8, line 58 skipping to change at page 9, line 34
that the device supports as well as the individual attributes that the device supports as well as the individual attributes
of each PRC. Using this information the PDP can potentially of each PRC. Using this information the PDP can potentially
tailor the policy to more closely match the capabilities of the tailor the policy to more closely match the capabilities of the
device. The PRC Support Table instances are specific to the device. The PRC Support Table instances are specific to the
particular Subject Category (Client-Type). That is, the PRC particular Subject Category (Client-Type). That is, the PRC
Support Table for Subject Category 'A' will not include Support Table for Subject Category 'A' will not include
instances for classes supported by the Subject Category 'B'. instances for classes supported by the Subject Category 'B'.
Note that the COPS client-type [COPS] used for Framework PIB Note that the COPS client-type [COPS] used for Framework PIB
PRIs sent/received over COPS-PR MUST be the unique SUBJECT- PRIs sent/received over COPS-PR MUST be the unique SUBJECT-
CATEGORY number assigned for the area of policy being managed CATEGORY number assigned for the area of policy being managed
(eg. QoS, Security etc). (e.g. QoS, Security etc).
Framework Policy Information Base March 2001
The PEP MUST ignore the attributes that it reports as not The PEP MUST ignore the attributes that it reports as not
Supported in the decision from the PDP. The PEP SHOULD not send Supported in the decision from the PDP. The PEP SHOULD not send
duplicate PRC support instances in a COPS Request and the PDP duplicate PRC support instances in a COPS Request and the PDP
MUST ignore duplicate instances and MUST use the first instance MUST ignore duplicate instances and MUST use the first instance
received for a supported PRC in a COPS Request. received for a supported PRC in a COPS Request.
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
skipping to change at page 9, line 32 skipping to change at page 10, line 4
of policy. The incarnation PRC also includes an attribute to of policy. The incarnation PRC also includes an attribute to
indicate which context is the active one at the present time. indicate which context is the active one at the present time.
The incarnation instance is specific to the particular Subject The incarnation instance is specific to the particular Subject
Category (Client-Type). Category (Client-Type).
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
skipping to change at page 10, line 4 skipping to change at page 10, line 35
2. Device Capabilities group 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
Framework Policy Information Base March 2001
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].
skipping to change at page 10, line 29 skipping to change at page 10, line 57
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 It is possible to tailor the behavior of interfaces by
assigning specific roles to the capability sets. This allows assigning specific roles to the capability sets. This allows
interfaces with the same capability sets to be assigned interfaces with the same capability sets to be assigned
different policies, based on the current roles assigned to different policies, based on the current roles assigned to
them. At the PDP, configuration is done in terms of these them. At the PDP, configuration is done in terms of these
interface capability set names (ifCapSetName) and the role interface capability set names (ifCapSetName) and the role
combinations assigned to them; The PDP does not deal with combinations assigned to them. Thus, each row of this
individual interfaces on the device. Thus, each row of this
class is a <interface capability set name, Role Combo> two- class is a <interface capability set name, Role Combo> two-
tuple, that indicates the roles that have been assigned to a 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 particular capability set (as identified by IfCapSetName). The
ifCapSetName is the grouping attribute used to form a set of ifCapSetName is the grouping attribute used to form a set of
role combinations that apply to this capability set. role combinations that apply to this capability set.
Interface and Role Combination Table
The Interface and Role Combination Table describes the
association between specific interfaces with each role
combination. It answers the questions of Šwhich interfaces
have a specific role combination?Ă and Šwhat role combination
a specific interface is a part of?Ă. The Interface and Role
Combination Table entries each contains a <ifIndex, Role Combo>
two-tuple to accomplish this mapping.
3. Classifier group 3. Classifier group
This group contains the IP and IEEE 802 Classifier elements. The This group contains the IP and IEEE 802 Classifier elements. The
set of tables consist of a Base Filter table that contains the set of tables consist of a Base Filter table that contains the
Index InstanceId and the Negation flag for the filter. This Index InstanceId and the Negation flag for the filter. This
frwkBaseFilterTable is extended to form the IP Filter table and frwkBaseFilterTable is extended to form the IP Filter table and
the 802 Filter table [802]. Filters may also be defined outside the 802 Filter table [802]. Filters may also be defined outside
this document and used to extend the Base Filter table. 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 March 2001 Framework Policy Information Base July 2001
6. The Framework PIB Module 6. 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 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
FROM FRAMEWORK-ROLE-PIB FROM FRAMEWORK-ROLE-PIB
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
InterfaceIndex
FROM IF-MIB
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 "200003010400Z"
ORGANIZATION "IETF RAP WG" ORGANIZATION "IETF RAP WG"
CONTACT-INFO " CONTACT-INFO "
skipping to change at page 11, line 56 skipping to change at page 12, line 58
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
classes that are required for support of policies for classes that are required for support of policies for
all subject-categories." all subject-categories."
::= { tbd } ::= { pib tbd } -- tbd to be assigned by IANA
Framework Policy Information Base March 2001 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 13, line 5 skipping to change at page 14, 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 March 2001 Framework Policy Information Base July 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 14, line 5 skipping to change at page 15, 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 March 2001 Framework Policy Information Base July 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
skipping to change at page 14, line 36 skipping to change at page 15, line 36
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"
PIB-INDEX { frwkPibIncarnationPrid } PIB-INDEX { frwkPibIncarnationPrid }
UNIQUENESS { frwkPibIncarnationName }
::= { 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 frwkPibIncarnationActive TruthValue
skipping to change at page 15, line 5 skipping to change at page 16, line 5
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 March 2001 Framework Policy Information Base July 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 16, line 5 skipping to change at page 17, 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 March 2001 Framework Policy Information Base July 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
skipping to change at page 16, line 31 skipping to change at page 17, line 31
::= { frwkPibIncarnationEntry 5 } ::= { frwkPibIncarnationEntry 5 }
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 "If this attribute is set to TRUE, then the PIB instance
to which this PRI belongs becomes the active PIB instance. to which this PRI belongs becomes the active PIB instance.
The previous active instance MUST become inactive and the The previous active instance MUST become inactive and the
frwkPibIncarnationActive attribute in that PIB instance frwkPibIncarnationActive attribute in that PIB instance
MUST be set to false." MUST be set to false.
When the PEP installs an attribute frwkPibIncarnationActive
that is 'true' in one PIB instance, the PEP must ensure,
re-setting the attribute if necessary, that the
frwkPibIncarnationActive attribute is 'false' in all other
contexts."
::= { frwkPibIncarnationEntry 6 } ::= { frwkPibIncarnationEntry 6 }
-- --
-- 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 }
Framework Policy Information Base March 2001
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 }
UNIQUENESS { frwkDeviceIdDescr }
::= { frwkDeviceIdTable 1 } ::= { frwkDeviceIdTable 1 }
FrwkDeviceIdEntry ::= SEQUENCE { FrwkDeviceIdEntry ::= SEQUENCE {
frwkDeviceIdPrid InstanceId, frwkDeviceIdPrid InstanceId,
frwkDeviceIdDescr SnmpAdminString, frwkDeviceIdDescr SnmpAdminString,
frwkDeviceIdMaxMsg Unsigned32, frwkDeviceIdMaxMsg Unsigned32,
frwkDeviceIdMaxContexts Unsigned32 frwkDeviceIdMaxContexts Unsigned32
} }
skipping to change at page 17, line 49 skipping to change at page 19, line 4
"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
Framework Policy Information Base March 2001
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 NULL for this attributes if it not
defined." defined."
::= { frwkDeviceIdEntry 3 } ::= { frwkDeviceIdEntry 3 }
frwkDeviceIdMaxContexts OBJECT-TYPE frwkDeviceIdMaxContexts OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "contexts" UNITS "contexts"
skipping to change at page 18, line 34 skipping to change at page 19, line 40
specified." specified."
::= { frwkDeviceIdEntry 4 } ::= { frwkDeviceIdEntry 4 }
-- --
-- Component Limitations Table -- Component Limitations Table
-- --
-- This table supports the ability to export information -- This table supports the ability to export information
-- detailing provisioning class/attribute implementation limitations -- detailing provisioning class/attribute implementation limitations
-- to the policy management system. -- to the policy management system. Instances of this PRC apply only
-- for PRCs with access type 'install' or 'install-notify'.
frwkCompLimitsTable OBJECT-TYPE frwkCompLimitsTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkCompLimitsEntry SYNTAX SEQUENCE OF FrwkCompLimitsEntry
PIB-ACCESS notify PIB-ACCESS notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each instance of this class identifies a provisioning class "Each instance of this class identifies a provisioning class
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
Framework Policy Information Base March 2001
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,
skipping to change at page 19, line 51 skipping to change at page 21, line 4
::= { 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 }
Framework Policy Information Base March 2001
frwkCompLimitsAttrPos OBJECT-TYPE frwkCompLimitsAttrPos OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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."
skipping to change at page 20, line 52 skipping to change at page 22, line 4
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
Framework Policy Information Base March 2001
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."
skipping to change at page 21, line 30 skipping to change at page 22, line 36
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),
valueOnly(9) valueOnly(9),
bitMask(10)
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the type of guidance related "This object indicates the type of guidance related
to the noted limitation (as indicated by the to the noted limitation (as indicated by the
frwkCompLimitsType attribute) that is provided frwkCompLimitsType attribute) that is provided
in the frwkCompLimitsGuidance attribute. in the frwkCompLimitsGuidance attribute.
A value of 'none(1)' means that no additional A value of 'none(1)' means that no additional
guidance is provided for the noted limitation type. guidance is provided for the noted limitation type.
skipping to change at page 21, line 53 skipping to change at page 23, line 4
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
Framework Policy Information Base March 2001
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.
skipping to change at page 22, line 41 skipping to change at page 23, line 48
A value of 'enumOnly(8)' means that the guidance A value of 'enumOnly(8)' means that the guidance
attribute provides data related to a single attribute provides data related to a single
enumeration acceptable for the value of the enumeration acceptable for the value of the
identified component. identified component.
A value of 'valueOnly(9)' means that the guidance A value of 'valueOnly(9)' means that the guidance
attribute provides data related to a single attribute provides data related to a single
value that is acceptable for the identified value that is acceptable for the identified
component. component.
A value of 'bitMask(10)' means that the guidance
attribute is a bit mask such that all the combinations of
bits set in the bitmask are acceptable values for the
identified component which should be an attribute of type
'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 Guidance
Framework Policy Information Base July 2001
Type Type
------------------------------------------------------------ ------------------------------------------------------------
frwkIpFilterDstAddrMask attrValueSupLimited valueOnly 24 frwkIpFilterDstAddrMask attrValueSupLimited valueOnly 24
frwkIpFilterSrcAddrMask attrValueSupLimited valueOnly 24 frwkIpFilterSrcAddrMask attrValueSupLimited valueOnly 24
frwkIpFilterProtocol attrValueSupLimited rangeMin 10 frwkIpFilterProtocol attrValueSupLimited rangeMin 10
frwkIpFilterProtocol attrValueSupLimited rangeMax 20 frwkIpFilterProtocol 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
Framework Policy Information Base March 2001
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."
::= { frwkCompLimitsEntry 6 } ::= { frwkCompLimitsEntry 6 }
frwkCompLimitsGuidance OBJECT-TYPE frwkCompLimitsGuidance OBJECT-TYPE
skipping to change at page 23, line 41 skipping to change at page 24, line 54
in the context of the frwkCompLimitsType and in the context of the frwkCompLimitsType and
frwkCompLimitsSubType values. frwkCompLimitsSubType values.
Note that numbers are encoded in network byte order. Note that numbers are encoded in network byte order.
Base Type Value Base Type Value
--------- ----- --------- -----
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
Component specified."
::= { frwkCompLimitsEntry 7 } ::= { frwkCompLimitsEntry 7 }
Framework Policy Information Base July 2001
-- --
-- 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 }
-- --
-- Interface Capability Set Table -- Interface Capability Set Table
-- --
Framework Policy Information Base March 2001
frwkIfCapSetTable OBJECT-TYPE frwkIfCapSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkIfCapSetEntry SYNTAX SEQUENCE OF FrwkIfCapSetEntry
PIB-ACCESS notify PIB-ACCESS install-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 24, line 47 skipping to change at page 26, line 5
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
"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 }
Framework Policy Information Base March 2001
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 Capabilities Set Name and Role Combination Table
-- --
frwkIfCapSetRoleComboTable OBJECT-TYPE frwkIfCapSetRoleComboTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkIfCapSetRoleComboEntry SYNTAX SEQUENCE OF FrwkIfCapSetRoleComboEntry
PIB-ACCESS notify PIB-ACCESS install-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Policy for an interface depends not only on the "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 capability set name, role
combination> tuples currently on the device." combination> tuples currently on the device."
::= { frwkDeviceCapClasses 2 } ::= { frwkDeviceCapClasses 2 }
frwkIfCapSetRoleComboEntry OBJECT-TYPE frwkIfCapSetRoleComboEntry OBJECT-TYPE
skipping to change at page 25, line 45 skipping to change at page 27, line 5
DESCRIPTION DESCRIPTION
"An instance of this class describes a combination of an "An instance of this class describes a combination of an
interface capability set name and a role combination." interface capability set name and a role combination."
PIB-INDEX { frwkIfCapSetRoleComboPrid } PIB-INDEX { frwkIfCapSetRoleComboPrid }
UNIQUENESS { frwkIfCapSetRoleComboName, UNIQUENESS { frwkIfCapSetRoleComboName,
frwkIfCapSetRoleComboRoles } frwkIfCapSetRoleComboRoles }
::= { frwkIfCapSetRoleComboTable 1 } ::= { frwkIfCapSetRoleComboTable 1 }
Framework Policy Information Base July 2001
FrwkIfCapSetRoleComboEntry ::= SEQUENCE { FrwkIfCapSetRoleComboEntry ::= SEQUENCE {
frwkIfCapSetRoleComboPrid InstanceId, frwkIfCapSetRoleComboPrid InstanceId,
frwkIfCapSetRoleComboName SnmpAdminString, frwkIfCapSetRoleComboName SnmpAdminString,
frwkIfCapSetRoleComboRoles RoleCombination frwkIfCapSetRoleComboRoles RoleCombination
} }
Framework Policy Information Base March 2001
frwkIfCapSetRoleComboPrid OBJECT-TYPE frwkIfCapSetRoleComboPrid 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 an
instance of the class." instance of the class."
::= { frwkIfCapSetRoleComboEntry 1 } ::= { frwkIfCapSetRoleComboEntry 1 }
frwkIfCapSetRoleComboName OBJECT-TYPE frwkIfCapSetRoleComboName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of the interface capability set. This name must "The name of the interface capability set. This name must
exist in frwkIfCapSetTable." exist in frwkIfCapSetTable."
skipping to change at page 26, line 36 skipping to change at page 27, line 42
SYNTAX RoleCombination SYNTAX RoleCombination
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A role combination. The PEP requires policy for interfaces "A role combination. The PEP requires policy for interfaces
with this role combination and of capability set name with this role combination and of capability set name
specified by frwkIfCapSetRoleComboName." specified by frwkIfCapSetRoleComboName."
::= { frwkIfCapSetRoleComboEntry 3 } ::= { frwkIfCapSetRoleComboEntry 3 }
-- --
-- Interface and Role Combination Table
--
frwkIfCapSetInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkIfCapSetInterfaceEntry
PIB-ACCESS install-notify
STATUS current
DESCRIPTION
Framework Policy Information Base July 2001
"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 }
UNIQUENESS { frwkIfCapSetInterfaceIfIndex,
frwkIfCapSetInterfaceRoles }
::= { frwkIfCapSetInterfaceTable 1 }
FrwkIfCapSetInterfaceEntry ::= SEQUENCE {
frwkIfCapSetInterfacePrid InstanceId,
frwkIfCapSetInterfaceIfIndex InterfaceIndex,
frwkIfCapSetInterfaceRoles RoleCombination
}
frwkIfCapSetInterfacePrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { frwkIfCapSetInterfaceEntry 1 }
frwkIfCapSetInterfaceIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
STATUS current
DESCRIPTION
"The ifIndex value for which this conceptual row provides
policy information via the use of role combination."
::= { frwkIfCapSetInterfaceEntry 2 }
frwkIfCapSetInterfaceRoles OBJECT-TYPE
SYNTAX RoleCombination
STATUS current
Framework Policy Information Base July 2001
DESCRIPTION
"The role combination of a specific interface. This
role combination must exist in frwkIfCapSetRoleComboTable."
::= { frwkIfCapSetInterfaceEntry 3 }
--
-- 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
-- --
frwkBaseFilterTable OBJECT-TYPE frwkBaseFilterTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkBaseFilterEntry SYNTAX SEQUENCE OF FrwkBaseFilterEntry
PIB-ACCESS install PIB-ACCESS install
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Base Filter class. A packet has to match all "The Base Filter class. A packet has to match all
fields in an Filter. Wildcards may be specified for those fields in an Filter. Wildcards may be specified for those
fields that are not relevant." fields that are not relevant."
::= { frwkClassifierClasses 1 } ::= { frwkClassifierClasses 1 }
Framework Policy Information Base March 2001
frwkBaseFilterEntry OBJECT-TYPE frwkBaseFilterEntry OBJECT-TYPE
SYNTAX FrwkBaseFilterEntry SYNTAX FrwkBaseFilterEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of the frwkBaseFilter class." "An instance of the frwkBaseFilter class."
PIB-INDEX { frwkBaseFilterPrid } PIB-INDEX { frwkBaseFilterPrid }
::= { frwkBaseFilterTable 1 } ::= { frwkBaseFilterTable 1 }
skipping to change at page 27, line 29 skipping to change at page 30, line 5
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.
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
skipping to change at page 28, line 5 skipping to change at page 30, line 35
frwkIpFilterTable OBJECT-TYPE frwkIpFilterTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkIpFilterEntry SYNTAX SEQUENCE OF FrwkIpFilterEntry
PIB-ACCESS install PIB-ACCESS install
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Filter definitions. A packet has to match all fields in a "Filter definitions. A packet has to match all fields in a
filter. Wildcards may be specified for those fields that filter. Wildcards may be specified for those fields that
are not relevant." are not relevant."
Framework Policy Information Base March 2001
INSTALL-ERRORS { INSTALL-ERRORS {
invalidDstL4PortData(1), invalidDstL4PortData(1),
invalidSrcL4PortData(2) invalidSrcL4PortData(2)
} }
::= { 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, frwkIpFilterDstAddrType,
frwkIpFilterDstAddr, frwkIpFilterDstAddr,
frwkIpFilterDstAddrMask, frwkIpFilterDstAddrMask,
frwkIpFilterSrcAddrType, frwkIpFilterSrcAddrType,
frwkIpFilterSrcAddr, frwkIpFilterSrcAddr,
frwkIpFilterSrcAddrMask, frwkIpFilterSrcAddrMask,
frwkIpFilterDscp, frwkIpFilterDscp,
frwkIpFilterProtocol, frwkIpFilterProtocol,
frwkIpFilterDstL4PortMin, frwkIpFilterDstL4PortMin,
Framework Policy Information Base July 2001
frwkIpFilterDstL4PortMax, frwkIpFilterDstL4PortMax,
frwkIpFilterSrcL4PortMin, frwkIpFilterSrcL4PortMin,
frwkIpFilterSrcL4PortMax } frwkIpFilterSrcL4PortMax }
::= { frwkIpFilterTable 1 } ::= { frwkIpFilterTable 1 }
FrwkIpFilterEntry ::= SEQUENCE { FrwkIpFilterEntry ::= SEQUENCE {
frwkIpFilterDstAddrType InetAddressType, frwkIpFilterDstAddrType InetAddressType,
frwkIpFilterDstAddr InetAddress, frwkIpFilterDstAddr InetAddress,
frwkIpFilterDstAddrMask Unsigned32, frwkIpFilterDstAddrMask Unsigned32,
skipping to change at page 29, line 5 skipping to change at page 31, line 38
frwkIpFilterDstAddrType OBJECT-TYPE frwkIpFilterDstAddrType 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 destination IP address."
::= { frwkIpFilterEntry 1 } ::= { frwkIpFilterEntry 1 }
Framework Policy Information Base March 2001
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."
::= { frwkIpFilterEntry 2 } ::= { frwkIpFilterEntry 2 }
skipping to change at page 29, line 28 skipping to change at page 32, line 4
SYNTAX Unsigned32 (0..128) SYNTAX Unsigned32 (0..128)
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 frwkIpFilterDstAddrMask bits length. All other bits in the
mask, up to the number needed to fill the length of the mask, up to the number needed to fill the length of the
address frwkIpFilterDstAddr are cleared to zero. A zero bit address frwkIpFilterDstAddr are cleared to zero. A zero bit
in the mask then means that the corresponding bit in the in the mask then means that the corresponding bit in the
Framework Policy Information Base July 2001
address always matches." address always matches."
::= { frwkIpFilterEntry 3 } ::= { frwkIpFilterEntry 3 }
frwkIpFilterSrcAddrType OBJECT-TYPE frwkIpFilterSrcAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type enumeration value to specify the type of "The address type enumeration value to specify the type of
skipping to change at page 30, line 4 skipping to change at page 32, line 35
"The IP address to match against the packet's source IP "The IP address to match against the packet's source IP
address." address."
::= { frwkIpFilterEntry 5 } ::= { frwkIpFilterEntry 5 }
frwkIpFilterSrcAddrMask OBJECT-TYPE frwkIpFilterSrcAddrMask OBJECT-TYPE
SYNTAX Unsigned32 (0..128) SYNTAX Unsigned32 (0..128)
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
Framework Policy Information Base March 2001
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 frwkIpFilterSrcAddrMask bits length. All other bits in the
mask, up to the number needed to fill the length of the mask, up to the number needed to fill the length of the
address frwkIpFilterSrcAddr are cleared to zero. A zero bit address frwkIpFilterSrcAddr are cleared to zero. A zero bit
in the mask then means that the corresponding bit in the in the mask then means that the corresponding bit in the
address always matches." address always matches."
::= { frwkIpFilterEntry 6 } ::= { frwkIpFilterEntry 6 }
skipping to change at page 30, line 29 skipping to change at page 33, line 4
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 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 }
frwkIpFilterDstL4PortMin OBJECT-TYPE frwkIpFilterDstL4PortMin OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
skipping to change at page 31, line 5 skipping to change at page 33, line 35
frwkIpFilterDstL4PortMax OBJECT-TYPE frwkIpFilterDstL4PortMax OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
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."
Framework Policy Information Base March 2001
::= { frwkIpFilterEntry 10 } ::= { frwkIpFilterEntry 10 }
frwkIpFilterSrcL4PortMin OBJECT-TYPE frwkIpFilterSrcL4PortMin OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
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."
skipping to change at page 31, line 29 skipping to change at page 34, line 5
frwkIpFilterSrcL4PortMax OBJECT-TYPE frwkIpFilterSrcL4PortMax OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
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 }
-- --
-- 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.
-- --
skipping to change at page 32, line 4 skipping to change at page 34, line 34
attributes of IEEE 802 (e.g., 802.3) traffic that form attributes of IEEE 802 (e.g., 802.3) traffic that form
filters that are used to perform traffic classification." filters that are used to perform traffic classification."
::= { frwkClassifierClasses 3 } ::= { frwkClassifierClasses 3 }
frwk802FilterEntry OBJECT-TYPE frwk802FilterEntry OBJECT-TYPE
SYNTAX Frwk802FilterEntry SYNTAX Frwk802FilterEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IEEE 802-based filter definitions. An entry specifies "IEEE 802-based filter definitions. An entry specifies
Framework Policy Information Base March 2001
(potentially) several distinct matching components. Each (potentially) several distinct matching components. Each
component is tested against the data in a frame component is tested against the data in a frame
individually. An overall match occurs when all of the individually. An overall match occurs when all of the
individual components match the data they are compared individual components match the data they are compared
against in the frame being processed. A failure of any against in the frame being processed. A failure of any
one test causes the overall match to fail. one test causes the overall match to fail.
Wildcards may be specified for those fields that are not Wildcards may be specified for those fields that are not
relevant." relevant."
skipping to change at page 32, line 30 skipping to change at page 35, 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
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 33, line 5 skipping to change at page 35, line 33
"The 802 address against which the 802 DA of incoming "The 802 address against which the 802 DA of incoming
traffic streams will be compared. Frames whose 802 DA traffic streams will be compared. Frames whose 802 DA
matches the physical address specified by this object, matches the physical address specified by this object,
taking into account address wildcarding as specified by the taking into account address wildcarding as specified by the
frwk802FilterDstAddrMask object, are potentially subject to frwk802FilterDstAddrMask object, are potentially subject to
the processing guidelines that are associated with this the processing guidelines that are associated with this
entry through the related action class." entry through the related action class."
::= { frwk802FilterEntry 1 } ::= { frwk802FilterEntry 1 }
Framework Policy Information Base March 2001
frwk802FilterDstAddrMask OBJECT-TYPE frwk802FilterDstAddrMask OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the bits in a 802 destination address "This object specifies the bits in a 802 destination address
that should be considered when performing a 802 DA that should be considered when performing a 802 DA
comparison against the address specified in the comparison against the address specified in the
frwk802FilterDstAddr object. frwk802FilterDstAddr object.
The value of this object represents a mask that is logically The value of this object represents a mask that is logically
skipping to change at page 33, line 31 skipping to change at page 36, 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
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
subject to the processing guidelines that are associated subject to the processing guidelines that are associated
skipping to change at page 34, line 4 skipping to change at page 36, line 35
"This object specifies the bits in a 802 MAC source address "This object specifies the bits in a 802 MAC source address
that should be considered when performing a 802 MAC SA that should be considered when performing a 802 MAC SA
comparison against the address specified in the comparison against the address specified in the
frwk802FilterSrcAddr object. frwk802FilterSrcAddr object.
The value of this object represents a mask that is logically The value of this object represents a mask that is logically
and'ed with the 802 MAC SA in received frames to derive the and'ed with the 802 MAC SA in received frames to derive the
value to be compared against the frwk802FilterSrcAddr value to be compared against the frwk802FilterSrcAddr
address. A zero bit in the mask thus means that the address. A zero bit in the mask thus means that the
corresponding bit in the address always matches. The corresponding bit in the address always matches. The
Framework Policy Information Base March 2001
frwk802FilterSrcAddr value must also be masked using this frwk802FilterSrcAddr 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 frwk802FilterSrcAddr. Note that a mask with no octets of the frwk802FilterSrcAddr. Note that a mask with no
bits set (i.e., all zeroes) effectively wildcards the bits set (i.e., all zeroes) effectively wildcards the
frwk802FilterSrcAddr object." frwk802FilterSrcAddr object."
::= { frwk802FilterEntry 4 } ::= { frwk802FilterEntry 4 }
skipping to change at page 34, line 29 skipping to change at page 37, line 4
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 }
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)
skipping to change at page 35, line 5 skipping to change at page 37, line 36
containing a VLAN tag with a non-Null VID (i.e., a containing a VLAN tag with a non-Null VID (i.e., a
VID in the range 1..4094) will be considered a match. VID in the range 1..4094) will be considered a match.
A value of 'priorityTaggedPlus(2)' means that only A value of 'priorityTaggedPlus(2)' means that only
frames containing a VLAN tag, regardless of the value frames containing a VLAN tag, regardless of the value
of the VID, will be considered a match. of the VID, will be considered a match.
A value of 'untaggedOnly(3)' indicates that only A value of 'untaggedOnly(3)' indicates that only
untagged frames will match this filter component. untagged frames will match this filter component.
Framework Policy Information Base March 2001
The presence of a VLAN tag is not taken into The presence of a VLAN tag is not taken into
consideration in terms of a match if the value is consideration in terms of a match if the value is
'ignoreTag(4)'." 'ignoreTag(4)'."
::= { frwk802FilterEntry 6 } ::= { frwk802FilterEntry 6 }
frwk802FilterEtherType OBJECT-TYPE frwk802FilterEtherType OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..'ffff'h) SYNTAX Integer32 (-1 | 0..'ffff'h)
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 35, line 29 skipping to change at page 38, line 4
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
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 }
skipping to change at page 36, line 4 skipping to change at page 38, line 36
matchPriority7(7) matchPriority7(7)
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of values, representing the potential range "The set of values, representing the potential range
of user priority values, against which the value contained of user priority values, against which the value contained
in the user priority field of a tagged 802.1 frame is in the user priority field of a tagged 802.1 frame is
compared. A test for equality is performed when determining compared. A test for equality is performed when determining
if a match exists between the data in a data link layer if a match exists between the data in a data link layer
frame and the value of this 802 filter component. Multiple frame and the value of this 802 filter component. Multiple
Framework Policy Information Base March 2001
values may be set at one time such that potentially several values may be set at one time such that potentially several
different user priority values may match this 802 filter different user priority values may match this 802 filter
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
-- --
-- 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 36, line 44 skipping to change at page 39, 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 } frwkIfCapSetRoleComboGroup,
frwkIfCapSetInterfaceGroup }
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 frwkPibIncarnationActive
PIB-MIN-ACCESS notify PIB-MIN-ACCESS notify
DESCRIPTION "Install support is not required." DESCRIPTION "Install support is not required."
Framework Policy Information Base March 2001
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."
::= { frwkBasePibCompliances 1 } ::= { frwkBasePibCompliances 1 }
frwkPrcSupportGroup OBJECT-GROUP frwkPrcSupportGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkPrcSupportSupportedPrc, frwkPrcSupportSupportedPrc,
frwkPrcSupportSupportedAttrs } frwkPrcSupportSupportedAttrs }
STATUS current STATUS current
skipping to change at page 38, line 5 skipping to change at page 40, line 46
OBJECTS { OBJECTS {
frwkDeviceIdDescr, frwkDeviceIdDescr,
frwkDeviceIdMaxMsg, frwkDeviceIdMaxMsg,
frwkDeviceIdMaxContexts } frwkDeviceIdMaxContexts }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkDeviceIdTable." "Objects from the frwkDeviceIdTable."
::= { frwkBasePibGroups 3 } ::= { frwkBasePibGroups 3 }
Framework Policy Information Base March 2001
frwkCompLimitsGroup OBJECT-GROUP frwkCompLimitsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
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 frwkIfCapSetGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkIfCapSetName, frwkIfCapSetName,
frwkIfCapSetCapability } frwkIfCapSetCapability }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkIfCapSetTable." "Objects from the frwkIfCapSetTable."
skipping to change at page 38, line 41 skipping to change at page 41, line 29
frwkIfCapSetRoleComboGroup OBJECT-GROUP frwkIfCapSetRoleComboGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkIfCapSetRoleComboName, frwkIfCapSetRoleComboName,
frwkIfCapSetRoleComboRoles } frwkIfCapSetRoleComboRoles }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkIfCapSetRoleComboTable." "Objects from the frwkIfCapSetRoleComboTable."
::= { frwkBasePibGroups 6 } ::= { frwkBasePibGroups 6 }
frwkIfCapSetInterfaceGroup OBJECT-GROUP
OBJECTS {
frwkIfCapSetInterfaceIfIndex,
frwkIfCapSetInterfaceRoles }
STATUS current
DESCRIPTION
"Objects from the frwkIfCapSetInterfaceTable."
::= { frwkBasePibGroups 7 }
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 7 } ::= { frwkBasePibGroups 8 }
frwkIpFilterGroup OBJECT-GROUP frwkIpFilterGroup OBJECT-GROUP
Framework Policy Information Base March 2001
OBJECTS { OBJECTS {
frwkIpFilterDstAddrType, frwkIpFilterDstAddrType,
frwkIpFilterDstAddr, frwkIpFilterDstAddr,
frwkIpFilterDstAddrMask, frwkIpFilterDstAddrMask,
frwkIpFilterSrcAddrType, frwkIpFilterSrcAddrType,
Framework Policy Information Base July 2001
frwkIpFilterSrcAddr, frwkIpFilterSrcAddr,
frwkIpFilterSrcAddrMask, frwkIpFilterSrcAddrMask,
frwkIpFilterDscp, frwkIpFilterDscp,
frwkIpFilterProtocol, frwkIpFilterProtocol,
frwkIpFilterDstL4PortMin, frwkIpFilterDstL4PortMin,
frwkIpFilterDstL4PortMax, frwkIpFilterDstL4PortMax,
frwkIpFilterSrcL4PortMin, frwkIpFilterSrcL4PortMin,
frwkIpFilterSrcL4PortMax } frwkIpFilterSrcL4PortMax }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkIpFilterTable." "Objects from the frwkIpFilterTable."
::= { frwkBasePibGroups 8 } ::= { frwkBasePibGroups 9 }
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 9 } ::= { frwkBasePibGroups 10 }
END END
Framework Policy Information Base July 2001
7. Security Considerations 7. 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 (read-create). Such objects may
be considered sensitive or vulnerable in some network environments. be considered sensitive or vulnerable in some network environments.
The support for "Install" decisions sent over [COPS-PR] in a non- The support for "Install" decisions sent over [COPS-PR] in a non-
Framework Policy Information Base March 2001
secure environment without proper protection can have a negative secure environment without proper protection can have a negative
effect on network operations. There are a number of provisioning effect on network operations. There are a number of provisioning
classes in this PIB that may contain information that may be classes in this PIB that may contain information that may be
sensitive from a business perspective, in that they may represent a sensitive from a business perspective, in that they may represent a
customer's service contract or the filters that the service provider customer's service contract or the filters that the service provider
chooses to apply to a customer's ingress or egress traffic. There chooses to apply to a customer's ingress or egress traffic. There
are no PRCs that are sensitive in their own right, such as passwords are no PRCs that are sensitive in their own right, such as passwords
or monetary amounts. It may be important to control even or monetary amounts. It may be important to control even
"Notify"(read-only) access to these PRCs and possibly to even "Notify"(read-only) access to these PRCs and possibly to even
encrypt the values of these PRIs when sending them over the network encrypt the values of these PRIs when sending them over the network
skipping to change at page 40, line 45 skipping to change at page 44, line 5
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
Billerica, MA 01821 USA Billerica, MA 01821 USA
Phone: +1 978 288 8175 Phone: +1 978 288 8175
Email: khchan@nortelnetworks.com Email: khchan@nortelnetworks.com
Framework Policy Information Base March 2001
Scott Hahn Scott Hahn
Intel Corp. Intel Corp.
2111 NE 25th Avenue 2111 NE 25th Avenue
Hillsboro, OR 97124 USA Hillsboro, OR 97124 USA
Phone: +1 503 264 8231 Phone: +1 503 264 8231
Email: scott.hahn@intel.com Email: scott.hahn@intel.com
Ravi Sahita Ravi Sahita
Intel Corp. Intel Corp.
2111 NE 25th Avenue 2111 NE 25th Avenue
skipping to change at page 41, line 40 skipping to change at page 45, line 5
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
9. 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," draft-ietf-rap-pr-05.txt, for Policy Provisioning," RFC 3084, March 2001.
October 30, 2000.
[SPPI] [SPPI]
K. McCloghrie, et.al., "Structure of Policy Provisioning K. McCloghrie, M. Fine, J. Seligson, K. Chan, S. Hahn,
Information," draft-ietf-rap-sppi-05.txt, February 2001. R. Sahita, A. Smith, F. Reichmeyer, "Structure of Policy
Provisioning Information," draft-ietf-rap-sppi-07.txt,
Framework Policy Information Base March 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" RFC 2851,
June 2000 June 2000
[IFMIB]
K. McCloghrie, F. Kastenholz, "The Interface Group MIB using
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.
[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
10. Full Copyright 10. Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved. This Copyright (C) The Internet Society (2000). 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
skipping to change at page 43, line 4 skipping to change at page 46, line 31
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
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
Framework Policy Information Base March 2001
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.
Table of Contents Table of Contents
Status of this Memo...............................................1 Status of this Memo...............................................1
1. Glossary.......................................................2 1. Glossary.......................................................2
2. Introduction...................................................2 2. Introduction...................................................2
3. General PIB Concepts...........................................2 3. General PIB Concepts...........................................2
3.1. Roles........................................................2 3.1. Roles........................................................2
3.1.1. An Example.................................................4 3.1.1. An Example.................................................4
3.2. Multiple PIB Instances.......................................5 3.2. Multiple PIB Instances.......................................5
3.3. Reporting of Device Capabilities.............................6 3.3. Reporting and Configuring of Device Capabilities.............6
3.4. Reporting of Device Limitations..............................6 3.4. Reporting of Device Limitations..............................6
4. The Framework Role PIB module..................................7 4. The Framework Role PIB module..................................7
5. Summary of the Framework PIB...................................8 5. Summary of the Framework PIB...................................9
6. The Framework PIB Module......................................11 6. The Framework PIB Module......................................12
7. Security Considerations.......................................39 7. Security Considerations.......................................43
8. Author Information and Acknowledgments........................40 8. Author Information and Acknowledgments........................43
9. References....................................................41 9. References....................................................45
10. Full Copyright...............................................42 10. Full Copyright...............................................46
 End of changes. 

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