My only concern with the document has to do with moving to RFC 2587 to historical. Are there any other RFCs from the PKIX group that depend on RFC 2587? If so, wouldn't moving 2587 to historical require them to be moved as well?
Internet-Drafts@ietf.org Sent by: owner-ietf-ldapbis@OpenLDAP.org
11/06/2001 02:03 PM
Please respond to Internet-Drafts
To: IETF-Announce: ;
Subject: I-D ACTION:draft-zeilenga-ldapv2-01.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories.
Title : LDAPv2 to Historical Status
Author(s) : K. Zeilenga
Filename : draft-zeilenga-ldapv2-01.txt
Pages : 4
Date : 05-Nov-01
This note discusses moving version 2 of the Lightweight Directory
Access Protocol [LDAPv2] and dependent specifications to Historic
A URL for this Internet-Draft is:
To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.
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
A list of Internet-Drafts directories can be found in
Internet-Drafts can also be obtained by e-mail.
Send a message to:
In the body type:
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