Definition of an Object Class to Hold LDAP Change Records
draft-good-ldap-changelog-04

Document Type Expired Internet-Draft (individual)
Authors Gordon Good  , Ludovic Poitou 
Last updated 2003-03-04
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-good-ldap-changelog-04.txt

Abstract

In order to support more flexible replication methods, it is desirable to specify some manner in which an LDAP client may retrieve a set of changes that have been applied to an LDAP server's database. The client, which may be another LDAP server, may then choose to update its own replicated copy of the data. This document specifies an object class that may be used to represent changes applied to an LDAP server. It also specifies a method for discovering the location of the container object that holds these change records, so that clients and servers have a common rendezvous point for this information.

Authors

Gordon Good (ggood@netscape.com)
Ludovic Poitou (ludovic.poitou@france.sun.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)