Re: I-D ACTION:draft-ietf-ldup-lcup-04.txt

At 07:09 AM 3/10/2003, Rich Megginson wrote:
>Kurt D. Zeilenga wrote:
>>
>>Is it the authors intent to allow state-based server 
>>implementation of this protocol?
>Yes.
>>
>>It appears to me that
>>server implementations would need to maintain historical
>>information in order to appropriately support this
>>protocol.
>Could you elaborate?

The most obvious problems are with the requests for content
refresh.

Without historical information, a server has no means to
determine whether or not an entry whose state indicates it was
updated (add,modify,rename) since the previous refresh
request has left the content.  It can only determine whether
the updated entry is currently in the content or not.  The
server must assume the entry was previously in the content.
Hence, the server must generate a message (update or entryLeft)
for each updated entry in the context or require a reload.

But worse, if any entry was deleted from the context, a
server which maintains no historical information is forced
to respond that a reload is required.

Kurt













>>Kurt
>>
>>At 03:53 AM 3/7/2003, <mailto:[email protected]>[email protected] wrote:
>>  
>>>
>>>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>This draft is a work item of the LDAP Duplication/Replication/Update Protocols Working Group of the IETF.
>>>
>>>       Title           : LDAP Client Update Protocol
>>>       Author(s)       : R. Megginson, M. Smith, O. Natkovich, J. Parham
>>>       Filename        : draft-ietf-ldup-lcup-04.txt
>>>       Pages           : 27
>>>       Date            : 2003-3-6
>>>       
>>>This document defines the Lightweight Directory Access Protocol 
>>>(LDAP) Client Update Protocol (LCUP). The protocol is intended to 
>>>allow an LDAP client to synchronize with the content of a directory 
>>>information tree (DIT) stored by an LDAP server and to be notified 
>>>about the changes to that content.
>>>
>>>A URL for this Internet-Draft is:
>>><http://www.ietf.org/internet-drafts/draft-ietf-ldup-lcup-04.txt>http://www.ietf.org/internet-drafts/draft-ietf-ldup-lcup-04.txt
>>>
>>>To remove yourself from the IETF Announcement list, send a message to 
>>>ietf-announce-request with the word unsubscribe in the body of the message.
>>>
>>>Internet-Drafts are also available by anonymous FTP. Login with the username
>>>"anonymous" and a password of your e-mail address. After logging in,
>>>type "cd internet-drafts" and then
>>>       "get draft-ietf-ldup-lcup-04.txt".
>>>
>>>A list of Internet-Drafts directories can be found in
>>><http://www.ietf.org/shadow.html>http://www.ietf.org/shadow.html 
>>>or <ftp://ftp.ietf.org/ietf/1shadow-sites.txt>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>
>>>
>>>Internet-Drafts can also be obtained by e-mail.
>>>
>>>Send a message to:
>>>       <mailto:[email protected]>[email protected].
>>>In the body type:
>>>       "FILE /internet-drafts/draft-ietf-ldup-lcup-04.txt".
>>>       
>>>NOTE:   The mail server at ietf.org can return the document in
>>>       MIME-encoded form by using the "mpack" utility.  To use this
>>>       feature, insert the command "ENCODING mime" before the "FILE"
>>>       command.  To decode the response(s), you will need "munpack" or
>>>       a MIME-compliant mail reader.  Different MIME-compliant mail readers
>>>       exhibit different behavior, especially when dealing with
>>>       "multipart" MIME messages (i.e. documents which have been split
>>>       up into multiple messages), so check your local documentation on
>>>       how to manipulate these messages.
>>>               
>>>               
>>>Below is the data which will enable a MIME compliant mail reader
>>>implementation to automatically retrieve the ASCII version of the
>>>Internet-Draft.
>>>Content-Type: text/plain
>>>Content-ID:     <mailto:[email protected]><[email protected]>
>>>
>>>ENCODING mime
>>>FILE /internet-drafts/draft-ietf-ldup-lcup-04.txt
>>>
>>><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ldup-lcup-04.txt>
>>>    
>>
>>
>>  
>