Skip to main content

Lightweight Directory Access Protocol (LDAP) Transactions
RFC 5805

Revision differences

Document history

Date Rev. By Action
2018-01-30
15 (System) Received changes through RFC Editor sync (added Errata tag)
2015-10-14
15 (System) Notify list changed from kurt.zeilenga@isode.com, draft-zeilenga-ldap-txn@ietf.org, rfc-ise@rfc-editor.org to rfc-ise@rfc-editor.org
2012-08-22
15 (System) post-migration administrative database adjustment to the No Objection position for Adrian Farrel
2010-03-10
15 Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2010-03-10
15 Amy Vezza [Note]: 'RFC 5805' added by Amy Vezza
2010-03-09
15 (System) RFC published
2010-03-02
15 Cindy Morgan State Change Notice email list have been change to kurt.zeilenga@isode.com, draft-zeilenga-ldap-txn@tools.ietf.org, rfc-ise@rfc-editor.org from kurt.zeilenga@isode.com, draft-zeilenga-ldap-txn@tools.ietf.org, rfc-editor@rfc-editor.org
2010-01-15
15 Cindy Morgan State Changes to RFC Ed Queue from Approved-announcement sent by Cindy Morgan
2010-01-08
15 (System) IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor
2010-01-06
15 (System) IANA Action state changed to Waiting on RFC Editor from In Progress
2010-01-06
15 (System) IANA Action state changed to In Progress from Waiting on Authors
2010-01-05
15 (System) IANA Action state changed to Waiting on Authors from In Progress
2010-01-05
15 (System) IANA Action state changed to In Progress from Waiting on Authors
2010-01-05
15 (System) IANA Action state changed to Waiting on Authors from In Progress
2009-12-22
15 (System) IANA Action state changed to In Progress
2009-12-21
15 Amy Vezza IESG state changed to Approved-announcement sent
2009-12-21
15 Amy Vezza IESG has approved the document
2009-12-21
15 Amy Vezza Closed "Approve" ballot
2009-12-18
15 (System) Removed from agenda for telechat - 2009-12-17
2009-12-17
15 Amy Vezza State Changes to Approved-announcement to be sent from IESG Evaluation by Amy Vezza
2009-12-17
15 Adrian Farrel [Ballot Position Update] Position for Adrian Farrel has been changed to No Objection from Discuss by Adrian Farrel
2009-12-17
15 Lisa Dusseault [Ballot Position Update] New position, No Objection, has been recorded by Lisa Dusseault
2009-12-17
15 Dan Romascanu
[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 …
[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.
2009-12-17
15 Dan Romascanu [Ballot Position Update] New position, No Objection, has been recorded by Dan Romascanu
2009-12-17
15 Cullen Jennings [Ballot Position Update] New position, No Objection, has been recorded by Cullen Jennings
2009-12-17
15 Magnus Westerlund [Ballot Position Update] New position, No Objection, has been recorded by Magnus Westerlund
2009-12-17
15 Adrian Farrel
[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 …
[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."
2009-12-17
15 Adrian Farrel [Ballot Position Update] New position, Discuss, has been recorded by Adrian Farrel
2009-12-17
15 Russ Housley
[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 …
[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.
2009-12-17
15 Russ Housley [Ballot Position Update] New position, No Objection, has been recorded by Russ Housley
2009-12-16
15 Amanda Baber
IANA comments:

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

======================================
======================================
in the "Lightweight Directory Access Protocol (LDAP) Parameter" registry …
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
2009-12-16
15 Lars Eggert [Ballot comment]
What's experimental about this protocol extension and why is it on the independent stream rather than going for PS?
2009-12-16
15 Lars Eggert [Ballot Position Update] New position, No Objection, has been recorded by Lars Eggert
2009-12-09
15 Robert Sparks [Ballot Position Update] New position, No Objection, has been recorded by Robert Sparks
2009-12-04
15 Alexey Melnikov
[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 …
[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?
2009-12-04
15 Alexey Melnikov State Changes to IESG Evaluation from AD Evaluation by Alexey Melnikov
2009-12-04
15 Alexey Melnikov [Ballot Position Update] New position, Yes, has been recorded for Alexey Melnikov
2009-12-04
15 Alexey Melnikov Ballot has been issued by Alexey Melnikov
2009-12-04
15 Alexey Melnikov Created "Approve" ballot
2009-12-04
15 (System) Ballot writeup text was added
2009-12-04
15 (System) Last call text was added
2009-12-04
15 (System) Ballot approval text was added
2009-12-02
15 Alexey Melnikov State Changes to AD Evaluation from Publication Requested by Alexey Melnikov
2009-12-02
15 Alexey Melnikov Placed on agenda for telechat - 2009-12-17 by Alexey Melnikov
2009-12-01
15 Russ Housley Removed from agenda for telechat - 2009-12-03 by Russ Housley
2009-12-01
15 Russ Housley Note field has been cleared by Russ Housley
2009-12-01
15 Russ Housley Responsible AD has been changed to Alexey Melnikov from Russ Housley
2009-12-01
15 Russ Housley Area acronymn has been changed to app from gen
2009-11-30
15 Cindy Morgan
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 …
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.
2009-11-30
15 Cindy Morgan Draft Added by Cindy Morgan in state Publication Requested
2008-12-19
15 (System) New version available: draft-zeilenga-ldap-txn-15.txt
2008-12-15
14 (System) New version available: draft-zeilenga-ldap-txn-14.txt
2008-11-24
13 (System) New version available: draft-zeilenga-ldap-txn-13.txt
2008-07-14
12 (System) New version available: draft-zeilenga-ldap-txn-12.txt
2007-11-20
11 (System) New version available: draft-zeilenga-ldap-txn-11.txt
2007-07-11
10 (System) New version available: draft-zeilenga-ldap-txn-10.txt
2006-10-24
09 (System) New version available: draft-zeilenga-ldap-txn-09.txt
2006-06-28
08 (System) New version available: draft-zeilenga-ldap-txn-08.txt
2006-03-07
07 (System) New version available: draft-zeilenga-ldap-txn-07.txt
2003-05-05
06 (System) New version available: draft-zeilenga-ldap-txn-06.txt
2002-11-06
05 (System) New version available: draft-zeilenga-ldap-txn-05.txt
2002-06-17
04 (System) New version available: draft-zeilenga-ldap-txn-04.txt
2001-11-26
03 (System) New version available: draft-zeilenga-ldap-txn-03.txt
2001-04-03
02 (System) New version available: draft-zeilenga-ldap-txn-02.txt
2001-02-12
01 (System) New version available: draft-zeilenga-ldap-txn-01.txt
2000-08-10
00 (System) New version available: draft-zeilenga-ldap-txn-00.txt