LDAP Duplication/Replication/Update Protocols (ldup)

This Working Group did not meet

NOTE: This charter is a snapshot of the 54th IETF Meeting in Yokohama, Japan. It may now be out-of-date.

Last Modifield: 06/07/2002

Chair(s):
Chris Apple <christopher.apple@verizon.net>
John Strassner <john.strassner@intelliden.com>
Applications Area Director(s):
Ned Freed <ned.freed@mrochek.com>
P. Faltstrom <paf@cisco.com>
Applications Area Advisor:
P. Faltstrom <paf@cisco.com>
Mailing Lists:
General Discussion: ietf-ldup@imc.org
To Subscribe: ietf-ldup-request@imc.org
In Body: subscribe
Archive: http://www.imc.org/ietf-ldup/
Description of Working Group:
As LDAPv3 becomes more widely deployed, replication of data across servers running different implementations becomes an important part of providing a distributed directory service. However, the LDAPv3 community, to date, has focused on standardizing the client-server access protocol. Therefore, this group will standardize master-slave and multi-master LDAPv3 replication as defined below:

o Multi-Master Replication - A replication model where entries can be written and updated on any of several replica copies, without requiring communication with other masters before the write or update is performed.

o Master-Slave, or Single-Master Replication - A replication model that assumes only one server, the master, allows write access to the replicated data. Note that Master-Slave replication can be considered a proper subset of multi-master replication.

The WG's approach is to first develop a set of requirements for LDAPv3 directory replication and write an applicability statement defining scenarios on which replication requirements are based. An engineering team was formed consisting of different vendors and the co-chairs in order to harmonize the existing approaches into a single standard approach. All of these have been accomplished during the pre-working group stage. It should be noted, however, that replication using heterogeneous servers is dependent on resolving access control issues, which are the domain of other working groups.

The new replication architecture support all forms of replication mentioned above. Seven areas of working group focus have been identified through LDUP Engineering Team discussions, each leading to one or more

Engineering Team discussions, each leading to one or more documents to be published:

o LDAPv3 Replication Architecture

This documents a general-purpose 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

o 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

o 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

o LDAPv3 Mandatory Replica Management

Specifications required to allow administration, maintenance, and provisioning of replicas and replication agreements. These specifications may take the form of definitions for LDAPv3 extended operations, controls, and/or new schema elements.

o 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.

o LDAPv3 Profiles

Including the LDAPv3 Replication Architecture, Information Model, Protocol Extensions, and Update Reconciliation Procedures for:

+ LDAPv3 Master-Slave Directory Replication

+ LDAPv3 Multi-Master Directory Replication

o 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 work being done in the LDUP WG should be coordinated to the closest extent possible with similar work being done in the ITU. This is necessary both because LDAP depends on X.500 and because it makes sense from an operational perspective.

Goals and Milestones:
Done  Submit I-D on LDAPv3 Directory Replication Requirements.
Done  Submit Internet-Draft on LDAPv3 Replication Information Model
Done  Submit I-D on LDAPv3 Update Reconciliation Procedures.
Done  Revise I-D on LDAPv3 Directory Replication Requirements.
Done  Revise I-D on LDAPv3 Replication Architecture.
Done  Submit I-D on LDAPv3 Replication Information Transport Protocol.
Done  Revise I-D on LDAPv3 Replication Architecture.
Done  Revise I-D on LDAPv3 Replication Information Model.
JAN 01  LDAPv3 Directory Replication Requirements I-D goes to WG Last Call as Informational.
JAN 01  LDAPv3 Update Reconciliation Procedures I-D goes to WG Last Call as Proposed Standard.
Done  Submit I-D on LDAPv3 Mandatory Replica Management.
MAR 01  Submit I-D on LDAPv3 Multi-Master Replication Profile.
MAR 01  Submit I-D on LDAPv3 Master-Slave Replication Profile.Submit I-D on LDAPv3 Master-Slave Replication Profile.
APR 01  LDAPv3 Replication Information Model I-D goes to WG Last Call as Proposed Standard.
APR 01  LDAPv3 Subentry Schema goes to WG Last Call (joint with LDAPEXT) as Proposed Standard.
APR 01  LDAPv3 Replication Architecture I-D goes to WG Last Call as Informational.
JUN 01  LDAPv3 Replication Information Transport Protocol I-D goes to WG Last Call as Proposed Standard.
JUN 01  LDAPv3 Client Update Protocol I-D goes to WG Last Call as Proposed Standard
AUG 01  LDAPv3 Extended Operations for Framing I-D goes to WG Last Call as Proposed Standard.
DEC 01  LDAPv3 Mandatory Replica Management I-D goes to WG Last Call as Proposed Standard.
DEC 01  LDAPv3 Multi-Master Replication Profile I-D goes to WG Last Call as Proposed Standard.
DEC 01  LDAPv3 Master-Slave Replication Profile I-D goes t WG Last Call as Proposed Standard.
DEC 01  Reevaluate Charter and Milestones
Internet-Drafts:
  • - draft-ietf-ldup-urp-06.txt
  • - draft-ietf-ldup-replica-req-12.txt
  • - draft-ietf-ldup-model-07.txt
  • - draft-ietf-ldup-usage-profile-03.txt
  • - draft-ietf-ldup-lcup-03.txt
  • - draft-ietf-ldup-mrm-01.txt
  • No Request For Comments

    Current Meeting Report

    None received.

    Slides

    None received.