<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-policy-core-schema" target="https://datatracker.ietf.org/doc/html/draft-ietf-policy-core-schema-16">
   <front>
      <title>Policy Core Lightweight Directory Access Protocol (LDAP) Schema</title>
      <author initials="E. J." surname="Ellesson" fullname="Ed J. Ellesson">
         </author>
      <author initials="R. C." surname="Moore" fullname="Dr. Robert C. Moore">
         <organization>IBM Corporation</organization>
      </author>
      <author initials="R." surname="Moats" fullname="Ryan Moats">
         <organization>Lemur Networks</organization>
      </author>
      <author initials="J." surname="Strassner" fullname="John Strassner">
         <organization>Intelliden Corporation</organization>
      </author>
      <date month="October" day="11" year="2002" />
      <abstract>
	 <t>This document defines a mapping of the Policy Core Information Model to a form that can be implemented in a directory that uses Lightweight Directory Access Protocol (LDAP) as its access protocol.  This model defines two hierarchies of object classes: structural classes representing information for representing and controlling policy data as specified in RFC 3060, and relationship classes that indicate how instances of the structural classes are related to each other.  Classes are also added to the LDAP schema to improve the performance of a client&#x27;s interactions with an LDAP server when the client is retrieving large amounts of policy-related information.  These classes exist only to optimize LDAP retrievals: there are no classes in the information model that correspond to them. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-policy-core-schema-16" />
   
</reference>
