1. Policy Framework Status aaaarch mtg, irtf, Aug. 2, 2000 Ed Ellesson co-chairs of policy framework wg: Ed Ellesson: ed_ellesson@tivoli.com John Strassner: johns@cisco.com

2. Overview Objectives Influences Framework Policy Core Information Model Status

3. Objectives Facilitate logically central administration by humans for a given policy domain Drive policy-based configuration of collections of systems/devices –Must map to lower level configuration models –Must scale to thousands of managed entities Produce effect of cooperation –among multiple heterogeneous managed entities –aggregated behavior with desired end-to-end characteristics Protocol, device and vendor independence

4. Influences IETF –Policy Framework Working Group Participants –DiffServ, IntServ, IPSEC, RAP/COPS/PIB, RSVP, IPSP, LDAPext, SNMP/MIB, DHCP, etc. –New potential influences: MPLS, VPN’s DMTF –CIM 2.3 Schema and earlier –WG’s: Network, User, SysDev, SLA, User, Applications, etc. DEN –pre-standard ad-hoc committee

5. Framework Picture is in common with rap: –Management Tool –Policy Repository (Focus of policy wg is here) –Policy Decision Point –Policy Enforcement Point Levels of Abstraction –SLA (Service Level Agreements) –SLO (Service Level Objectives) –Policy (Rules) –Configured Device Level

6. Basic Policy Classes

7. Policy Deliverables/Status Policy Core Info Model (-07) in last call in IESG PCIM mapped to directory representation to be updated and advanced dependent on above (-07) First worked example (QOS) Policy in -01 draft QOS device model in -01 draft, and being reconciled with mibs/pibs/conceptual model Policy terminology draft being distributed for review by policy-related wg’s Non-chartered drafts in other areas: mpls, ipsec, vpn’s, sls framework draft on hold for terminology agreement