From owner-ietf-ldup@imc.org  Sun Dec  5 20:27:05 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24198
	for <ldup-archive@odin.ietf.org>; Sun, 5 Dec 1999 20:27:04 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id QAA11844
	for ietf-ldup-bks; Sun, 5 Dec 1999 16:40:05 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id QAA11840
	for <ietf-ldup@imc.org>; Sun, 5 Dec 1999 16:40:05 -0800 (PST)
Received: from jstrassn-pc ([10.19.223.163])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id QAA20157
	for <ietf-ldup@imc.org>; Sun, 5 Dec 1999 16:42:24 -0800 (PST)
Message-Id: <4.1.19991205163208.009f11d0@omega.cisco.com>
X-Sender: jstrassn@omega.cisco.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Sun, 05 Dec 1999 16:34:50 -0800
To: ietf-ldup@imc.org
From: John Strassner <jstrassn@cisco.com>
Subject: Draft Minutes from the 46th IETF
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ns.secondary.com id QAA11841
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Meeting Minutes for the LDUP Working Group, 46th IETF
Minutes recorded by John Strassner

Requirements I-D  Chris Apple

Gone through WG Last Call. Unfortunately, the updated document missed the
cutoff date. Shortly after this meeting, we will incorporate comments and
submit to our ADs with a recommendation to publish this document as
informational. Chairs to ensure that bulk updates are either not prohibited or
(better) explicitly allowed in this document.

Architecture I-D  Chris Apple

We feel that it is ready for WG Last Call (No comments from the floor). We will
do so shortly after everyone returns from the IETF.

URP I-D  Steven Legg

Major change from log-based replication to implementation neutral
specification. Overt references to a replication log have been removed.
Previous draft had updates generating replication primitives that altered the
CSNs. The new draft change the handling of internal updates slightly. it should
be noted that although this means that the draft reads differently, no
behavioral changes have been issued.

Another change is the present/not present qualification of distinguished
values. There were four options that the design team was considering. The last
draft used option 2. Another option was to simply delete the distinguished
value. Option 4 was one that David Chadwick presented  it recommended ignoring
a delete request for a value that was distinguished. The difficulty with this
option is that you don’t necessarily know that the value is or will be
distinguished at the time that the deletion request was issued. The other
problem is that you need to store a considerable extra amount of state for each
value (e.g., the times that it was distinguished). Option 3 was to ignore the
delete by reasserting that the value was distinguished, but needs to add a set
of extra primitives. This is easy to implement, but may conflict with another
operation. It has one unfortunate side-effect, which is that read-only replicas
can generate update primitives.

Options 1 and 3 can be used together. The latest draft takes this approach 
recommends #1, but allows for the use of #3.

Another change, and one where a read-only replica may need to emit replication
primitives, is to resolve name clashes. So we added a unique identifier that is
appended to RDNs by the server as required to ensure the uniqueness of the DN.
UIDs are stripped out of the RDN when no longer needed. This avoids generating
explicit rename primitives. Note that we need to update the security section to
reflect the consequences of renaming an object.

Alternatives were discussed in the architecture group. For example, should the
p-add-entry be split into 3 primitives? A simple p-add primitive simply asserts
that a unique identifier exists, without where it should be placed in the DIT.
This would lead to generating 3 primitives (add, move, rename), but would
simplify the description of the process.

An entry will have a CSN for itself, its superior, and the position in the DIT.
These three CSNs can over time diverge. If we break up the p-add-entry
primitive into 3 separate entries, this will also simplify this.

Both authors will have new addresses by 12/1, as follows:

    Steven.legg@adacel.com
    a.payne@trl.telstra.com.au


LDUP Protocol Draft (draft-ietf-protocol…) from Gordon and Ellen

This is admittedly an early draft, but the authors thought that it should be
released to get people’s thoughts. Several changes are planned for the 01
draft. One thing to do is in the initial exchange, the supplier will output a
CSN. This will enable the consumer to detect a clock skew between the two
different servers. This gets rid of some nasty corner cases. However, we need a
bit of discussion over what happens on the different directions of the skew.
This should be bound to the architecture draft. Chairs suggest that comments on
this go out as part of the WG Last Call for the architecture draft.

Ordering of operations is significantly simplified if the ordering of updates
is either applied in the order received, or the output of the replication has
the same effect as this.

Problem with the possibility of losing a connection. Some state-based systems
traverse the DIT in an order different than CSN order. So this would help this
case.

One potentially large change would be to split the document into 3 documents.
What they’ll probably do is to have a draft that describes the basic begin and
end framework, one draft for the LDUP protocol itself, and one draft for LBURP
(or whatever name we give Roger’s draft, as long as it has a suitable
gastronomic reference ;-) )

Q (Ed): will there be different protocol identifiers?
A: Yes. For example, different OIDs to identify LDUP vs. LBURP

Open question: we want to distinguish between consumer- and supplier-initiated
replication. Advantage: one protocol. Disadvantage: certain firewall
configurations inhibit connectivity, so this may be hard to implement. Harald
suggests that this is more of a firewall administrator issue, so please don’t
compromise the design of the protocol to accommodate firewalls. Ed suggests
that this is similar in operation to passive mode in FTP. So you could have a
variation of the LDUP protocol such that the consumer has more freedom in
defining the connections and ports used. Harald agrees that this is a good
reason to change it. Discussion to be taken to the list.

Another change is the size of the Replica ID Lookup table. Compromise is to use
a large number internally but map them to a small number for efficient
transmission. Harald points out that this is similar in nature to the schemes
used in, for example, TCP header compression, and asks if any thought has been
given to applying this technique to other objects and/or data streams. John
thinks that that is an interesting idea, but that we should gain implementation
experience first.

Also, we need to describe error conditions better, as well as use the updated
2234 ABNF. Need to express more semantics with respect to access control. 

Info Model/Sub-Entry I-Ds  Ed Reed

Synchronized LDUP/LDAPEXT WG Last Calls for the Sub-Entry I-Ds. It is intended
to be almost a proper subset of the X.500 subentry spec. Main thing missing is
that it doesn’t use subtree specifications, and that it is explicitly a
container class (which the X.500 variation is not). No public comments
including none from the X.500 crowd. 

Information model  architecture team was able to resolve some outstanding open
issues. New draft anticipated by the end of November. Current plan is to make
the replication agreement schedule a single-value, of syntax distinguished
name. Define two subclasses, one for event-driven policy and one for
scheduled-policy (e.g., cron-like). By setting up this structure, people will
be able to define more complex relationships in the future.

Earlier suggestion of creating an LDAP DSA has been simplified to using a URI
syntax instead.

Profiles  Ed Reed

We’ve identified 3 profiles that should be described: Single master plus one or
more read-only replicas; single primary plus at least one additional updateable
replicas plus zero or more read-only replicas; no primary replica plus more
than one updateable replicas. The advantage of #2 is that it simplifies the
process of adding a replica into the group. The #3 alternative is more general,
but we must think very carefully about how a new replica is added, as well as
how it is propagated.

Comment: problem is that alternative #2 is not formally covered in the charter.
Also, although #2 is easier to do than #3, why should we do both?
A: If you view #2 as a bootstrapping mechanism, then there is operational
experience that defines how this works. Alternative #3 lacks this experience.
We need to add authors that have such experience. We also need to possibly
amend the charter to include 3 profiles instead of 2.

Chairs recommend that this be discussed further on the list.

Bulk Updates  Roger Harrison

Design meeting held, which produced this draft. Originated from a need to send
LDIF updates efficiently, but additional uses are being discovered as we speak.
No public discussion on this mail list yet, but some private comments from the
design team.

Areas of controversy: one is the types of operations that the server is allowed
to perform during the BURPing ;-). For example, since the BURP operation may
potentially blow away the naming context, the draft currently says MUST NOT
change naming. Private comments indicate that we could make some clever changes
to enable the server to process requests, so this is likely to be changed to a
SHOULD.

Wants to propose that this be formally added to our charter. Room consensus was
that we should add this to the charter, so we’ll formally ask this on the list.

Architecture  John Merrells

Changes consisted mostly of minor editorial changes. Currently a dangling
reference to a UUID draft to a draft authored by Paul Leach, which has expired.
Chris Harding reports that this is present in the DCE Procedure Calls
specification. There is a patent application by Novell for transitive update
vectors. The Novell representatives to LDUP are handling this. Creation and
deletion of replicas needs more wording.

Architecture says that there is a unique identifier in every entry. This
possibly should be pulled into its own standards track and put into LDAPEXT, so
that it gets the attention of all directory people, instead of just server
people.

