NOTE: This charter is a snapshot of the 49th IETF Meeting in San Diego, California. It may now be out-of-date. Last Modified: 24-Oct-00
Chair(s):
Chris Apple <capple@ecal.com>
John Strassner <johns@cisco.com>
Applications Area Director(s):
Ned Freed <ned.freed@innosoft.com>
Patrik Faltstrom <paf@cisco.com>
Applications Area Advisor:
Patrik 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. Six areas of working group focus have been identified through LDUP 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
The LDUP WG Chairs will assign to one or two persons to be official LDUP WG liasons to ITU, to monitor X.500 replication work in ITU, and to coordinate the work of the LDUP WG with similar work in ITU.
Goals and Milestones:
Nov 98 |
|
Submit I-D on LDAPv3 Directory Replication Requirements. |
Nov 98 |
|
Submit Internet-Draft on LDAPv3 Replication Information Model |
Feb 99 |
|
Submit I-D on LDAPv3 Update Reconciliation Procedures. |
Feb 99 |
|
Revise I-D on LDAPv3 Directory Replication Requirements. |
Apr 99 |
|
Revise I-D on LDAPv3 Replication Architecture. |
Aug 99 |
|
Revise I-D on LDAPv3 Replication Architecture. |
Aug 99 |
|
Submit I-D on LDAPv3 Mandatory Replica Management. |
Aug 99 |
|
Submit I-D on LDAPv3 Replication Information Transport Protocol. |
Aug 99 |
|
Revise I-D on LDAPv3 Replication Information Model. |
Sep 99 |
|
LDAPv3 Directory Replication Requirements I-D goes to WG Last Call as Informational. |
Sep 99 |
|
Submit I-D on LDAPv3 Multi-Master Replication Profile. |
Sep 99 |
|
Submit I-D on LDAPv3 Master-Slave Replication Profile.Submit I-D on LDAPv3 Master-Slave Replication Profile. |
Nov 99 |
|
LDAPv3 Replication Information Model I-D goes to WG Last Call as Proposed Standard. |
Nov 99 |
|
LDAPv3 Replication Architecture I-D goes to WG Last Call as Informational. |
Nov 99 |
|
LDAPv3 Update Reconciliation Procedures I-D goes to WG Last Call as Proposed Standard. |
Nov 99 |
|
LDAPv3 Replication Information Transport Protocol I-D goes to WG Last Call as Proposed Standard. |
Mar 00 |
|
LDAPv3 Mandatory Replica Management I-D goes to WG Last Call as Proposed Standard. |
Mar 00 |
|
LDAPv3 Master-Slave Replication Profile I-D goes t WG Last Call as Proposed Standard. |
Mar 00 |
|
LDAPv3 Multi-Master Replication Profile I-D goes to WG Last Call as Proposed Standard. |
Internet-Drafts:
· LDUP Update Reconciliation Procedures
· LDAPv3 Replication Requirements
No Request For Comments
None received.
LDUP Requirements Draft
LDUP Architecture Draft - Status
LDAP Subentries