Re: Transactions in LDAP

[capple@master.control.att.com (Christopher W Apple)]

>The consensus was to keep it simple (no requirement for 2-phase commit).  
>The proposal on the table is to add an ldap extension (could be an ldap
>control or ldap protocol extension or something else) for begin/end/abort 
>transaction.  Three scenarios were identified and these will be used to
>evaluate the solution:
>  client-server:  treat several ldap operations as a transaction (single 
>			server)
>  client-server: above case extended to multi-server for transactional 
>			support in the ldap in support of intelligent networks 
>			and routers

Since there is already talk of having multi-master replication policies,
does it make sense to treat this case as a particular configuration of
using client-server LDAP transactions against multiple-masters of information
in conjunction with such a replication policy?

>  server-server: replication cases

Is the idea here to have one server act as a client and the other as
the true server within the context of one transaction? And that the roles
might be reversed on the next transaction?

>
>Cisco volunteered to co-author a draft with IBM in this ldap transactions
>area. 

Is this going to be a requirements document, or a extension/control
specification straight out of the BOF?

Chris Apple
Internet Directory Group
AT&T Laboratories
capple@master.control.att.com
+1 908 582 2409