[rfc-dist] RFC 3703 on Policy Core Lightweight Directory Access Protocol (LDAP) Schema
rfc-editor@rfc-editor.org (rfc-editor@rfc-editor.org) Thu, 26 February 2004 19:49 UTC
From: rfc-editor@rfc-editor.org
Date: Thu, 26 Feb 2004 11:49:20 -0800
Subject: [rfc-dist] RFC 3703 on Policy Core Lightweight Directory Access Protocol (LDAP) Schema
Message-ID: <200402261949.i1QJnKk09926@gamma.isi.edu>
--NextPart A new Request for Comments is now available in online RFC libraries. RFC 3703 Title: Policy Core Lightweight Directory Access Protocol (LDAP) Schema Author(s): J. Strassner, B. Moore, R. Moats, E. Ellesson Status: Standards Track Date: February 2004 Mailbox: john.strassner@intelliden.com, remoore@us.ibm.com, rmoats@lemurnetworks.net, ellesson@mindspring.com Pages: 61 Characters: 142983 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-policy-core-schema-16.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3703.txt 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'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. This document is a product of the Policy Framework Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040226114717.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3703 --OtherAccess Content-Type: Message/External-body; name="rfc3703.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040226114717.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--
- [rfc-dist] RFC 3703 on Policy Core Lightweight Di… rfc-editor@rfc-editor.org