Client consistency models. The constraints that LDAP imposes are considerable.
From the client perspective, where in a single server you have full read and
write serialization, to single-master (read serialization) to multi-master
(neither) will probably be quite surprising to the client writers. So we should
write a BCP draft that formalizes a set of rules into guidelines that help
writers of the client. This is a call for client writers. Jeff Hodges is
interested but must get cleared.

State information as LDIF. Should this be standardized? So, we first need to
determine if there is a need for this. There is a small contingent that thinks
that this is important, so we’ll ask the list. Jim and Gordon have volunteered
(or threatened) to work on it. Once we determine the need, then we need to
determine the correct method of representation.

Synchronization

There may be a synchronization agent that sits between an LDAP server and some
other type of repository (e.g., a database) and you want to connect these
solutions together. So people have started to deploy meta-directories that
implement an n-to-m mapping to hook these together. But it would be preferable
if there was a defined protocol that could be used to link these systems
together. Another motivation is that there are a lot of simple applications,
such as address books, that want a lightweight way of synchronizing with the
directory. Such systems want a lighter weight solution than LDUP provides. So,
this proposal is to use key elements of LDUP, such as update vectors, to
provide a lighter weight mechanism. These tools should be combined with LDAPEXT
work (e.g., Armijo’s description of AD synchronization, as well as the
triggered and persistent search drafts). But none of these drafts provides a
complete solution. So if we could harmonize these approaches, and combine them
with LDUP principles, that would be good. General consensus to create a new
mailing list and propose this as a new WG to the ADs.



From owner-ietf-ldup@imc.org  Mon Dec  6 11:49:30 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15425
	for <ldup-archive@odin.ietf.org>; Mon, 6 Dec 1999 11:49:28 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id HAA16443
	for ietf-ldup-bks; Mon, 6 Dec 1999 07:04:14 -0800 (PST)
Received: from monet.digsigtrust.com ([208.30.69.50])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id HAA16439
	for <ietf-ldup@imc.org>; Mon, 6 Dec 1999 07:04:12 -0800 (PST)
Received: from digsigtrust.com (rfwlaptop.digsigtrust.com [208.30.64.125])
	by monet.digsigtrust.com (8.9.3/8.9.3) with SMTP id IAA27144;
	Mon, 6 Dec 1999 08:05:53 -0700 (MST)
Message-ID: <384BCE54.C4FEFB54@digsigtrust.com>
Date: Mon, 06 Dec 1999 07:55:16 -0700
From: "Russel F. Weiser" <rweiser@digsigtrust.com>
X-Mailer: Mozilla 4.6 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: internet-drafts@ietf.org, ietf-ldup@imc.org
Subject: Revised Draft-ietf-ldup-replica-req-02.txt
Content-Type: multipart/mixed;
 boundary="------------37212C9504154C14FE2FED89"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

This is a multi-part message in MIME format.
--------------37212C9504154C14FE2FED89
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I made several revisions that were requested and missed in the last
revision. I hope that this will be accepted for last call if not I am
also submitting it to the LDUP list for consideration to moving to LAST
CALL as an information draft. 

cheers
RFW
--------------37212C9504154C14FE2FED89
Content-Type: text/plain; charset=iso-8859-1;
 name="draft-ietf-ldup-replica-req-02.txt"
Content-Disposition: inline;
 filename="draft-ietf-ldup-replica-req-02.txt"
