LDUP Multiple Draft Conflict Resolution (MDCR)
draft-langer-ldup-mdcr-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Albert Langer | ||
| Last updated | 2000-04-10 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Concurrent changes in a Multi-Master directory are a partially ordered tree. 'LDUP Update Reconciliation Procedures' (URP) uses timestamps to impose a strict linear order on this tree, and merges changes to fit that imposed order. Merged changes violate the semantics of the LDAP/X.500 data model. No specific 'modifierName' can be assigned to a merged change and requirements to support audit trails and access controls and not to break applications or impede future work on transactions cannot be met. The current LDUP requirements draft avoids dealing with these critical issues.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)