1. Policy Modeling in a PBM Architecture 6WIND / Euronetlab olivier.corre@6wind.com vladimir.ksinant@6wind.com

2. Agenda Why the concept of PBM ? Policy and Modeling History of the models CIM DEN WBEM and WIN32 ® Schema PCIM(e) Conclusions Future Work, Q and A

3. Why the concept of PBM ? ISP’s new requirements for value-added services  Increase the Service Management Load. Bad use of network resources  Network must do more and be more flexible. Vendor product cannot easily interoperate  Not the same Management protocols, capabilities, APIs, CLIs …

4. Why the concept of PBM ? (2) Existing solutions :  CLI : complex and platform dependent.  SNMP and MIBs/PIBs : difficult to design, and interoperability hardly offered due to proprietary MIBs/PIBs. Vendors point of view :  Difficulty and cost to be standard compliant,  Will follow the customer demands to go to the standards.  Need of high-level concept for managing the network Solution : POLICY-BASED MANAGEMENT

5. Policy and Modeling [RFC3198] « Policy can be defined from 2 perspectives: - A definite goal, course or method of action to guide and determine present and future decisions. … - Policies as a set of rules to administer, manage and control access to network resources »  separation between low-level network device mechanisms and high-level policy management.

6. Policy and Modeling (2) PBM allows a dynamic and global network management. Global : network as a state machine. The union of all local device states gives the global network state. Dynamic : policy enables network state changing. Reaction to an event. Bidirectional management.

7. Policy and Modeling (3) Policies = tools for provoking changes in the automaton. Policies can be applied in different domains : security, QoS, mobility …  Necessity to have several models for representing appropriate policies. conditionaction POLICY

8. History of Policy Models CIM (DMTF) WBEM (DMTF – Microsoft) DEN (DMTF), J.Strassner CISCO  INTELLIDEN The basic idea is the same than in CIM, but adaptation to a particular context

9. History of Policy Models CIM (DMTF) WBEM (DMTF – Microsoft) DEN (DMTF), J.Strassner CISCO  INTELLIDEN WIN32 ® (Schema Microsoft) PCIM (version 1) (IETF), B.Moore (IBM) J.Strassner (CISCO), Direct instanciation of the CIM Model. Implementation of the class methods.

10. History of Policy Models CIM (DMTF) WBEM (DMTF – Microsoft) DEN (DMTF), J.Strassner CISCO  INTELLIDEN WIN32 ® (Schema Microsoft) PCIM (version 1) (IETF), B.Moore (IBM) J.Strassner (CISCO), ICPM (IETF, Nov. 2001) QPIM (IETF, Nov. 2001) QPLS (IETF, Nov. 2001) QDDIM (IETF, ?) DENng (INTELLIDEN) PCIMe (IETF, Nov. 2001)

11. Common Information Model (CIM) [DMTF] « CIM is an Object-Oriented Model describing the elements and entities in a managed environment, and how they are related to each other. » First designed to model computing systems in an enterprise environment. Now used for systems and network management.

12. Common Information Model (2) 2 components :  Specification : defines details for integration with other management models (SNMP’s MIBs …).  Schema : provides the model description. made up of the Core Model and the Common Model. Core Model : notions applicable to all management areas. Basic framework to derive more specific models. Common Model : notions common to particular management areas (devices, application, …). 12 (inherited) submodels

13. Directory-Enabled Network (DEN) Mapping of CIM, but not derived from. Target : ISP/Telcos and large enterprises. Network Services modeled in a Directory. Global view of the network. Consequence : managing the whole network, and not individual devices. New version : DENng is being designed.

14. WBEM and Win32 ® Schema Web-Based Enterprise Management (WBEM) :  Microsoft initiative  For unifying management of computing systems in enterprise. Provide a set of tools for that (CIM  XML).  Mapping from CIM. WIN32 ® Schema :  Microsoft extension of CIM Schema.  For representing objects existing in a typical WIN32 environment.  Inherited from CIM.

15. Policy Core Information Model (PCIM) Inherited from CIM. Designed by the policy WG of the IETF. Goal : modeling policy information in a network sense. For representing the structure and not the content of a policy. Terminology : objects are called classes, and instaciation of classes are called objects.

16. Policy Core Information Model (2) SLA, guidelines, high-level or human language Device and technology independent Device independent and technology dependent Device and technology dependent. MIB and PIB implementation CIM PCIM QPIM Instanciation of QPIM

17. Policy Core Information Model (3) For that : provide a set of classes and relationships to modelize policy control of managed network. Classes and relationship sufficiently generic to represent policies about anything.  Model derived in specific management area models : QPIM (QoS), ICPM (Security), QPLS (MPLS) … and more to come ! ! ! ! MODEL CHOSEN AS A BASIS TO REPRESENT POLICIES ! ! !

18. Conclusions Business Management Service Management Network and System Management Component and Element Management WBEM PCIM(e) and inherited Models DEN, DENng 6WIND Positioning

19. Future Work Further study of PCIM and PCIMe already done. Study of QPIM, ICPM, QPLS … How to integrate these models in our device ? Prototype and make some feasability and performance tests in Research Project based on the COPS Architecture use. Ideas in concrete form  papers …