Content-Transfer-Encoding: 8bit








         INTERNET-DRAFT                                     Russel F. Weiser
         Informational Draft                     Digital Signature Trust Co.
         Expires 21 April 2000                                  Ellen Stokes
                                                                         IBM
                                                             21 October 1999





                        LDAP V3 Replication Requirements

                        <draft-ietf-ldup-replica-req-02.txt>



  Status of this Memo



      This document is am Internet-Draft and is in full conformance with
      all provisions of Section 10 of RFC2026.


      Internet-Drafts are working documents of the Internet Engineering
      Task Force (IETF), its areas, and its working groups.  Note that
      other groups may also distribute working documents as Internet-
      Drafts.


      Internet-Drafts are draft documents valid for a maximum of six
      months and may be updated, replaced, or obsoleted by other documents
      at any time.  It is inappropriate to use Internet-Drafts as
      reference material or to cite them other than as ``work in
      progress.''


      The list of current Internet-Drafts can be accessed at
      http://www.ietf.org/ietf/lid-abstracts.txt


      The list of Internet-Drafts Shadow Directories can be accessed at
      http://www.ietf.org/shadow.html.




  Abstract


      This document discusses the fundamental requirements for replication
      of data accessible via the LDAPv3 [RFC2251] protocol. It is intended
      to be a gathering place for general replication requirements needed
      to provide interoperability between informational directories.


      The key words MUST, MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
      document are to be interpreted as described in [RFC2119].







         Weiser & Stokes       21 April   2000                    [PAGE 1]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999







                             Table of Contents


      1.Introduction.....................................................3
      2. Terminology.....................................................3
      3. Objective.......................................................5
      4. Applicability Statement.........................................5
      5. Replication Model..............................................10
      6. Replication Protocol...........................................12
      7. Schema.........................................................13
      8. Administration and Management Considerations...................13
      9. Acknowledgement................................................14
      10. References....................................................15
      11. Author's Address..............................................15







































         Weiser & Stokes       21 April 2000                   [Page 2]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999









  1. Introduction


      The ability to distribute directory information throughout the
      network provides a two fold benefit to the network: (1) increasing
      the reliability of the directory through fault tolerance, and
      (2) brings the directory content closer to the clients using the
      data. LDAP’s acceptance as an access protocol for directory
      information is driving the need to distribute LDAP directory content
      among servers within enterprise and Internet.  Currently LDAP does
      not define a replication mechanism and only generally mentions LDAP
      shadow servers (see [RFC2251] and [Changelog]) in passing. The
      requirements for replication are critical to the successful
      deployment and acceptance of LDAP in the market place.



  2.  Terminology


      For the purposes of this document, the following terminology
      definitions are used:


      Area of replication - A whole or portion of a directory tree(DIT)
      making up a distinct unit of data to be replicated. This may also be
      known as "unit of replication".

      Atomic operation - The ability to treat and contain several updates
      or attribute changes as a single operation for replication purposes
      to guarantee that the several updates or attribute changes are
      propagated to a replica as a single unit.

      Authoritative Master Replica - The Primary updateable replica of the
      replicated information.


      Conflict resolution - Deterministic procedures within replication
      protocols, utilized to resolve change information conflicts that may
      arise due to conflicting changes affecting a directory entry.


      Fractional replication - The capability to replicate a subset of
      attributes of any given entry.

      Incremental Update - The process of updating a replica, or copy, of
      a naming context, by updating only those fields or objects which
      have changed.


      Master Slave, or Single Master Replication - Replication model that
      assumes only one server, the master, allows write access to the
      replicated data. Note that Master-Slave replication can be
      considered a proper subset of multi-master replication.



         Weiser & Stokes       21 April 2000                   [Page 3]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999







      Multi-Master Replication - A replication model where entries can be
      written and updated on any of several updateable replica copies
      without requiring communication with other updateable replicas
      before the write or update is performed.


      Naming Context - Suffix of a Sub-tree. A sub-tree of entries held in
      a single server [X.500].


      One-way Replication  - The process of synchronization in a single
      direction where the authoritative source information is provided to
      a replica.


      Partial Replication - The capability to replicate some subset of
      entries in a naming context.


      Propagation behavior - The general behavior of the actual
      synchronization process between a consumer and a provider of
      replication information.

      Read-only Replica - A read-only copy of a replicated directory. A
      read-only replica is assumed to be a slave replica of master slave
      or single master replication definition.


      Replica - A single instance of a whole or portion of the Directory
      tree (DIT) as defined by area of replication.


      Replica Ring - A set of servers, which hold in common the same DIT
      information as, defined by “Area of replication”. These servers may
      be managed under a single replication agreement that handles all
      members of the set of servers as a group.


      Replica Cycle - When a change or groups of changes need to be
      propagated to the other member of a replica ring. The process of
      contacting a replica member would be considered the beginning of a
      replication cycle; the termination of communications with a replica
      is the end of the cycle whether its due to an error or successful
      exchange of update records.


      Replication - The process of copying portions of naming context
      information and content between multiple LDAP servers, such that
      certain predefined portions of the information are available from
      different servers. Replication can occur between either homogeneous
      implementations across heterogeneous platforms (operating systems)
      or heterogeneous implementations supporting identical replication
      across heterogeneous platforms (operating systems).


      Sparse Replica - A incomplete copy of a sub-tree which maybe
      inclusive with updateable, or Read-only. See Partial replication and




         Weiser & Stokes       21 April 2000                   [Page 4]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





      Fractional replication.


      Topology - Refers to the shape of the directed graph describing the
      relationships between replicas, as in the replicated directory
      topology.


      Two-way Replication  - The process of synchronization where change
      information may flow bi-directionally between two replica.

      Update Propagation - Protocol-based process by which directory
      replicas are reconciled.


      Updateable Replica - A Non-authoritative read-writeable copy of the
      replicated information. Such that during conflict resolution a
      authoritative master takes precedents in resolving conflicts.



  3.  Objective


      The major objective is to provide an interoperable LDAP V3 directory
      synchronization protocol which is simple, highly efficient and
      flexible enough to support both multi-master and master-slave
      replication operations to meet the needs of both the internet and
      enterprise environments.


  4.  Applicability Statement


      Generally replication can be characterized by looking at data
      consistency models across existing technologies. This may provide
      insight to LDAP v3 replication requirements. The following is a
      brief examination of the following data models.


      Model 1: Tight Consistency -- Includes environments where all
      replicas must always contain exactly the same directory content. Two
      phase commit transaction models may be used to preserve transaction
      consistency.


      Model 2: Eventual Consistency or Transient Consistency -- Includes
      X.500 Directories, Bayou [XEROX], and NDS (Novell Directory
      Services) names service where definite knowledge of the global
      replica topology is provided through predetermined replication
      agreements. Such that every update propagates to every replica that
      it can reach via a path of stepwise eventual connectivity.
      Transaction consistency is preserved for transactions directed at
      the master server in X.500 implementations. NDS additionally
      provides deterministic consistency over time to all replicas due to
      its inherent replication policies.




         Weiser & Stokes       21 April 2000                   [Page 5]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





      Model 3: Limited Effort Eventual Consistency -- Includes Xerox
      Clearinghouse [XEROX] that provides a statistical probability of
      convergence with global knowledge of replica topology. Similar to
      "Eventual Consistency", except where replicas may purge updates
      therefore dropping propagation changes when some replica time
      boundary is exceeded, thus leaving some changes replicated to a
      portion of the replica topology. Transactional consistency is not
      preserved, though some weaker constraints on consistency are
      available.

      Model 4: Loosest Consistency -- Includes opportunistic or simple
      cache where information is provided from the cache until stale.


      Model 5: Ad hoc -- A copy of a date store where no follow up checks
      are made for the accuracy/freshness of the data.


      Consistency models 2, and 3 involve the use of prearranged
      replication agreements or "Predefined Replication Agreements"
      between cooperating servers. The complexity of Model 1's use of 2-
      phase commit adds additional overhead that should not considered at
      this time. Models 4 and 5 involve unregistered replicas which
      "pull" updates from another directory server without that server's
      knowledge. These models can be considered to violate a directory's
      security policies. Therefore models 1, 4, and 5 are declared to be
      out of scope of this working group.


      So through further review of these consistency models two
      application areas can then be derived with even further
      characterizations of the data types usages.

      Eventual Consistency or Transient Consistency (Model 2) - This model
      provides policy configuration through security management
      parameters; the data is more dynamic and utilizes dynamic address
      information.

      Limited Effort Eventual Consistency (Model 3) - This model matches a
      white-pages environment which contains fairly static data and
      address information. This model mainly replicates message
      attributes.

      Therefore it is believed an LDAP replication should be flexible
      enough to cover the above range of capabilities. The generalized use
      of LDUP replication environment is to provide for the distribution
      of LDAP directory information in order to improve accessibility and
      consistency of the information held by the directory.



      4.1 Replication Scenarios





         Weiser & Stokes       21 April 2000                   [Page 6]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





      The following directory deployment examples are intended to
      substantiate and validate our replication requirements. It is
      assumed in all cases that directory implementations from different
      vendors are involved.

      4.1.1 Extranet Example


      A company has a trading partner to whom it wishes to provide
      directory information.  This information may be as simple as a
      corporate telephone directory, or as complex as an extranet work
      flow application.  For performance reasons the company may wish to
      have a replica of its directory within the Partner Company, rather
      than simply exposed beyond its firewall.


       The requirements, which follow from this scenario, are:

      - One-way replication, single mastered.
      - Authentication of clients.
      - Common access control and access control identification.
      - Secure transmission of updates.
      - Selective attribute replication (Fractional Replication), so that
        only partial entries can be replicated.



        4.1.2 Consolidation Example


      Company A acquires company B. In the transition period, whilst the
      organizations are merged, both directory services must coexist.
      Company A may wish to attach company B's directory to its own.

      The requirements, which follow from this scenario, are:

      - Multi-Master replication.
      - Common access control model. Access control model identification.
      - Secure transmission of updates.
      - Replication between DITs with potentially differing schema.


        4.1.3 Replication Heterogeneous Deployment Example

      An organization may deliberately deploy multiple directory services
      within their enterprise to employ the differing benefits of each
      service.  In this case multi-master replication will be required to
      ensure that the multiple updateable replicas of the DIT are
      synchronized. Some vendors may provide directory clients, which are
      tied to their own directory service.


      The requirements, which follow from this scenario, are:


      - Multi-Master replication



         Weiser & Stokes       21 April 2000                   [Page 7]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





      - Common access control model and Access control model
      identification.
      - Secure transmission of updates.
      - Replication between DITs with potentially differing schemas.

      4.1.4 Shared Name Space Example


      Two organizations may choose to cooperate on some venture and need a
      shared name space to manage their operation.  Both organizations
      will require administrative rights over the shared name space.

      The requirements, which follow from this scenario, are:

      - Multi-Master replication.
      - Common access control model and Access control model
      identification.
      - Secure transmission of updates.

      4.1.5 Supplier Initiated Replication

      A single master environment, which maintains a number of replicas of
      the DIT by pushing changes, based on a defined schedule.


      The requirements, which follow from this scenario, are:

      - Single-master environment.
      - Supplier-initiated replication.
      - Secure transmission of updates.


      4.1.6 Consumer Initiated Replication


      Again a single mastered replication topology, but the replica
      initiates the replication exchange rather than the master. An
      example of this is a replica that resides on a laptop computer that
      may run disconnected for a period of time.


      The requirements, which follow from this scenario, are:

      - Single-master environment.
      - Consumer initiated replication.
      - Open scheduling (anytime).

      4.1.7 Prioritized attribute replication


      The password attribute can provide an example of the requirement for
      prioritized attribute replication. A user is working in Utah and the
      administrator resides in California. The user has forgotten his
      password. So the user calls or emails the administrator to request a
      new password. The administrator provides the updated password (a
      change). Policy states that this attribute is critical and must be



         Weiser & Stokes       21 April 2000                   [Page 8]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





      available to the user for login immediately (e.g. shortly) after the
      administrator changed it. Replication needs to occur immediately for
      critical attributes/objects.


      The requirements, which follow from this scenario, are:

      - Incremental replication of changes.
      - Automatic replication on change of certain attributes.
      - Replicate based on time/attribute semantics.

      4.1.8 Bandwidth issues


      The replication of Server (A) R/W replica (a) in Katmandu is handled
      via a dial up phone link to Paris where server (B) R/W replica of
      (a) resides. Server (C) R/W replica of(a) is connected by a T1
      connection to server (B). Each connection has a different
      performance characteristic.


      The requirements, which follow from this scenario, are:
            
      - Minimize repetitive updates when replicating from multiple
        replication paths.
      - Incremental replication of changes.
      - Provide replication cycles to delay and/or retry when connections
        can not be reached.
      - Allowances for consumer initiated or supplier initiated
        replication.


      4.1.9 Interoperable Administration and Management

      The administrator with administrative authority of the corporate
      directory which is replicated by numerous geographically dispersed
      LDAP servers from different vendors notices that the replication
      process is not completing correctly as the change log is continuing
      to grow and/or error message informs him. The administrator uses his
      $19.95 RepCo LDAP directory replication diagnostics tools to look at
      Root DSE replica knowledge on server 17 and determines that server
      42 made by LDAP’RUS Inc. is not replicating properly due to an
      Object conflict. Using his Repco Remote repair tools he connects to
      server 42 and resolves the conflict on the remote server.


      The requirements, which follow from this scenario, are:

      - Provides replication audit history.
      - Provisions for managing conflict resolution.
      - Provide LDAP access to predetermined agreements, topology and
        policy attributes.
      - Provide operations for comparing replica’s content for validity.
      - Provide LDAP access to status and audit information.




         Weiser & Stokes       21 April 2000                   [Page 9]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





      4.1.10 Enterprise Directory Replication Mesh


      A Corporation builds a mesh of directory servers within the
      enterprise utilizing LDAP servers from various vendors. Five servers
      are holding the same area of replication. The predetermined
      replication agreement(s) for the enterprise mesh are under a single
      management, and the security domain allows a single predetermined
      replication agreement to manage the 5 servers replication.


      The requirements, which follow from this scenario, are:

      - Predefined replication agreements that manage more than a single
        area of replication that is held on numerous servers.
      - Common support of replication management knowledge across vendor
        implementation.
      - Rescheduling and continuation of a replication cycle when one
        server in a replica ring is busy and/or unavailable.  

  5. Replication Model


      5.1  LDAP Replication MUST be allowed to span different vendors
           directory services in order to provide interoperability.

      5.2  All replicas MUST eventually be updated with the changed
           information, if specified by the replication policy.


      5.3  Replication schedules MUST be configurable to allow for
           periodic replication, with the replication period determined by
           administrator of the replicated system.


      5.4  Replication Model MUST enable replication cycle to be initiated
           on change or based on the number of pending changes.

      5.5  The replication model MUST allow for administrative
           initiation of replication cycle for any replica that may have
           just come back online or was unavailable during previous 
           replication cycles.

      5.6  The replication model MUST support both master-slave and
           authoritative multi-updateable replica relationships.


      5.7  All replicated information between the master database and its
	   replica databases MUST be identical including all non-user
           modify operational attributes such as time stamps. Note this
           does not imply that the entire database is identical from
           replica to replica, but that the subset of data, chosen to
           replicate is identical from replica to replica. Some
           operational attributes may be dynamically evaluated; these
           attributes will not necessarily appear to be identical.






         Weiser & Stokes       21 April 2000                   [Page 10]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





      5.8  In distributed multi-vendor environment, LDAP replication MUST
           NOT require all copies of the replicated information be
           complete copies of the replicated object.


      5.9  LDAP replication MUST encompass common schema objects and
           attributes, access control, and name space information.


      5.10 Sub-tree Replication MUST be defined to allow for greater
           flexibility in replication topologies of the DIT as defined by
           the area of replication called partial replication.


      5.11 Replication of critical values MUST be synchronized and have
           priority over non-critical values. An example of a critical
           value might be a password or certificate value.

      5.12 Replication activities MUST occur within the context of a
           predefined replication agreement that addresses proper
           knowledge of access requirements and credentials between the
           synchronizing directories. Currently X.525 DISP [X.525]
           discusses this as a shadowing agreement including such
           information as unit of replication, update mode, and access
           point defining many of the policies between the master and a
           replica.


      5.13 The acceptance and usage of the Internet requires that LDAP
           replication be available across disparate vendor directory
           services.


      5.14 LDAP replication MUST provide scalability to both enterprise
           and Internet environments, e.g. an LDAP server may provide
           replication services to replicas within an enterprise as well
           as across the Internet.


      5.15 The replication model MUST define deterministic policy such
           that replication cycle startup time conflicts between two or
           more competing master replicas may be resolved
           programmatically. An example might be automatic submission and
           rescheduling by one of the masters.  In such a case, these
           replication "conflicts" MUST be resolved by the replication
           policy.


      5.16 Any replication capable LDAP server MUST allow replication
           where the 2 replicating servers agree they can replicate. This
           may be accomplished through administrative agreements assuming
           compatible access control model and common schema are provided.


      5.17 The replication model MUST be able to handle convergence and
           resurrection of attributes and objects. This is a consequence
           of delete and move with respect to the replication process.




         Weiser & Stokes       21 April 2000                   [Page 11]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





      5.18 It is not realistic to assume that all vendors have cooperating
           schemas, but that replication may be allowed between diverse
           schema. The Model MAY allow for replication between divergent
           schema of objects.


  6. Replication Protocol


      6.1  The act of replication SHOULD have minimal impact on both the
           system and network performance.

      6.2  The replica synchronization SHOULD be handled in such a manner
           as to not saturate network with repetitive entry replication
           from multiple synchronization providers points.


      6.3  Replication MUST only be allowed after the authentication and
           verification of authorization of both the replica and the
           source directory.


      6.4  The transport for LDAP synchronization MUST allow for the
           integrity and confidentiality of each replicated server.


      6.5  Replicated data MUST be transferable in a secure manner.


      6.6  Replication protocol MUST provide for recovery and rescheduling
           of a replication cycle due to a replication initiation
           conflicts (e.g. consumer busy replicating with other servers)
           and or loss of connection(e.g. supplier cannot reach a
           replica). The replication protocol MUST include restarting at
           the last acknowledged update prior to interruption rather than
           re-sending updates it had already sent to a consuming replica.


      6.7  LDAP replication MUST allow for full update to facilitate
           replica initialization and reset loading utilizing a
           standardized format such as LDIF [LDIF] format.

      6.8  The replication standard SHOULD NOT limit the size of a
           replica. The area of replication is defined to be a whole or
           portion of a DIT, also allowing a portion of a naming context
           to be replicated. Incremental replication SHOULD be allowed.

      6.9 The replication agreements MUST accommodate multiple servers
           receiving the same replica under a single predefined agreement.


      6.10 The replication protocol MUST allow either a master or replica
           to initiate the replication process.


      6.11 Additionally the initiator MUST be allowed to determine
           whether it will become a consumer or supplier during the
           synchronization startup process. This would allow a replica to



         Weiser & Stokes       21 April 2000                   [Page 12]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





           be periodically connected and synchronized from remote sites at
           the local administrator's discretion.


      6.12 Multiple LDAP changes to a single server: If transactional
           consistency is propagated during replication, then multiple LDAP
           changes submitted to a single server SHOULD BE treated as a 
           single 'atomic unit of work'.


      6.13 An LDAP Replication Standard SHOULD NOT limit the transaction
           rate of a replication session.


      6.14 Entry change information MUST be purged or discarded in a
           timely manner when change information becomes outdated due to
           propagated to all replica members.




      7. Schema


      7.1  Replica knowledge MUST be provided as DSE attributes.

      7.2  The Replication Protocol documents MUST define standard schema
           for representing replication agreements, and MUST define the
           semantics associated with modifying the attributes of
           replication agreements. The documents MUST also define a
           standard method for determining the location of these
           agreements accessible utilizing LDAP.


      7.3  The Replication Protocol documents MUST define standard schema
           for publishing state information about a given replica, and
           MUST define a standard method for determining the location of
           this information.


      7.4  A location independent management point MUST be defined to
           provide authorized administrators with well known access to the
           replication policies, regardless of network location.


      7.5  Replication agreements of all servers containing replicated
           information MUST be accessible via LDAP.


      7.6  All objects MUST be uniquely identifiable throughout the object
           lifetime .




  8. Administration and Management Considerations



      8.1  Replication policies MUST allow replication of changed
           information to be administratively postponed to a more



         Weiser & Stokes       21 April 2000                   [Page 13]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





           convenient period.


      8.2  Allowance for non-scheduled replication of a replica MUST be
           provided upon request such that the replica server has been
           down or unconnected for a period of time.


      8.3  Each copy of a replica MUST maintain audit history information
           of which servers it has replicated with and which servers have
           replicated with it.

      8.4  A replica MUST store conflicted versions of the replicated
           object to allow optional human review and intervention.


      8.5  Access to replication predetermined agreements, topologies, and
           policies attributes MUST be provided through LDAP access.


      8.6  The capability to check the differences between two replicas
           for the same information SHOULD be provided for. This should
           entail a client invoking an operation at some server, which
           causes that server to extract the contents from some other
           server it has a replication agreement with and report the
           differences back to the client as the result.


      8.7  Authenticated access SHOULD be provided so that Administrative
           LDAP clients may query a server for the current state and
           replication history for each replica that the server maintains
           replication agreements with.


      8.8  The ability to view replication conflicts, and override the
           resolution derived by the replication policy MUST be provided.


      8.9  The deletion of sensitive data MUST be handled in an orderly
           manner so that at no time will that data be available without
           proper access control. That is, access control information
           (ACI) associated with sensitive data must be deleted after or
           simultaneously with the delete of the sensitive data. Likewise,
           when adding sensitive data, ACI MUST be added first or
           simultaneously with the addition of that data.




  9. Acknowledgement


      This document is based on input from IETF members interested in LDUP
      Replication.








         Weiser & Stokes       21 April 2000                   [Page 14]


         INTERNET-DRAFT     LDAP Replication Requirements     21 October 1999





  10. References



      [RFC2251]  M. Wahl, T. Howes, S. Kille "Lightweight Directory Access
      Protocal", RFC 2251.


      [RFC2119]  S.Bradner, " Key words for use in RFCs to indicate
      Requirement Levels", RFC 2119.


      [LDIF]  Gordon Good, "The LDAP Data Interchange Format (LDIF)",
      Internet draft,  draft-ietf-asid-ldif-00.txt, November 1996.


      [Changelog]  Gordon Good, "Definitions of an Object Class to Hold
      LDAP Change records", Internet Draft, draft-ietf-asid-changelog-
      00.txt,  November  1996.


      [X.501] ITU-T Recommendation X.501 (1993), | ISO/IEC 9594-2: 1993,
      Information Technology - Open Systems Interconnection - The
      Directory: Models

      [XEROX] Hauser, C. "Managing update conflicts in Bayou, a weakly
      connected replicated storage system". Palo Alto, CA: Xerox PARC,
      Computer Science Laboratory; 1995 August; CSL-95-4. [CSL-95-04]



   11. Author's Address


      Russel F. Weiser
      Digital Signature Trust Co.
      One South Main Street
      Salt Lake City, Utah 84111
      USA


      E-mail: rweiser@digsigtrust.com
      Telephone: +1-801-983-4415
      Fax +1-801-983-4408



      Ellen J. Stokes
      IBM
      11400 Burnet Rd.
      Austin, Texas 78758
      USA

      E-mail: stokes@austin.ibm.com
      Telephone: +1-512-838-3725
      Fax: +1-512-838-0156





         Weiser & Stokes       21 April 2000                   [Page 15]

