Subject: Core LDAP Specifications
Author: SteveHB
Posted on: 06/12/2006 06:13:00 PM
The core LDAP protocol is defined in the following RFC's
X.500 Directory Access Protocol (DAP)
ISO (http://www.iso.org) and ITU-T (http://www.itu.org)
X.500, the directory Access Protocol (DAP) by ITU-T (X.500) and also ISO (ISO/IEC 9594), is a standard way to develop an electronic directory of people in an organization so that it can be part of a global directory available to anyone in the world with Internet access.
In the X.500 directory architecture, the client queries and receives responses from one or more servers in the server Directory Service with the Directory Access Protocol(DAP) controlling the communication between the client and the server
RFC-1777 Lightweight Directory Access Protocol (v2)
http://www.ietf.org/rfc/rfc1777.txt
The protocol described in this document is designed to provide access to directories supporting the X.500 models, while not incurring the resource requirements of the X.500 Directory Access Protocol (DAP). This protocol is specifically targeted at management applications and browser applications that provide read/write interactive access to directories. When used with a directory supporting the X.500 protocols, it is intended to be a complement to the X.500 DAP.
RFC-2252 LDAPv3 Attribute Syntax Definitions
http://www.ietf.org/rfc/rfc2252.txt
The LDAP requires that the contents of AttributeValue fields in protocol elements be octet strings. This document defines a set of syntaxes for LDAPv3, and the rules by which attribute values of these syntaxes are represented as octet strings for transmission in the LDAP protocol. The syntaxes defined in this document are referenced by this and other documents that define attribute types. This document also defines the set of attribute types which LDAP servers should support.
RFC-2253 UTF-8 String Representation of Distinguished Names
http://www.ietf.org/rfc/rfc2253.txt
The X.500 Directory uses distinguished names as the primary keys to entries in the directory. Distinguished Names are encoded in ASN.1 in the X.500 Directory protocols. In the LDAP, a string representation of distinguished names is transferred. This specification defines the string format for representing names, which is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name.
RFC-2254 The String Representation of LDAP Search Filters
http://www.ietf.org/rfc/rfc2254.txt
The LDAP defines a network representation of a search filter transmitted to an LDAP server. Some applications may find it useful to have a common way of representing these search filters in a human-readable form. This document defines a human-readable string format for representing LDAP search filters. This document replaces RFC 1960, extending the string LDAP filter definition to include support for LDAPv3 extended match filters.
RFC-2255 The LDAP URL Format
http://www.ietf.org/rfc/rfc2255.txt
This document describes a format for an LDAP Uniform Resource Locator, and describes an LDAP search operation performed to retrieve information from an LDAP directory. It updates the LDAP URL format for LDAPv3. This document also defines a second URL scheme prefix for LDAP running over the TLS protocol.
RFC-2256 A Summary of the X.500(96) User Schema for use with LDAPv3
http://www.ietf.org/rfc/rfc2256.txt
This document provides an overview of the attribute types and object classes defined by the ISO and ITU-T committees in the X.500 documents, in particular those intended for use by directory clients. This is the most widely used schema for LDAP/X.500 directories, and many other schema definitions for white pages objects use it as a basis. This document does not cover attributes used for the administration of X.500 directory servers, nor does it include attributes defined
References:
