A Configuration Profile Schema for Lightweight Directory Access Protocol -Based Agents
RFC 4876, “A Configuration Profile Schema for Lightweight Directory Access Protocol -Based Agents”, is an Informational document published in May 2007 by B. Neal-Joslin, L. Howard, M. Ansari. The canonical text is published by the RFC Editor.
Abstract
This document consists of two primary components, a schema for agents that make use of the Lightweight Directory Access protocol (LDAP) and a proposed use case of that schema, for distributed configuration of similar directory user agents. A set of attribute types and an object class are proposed. In the proposed use case, directory user agents (DUAs) can use this schema to determine directory data location and access parameters for specific services they support. In addition, in the proposed use case, attribute and object class mapping allows DUAs to reconfigure their expected (default) schema to match that of the end user's environment. This document is intended to be a skeleton for future documents that describe configuration of specific DUA services. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 4876 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4875 Extensions to Resource Reservation Protocol - Traffic Engineering for Point-to-Multipoint TE Label Switched Paths
- RFC 4877 Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture
- RFC 4874 Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering
- RFC 4878 Definitions and Managed Objects for Operations, Administration, and Maintenance Functions on Ethernet-Like Interfaces
- RFC 4873 GMPLS Segment Recovery
- RFC 4879 Clarification of the Third Party Disclosure Procedure in RFC 3979
- RFC 4872 RSVP-TE Extensions in Support of End-to-End Generalized Multi- Protocol Label Switching Recovery
- RFC 4880 OpenPGP Message Format