--------------37212C9504154C14FE2FED89--



From owner-ietf-ldup@imc.org  Mon Dec  6 17:47:19 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16013
	for <ldup-archive@odin.ietf.org>; Mon, 6 Dec 1999 17:47:19 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id OAA01717
	for ietf-ldup-bks; Mon, 6 Dec 1999 14:14:22 -0800 (PST)
Received: from dir1.control.att.com ([135.207.251.15])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id OAA01713
	for <ietf-ldup@imc.org>; Mon, 6 Dec 1999 14:14:20 -0800 (PST)
Received: from att.com (pest.control.att.com [135.207.251.76])
	by dir1.control.att.com (Postfix) with ESMTP
	id 92C8471F6; Mon,  6 Dec 1999 17:17:13 -0500 (EST)
Message-ID: <384C364B.933A77AB@att.com>
Date: Mon, 06 Dec 1999 17:18:51 -0500
From: Chris Apple <capple@att.com>
Organization: AT&T Labs
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Russel F. Weiser" <rweiser@digsigtrust.com>
Cc: ietf-ldup@imc.org
Subject: Re: Revised Draft-ietf-ldup-replica-req-02.txt
References: <384BCE54.C4FEFB54@digsigtrust.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

When it is available in the repository, we'll issue a request
that it be considered for IETF Last Call by the IESG.

