RFC 4373 on Lightweight Directory Access Protocol (LDAP) Bulk Update/Replication Protocol (LBURP)
rfc-editor@rfc-editor.org Mon, 30 January 2006 20:55 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F3g42-0005no-QI; Mon, 30 Jan 2006 15:55:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F3g40-0005cP-6e for ietf-announce@megatron.ietf.org; Mon, 30 Jan 2006 15:55:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27099 for <ietf-announce@ietf.org>; Mon, 30 Jan 2006 15:53:59 -0500 (EST)
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F3gEZ-0001sh-2T for ietf-announce@ietf.org; Mon, 30 Jan 2006 16:06:47 -0500
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k0UKtX55015982; Mon, 30 Jan 2006 12:55:33 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id k0UKtXuL015981; Mon, 30 Jan 2006 12:55:33 -0800
Date: Mon, 30 Jan 2006 12:55:33 -0800
Message-Id: <200601302055.k0UKtXuL015981@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="04dd299b1861c67629992514689cd2d5"
X-Spam-Score: -13.9 (-------------)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4373 on Lightweight Directory Access Protocol (LDAP) Bulk Update/Replication Protocol (LBURP)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries. RFC 4373 Title: Lightweight Directory Access Protocol LDAP Bulk Update Replication Protocol LBURP Author: R. Harrison, J. Sermersheim, Y. Dong Status: Informational Date: January 2006 Mailbox: rharrison@novell.com, jimse@novell.com, yulindong@gmail.com Pages: 16 Characters: 31091 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-rharrison-lburp-05.txt URL: http://www.rfc-editor.org/rfc/rfc4373.txt 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. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ...
A new Request for Comments is now available in online RFC libraries. RFC 4373 Title: Lightweight Directory Access Protocol LDAP Bulk Update Replication Protocol LBURP Author: R. Harrison, J. Sermersheim, Y. Dong Status: Informational Date: January 2006 Mailbox: rharrison@novell.com, jimse@novell.com, yulindong@gmail.com Pages: 16 Characters: 31091 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-rharrison-lburp-05.txt URL: http://www.rfc-editor.org/rfc/rfc4373.txt 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. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ...
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce