Mandatory LDAP Replica Management
draft-ietf-ldup-mrm-02
| Document | Type |
Expired Internet-Draft
(ldup WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ryan Moats , Dr. Rick Huber , John McMeeking | ||
| Last updated | 2003-03-06 | ||
| 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
The goal of standards for LDAP replication is to allow interoperable replication among products from many different vendors. Defining the mechanism to move data among replicas is a necessary part of this work, but management of the replicated environment must also be standardized for replication to be truly interoperable. This document presents the replication management functions that must be performed. Whenever possible, these functions are defined in terms of existing LDAP functionality using existing LDAP operations and existing data definitions. In some cases, changes or additions to the existing model are required, and specifications for these changes are included in this document
Authors
Ryan Moats
Dr. Rick Huber
John McMeeking
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)