Work in progress This site is in the process of being reviewed and updated.

Introduction

This document lists the requirements for ApacheDS replication (a.k.a. Mitosis). It draws from several other specifications and drafts which are listed below:

• X.525
• X.501
• LDAP Duplication/Replication/Update Protocols (ldup)
  • RFCs
    • LDAPv3 Replication Requirements (RFC 3384)
    • LDAP Client Update Protocol (RFC 3928)
  • Internet-Drafts
    • LDUP Update Reconciliation Procedures
    • LDAP Replication Architecture
    • LDUP Replication Information Model
    • The LDUP Replication Update Protocol
  • All "LDUP" Drafts

General Requirements

These are requirements in addition to RFC 3384.

• Multi-Master Only support
• Use the X.500 replication model
• Per replication area have a configurable lost and found area (DN) for entries
• Require mutual authentication between replication partners
• Allow for encrypted replication channels between replication partners
• Per replication area with configurable critical OID list
• Allow for fractional replication: Per replication area with configurable attributes to replicate
• Allow for sparse replication (subtree refinements with glue entries)
• Configurable transport mechanism (LDAP, Custom, JMS)
• Configurable scheduling
  • On update
  • Periodic
  • Non Periodic Scheduled Times
  • Based on the number of changes
  • Based on the criticality of attributes and entries changed
  • Based on a maximum time between replication cycles
  • Manual requests for replication
• Configurable replication log store
• Must support reconnect strategies: would be nice if the server can announce when and for how long it will be down so other replicas can handle this. Namely by not showing the other replica as a viable replica to use in the RootDSE and making sure resynch is performed when that server does come back online after service.
• Must show in LDAP replication agreements
• Must show in LDAP replication state information for an area
• Configurable notification mechanisms for unresolved conflicts
• Configurable and plugable audit history of what has replicated with whom
• It MUST be possible to add a 'blank' replica to a replica-group, and force a full update from (one of) the Master(s), for the purpose of adding a new directory server to the system.
  .