<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.waters-policy-arch" target="https://datatracker.ietf.org/doc/html/draft-waters-policy-arch-00">
   <front>
      <title>Policy Framework Architecture</title>
      <author initials="G. G." surname="Waters" fullname="Glenn G. Waters">
         <organization>Nortel Networks</organization>
      </author>
      <author initials="L. M." surname="Rafalow" fullname="Lee M. Rafalow">
         <organization>IBM</organization>
      </author>
      <author initials="R. C." surname="Moore" fullname="Dr. Robert C. Moore">
         <organization>IBM</organization>
      </author>
      <author initials="J. S." surname="Wheeler" fullname="Jeffrey S. Wheeler">
         <organization>Nortel Networks</organization>
      </author>
      <author initials="A." surname="Westerinen" fullname="Andrea Westerinen">
         <organization>Microsoft</organization>
      </author>
      <date month="March" day="3" year="1999" />
      <abstract>
	 <t>This document articulates the requirements and basic components of a
   policy-based management architecture.  It focuses on the storage and
   retrieval of policy rules from a directory-based repository, for use
   in the management of network devices.  The architecture is described
   in terms of its functional components and operational characteristics.
   It is intended to be device and vendor independent, interoperable and
   scalable.
 
   There are three basic sections of this draft, addressing:
 
   o the motivation for policy-based management that briefly describes
     the requirements for a policy framework architecture;
 
   o a reference model that defines a first-level functional
     decomposition and captures the key concepts in defining policy
     tools, policy rules, the use of a repository and schema, and the
     mechanisms underlying the definition, storage and retrieval of
     policies; and
 
   o an architecture that describes each of the functional components,
     and includes a narrative about how the architecture will execute.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-waters-policy-arch-00" />
   
</reference>