Chris.

"Russel F. Weiser" wrote:
> 
> I made several revisions that were requested and missed in the last
> revision. I hope that this will be accepted for last call if not I am
> also submitting it to the LDUP list for consideration to moving to LAST
> CALL as an information draft.
> 
> cheers
> RFW


From owner-ietf-ldup@imc.org  Tue Dec  7 07:47:21 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16572
	for <ldup-archive@odin.ietf.org>; Tue, 7 Dec 1999 07:47:20 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id DAA21753
	for ietf-ldup-bks; Tue, 7 Dec 1999 03:52:58 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id DAA21749
	for <ietf-ldup@imc.org>; Tue, 7 Dec 1999 03:52:56 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20437;
	Tue, 7 Dec 1999 06:55:58 -0500 (EST)
Message-Id: <199912071155.GAA20437@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ldup@imc.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ldup-replica-req-02.txt
Date: Tue, 07 Dec 1999 06:55:57 -0500
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

--NextPart

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 V3 Replication Requirements
	Author(s)	: R. Weiser, E. Stokes
	Filename	: draft-ietf-ldup-replica-req-02.txt
	Pages		: 15
	Date		: 06-Dec-99
	
This document discusses the fundamental requirements for replication
of data accessible via the LDAPv3 [RFC2251] protocol. It is intended
to be a gathering place for general replication requirements needed
to provide interoperability between informational directories.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldup-replica-req-02.txt

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-replica-req-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ldup-replica-req-02.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19991206101514.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ldup-replica-req-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ldup-replica-req-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19991206101514.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-ldup@imc.org  Fri Dec 10 02:28:47 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26269
	for <ldup-archive@odin.ietf.org>; Fri, 10 Dec 1999 02:28:47 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id WAA04670
	for ietf-ldup-bks; Thu, 9 Dec 1999 22:47:13 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id WAA04666
	for <ietf-ldup@imc.org>; Thu, 9 Dec 1999 22:47:12 -0800 (PST)
Received: from jstrassn-pc (rtp-dial-1-46.cisco.com [161.44.116.46])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id WAA29911;
	Thu, 9 Dec 1999 22:49:55 -0800 (PST)
Message-Id: <4.1.19991209223541.00c76240@omega.cisco.com>
X-Sender: jstrassn@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 09 Dec 1999 22:42:23 -0800
To: ietf-ldup@imc.org
From: John Strassner <jstrassn@cisco.com>
Subject: WG Last Call:  draft-ietf-ldup-model-02.txt
Cc: johns@cisco.com, capple@att.com, paf@swip.net, moore@cs.utk.edu
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

PURPOSE?

The purpose of this message is to initiate the LDUP working
group last call on the LDAPv3 Replication Architecture document.
 
WHAT DOCUMENT?
 
The LDAPv3 Replication Architecture document in last call is:
 
         draft-ietf-ldup-model-02.txt
 
WHAT IS A LAST CALL FOR?
 
The purpose of the working group last call is to ensure
that the working group has reached consensus on the
document, believes that all the known outstanding issues
have been addressed, and is ready to put the document
forward for proposed standard status.
 
During the last call, any comments on the documents are
collected and discussed on the mailing list.
 
HOW LONG DOES IT LAST?
 
The last call starts today (Friday, December 10, 1999) and
will last approximately two weeks. It will end on 
Friday, December 24, 1999.
 
WHAT'S THE NEXT STEP?
 
After the last call completes, there are three possible
outcomes:
 
1) No changes are required and we request our ADs to put
forward the documents to the IESG for Proposed Standard
status.
 
2) Minor changes agreed to on the list are required, and
the documents are revised. We then ask our ADs to put
forward the revised documents to the IESG for Proposed
Standard status.
 
3) Major issues are raised and no consensus is reached on
the list. In this case, we slink back and discuss things
until consensus is reached, at which time another working
group last call will be issued.
 
Assuming we achieve outcome 1) or 2), and that the ADs
agree with our assessment, the next stop for the documents
is with the IESG. The IESG reads them and may approve the
documents (with or without changes), or send the documents
back to the working group to have major issues addressed.
 
If the first outcome happens, the documents are put forward
for a two-week last call to the entire IETF, and after
successful completion the documents are published as RFCs
with proposed standard status.
 
If the second outcome happens, we go back and address
the issues, putting the documents forward again when we
believe they're ready.
 
WHAT SHOULD YOU DO?
 
You should read the documents, making sure that 1) there
are no problems or deficiencies or outstanding issues that
need to be resolved; and 2) that there are no typos,
formatting problems, grammatical errors, etc.
 
Any substantive problems you find, you should send to the
list. Any minor problems (typos, etc.) you may send to the
list or just to the authors. If, for some reason, you have
comments you don't want to send to the entire list, you may
send them to me (johns@cisco.com) or my co-chair 
Chris Apple (capple@att.com).
 
Read, enjoy, and send your comments in!

Thanks and regards,
John and Chris



From owner-ietf-ldup@imc.org  Fri Dec 10 17:12:00 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04190
	for <ldup-archive@odin.ietf.org>; Fri, 10 Dec 1999 17:12:00 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id NAA26323
	for ietf-ldup-bks; Fri, 10 Dec 1999 13:31:08 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA26319
	for <ietf-ldup@imc.org>; Fri, 10 Dec 1999 13:31:08 -0800 (PST)
Received: from jstrassn-pc (rtp-dial-1-21.cisco.com [161.44.116.21])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id NAA14469;
	Fri, 10 Dec 1999 13:33:51 -0800 (PST)
Message-Id: <4.1.19991210132519.019bd800@omega.cisco.com>
X-Sender: jstrassn@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Fri, 10 Dec 1999 13:26:20 -0800
To: "Paul Leach (Exchange)" <paulle@Exchange.MICROSOFT.com>,
        "'John Strassner'" <jstrassn@cisco.com>, ietf-ldup@imc.org
