LDAP Requests for Comments and Drafts
This section provides a list of RFCs that describe the LDAP protocol and its extensions. All RFCs are available from the IETF Web site (http://www.ietf.org/rfc.html). You can also get an up-to-date list of all available RFCs at http://www.ietf.org/iesg/lrfc_index.txt. The Internet FAQ Consortium has a very useful Web site (http://isc.faqs.org), which offers FAQs, Internet RFCs, and Internet-Drafts (available in PDF format). This site also offers a complete and updated list of RFCs. Both sites also offer search engines to search for the RFC addressing the subject you are interested in. We will discuss the RFCs that address the LDAP protocol.
This section is divided into two parts. The first part shows you the RFCs relevant for work with LDAP, the ones defining the actual standard used. I have described these RFCs for your convenience. The second part lists all RFCs relevant for LDAP. I attached this list because it is interesting to see how the concepts have evolved over time; the list will help you to better understand what is happening behind the scenes and how the LDAP protocol got to its actual definition.
The list reflects all RFCs at the time this book was written and may not be complete because RFCs are subject to continuous update. You will need to look at the RFC site from time to time to get the updated version of the RFC list.
Comments about the Most Important LDAP RFCs
RFC3377: “Lightweight Directory Access Protocol (v3): Technical Specification”: Defines the set of RFCs comprising the Directory Access Protocol v3.
RFC2251: “Lightweight Directory Access Protocol (v3)”: Defines the protocol itself, particularly the specification of what really travels on the wire. This is the heart of the LDAP RFCs.
RFC2252: “Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions”: Describes the syntax of attribute definitions and contains a list of attributes a server should implement. It classifies the different attribute types that LDAP knows and lists the standard matching rules to use in comparisons. It also describes how the attribute values should be encoded into strings to be transmitted over the wire.
RFC2253: “Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names”: The LDAP protocol transmits messages in the form of strings; however, Distinguished Names can contain characters that have to be converted before transmission. Examples are reserved characters or language-specific characters. This RFC describes how Distinguished Names are converted into string and how strings are converted back into Distinguished Names.
RFC2254: “The String Representation of LDAP Search Filters”: This RFC replaces RFC1960, extending the string filter definition. It defines the syntax of a filter expression and how to convert a filter in a string expression.
RFC2255: “The LDAP URL Format”: The URL format of an LDAP search can be used in every Web browser. This URL defines the syntax of the URL format. It also defines how a client should parse and resolve the LDAP URL to a search expression.
RFC2256: “A Summary of the X.500 User Schema for Use with LDAPv3”: LDAP inherits a large part of the schema of X.500. This RFC defines a set of object classes and attribute types that should be implemented in a directory server.
RFC2829: “Authentication Methods for LDAP”: The first LDAP RFCs did not specify anything about authentication. This RFC specifies which authentication methods should be implemented in an LDAP server.
RFC2830: “Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security”: TLS is defined as a so-called extended operation in LDAP. This RFC describes how to establish a TLS session using the LDAP protocol.
■ 1107 Plan for Internet Directory Services. K.R. Sollins. Jul-01-1989. (Format: TXT=51773 bytes) (Status: Informational)
■ 1202 Directory Assistance Service. M.T. Rose. Feb-01-1991. (Format: TXT=2l645 bytes) (Status: Informational)
■ 1249 DIXIE Protocol Specification. T. Howes, M. Smith, B. Beecher. Aug-01-1991. (Format: TXT=20028 bytes) (Also RFC1202) (Status: Informational)
■ 1274 The COSINE and Internet X.500 Schema. P. Barker, S. Kille. November 1991. (Format: TXT=92827 bytes) (Status: Proposed Standard)
■ 1275 Replication Requirements to Provide an Internet Directory Using X.500. S.E. Hardcastle-Kille. November 1991. (Format: TXT=46l6, PS=83736, PDF=62498 bytes) (Status: Informational)
■ 1276 Replication and Distributed Operations Extensions to Provide an Internet Directory Using X.500. S.E. Hardcastle-Kille. November 1991. (Format: TXT=33731, PS=217170 bytes) (Status: Proposed Standard)
■ 1279 X.500 and Domains. S.E. Hardcastle-Kille. November 1991. (Format: TXT=26669, PS=170029 bytes) (Status: Experimental)
■ 1292 A Catalog of Available X.500 Implementations. R. Lang, R. Wright. January 1992. (Format: TXT=129468 bytes) (Obsoleted by RFC1632) (Status: Informational)
■ 1308 Executive Introduction to Directory Services Using the X.500 Protocol. C. Weider, J. Reynolds. March 1992. (Format: TXT=9392 bytes) (Also FYI0013) (Status: Informational)
■ 1309 Technical Overview of Directory Services Using the X.500 Protocol. C. Weider, J. Reynolds, S. Heker. March 1992. (Format: TXT=35694 bytes) (Also FYI0014) (Status: Informational)
■ 1330 Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESNET Community. ESCC X.500/X.400 Task Force, ESnet Site Coordinating Committee (ESCC), Energy Sciences Network (ESnet). May 1992. (Format: TXT= 192925 bytes) (Status: Informational)
■ 1430 A Strategic Plan for Deploying an Internet X.500 Directory Service. S. Hardcastle-Kille, E. Huizer, V. Cerf, R. Hobby, S. Kent. February 1993. (Format: TXT=47587 bytes) (Status: Informational)
■ 1484 Using the OSI Directory to Achieve User-Friendly Naming (OSI-DS 24 (vl.2)). S. Hardcastle-Kille. July 1993. (Format: TXT=48974 bytes) (Obsoleted by RFC1781, RFC3494) (Status: Experimental)
■ 1485 A String Representation of Distinguished Names (OSI-DS 23 (v5)). S. Hardcastle-Kille. July 1993. (Format: TXT=11158 bytes) (Obsoleted by RFC1779, RFC3494) (Status: Proposed Standard)
■ 1487 X.500 Lightweight Directory Access Protocol. W. Yeong, T. Howes, S. Kille. July 1993. (Format: TXT=44947 bytes) (Obsoleted by RFC1777, RFC3494) (Status: Proposed Standard)
■ 1488 The X.500 String Representation of Standard Attribute Syntaxes. T. Howes, S. Kille, W. Yeong, C. Robbins. July 1993. (Format: TXT=17182 bytes) (Obsoleted by RFC1778) (Status: Proposed Standard)
■ 1558 A String Representation of LDAP Search Filters. T. Howes. December 1993. (Format: TXT=5239 bytes) (Obsoleted by RFC1960) (Status: Informational)
■ 1562 Naming Guidelines for the AARNet X.500 Directory Service. G. Michaelson, M. Prior. December 1993. (Format: TXT=6884 bytes) (Status: Informational)
■ 1564 DSA Metrics (OSI-DS 34 (v3)). P. Barker, R. Hedberg. January 1994. (Format: TXT=46205 bytes) (Status: Informational)
■ 1567 X.500 Directory Monitoring MIB. G. Mansfield, S. Kille. January 1994. (Format: TXT=33527 bytes) (Obsoleted by RFC2605) (Status: Proposed Standard)
■ 1608 Representing IP Information in the X.500 Directory. T. Johannsen, G. Mansfield, M. Kosters, S. Sataluri. March 1994. (Format: TXT=40269 bytes) (Status: Experimental)
■ 1609 Charting Networks in the X.500 Directory. G. Mansfield, T. Johannsen, M. Knopper. March 1994. (Format: TXT=30044 bytes) (Status: Experimental)
■ 1617 Naming and Structuring Guidelines for X.500 Directory Pilots. P. Barker, S. Kille, T. Lenggenhager. May 1994. (Format: TXT=56739 bytes) (Obsoletes RFC1384) (Status: Informational)
■ 1632 A Revised Catalog of Available X.500 Implementations. A. Getchell, S. Sataluri, Eds. May 1994. (Format: TXT=124lll bytes) (Obsoletes RFC1292) (Obsoleted by RFC2116) (Status: Informational)
■ 1684 Introduction to White Pages Services Based on X.500. P. Jurg. August 1994. (Format: TXT=22985 bytes) (Status: Informational)
■ 1777 Lightweight Directory Access Protocol. W. Yeong, T. Howes, S. Kille. March 1995. (Format: TXT=45459 bytes) (Obsoletes RFC1487) (Obsoleted by RFC3494) (Status: Historic)
■ 1778 The String Representation of Standard Attribute Syntaxes. T. Howes, S. Kille, W. Yeong, C. Robbins. March 1995. (Format: TXT= 19053 bytes) (Obsoletes RFC1488) (Obsoleted by RFC3494) (Updated by RFC2559) (Status: Historic)
■ 1779 A String Representation of Distinguished Names. S. Kille. March 1995. (Format: TXT=12429 bytes) (Obsoletes RFC1485) (Obsoleted by RFC2253, RFC3494) (Status: Historic)
■ 1781 Using the OSI Directory to Achieve User-Friendly Naming. S. Kille. March 1995. (Format: TXT=47129 bytes) (Obsoletes RFC1484) (Obsoleted by RFC3494) (Status: Historic)
■ 1798 Connection-less Lightweight X.500 Directory Access Protocol. A. Young. June 1995. (Format: TXT=18548 bytes) (Obsoleted by RFC3352) (Status: Historic)
■ 1801 MHS Use of the X.500 Directory to Support MHS Routing. S. Kille. June 1995. (Format: TXT=156462 bytes) (Status: Experimental)
■ 1802 Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing. H. Alvestrand, K. Jordan, S. Langlois, J. Romaguera. June 1995. (Format: TXT=24637 bytes) (Status: Informational)
■ 1803 Recommendations for an X.500 Production Directory Service. R. Wright, A. Getchell, T. Howes, S. Sataluri, P. Yee, W. Yeong. June 1995. (Format: TXT=l4721 bytes) (Status: Informational)
■ 1804 Schema Publishing in X.500 Directory. G. Mansfield, P. Rajeev, S. Raghavan, T. Howes. June 1995. (Format: TXT=18268 bytes) (Status: Experimental)
■ 1823 The LDAP Application Program Interface. T. Howes, M. Smith. August 1995. (Format: TXT=41081 bytes) (Status: Informational)
■ 1836 Representing the O/R Address Hierarchy in the X.500 Directory Information Tree. S. Kille. August 1995. (Format: TXT=20175 bytes) (Obsoleted by RFC2294) (Status: Experimental)
■ 1837 Representing Tables and Subtrees in the X.500 Directory. S. Kille. August 1995. (Format: TXT=10924 bytes) (Obsoleted by RFC2293) (Status: Experimental)
■ 1838 Use of the X.500 Directory to Support Mapping between X.400 and RFC 822 Addresses. S. Kille. August 1995. (Format: TXT=122l6 bytes) (Obsoleted by RFC2164) (Status: Experimental)
■ 1943 Building an X.500 Directory Service in the U.S. B. Jennings. May 1996. (Format: TXT=51266 bytes) (Status: Informational)
■ 1959 An LDAP URL Format. T. Howes, M. Smith. June 1996. (Format: TXT=7243 bytes) (Obsoleted by RFC2255) (Status: Proposed Standard)
■ I960 A String Representation of LDAP Search Filters. T. Howes. June 1996. (Format: TXT=5288 bytes) (Obsoletes RFC1558) (Obsoleted by RFC2254) (Status: Proposed Standard)
■ 2010 Operational Criteria for Root Name Servers. B. Manning, P. Vixie. October 1996. (Format: TXT=14870 bytes) (Obsoleted by RFC2870) (Status: Informational)
■ 2079 Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs). M. Smith. January 1997. (Format: TXT=8757 bytes) (Status: Proposed Standard)
■ 2120 Managing the X.500 Root Naming Context. D. Chadwick. March 1997. (Format: TXT=30773 bytes) (Status: Experimental)
■ 2164 Use of an X. 500/LDAP Directory to Support MIXER Address Mapping. S. Kille. January 1998. (Format: TXT=l6701 bytes) (Obsoletes RFC1838) (Status: Proposed Standard)
■ 2247 Using Domains in LDAP/X.500 Distinguished Names. S. Kille, M. Wahl, A. Grimstad, R. Huber, S. Sataluri. January 1998. (Format: TXT= 12411 bytes) (Status: Proposed Standard)
■ 2251 Lightweight Directory Access Protocol (v3). M. Wahl, T. Howes, S. Kille. December 1997. (Format: TXT=114488 bytes) (Updated by RFC3377) (Status: Proposed Standard)
■ 2252 Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions. M. Wahl, A. Coulbeck, T. Howes, S. Kille. December 1997. (Format: TXT=60204 bytes) (Updated by RFC3377) (Status: Proposed Standard)
■ 2253 Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names. M. Wahl, S. Kille, T. Howes. December 1997. (Format: TXT=18226 bytes) (Obsoletes RFC1779) (Updated by RFC3377) (Status: Proposed Standard)
■ 2254 The String Representation of LDAP Search Filters. T. Howes. December 1997. (Format: TXT=13511 bytes) (Obsoletes RFC1960) (Updated by RFC3377) (Status: Proposed Standard)
■ 2255 The LDAP URL Format. T. Howes, M. Smith. December 1997. (Format: TXT=20685 bytes) (Obsoletes RFC1959) (Updated by RFC3377) (Status: Proposed Standard)
■ 2256 A Summary of the X.500(96) User Schema for Use with LDAPv3. M. Wahl. December 1997. (Format: TXT=32377 bytes) (Updated by RFC3377) (Status: Proposed Standard)
■ 2293 Representing Tables and Subtrees in the X.500 Directory. S. Kille. March 1998. (Format: TXT=12539 bytes) (Obsoletes RFC1837) (Status: Proposed Standard)
■ 2294 Representing the O/R Address Hierarchy in the X.500 Directory Information Tree. S. Kille. March 1998. (Format: TXT=22059 bytes) (Obsoletes RFC1836) (Status: Proposed Standard)
■ 2307 An Approach for Using LDAP as a Network Information Service. L. Howard. March 1998. (Format: TXT=41396 bytes) (Status: Experimental)
■ 2377 Naming Plan for Internet Directory-Enabled Applications. A. Grimstad, R. Huber, S. Sataluri, M. Wahl. September 1998. (Format: TXT=38274 bytes) (Status: Informational)
■ 2425 A MIME Content-Type for Directory Information. T. Howes, M. Smith, F. Dawson. September 1998. (Format: TXT=64478 bytes) (Status: Proposed Standard)
■ 2426 vCard MIME Directory Profile. F. Dawson, T. Howes. September 1998. (Format: TXT=74646 bytes) (Status: Proposed Standard)
■ 2517 Building Directories from DNS: Experiences from WWW-Seeker. R. Moats, R. Huber. February 1999. (Format: TXT=14001 bytes) (Status: Informational)
■ 2589 Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services. Y. Yaacovi, M. Wahl, T. Genovese. May 1999. (Format: TXT=26855 bytes) (Status: Proposed Standard)
■ 2596 Use of Language Codes in LDAP. M. Wahl, T. Howes. May 1999. (Format: TXT=17413 bytes) (Status: Proposed Standard)
■ 2605 Directory Server Monitoring MIB. G. Mansfield, S. Kille. June 1999. (Format: TXT=49l66 bytes) (Obsoletes RFC1567) (Status: Proposed Standard)
■ 2649 An LDAP Control and Schema for Holding Operation Signatures. B. Greenblatt, P. Richard. August 1999. (Format: TXT=20470 bytes) (Status: Experimental)
■ 2657 LDAPv2 Client vs. the Index Mesh. R. Hedberg. August 1999. (Format: TXT=19251 bytes) (Status: Experimental)
■ 2696 LDAP Control Extension for Simple Paged Results Manipulation. C. Weider, A. Herron, A. Anantha, T. Howes. September 1999. (Format: TXT= 12809 bytes) (Status: Informational)
■ 2713 Schema for Representing Java(™) Objects in an LDAP Directory. V. Ryan, S. Seligman, R. Lee. October 1999. (Format: TXT=40745 bytes) (Status: Informational)
■ 2798 Definition of the inetOrgPerson LDAP Object Class. M. Smith. April 2000. (Format: TXT=32929 bytes) (Status: Informational)
■ 2820 Access Control Requirements for LDAP. E. Stokes, D. Byrne, B. Blakley, P. Behera. May 2000. (Format: TXT=18172 bytes) (Status: Informational)
■ 2829 Authentication Methods for LDAP. M. Wahl, H. Alvestrand, J. Hodges, R. Morgan. May 2000. (Format: TXT=33471 bytes) (Updated by RFC3377) (Status: Proposed Standard)
■ 2830 Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security. J. Hodges, R. Morgan, M. Wahl. May 2000. (Format: TXT=24469 bytes) (Updated by RFC3377) (Status: Proposed Standard)
■ 2849 The LDAP Data Interchange Format (LDIF) — Technical Specification. G. Good. June 2000. (Format: TXT=26017 bytes) (Status: Proposed Standard)
■ 2891 LDAP Control Extension for Server Side Sorting of Search Results. T. Howes, M. Wahl, A. Anantha. August 2000. (Format: TXT= 15833 bytes) (Status: Proposed Standard)
■ 2926 Conversion of LDAP Schemas to and from SLP Templates. J. Kempf, R. Moats, P. St. Pierre. September 2000. (Format: TXT=55365 bytes) (Status: Informational)
■ 2927 MIME Directory Profile for LDAP Schema. M. Wahl. September 2000. (Format: TXT=l6l22 bytes) (Status: Informational)
■ 2967 TISDAG — Technical Infrastructure for Swedish Directory Access Gateways. L. Daigle, R. Hedberg. October 2000. (Format: TXT=209845 bytes) (Status: Informational)
■ 2968 Mesh of Multiple DAG Servers — Results from TISDAG. L. Daigle, T. Eklof. October 2000. (Format: TXT=19306 bytes) (Status: Informational)
■ 2969 Wide Area Directory Deployment — Experiences from TISDAG. T. Eklof, L. Daigle. October 2000. (Format: TXT=43002 bytes) (Status: Informational)
■ 2970 Architecture for Integrated Directory Services — Result from TISDAG. L. Daigle, T. Eklof. October 2000. (Format: TXT=40448 bytes) (Status: Informational)
■ 3045 Storing Vendor Information in the LDAP Root DSE. M. Meredith. January 2001. (Format: TXT=10518 bytes) (Status: Informational)
■ 3062 LDAP Password Modify Extended Operation. K. Zeilenga. February 2001. (Format: TXT=11807 bytes) (Status: Proposed Standard)
■ 3088 OpenLDAP Root Service: An Experimental LDAP Referral Service. K. Zeilenga. April 2001. (Format: TXT=19471 bytes) (Status: Experimental)
■ 3112 LDAP Authentication Password Schema. K. Zeilenga. May 2001. (Format: TXT=171l6 bytes) (Status: Informational)
■ 3296 Named Subordinate References in Lightweight Directory Access Protocol (LDAP) Directories. K. Zeilenga. July 2002. (Format: TXT=27389 bytes) (Status: Proposed Standard)
■ 3352 Connection-less Lightweight Directory Access Protocol (CLDAP) to Historic Status. K. Zeilenga. March 2003. (Format: TXT=7265 bytes) (Obsoletes RFC1798) (Status: Informational)
■ 3377 Lightweight Directory Access Protocol (v3): Technical Specification. J. Hodges, R. Morgan. September 2002. (Format: TXT=9981 bytes) (Updates RFC2251-RFC2256, RFC2829, RFC2830) (Status: Proposed Standard)
■ 3383 Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP). K. Zeilenga. September 2002. (Format: TXT=45893 bytes) (Also BCP0064) (Status: Best Current Practice)
■ 3384 Lightweight Directory Access Protocol (version 3) Replication Requirements. E. Stokes, R. Weiser, R. Moats, R. Huber. October 2002. (Format: TXT=66871 bytes) (Status: Informational)
■ 3494 Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status. K. Zeilenga. March 2003. (Format: TXT=9225 bytes) (Obsoletes RFC1484, RFC1485, RFC1487, RFC 1777-RFC1779, RFC1781, RFC2559) (Status: Informational)
In Chapter 4 of this book, I explained in detail the work on the LDAP protocol that is underway and the standardization of the LDAP protocol by various Working Groups. There are still a number of topics that are not yet standardized, e.g., the replication protocol. This section is intended mainly to complete the list of RFCs with the drafts. It contains the description of the Working Group as it appears on the Web site.
At the time of this writing, there are two Working Groups hosted on the IETF Web site (http://www.ietf.org): LDAP (v3) Revision (ldapbis) and LDAP Duplication/Replication/Update Protocols (ldup). There had been a third Working Group dealing with LDAP extensions (ldapext), but it has been closed. However, the mailing list of ldapext is still alive, and you can subscribe to it.
I will give you a short description of what each of these groups is doing; for more information, visit the IETF Web site at http://www.ietf.org/html.charters/wg-dir.html.
All Internet-Drafts are available via ftp access from the following sites:
IETF |
ftp://ftp.ietf.org/internet-drafts |
Africa |
ftp://ftp.is.co.za/internet-drafts |
Canada |
ftp://ftp.normos.org/ietf/internet-drafts |
Sweden |
ftp://ftp.nordu.net/internet-drafts |
Italy |
ftp://ftp.nic.it/internet-drafts |
Pacific |
Rim ftp://munnari.oz.au/internet-drafts |
U.S. West Coast |
ftp://ftp.isi.edu/internet-drafts |
The work of this group is based on RFCs 2251-2256 and RFCs 2829-2831, which have been published on the IETF Web site recently. The objective is a revision of these RFCs and a publication of the revised work in the form of a Draft Standard. At the time of this writing, the Working Group has just delivered two RFCs:
1. RFC3377 “Lightweight Directory Access Protocol (v3): Technical Specification”
2. RFC3383 “Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)”
Following is a list of valid RFCs (at the time of this writing):
LDAP: String Representation of Distinguished Names
LDAP: The Protocol
LDAP: String Representation of Search Filters
LDAP: Authentication Methods and Connection Level Security Mechanism
LDAP: Uniform Resource Locator
LDAP: Schema for User Applications
LDAP: Syntaxes and Matching Rules
LDAP: Technical Specification Road Map
LDAP: Directory Information Models
LDAP: Internationalized String Preparation
IANA: Considerations for LDAP
I did not include the URLs because these drafts will be updated; for more information, go to the Working Group’s Web site (http://www.ietf.org/html.charters/ldapbis-charter.html). The Working Group also maintains a mailing list, which you can subscribe to by sending an e-mail to [email protected]. Be sure to type “Subscribe” in the Subject line of the e-mail.
LDAP Duplication/Replication/Update Protocols (Idup)
The work of this team originally was to address issues on multi-master and master-slave replication, and therefore depended on the work of another Working Group exploring questions of access control. This team, however, failed to reach consensus, and therefore the objective of the Working Group changed. Due to the lack of an access control model, the Working Group decided to release an experimental rather than a standard protocol. The Working Group identified the following issues to be defined:
LDAPv3 Replication Architecture: This documents a generalpurpose LDAPv3 replication architecture, defines key components of this architecture, describes how these key components functionally behave, and describes how these components interact with each other when in various modes of operation. LDAPv3 Replication Information Model: Defines the schema and semantics of information used to operate, administer, maintain, and provision replication between LDAPv3 servers. Specifically, this document will contain common schema specifications intended to facilitate interoperable implementations with respect to:
■ Replication agreements
■ Consistency models
■ Replication topologies
■ Managing deleted objects and their states
■ Administration and management
LDAPv3 Replication Information Transport Protocol: LDAPv3 extended operation and control specifications required to allow LDAPv3 to be used as the transport protocol for information being replicated.
LDAPv3 Replica Management: Specifications designed to support administration, maintenance, and provisioning of replicas and replication agreements. These specifications may take the form of definitions for LDAPv3 extended operations, controls, and new schema elements.
LDAPv3 Update Reconciliation Procedures: Procedures for detection and resolution of conflicts between the state of multiple replicas that contain information from the same unit of replication.
A General Usage Profile of the LDAPv3 Replication Architecture, Information Model, Protocol Extensions, and Update Reconciliation Procedures.
LDAPv3 Client Update: A protocol that enables an LDAP client to synchronize with the content of a directory information tree (DIT) stored by an LDAP server and to be notified about the changes to that content.
The Working Group released RFC3384 “Lightweight Directory Access Protocol (version 3) Replication Requirements,” which can be found at the Working Group’s Web site (http://www.ietf.org/html.charters/ldup-charter.html). There is also a mailing list, which you can subscribe to by sending an e-mail to [email protected]; be sure to type “Subscribe” in the Subject line of the e-mail.