RFC 2589 on LDAPv3 Extensions for Dynamic Directory Services
RFC Editor <rfc-ed@ISI.EDU> Tue, 01 June 1999 22:10 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07083; Tue, 1 Jun 1999 18:10:20 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA09081 for ietf-123-outbound.10@ietf.org; Tue, 1 Jun 1999 18:05: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 SAA09059 for <all-ietf@loki.ietf.org>; Tue, 1 Jun 1999 18:03:28 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06983 for <all-ietf@ietf.org>; Tue, 1 Jun 1999 18:00:00 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA14584; Tue, 1 Jun 1999 15:00:00 -0700 (PDT)
Message-Id: <199906012200.PAA14584@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2589 on LDAPv3 Extensions for Dynamic Directory Services
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 01 Jun 1999 14:59:59 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
RFC 2589:
Title: Lightweight Directory Access Protocol (v3):
Extensions for Dynamic Directory Services
Author(s): Y. Yaacovi, M. Wahl, T. Genovese
Status: Proposed Standard
Date: May 1999
Mailbox: yoramy@microsoft.com, Mark.Wahl@INNOSOFT.COM,
tonyg@microsoft.com
Pages: 12
Characters: 26855
Updates/Obsoletes/See Also: None
I-D Tag: draft-ietf-asid-ldapv3-dynamic-08.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2589.txt
This document defines the requirements for dynamic directory services
and specifies the format of request and response extended operations
for supporting client-server interoperation in a dynamic directories
environment.
This document is a product of the Access, Searching and Indexing of
Directories Working Group of the IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. 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.echo
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 Alegre Ramos
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.