From: John Strassner <jstrassn@cisco.com>
Subject: RE: WG Last Call:  draft-ietf-ldup-model-02.txt
Cc: johns@cisco.com, capple@att.com, paf@swip.net, moore@cs.utk.edu
In-Reply-To: <19398D273324D3118A2B0008C7E9A569051BEB95@SIT.platinum.corp
 .microsoft.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_1489541==_.ALT"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

--=====================_1489541==_.ALT
Content-Type: text/plain; charset="us-ascii"

We're just following what we agreed to in Washington. There has been no
discussion as of late, so it is unclear why we need to extend it.

regards,
John

At 11:59 AM 12/10/99 -0800, Paul Leach (Exchange) wrote: 

>
> I think that last calls in the holiday season should have an extended comment
> period. 
>
> > -----Original Message----- 
> > From: John Strassner [<mailto:jstrassn@cisco.com>mailto:jstrassn@cisco.com] 
> > Sent: Thursday, December 09, 1999 10:42 PM 
> > To: ietf-ldup@imc.org 
> > Cc: johns@cisco.com; capple@att.com; paf@swip.net; moore@cs.utk.edu 
> > Subject: WG Last Call: draft-ietf-ldup-model-02.txt 
> > 
> > 
> > PURPOSE? 
> > 
> > The purpose of this message is to initiate the LDUP working 
> > group last call on the LDAPv3 Replication Architecture document. 
>
> Paul 




--=====================_1489541==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
We're just following what we agreed to in Washington. There has been no
discussion as of late, so it is unclear why we need to extend it.<br>
<br>
regards,<br>
John<br>
<br>
At 11:59 AM 12/10/99 -0800, Paul Leach (Exchange) wrote: <br>
<br>
<font size=2><blockquote type=cite cite>I think that last calls in the
holiday season should have an extended comment period.</font> <br>
<br>
<font size=2>&gt; -----Original Message-----</font> <br>
<font size=2>&gt; From: John Strassner
[<a href="mailto:jstrassn@cisco.com">mailto:jstrassn@cisco.com</a>]</font>
<br>
<font size=2>&gt; Sent: Thursday, December 09, 1999 10:42 PM</font> 
<br>
<font size=2>&gt; To: ietf-ldup@imc.org</font> <br>
<font size=2>&gt; Cc: johns@cisco.com; capple@att.com; paf@swip.net; moore@cs.utk.edu</font> <br>
<font size=2>&gt; Subject: WG Last Call: draft-ietf-ldup-model-02.txt</font> <br>
<font size=2>&gt; </font><br>
&gt; <br>
&gt; PURPOSE? <br>
<font size=2>&gt; </font><br>
&gt; The purpose of this message is to initiate the LDUP working <br>
<font size=2>&gt; group last call on the LDAPv3 Replication Architecture document.</font> <br>
<br>
<font size=2>Paul</font> </blockquote><br>
<br>
</html>

--=====================_1489541==_.ALT--



From owner-ietf-ldup@imc.org  Fri Dec 10 19:14:19 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05511
	for <ldup-archive@odin.ietf.org>; Fri, 10 Dec 1999 19:14:19 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id PAA27873
	for ietf-ldup-bks; Fri, 10 Dec 1999 15:30:08 -0800 (PST)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by ns.secondary.com (8.9.3/8.9.3) with SMTP id PAA27866
	for <ietf-ldup@imc.org>; Fri, 10 Dec 1999 15:30:05 -0800 (PST)
Received: from 127.0.0.1 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 10 Dec 1999 14:52:01 -0800 (Pacific Standard Time)
Received: by dfssl with Internet Mail Service (5.5.2650.21)
	id <Y4X1BK49>; Fri, 10 Dec 1999 14:52:01 -0800
Message-ID: <19398D273324D3118A2B0008C7E9A569051BEB9E@SIT.platinum.corp.microsoft.com>
From: "Paul Leach (Exchange)" <paulle@Exchange.MICROSOFT.com>
To: "'John Strassner'" <jstrassn@cisco.com>,
        "Paul Leach (Exchange)"
	 <paulle@Exchange.MICROSOFT.com>,
        ietf-ldup@imc.org
Cc: johns@cisco.com, capple@att.com, paf@swip.net, moore@cs.utk.edu
Subject: RE: WG Last Call:  draft-ietf-ldup-model-02.txt
Date: Fri, 10 Dec 1999 14:51:58 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BF4361.2B735772"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BF4361.2B735772
Content-Type: text/plain

If no one objects, fine. But if someone says they have comments, and given
that the holiday season is typically very busy, I think that the spirit of
the last call period would be better observed by allowing 2 "working weeks"
for last call, and giving them more time if they want it.

-----Original Message-----
From: John Strassner [mailto:jstrassn@cisco.com]
Sent: Friday, December 10, 1999 1:26 PM
To: Paul Leach (Exchange); 'John Strassner'; ietf-ldup@imc.org
Cc: johns@cisco.com; capple@att.com; paf@swip.net; moore@cs.utk.edu
Subject: RE: WG Last Call: draft-ietf-ldup-model-02.txt


We're just following what we agreed to in Washington. There has been no
discussion as of late, so it is unclear why we need to extend it.

regards,
John

At 11:59 AM 12/10/99 -0800, Paul Leach (Exchange) wrote: 



I think that last calls in the holiday season should have an extended
comment period. 

> -----Original Message----- 
> From: John Strassner [ mailto:jstrassn@cisco.com
<mailto:jstrassn@cisco.com> ] 
> Sent: Thursday, December 09, 1999 10:42 PM 
> To: ietf-ldup@imc.org 
> Cc: johns@cisco.com; capple@att.com; paf@swip.net; moore@cs.utk.edu 
> Subject: WG Last Call: draft-ietf-ldup-model-02.txt 
> 
> 
> PURPOSE? 
> 
> The purpose of this message is to initiate the LDUP working 
> group last call on the LDAPv3 Replication Architecture document. 

Paul 




------_=_NextPart_001_01BF4361.2B735772
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<META content="MSHTML 5.00.2920.0" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=630454922-10121999>If no 
one objects, fine. But if someone says they have comments, and given that the 
holiday season is typically very busy, I think that the spirit of the last call 
period would be better observed by allowing 2 "working weeks" for last call, and 
giving them more time if they want it.</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> John Strassner 
  [mailto:jstrassn@cisco.com]<BR><B>Sent:</B> Friday, December 10, 1999 1:26 
  PM<BR><B>To:</B> Paul Leach (Exchange); 'John Strassner'; 
  ietf-ldup@imc.org<BR><B>Cc:</B> johns@cisco.com; capple@att.com; paf@swip.net; 
  moore@cs.utk.edu<BR><B>Subject:</B> RE: WG Last Call: 
  draft-ietf-ldup-model-02.txt<BR><BR></DIV></FONT>We're just following what we 
  agreed to in Washington. There has been no discussion as of late, so it is 
  unclear why we need to extend it.<BR><BR>regards,<BR>John<BR><BR>At 11:59 AM 
  12/10/99 -0800, Paul Leach (Exchange) wrote: <BR><BR><FONT size=2>
  <BLOCKQUOTE cite type="cite">I think that last calls in the holiday season 
    should have an extended comment period.</FONT> <BR><BR><FONT size=2>&gt; 
    -----Original Message-----</FONT> <BR><FONT size=2>&gt; From: John Strassner 
    [<A href="mailto:jstrassn@cisco.com">mailto:jstrassn@cisco.com</A>]</FONT> 
    <BR><FONT size=2>&gt; Sent: Thursday, December 09, 1999 10:42 PM</FONT> 
    <BR><FONT size=2>&gt; To: ietf-ldup@imc.org</FONT> <BR><FONT size=2>&gt; Cc: 
    johns@cisco.com; capple@att.com; paf@swip.net; moore@cs.utk.edu</FONT> 
    <BR><FONT size=2>&gt; Subject: WG Last Call: 
    draft-ietf-ldup-model-02.txt</FONT> <BR><FONT size=2>&gt; </FONT><BR>&gt; 
    <BR>&gt; PURPOSE? <BR><FONT size=2>&gt; </FONT><BR>&gt; The purpose of this 
    message is to initiate the LDUP working <BR><FONT size=2>&gt; group last 
    call on the LDAPv3 Replication Architecture document.</FONT> <BR><BR><FONT 
    size=2>Paul</FONT> </BLOCKQUOTE><BR><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01BF4361.2B735772--


