Lightweight Directory Access Protocol (LDAP) Transactions
draft-zeilenga-ldap-txn-15

[Ballot comment]
I support Adrian's DISCUSS. I believe that this document is very useful and that Experimental is the right status for it, and for these reasons I would like to see the conditions of the experiment and the criteria for success clearly defined.

[Ballot discuss]
I note the email exchange with Kurt about why this I-D is presented as
Experimental. However, this document really isn't phrased as an
Experiment. For example, the Abstract says "This document extends LDAP
to support transactions." An Experiment would be more likely to say
"This document defines experimental extensions to LDAP to support
transactions. It is intented that these extensions be used in a
controlled environment while the experiment is evaluated."

I would also expect a note somewhere in the document that describes the
scope of the Experiment and says how it will be evaluated.

On the other hand, Kurt's explanation makes this work sound more like an
Informational publication. In that case the Abstract and Introduction
might include some text along the lines of "This document describes
extensions made to LDAP to support transactions in a private
implementation. The extensions are documented to allow other
implementers to understand this work and to leverage it if they want."

[Ballot comment]
I think the section in the write-up labelled "IESG Note" should be
  labelled "Note to RFC Editor".  The intent is not to put the text
  in that section into the document.

IANA comments:

Upon approval of this document, the IANA will make the following
assignments:

======================================
======================================
in the "Lightweight Directory Access Protocol (LDAP) Parameter" registry
located at
http://www.iana.org/assignments/ldap-parameters
sub-registry "Object Identifier Descriptors"

NAME Type OID Reference
---- ---- ----------------- ---------
txn O IANA-ASSIGNED-OID [RFC-zeilenga-ldap-txn-15]

Legend
------------------------
O => Object Class


======================================
======================================
in the "Lightweight Directory Access Protocol (LDAP) Parameter" registry
located at
http://www.iana.org/assignments/ldap-parameters
sub-registry "Protocol Mechanisms"

Object Identifier Type Description Reference
------------------- ---- ---------------------------------- ---------
IANA-ASSIGNED-OID.1 E Start Transaction Extended Request
[RFC-zeilenga-ldap-txn-15]
IANA-ASSIGNED-OID.2 C Transaction Specification Control
[RFC-zeilenga-ldap-txn-15]
IANA-ASSIGNED-OID.3 E End Transaction Extended Request
[RFC-zeilenga-ldap-txn-15]
IANA-ASSIGNED-OID.4 N Aborted Transaction Notice
[RFC-zeilenga-ldap-txn-15]

Legend
------------------------
N => Unsolicited Notice

[Ballot comment]
>3.5. Miscellaneous Issues
>
>  Transactions cannot be nested.

Can you clarify what you mean here?
Do you mean that the client can't issue several Transaction Start commands in a row (on a single LDAP association)?

>5. Distributed Directory Considerations
>
>  This mechanism defined by this document does not support client-side
>  chasing.  Transaction identifiers are specific to a particular LDAP
>  association (as established via the LDAP Bind operation).

Just to double check: does this mean that transaction identifiers can't be reused on other LDAP connections and that they don't have to be globally unique?

>10.2. Informative References
>
>  [DONTUSECOPY] Zeilenga, K., "LDAP Don't Use Copy Control", draft-
>                zeilenga-ldap-dontusecopy-xx.txt, a work in progress.

Expired?

This document was submitted to the RFC Editor to be published as an
Experimental Independent Submission: draft-zeilenga-ldap-txn-15.txt.

Please let us know if this document conflicts with the IETF standards
process or other work being done in the IETF community.

Four week timeout expires on 28 December 2009.


LDAP Transactions

Lightweight Directory Access Protocol (LDAP) update operations, such
as Add, Delete, and Modify operations, have atomic, consistency,
isolation, durability (ACID) properties. Each of these update
operations act upon an entry. It is often desirable to update two
or more entries in a single unit of interaction, a transaction.
Transactions are necessary to support a number of applications
including resource provisioning. This document extends LDAP to
support transactions.