Skip to main content

Lightweight Directory Access Protocol (version 3) Replication Requirements

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3384.
Authors Ryan Moats , Ellen Stokes , Dr. Rick Huber , Russel F. Weiser
Last updated 2015-10-14 (Latest revision 2002-04-01)
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3384 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Patrik Fältström
IESG note Allison:It requires minimum Mandatory-to-implement encryption, but fails to do same for integrity. It needs a statement that avoidance of congestion and over-chattiness of the replication protocol must be considered in the Design.
Responsible: RFC Editor
Send notices to <>
A new Request for Comments is now available in online RFC libraries.

        RFC 3384
        Title:      Lightweight Directory Access Protocol (version 3)
                    Replication Requirements
        Author(s):  E. Stokes, R. Weiser, R. Moats, R. Huber
        Status:     Informational
        Date:       October 2002
        Pages:      31
        Characters: 66871
        Updates/Obsoletes/SeeAlso:    None
        I-D Tag:    draft-ietf-ldup-replica-req-12.txt


This document discusses the fundamental requirements for replication
of data accessible via the Lightweight Directory Access Protocol
(version 3) (LDAPv3).  It is intended to be a gathering place for
general replication requirements needed to provide interoperability
between informational directories.

This document is a product of the LDAP Duplication/Replication/Update
Protocols Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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

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.