Re: Experimental RFC to be: draft-zeilenga-ldap-txn-15.txt

The IESG <> Mon, 21 December 2009 20:45 UTC

Return-Path: <>
Received: by (Postfix, from userid 30) id A14A728C176; Mon, 21 Dec 2009 12:45:14 -0800 (PST)
X-idtracker: yes
From: The IESG <>
To: RFC Editor <>
Subject: Re: Experimental RFC to be: draft-zeilenga-ldap-txn-15.txt
Message-Id: <>
Date: Mon, 21 Dec 2009 12:45:14 -0800 (PST)
Cc:, The IESG <>,
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 21 Dec 2009 20:45:14 -0000

The IESG has no problem with the publication of 'LDAP Transactions' <draft-zeilenga-ldap-txn-15.txt> as an Experimental RFC.

The IESG would also like the IRSG or RFC-Editor to review the comments in 
the datatracker 
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is Alexey Melnikov.

A URL of this Internet-Draft is:

The process for such documents is described at

Thank you,

The IESG Secretary

Technical Summary

   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.

Working Group Summary

   This document is not the result of any IETF Working Group,
   it is an independent submission to the RFC Editor.

Document Quality

   Alexey Melnikov has reviewed this specification for conformance
   with the RFC 4520 requirements for allocation of new LDAP protocol
   mechanisms (FCFS policy), and for RFC 3932 requirements for conflict
   with IETF work or processes.


   Alexey Melnikov is the Responsible Area Director.

RFC Editor Note

  The IESG believes that this work doesn't conflict with any work
  done in IETF, so it has no note to insert into this document,
  and no objection to its publication.