Lightweight Directory Access Protocol (LDAP) Bulk Update/Replication Protocol (LBURP)
RFC 4373

Received changes through RFC Editor sync (changed abstract to 'The Lightweight Directory Access Protocol (LDAP) Bulk Update/Replication Protocol (LBURP) allows an LDAP client to perform a bulk update to an LDAP server. The protocol frames a sequenced set of update operations within a pair of LDAP extended operations to notify the server that the update operations in the framed set are related in such a way that the ordering of all operations can be preserved during processing even when they are sent asynchronously by the client. Update operations can be grouped within a single protocol message to maximize the efficiency of client-server communication.

The protocol is suitable for efficiently making a substantial set of updates to the entries in an LDAP server. This memo provides information for the Internet community.')

[Ballot comment]
inconsistency:

!! Missing Reference for citation: [X.680]
  P003 L035:    [X.680] message types specified in [RFC2251].

!! Missing citation for Normative reference:
  P012 L017:    [X680]    International Telecommunications Union, "Abstract Syntax

IANA Comments:
Upon approval of this document the IANA will assign a LDAP Object Identifier in the following registry:
http://www.iana.org/assignments/smi-numbers under the Prefix: iso.org.dod.internet.directory (1.3.6.1.1.)
For the 7 registrations under this OID, are these protocol mechanisms or Descriptors?  IANA needs clarification as to where these should be placed in the registry as well as what the type will be for these.
These will be placed in one of the registries found at the following:
http://www.iana.org/assignments/ldap-parameters

[Ballot discuss]
The first paragraph of the Security Considerations needs to
  discuss authentication as well as authorization.  How can the
  authorization decision be made without first performing
  identification and authentication?

  The Security Considerations include:
  >
  > The data contained in the update stream may contain passwords and
  > other sensitive data.  Care should be taken to properly safeguard
  > this information while in transit between supplier and consumer.
  >
  This is justification for confidentiality and integrity protections.
  How should they be provided?  If two LDAP servers in the same room
  are using this protocol for replication, it is probably not a big
  deal.  However, if the two servers are on different continents, then
  a security protocol is needed.  Any suggestions?  TLS?

New version needed which handle editorial nits. Has passed external review in LDAP Directorate.

Also, some clarification of how this I-D relates to LDUP WG work may be appropriate.