Title: QPIM
1QPIM
QoS Policy Information Model draft-ietf-policy-qos
-info-model-02 Yoram Snir Yoram Ramberg John
Strassner Ron Cohen
- 49th IETF San Diego
- Policy WG
2Agenda
- Overview
- Changes from last version
- Examples
- Discussion
3Overview
- 4th version of QPIM
- Extends PCIM
- IntServ DiffServ Policy modeling
- General Policy Use
- DiffServ model can be translated to PIB and MIB
- IntServ model can be enforced using COPS for RSVP
- LDAP mapping to be updated
4Changes made
- Separate between QoS and General PCIM extensions
- Complete Diffserv modeling including PHB modeling
- Remove LDAPism and storage dependent modeling
- Various improvements and changes due to feedback
5General PCIM extensions
- Prefix General Use Classes with gps, attributes
with gp - Variables and Values
- Simple and Compound Conditions
- Policy Containers inc. Decision Strategy
- Meters and Traffic Profiles
6QPIM CLASSES
PCIM QPIM General
7General PCIM extensions
- General Associations and Aggregation to allow
- Building Simple conditions from Variables and
Values - Creation of Compound reusable Conditions
- Building sub-rules
- Reuse of policy groups
- Flexible repository reuse
- Bind Traffic Profiles to Meters
8Diffserv PHB modeling
- Model PHBs using policy rules
- Example
MyDomainPHB group If (EF)
do EF-action If (AF11) do AF11-action
If (AF12) do AF12-action If
(AF13) do AF13-action If (default) do
BE-action
9Diffserv PHB modeling
- Add PHB action
- Add Queue Class
EF-Action DropAlg Tail MaxThrsh
3Pckts
EF-Queue Priority 1 MaxBW 25
AF11-Action DropAlg Red MaxThrsh
20Pckts MinThrsh 4Pckts
AF1x-Queue MinBW 512Kb/s
AF12-Action DropAlg Red MaxThrsh
16Pckts MinThrsh 2Pckts
10Diffserv PHB modeling
- Alternative representation using hierarchy
MyDomainPHB group If (EF)
do EF-action If (AF1x) do AF1x-action
If (AF11) do AF11-action
If (AF12) do AF12-action
If (AF13) do AF13-action If (default)
do BE-action
11Diffserv PHB modeling
- Hierarchical AF PHB modeling
AF1x-Action DropAlg Red
AF1x-Queue MinBW 512Kb/s
AF11-Action MaxThrsh 20Pckts
MinThrsh 4Pckts
AF12-Action MaxThrsh 16Pckts
MinThrsh 2Pckts
12Storage independence
- Object references are modeled as Association and
Aggregations - PolicyVariableInPolicySimpleCondition
- PolicyValueInPolicySimpleCondition
- PolicyConditionInCompoundCondition
- PolicyRuleInPolicyRule
- PolicyGroupInPolicyRule
- PolicyValueConstraintsInVariable
- PolicyElementInPolicyRepository
13Storage independence
- Association and Aggregation Cont.
- PolicyMeterInAction
- PolicyTrfcProfileInMeter
- PolicyQueueInPHBAction
- PolicyConformNextAction
- PolicyExcessNextAction
- PolicyViolateNextAction
14Other additions/Changes
- Add Compound Conditions - Reusable (sub)
conditions.
Values XX-Servers 1.2.33.2,
boo.x.com, 3.3.34 Simple Conditions
XX-ServerTraffic src-ip match
XX-servers Compound Conditions
XXServerApplicationTraffic
XX-ServerTraffic AND XX-ServerAppPorts
15Other additions/Changes
- Compound Conditions Cont.
CompoundCondition conditionListType CNF/DNF
ConditionInCompoundCondition Group 1
NegatedFalse
ConditionInCompoundCondition Group 1
NegatedFalse
PolicyCondition
PolicyCondition
16Other additions/Changes
- PCIM Role A role is a type of attribute that
is used to select one or more policies for a set
of entities and/or components from among a much
larger set of available policies. - The selection process for a role combination
chooses policies associated with the combination
itself, policies associated with each of its
sub-combinations, and policies associated with
each of the individual roles in the
role-combination.
17Other additions/Changes
- Add Role attribute defined in PCIM for a Policy
Rule to gpsPolicyGroup
ServerFarmRules Role server-farm-edge,
server-farm-backup If (xxx) do
aaa If (yyy) do bbb
18Other additions/Changes
- Associate Traffic Profile to Meter (not directly
to action)
TrafficProfile FRCir Rate 64kb/sec
Bc 2000bytes Be 3000bytes
Meter LocalMeter Interval 50msec
ProvisioningAction EdgeAF Mark AF11
ExcessAction Mark AF12 ViolateAction
Mark AF13
19Examples
- Map Policy Rules to Network Configuration
GroupA Role ParisEdge If (UDP)
MinBW 30 If (TFTP) MinBW
10 If (NFS) MinBW 30 If
(TCP) MinBW 60 If (HTTP)
MinBW 40 If (FTP) MinBW 20,
MaxBW 60
20Examples
- Map Policy Rules to Network Configuration
DiffServ MIB representation
21Discussion
- Issues on WG agenda
- QPIMs Conditions vs. CIMs Filters
- Mapping to Diffserv MIB
- WG missing pieces
- Modeling of QoS capabilities
- Binding Roles to entities
- Status
- Questions?
22Condition Modeling Goals
- Extend PCIM
- Extend PolicyCondition
- Use PolicyConditionInPolicyRule aggregation
- Modeling of Variable and Values
- Reusable Values
- Specify Value constraints to Variables
- Add new Variables and Values without changing the
structure of conditions - Add semantics without
changing syntax - Flexible reuse of Conditions
23Mapping to Diffserv MIB
- Diffserv Modeling
- PHB Actions model PHBs
- PR Actions model Diffserv-Edge actions
- Policy Definition oriented
- Three level meters - easier AF policing
- Shaping in PRAction, MaxBW in PHBAction although
implemented by same mechanism in Diffserv-MIB - Separate Traffic Profile from Meter. Allow
reusability of traffic templates - Hierarchical rules instead of forwarding path
binding
24Discussion
- Issues on WG agenda
- QPIMs Conditions vs. CIMs Filters
- Mapping to Diffserv MIB
- WG missing pieces
- Modeling of QoS capabilities
- Binding Roles to entities
- Status
- Questions?
25qosPolicyPRAction
MeterInAction
TrfcProfInMeter
ConformNextAction
ExcessNextAction
ViolateNextAction
26qosPolicyPHBAction
QueuInPHBAction
27qosPolicyRSVPAction
28Rule Processing Order
- Rule 1
- Rule 1.2
- Rule 1.1
- Rule 4
- Rule 3