Policy-Enabled%20Path%20Computation%20Framework%20(draft-bryskin-pce-policy-enabled-path-comp-01.txt%20)

1
Policy-Enabled Path Computation
Framework(draft-bryskin-pce-policy-enabled-path-
comp-01.txt )
Igor Bryskin (Movaz Networks) ibryskin_at_movaz.com
Dimitri Papadimitriou (Alcatel)
dimitri.papadimitriou_at_alcatel.be
Lou Berger (LabN Consulting, LLC)
lberger_at_labn.net
2
Changes since IETF64

• Two PCE policy related drafts were presented at
  IETF64
• draft-berger-pce-policy-architecture-0
  0.txt
• draft-bryskin-pce-policy-enabled-path-
  comp-00.txt
• Large piece of the first document was
  incorporated into
• draft-ietf-pce-architecture-04.txt
• The remainder is merged with the second document

3
Status of the document

• The merged document contains
• Background
• motivations, representative scenarios, usage
  cases
• Requirements for policy enabled path computation
  framework
• Policy enabled path computation framework
  components
• Introduction of PCPIM
• Policy application and configuration scenarios
• Inter-component communications
• Name change
• ? Policy-Enabled Path Computation Framework

4
Solution Requirements

• (G)MPLS path computation-specific
• Support for various policies and policy
  configurations
• Provision for Monitoring and Accounting
  Information
• Fault tolerance and recovery
• Support for policy-ignorant nodes
• Scalability
• Security and denial of service considerations
• Reuse of existing policy infrastructures (e.g.
  PCIM) management tools, access and communication
  protocols

5
Path Computation Core Information Model(PCCIM)

• Policy Core Information Model (PCIM) is
  introduced in RFC 3060 and expanded in RFC 3460
• Presents the object-oriented information model
  for representing general policy information
• Defines two hierarchies of object classes
• structural classes representing policy
  information and control of policies
• association classes that indicate how instances
  of the structural classes are related to each
  other
• Classes could be mapped to various concrete
  implementations, for example, to a directory that
  uses LDAPv3 as its access protocol

6
Policy (abstract)
PolicySet (abstract)
PolicyCondition (abstract)
PolicyAction (abstract)
PolicyVariable (abstract)
PolicyValue (abstract)
PolicyGroup
VendorPolicyAction
PolicyExplicitVariable
PolicyRule
SimplePolicyAction
PolicyImplicitVariable
PolicyTimePeriodCondition
CompoundPolicyAction
Sub-tree of more specific classes
VendorPolicyCondition
CompoundPolicyCondition
Sub-tree of more specific classes
SimplePolicyCondition
CompoundFilterCondition
7
Policy Enabled Path Computation Framework
Components

• PC Policy Repository
• PCE Policy Decision Point (PCE-PDP)
• PCE Policy Enforcement Point (PCE-PEP)
• PCC Policy Decision Point (PCC-PDP)
• PCC Policy Enforcement Point (PCC-PEP)
• Policy Communication Protocol
• PCC-PCE Communication Protocol

8
PCC-PCE configurationSingle repository
PC Policy Management
Policy A
Policy B
PC Policy Repository
PCC-PDP
PCE-PDP
e.g. COPS, COPS-PR
e.g. COPS, COPS-PR
PCC-PCE communication protocol
PCC-PEP
PCE-PEP
9
PCC-PCE configurationMultiple repositories
PC Policy Repository 1
PC Policy Repository 2
Policy A
Policy B
PCC-PDP
PCE-PDP
e.g. COPS, COPS-PR
e.g. COPS, COPS-PR
PCC-PCE communication protocol
PCC-PEP
PCE-PEP
10
Policy Application(Policy applied only on PCE)
PC Policy Management
Policy
PC Policy Repository
PCE-PDP
e.g. COPS, COPS-PR
PCC-PCE communication protocol
PCC
PCE-PEP
11
Policy Application (Policy applied only on PCC)
PC Policy Management
Policy
PC Policy Repository
PCC-PDP
e.g. COPS, COPS-PR
PCC-PCE communication protocol
PCC-PEP
PCE
12
Policy Application (Policy applied on PCC and PCE)
PC Policy Management
Policy A
Policy B
PC Policy Repository
PCC-PDP
PCE-PDP
e.g. COPS, COPS-PR
e.g. COPS, COPS-PR
PCC-PCE communication protocol
PCC-PEP
PCE-PEP
13
Next Steps

• Path Computation Policy Information Model
• PCIM sub-model
• Extension of QPIM
• Detailed specification of functions performed by
  each of the framework components
• WG document?

14
Thank You