From owner-ietf-ldup@imc.org  Fri Dec 10 21:12:16 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07014
	for <ldup-archive@odin.ietf.org>; Fri, 10 Dec 1999 21:12:16 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id RAA29517
	for ietf-ldup-bks; Fri, 10 Dec 1999 17:42:47 -0800 (PST)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by ns.secondary.com (8.9.3/8.9.3) with SMTP id RAA29512
	for <ietf-ldup@imc.org>; Fri, 10 Dec 1999 17:42:44 -0800 (PST)
Received: from 127.0.0.1 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 10 Dec 1999 11:59:05 -0800 (Pacific Standard Time)
Received: by dfssl with Internet Mail Service (5.5.2650.21)
	id <YTS18CPS>; Fri, 10 Dec 1999 11:59:05 -0800
Message-ID: <19398D273324D3118A2B0008C7E9A569051BEB95@SIT.platinum.corp.microsoft.com>
From: "Paul Leach (Exchange)" <paulle@Exchange.MICROSOFT.com>
To: "'John Strassner'" <jstrassn@cisco.com>, ietf-ldup@imc.org
Cc: johns@cisco.com, capple@att.com, paf@swip.net, moore@cs.utk.edu
Subject: RE: WG Last Call:  draft-ietf-ldup-model-02.txt
Date: Fri, 10 Dec 1999 11:59:02 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BF4349.030326B8"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BF4349.030326B8
Content-Type: text/plain

I think that last calls in the holiday season should have an extended
comment period.

> -----Original Message-----
> From: John Strassner [mailto:jstrassn@cisco.com]
> Sent: Thursday, December 09, 1999 10:42 PM
> To: ietf-ldup@imc.org
> Cc: johns@cisco.com; capple@att.com; paf@swip.net; moore@cs.utk.edu
> Subject: WG Last Call: draft-ietf-ldup-model-02.txt
> 
> 
> PURPOSE?
> 
> The purpose of this message is to initiate the LDUP working
> group last call on the LDAPv3 Replication Architecture document.

Paul

------_=_NextPart_001_01BF4349.030326B8
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>RE: WG Last Call:  draft-ietf-ldup-model-02.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>I think that last calls in the holiday season should have an extended comment period.</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: John Strassner [<A HREF="mailto:jstrassn@cisco.com">mailto:jstrassn@cisco.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Thursday, December 09, 1999 10:42 PM</FONT>
<BR><FONT SIZE=2>&gt; To: ietf-ldup@imc.org</FONT>
<BR><FONT SIZE=2>&gt; Cc: johns@cisco.com; capple@att.com; paf@swip.net; moore@cs.utk.edu</FONT>
<BR><FONT SIZE=2>&gt; Subject: WG Last Call: draft-ietf-ldup-model-02.txt</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; PURPOSE?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; The purpose of this message is to initiate the LDUP working</FONT>
<BR><FONT SIZE=2>&gt; group last call on the LDAPv3 Replication Architecture document.</FONT>
</P>

<P><FONT SIZE=2>Paul</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BF4349.030326B8--


From owner-ietf-ldup@imc.org  Sat Dec 11 16:55:05 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29458
	for <ldup-archive@odin.ietf.org>; Sat, 11 Dec 1999 16:55:05 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id NAA14309
	for ietf-ldup-bks; Sat, 11 Dec 1999 13:16:41 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA14305
	for <ietf-ldup@imc.org>; Sat, 11 Dec 1999 13:16:40 -0800 (PST)
Received: from jstrassn-pc (sj-dial-5-22.cisco.com [10.19.223.23])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id NAA17397;
	Sat, 11 Dec 1999 13:19:28 -0800 (PST)
Message-Id: <4.1.19991211130811.032bd2a0@omega.cisco.com>
X-Sender: jstrassn@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Sat, 11 Dec 1999 13:11:57 -0800
To: "Paul Leach (Exchange)" <paulle@Exchange.MICROSOFT.com>,
        "'John Strassner'" <jstrassn@cisco.com>,
        "Paul Leach (Exchange)" <paulle@Exchange.MICROSOFT.com>,
        ietf-ldup@imc.org
From: John Strassner <jstrassn@cisco.com>
Subject: RE: WG Last Call:  draft-ietf-ldup-model-02.txt
Cc: johns@cisco.com, capple@att.com, paf@swip.net, moore@cs.utk.edu
In-Reply-To: <19398D273324D3118A2B0008C7E9A569051BEB9E@SIT.platinum.corp
 .microsoft.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_57629036==_.ALT"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

--=====================_57629036==_.ALT
Content-Type: text/plain; charset="us-ascii"

OK,

now that I lived up to my duty to keep things moving, and after Chris and I
talked, I agree. So how about extending it to 12/31 (in order to beat the Y2K
problems ;-)  )?

If you agree, I'll reissue the Last Call announcement with this change.  Anyone
else have any comments about the length of the review period?

regards,
John

At 02:51 PM 12/10/99 -0800, Paul Leach (Exchange) wrote: 
>
> If no one objects, fine. But if someone says they have comments, and given
> that the holiday season is typically very busy, I think that the spirit of
> the last call period would be better observed by allowing 2 "working weeks"
> for last call, and giving them more time if they want it.
>>
>> -----Original Message-----
>> From: John Strassner [mailto:jstrassn@cisco.com]
>> Sent: Friday, December 10, 1999 1:26 PM
>> To: Paul Leach (Exchange); 'John Strassner'; ietf-ldup@imc.org
>> Cc: johns@cisco.com; capple@att.com; paf@swip.net; moore@cs.utk.edu
>> Subject: RE: WG Last Call: draft-ietf-ldup-model-02.txt
>>
>> We're just following what we agreed to in Washington. There has been no
>> discussion as of late, so it is unclear why we need to extend it.
>>
>> regards,
>> John
>>
>> At 11:59 AM 12/10/99 -0800, Paul Leach (Exchange) wrote: 
>>
>>>
>>> I think that last calls in the holiday season should have an extended
>>> comment period. 
>>>
>>> > -----Original Message----- 
>>> > From: John Strassner
>>> [<mailto:jstrassn@cisco.com>mailto:jstrassn@cisco.com] 
>>> > Sent: Thursday, December 09, 1999 10:42 PM 
>>> > To: ietf-ldup@imc.org 
>>> > Cc: johns@cisco.com; capple@att.com; paf@swip.net; moore@cs.utk.edu 
>>> > Subject: WG Last Call: draft-ietf-ldup-model-02.txt 
>>> > 
>>> > 
>>> > PURPOSE? 
>>> > 
>>> > The purpose of this message is to initiate the LDUP working 
>>> > group last call on the LDAPv3 Replication Architecture document. 
>>>
>>> Paul 
>>
>>
>




--=====================_57629036==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
OK,<br>
<br>
now that I lived up to my duty to keep things moving, and after Chris and
I talked, I agree. So how about extending it to 12/31 (in order to beat
the Y2K problems ;-)&nbsp; )?<br>
<br>
If you agree, I'll reissue the Last Call announcement with this
change.&nbsp; Anyone else have any comments about the length of the
review period?<br>
<br>
regards,<br>
John<br>
<br>
At 02:51 PM 12/10/99 -0800, Paul Leach (Exchange) wrote: <br>
<font face="arial" size=2 color="#0000FF"><blockquote type=cite cite>If
no one objects, fine. But if someone says they have comments, and given
that the holiday season is typically very busy, I think that the spirit
of the last call period would be better observed by allowing 2
&quot;working weeks&quot; for last call, and giving them more time if
they want it.</font><br>
<font face="tahoma" size=2><blockquote type=cite cite>-----Original
Message-----<br>
<b>From:</b> John Strassner
[<a href="mailto:jstrassn@cisco.com" eudora="autourl">mailto:jstrassn@cisco.com</a>]<br>
<b>Sent:</b> Friday, December 10, 1999 1:26 PM<br>
<b>To:</b> Paul Leach (Exchange); 'John Strassner';
ietf-ldup@imc.org<br>
<b>Cc:</b> johns@cisco.com; capple@att.com; paf@swip.net;
moore@cs.utk.edu<br>
<b>Subject:</b> RE: WG Last Call: draft-ietf-ldup-model-02.txt<br>
<br>
</font>We're just following what we agreed to in Washington. There has
been no discussion as of late, so it is unclear why we need to extend
it.<br>
<br>
regards,<br>
John<br>
<br>
At 11:59 AM 12/10/99 -0800, Paul Leach (Exchange) wrote: <br>
<br>
<font size=2><blockquote type=cite cite>I think that last calls in the
holiday season should have an extended comment period.</font> <br>
<br>
<font size=2>&gt; -----Original Message-----</font> <br>
<font size=2>&gt; From: John Strassner
[<a href="mailto:jstrassn@cisco.com">mailto:jstrassn@cisco.com</a>]</font>
<br>
<font size=2>&gt; Sent: Thursday, December 09, 1999 10:42 PM</font> 
<br>
<font size=2>&gt; To: ietf-ldup@imc.org</font> <br>
<font size=2>&gt; Cc: johns@cisco.com; capple@att.com; paf@swip.net; moore@cs.utk.edu</font> <br>
<font size=2>&gt; Subject: WG Last Call: draft-ietf-ldup-model-02.txt</font> <br>
<font size=2>&gt; </font><br>
&gt; <br>
&gt; PURPOSE? <br>
<font size=2>&gt; </font><br>
&gt; The purpose of this message is to initiate the LDUP working <br>
<font size=2>&gt; group last call on the LDAPv3 Replication Architecture document.</font> <br>
<br>
<font size=2>Paul</font> </blockquote><br>
</blockquote></blockquote><br>
<br>
</html>

