[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Fwd: I-D ACTION:draft-rharrison-bulkldif-00.txt
Have you examined the work of the FIND group, in which the CIP (v2)
protocol has recently been moved to proposed standard? I think that there
is a certain similiarity between what you are trying to do and CIP and the
Tagged Index Object specification.
Bruce
At 12:37 PM 7/6/99 -0600, Roger Harrison wrote:
>Jim Sermersheim and I have published a draft describing an LDAP v3
extension to efficiently deliver and import LDIF data into an LDAP server.
>
>Our goal in writing this draft was to define a mechanism that allows large
numbers of LDAP operations to be specified by a remote client without the
overhead of responses for each operation. To do this, we've combined the
LDIF data format with a wire protocol that allows a client to initiate and
send LDIF data to the server and get periodic updates on the server's
progress in processing the data.
>
>We'd like to get input and feedback from the LDAP community both from a
design standpoint and to see if this is something that should be added to
the charter of the ldap-ext working group.
>
>If it's possible, we'd also like to get 5 minutes of time on the agenda to
discuss this idea in the ldap-ext meeting in Oslo.
>
>Thanks,
>
>Roger
>Received: from prv1-mx.provo.novell.com
> by prv-mail25.provo.novell.com; Fri, 02 Jul 1999 19:31:05 -0600
>Received: from loki.ietf.org
> by prv1-mx.provo.novell.com; Fri, 02 Jul 1999 19:33:36 -0600
>Received: (from adm@localhost)
> by loki.ietf.org (8.9.1b+Sun/8.9.1) id LAA06183
> for ietf-123-outbound.04@ietf.org; Fri, 2 Jul 1999 11:55:01 -0400 (EDT)
>Received: from ietf.org (odin.ietf.org [10.27.2.28])
> by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA05152
> for <all-ietf@loki.ietf.org>; Fri, 2 Jul 1999 07:55:32 -0400 (EDT)
>Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
> by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05792
> for <all-ietf@ietf.org>; Fri, 2 Jul 1999 07:51:25 -0400 (EDT)
>Message-Id: <199907021151.HAA05792@ietf.org>
>Mime-Version: 1.0
>Content-Type: Multipart/Mixed; Boundary="NextPart"
>To: IETF-Announce: ;
>From: Internet-Drafts@ietf.org
>Reply-to: Internet-Drafts@ietf.org
>Subject: I-D ACTION:draft-rharrison-bulkldif-00.txt
>Date: Fri, 02 Jul 1999 07:51:25 -0400
>Sender: nsyracus@NS.CNRI.RESTON.VA.US
>
>A New Internet-Draft is available from the on-line Internet-Drafts
directories.
>
>
> Title : LDAP v3 Extensions for Bulk Transfer of LDIF Data
> Author(s) : R. Harrison, J. Sermersheim
> Filename : draft-rharrison-bulkldif-00.txt
> Pages : 8
> Date : 01-Jul-99
>
>This document defines an LDAP extension to efficiently import LDIF
>into an LDAP server. The extension utilizes a protocol that
>maximizes the speed with which LDIF data can be presented to the
>LDAP server and yet allows the LDAP client to be kept apprised of
>errors and the progress of its request.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-rharrison-bulkldif-00.txt
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
> "get draft-rharrison-bulkldif-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
> mailserv@ietf.org.
>In the body type:
> "FILE /internet-drafts/draft-rharrison-bulkldif-00.txt".
>
>NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility. To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command. To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader. Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID: <19990701144022.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-rharrison-bulkldif-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-rharrison-bulkldif-00.txt>
>