Subject: draft-ietf-ldup-model-07.txt

From: "Ed Reed" <[email-masked]>
Date: Fri, 01 Mar 2002 15:37:36 -0700

Please publish the attached updated internet draft.

Abstract:

   This architectural document outlines a suite of schema and protocol 
   extensions to LDAPv3 that enables the robust, reliable, server-to-
   server exchange of directory content and changes. 

Thank you,
Ed Reed

==================
To the working group:

This version of the document includes notes addressed to other
document authors and raises issues to the LDUP working group.

Changes include:

converted document to (yet another) ms word template-based document, sort of.

changed "Updateable Replica" to "Master Replica"

dropped some non-objectives (!) of the document

8.5
added  Rick Huber's description of major replication states and state changes (as needed by MRM) document.  It is added to the "Update Protocol Framework" sub section 8.5.

3.2:        
Cleaned up "document objectives" so that all of them have a similar tone.  Items retained are those bullets that spell out issues this  document is meant to address and what purpose it is to serve for other design documents.

Added another line about how some prevalant concepts and their intent in current commercial products are outlined as a way to allow the reader to relate the LDUP protocol design choices, even if the LDUP protocols do not support these concepts (e-g primary replica, state-based replication, fractional replica etc.)

3.3:        
Cleaned up non-objectives to be about architectural issues not addressed

3.4:       
 Added that architecture draft does not dictate either state or log based approach

3.5:        
  a.. Minor changes in definitions (to remove references to primary replica) 
  b.. pruned all references to primary replica

4 & 5: 
Reorganized and cleaned up these two sections:
Section 4 used to have a combination of schema element defintions such as CSN, subentry etc., It also had replica type definitions and theory of operation w.r.t usage of CSN.
  a.. Section 4 just defines the replica types
  b.. Moved the schema elements into the section 5 (information model section) 
  c.. Pruned any detailed descriptions regarding state based replication from both sections 
  d.. Made the discussion of how CSN is used neutral w.r.t log-based vs state based and moved it to a new section # 7 called "Change Representation and Update Resolution".  It now flows well, comes after information model discussion and is presented like a theory of operation.

G6 Action Item: 

We reviewd it and believe that there is no need to add any additional caution w.r.t DOS.  Because faster purging won't really address DOS attack.  What is generally useful is the knowledge that log based systems accumulate logs at a larger rate than state based and so purging rate has to be carefully tuned.

G10 Action Item:
Added necessary verbiage information model under sections titled "Root DSE attributes".

AM2 Action Item:
Added need for audit logging capability under securuity discussion.

AM6 Actions item:
Did nothing, since it is not a problem in log based system where things are applied in order of CSN (from within a node).  

=================
Ed Reed
Reed-Matthews, Inc.
+1 585 624 2402
http://www.Reed-Matthews.COM
Note:  Area code is 585