--=====================_57629036==_.ALT--



From owner-ietf-ldup@imc.org  Mon Dec 13 02:23:19 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28989
	for <ldup-archive@odin.ietf.org>; Mon, 13 Dec 1999 02:23:19 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id WAA25809
	for ietf-ldup-bks; Sun, 12 Dec 1999 22:45:42 -0800 (PST)
Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id WAA25805
	for <ietf-ldup@imc.org>; Sun, 12 Dec 1999 22:45:39 -0800 (PST)
Received: from sendout.icomverse.com (Efrat-FR3.ser.netvision.net.il [199.203.174.65])
	by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id IAA06015;
	Mon, 13 Dec 1999 08:49:00 +0200 (IST)
Received: from ismailmkt.icomverse.com (ismailmkt.icomverse.com [190.190.55.28])
	by sendout.icomverse.com (8.9.3/8.8.7) with ESMTP id IAA15971;
	Mon, 13 Dec 1999 08:48:13 +0200
Received: from unity-mail.icomverse.com (unity-mail.quantum.icomverse.com [89.119.41.3]) by ismailmkt.icomverse.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id YJHQ1KYW; Mon, 13 Dec 1999 08:48:23 +0200
Received: by UNITY-MAIL.QUANTUM.icomverse.com with Internet Mail Service (5.5.2650.21)
	id <YCY1SPRH>; Mon, 13 Dec 1999 08:48:56 +0200
Message-ID: <5B34AF33D291D311A06D0004AC1509D70120F5@UNITY-MAIL.QUANTUM.icomverse.com>
From: "Pearlman, Naty" <Naty_Pearlman@icomverse.com>
To: ietf-ldup@imc.org
Cc: "'rweiser@digsigtrust.com'" <rweiser@digsigtrust.com>,
        "'stokes@austin.ibm.com'" <stokes@austin.ibm.com>
Subject: Comments to ldup draft
Date: Mon, 13 Dec 1999 08:48:55 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>

Hello,

I suggest that the terms "Replica Ring" and " Replication" should explicitly
define that standard replication is to be enabled between different
Directory vendors, even though it is defined in 5.1

I suggest that it is the mission of the working group to define the standard
schema (as part of the draft or as part of the RFC) that is mentioned in
7.1, 7.2 in order to make sure that all Directory vendors implementations
expose the same information.

I suggest that a conceptual outline of conflict resolution procedures should
be part of the draft (or the RFC) , to make sure that the tools developed by
Directory vendors for conflict resolution enable resolution on all
Directories participating in any replication agreement, especially when they
are not from a single Directory vendor.

Regards,

Naty Pearlman
Comverse Network Systems
Tel: (972) 3 645 2047
Fax:(972) 3 645 4866
Email: naty_pearlman@comverse.com



From owner-ietf-ldup@imc.org  Tue Dec 21 22:01:29 1999
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18511
	for <ldup-archive@odin.ietf.org>; Tue, 21 Dec 1999 22:01:28 -0500 (EST)
Received: (from majordomo@localhost)
	by ns.secondary.com (8.9.3/8.9.3) id SAA29338
	for ietf-ldup-bks; Tue, 21 Dec 1999 18:29:06 -0800 (PST)
Received: from THOR.INNOSOFT.COM (SYSTEM@THOR.INNOSOFT.COM [192.160.253.66])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id SAA29329
	for <ietf-ldup@imc.org>; Tue, 21 Dec 1999 18:29:04 -0800 (PST)
Received: from threadgill.austin.innosoft.com ([207.8.108.5])
 by INNOSOFT.COM (PMDF V5.2-32 #30494)
 with ESMTP id <01JJRUJMRNC491VTPN@INNOSOFT.COM> for ietf-ldup@imc.org; Tue,
 21 Dec 1999 18:32:34 PST
Received: from threadgill.austin.innosoft.com
 (threadgill.austin.innosoft.com [207.8.108.5])
 by austin.innosoft.com (PMDF V5.2-32 #41296)
 with SMTP id <0FN400IL0F284N@austin.innosoft.com>; Tue,
 21 Dec 1999 20:32:32 -0600 (CST)
Date: Tue, 21 Dec 1999 20:32:32 -0600
From: Mark Wahl <M.Wahl@innosoft.com>
Subject: Re: WG Last Call: draft-ietf-ldup-model-02.txt
In-reply-to: "Your message of Thu, 09 Dec 1999 22:42:23 PST."
 <4.1.19991209223541.00c76240@omega.cisco.com>
To: John Strassner <jstrassn@cisco.com>, capple@att.com
Cc: Mark Wahl <M.Wahl@innosoft.com>
Cc: ietf-ldup@imc.org
Message-id: <25202.945829952@threadgill.austin.innosoft.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 8BIT
Sender: owner-ietf-ldup@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ldup/mail-archive/>
List-ID: <ietf-ldup.imc.org>
List-Unsubscribe: <mailto:ietf-ldup-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8BIT


I have a procedural question on this last call.   draft-ietf-ldup-model-02.txt
references the following drafts, among others, which I believe have never been
through a working group last call.

    [LDUP Info.] - E. Reed, "LDUP Replication Information Model", Internet
    Draft, draft-reed-ldup-infomod-00-1.txt, August 1998.

    [LDUP Protocol] - G. Good, E. Stokes 'The LDUP Replication Update
    Protocol' , Internet Draft, draft-ietf-ldup-protocol-00.txt, May 1999.

    [LDUP URP] -  S. Legg 'LDUP Update Reconciliation Procedures',
    Internet Draft, draft-legg-ldup-urp-00.txt, February 1999.

    [UUID] - P. Leach, R. Salz, "UUIDs and GUIDs", Internet draft, draft-
    leach-uuids-guids-01.txt, February 1998.

The draft-ietf-ldup-model-02.txt make explicit reference to these drafts
to define how LDUP operates.  Furthermore, draft-ietf-ldup-model-02.txt
fairly significantly constrains the contents of these documents, for 
example:

    The LDUP Protocol document [LDUP Protocol] defines an LDAP Extended
    Response, End Replication Response, that is sent in reply to an End
    Replication Request, from the Responder to the Supplier. The Response
    can optionally include an Update Vector.

    If the [*** NON ASCII CHARACTER 0221 ***]return update vector’ flag in the request was set then the
    Consumer should return its Update Vector to the Supplier.

Now in LDAPEXT we just ran into a problem where we last called the Java LDAP 
API, but I didn't notice that it relied on a Java SASL API internet draft 
until after the Java LDAP API last call ended.  Then we found that the Java 
SASL API draft had not gone through last call, and so we might need to rework 
one part of the LDAP API to change the use to the SASL API draft.

I wouldn't think the model draft would go through the IESG without them
wanting to review the documents on which this depend.  

So in reviewing draft-ietf-ldup-model-02.txt, how should we treat sections of 
this draft which depend on these other drafts?  Should we assume the 
information model, protocol, URP are part of this last call?  If so, should
the last call make this explicit?  

If not, then the problem would be if model goes through last call, but a 
dependency draft in its last call sometime later needs a change which would 
affect the model draft.  The model draft would then presumably come back to 
the working group, we last call it, and start again.  If this has to happen 
for each of the other LDUP drafts then it might be easier to do this all at 
once.

For one example, I feel strongly that naming contexts are identified by 
operational attributes and pointers from other entries, not by their object 
class values.  This change would primarily impact the Information Model, 
except that the Replication Architecture section 5.1 states as well

    The Naming Context Auxiliary Class is added to container entries that
    may have separately defined replication policy. [LDUP Info]

If my comment were submitted during the last call for draft-reed-ldup-infomod
and accepted, then the drafts would be out of synch with each other.  

Mark Wahl, Directory Product Architect
Innosoft International, Inc.


