General Usage Profile for LDAPv3 Replication
draft-ietf-ldup-usage-profile-06
| Document | Type |
Expired Internet-Draft
(ldup WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gerald Maziarski , Dr. Rick Huber , Ryan Moats | ||
| Last updated | 2003-09-29 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
Support for replication in LDAP directory systems is often one of the key factors in the decision to deploy them. But replication brings design constraints along with its benefits. We discuss some of the factors that should be taken into consideration when designing a replicated directory system. Both programming and architectural/operational concerns are addressed and both single- and multi-master directories are considered.
Authors
Gerald Maziarski
Dr. Rick Huber
Ryan Moats
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)