Policy-Enabled Path Computation Communication Requirements (draft-bryskin-pce-policy-enabled-path-comp-00.txt )

1
Policy-Enabled Path Computation Communication
Requirements (draft-bryskin-pce-policy-enabled-p
ath-comp-00.txt )
Igor Bryskin (Movaz Networks) ibryskin_at_movaz.com
Dimitri Papadimitriou (Alcatel)
dimitri.papadimitriou_at_alcatel.be
Lou Berger (Movaz Networks) lberger_at_movaz.com
2
Purpose of the document

• Introduce the idea of policy enabled path
  computation
• Outline the framework for such path computation
• Note name change planned

3
Why policies?

• Reason1 Many path computation operations could
  be governed by policies
• User service specific policies to form pc
  requests (to define what constraints should be
  applied)
• PCE specific policies to map requests on PCE
  capabilities (to choose PCE)
• PCC specific policies to choose path
  computation engine and methods to satisfy a
  request
• Domain specific policies to decide what PCE
  information to advertise within a given domain

4
Why policies?

• Reason2 Path computation constraints,
  diversities,
• their relaxations,
  optimization functions
• could be viewed as request specific
  policies
• New path computation capabilities could be
  introduced with changing neither PCE-PCC
  communication and discovery protocols nor PCC
  software
• Existing constraints could be aggregated and
  otherwise associated together, thus, producing
  new more complex constraints

5
Requirements

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

6
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

7
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
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
Next Steps

• Policy Enabled PCE framework document
• Based on presented drafts
• Will assume opaque object support in PC related
  protocols
• Path Computation Policy Information Model
• PCIM sub-model
• Definition of opaque objects

11
Thank You