@techreport{good-ldap-changelog-04,
    number =    {draft-good-ldap-changelog-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-good-ldap-changelog/04/},
    author =    {Gordon Good and Ludovic Poitou},
    title =     {{Definition of an Object Class to Hold LDAP Change Records}},
    pagetotal = 9,
    year =      2003,
    month =     mar,
    day =       4,
    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.},
}