Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status
draft-zeilenga-ldapv2-04

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3494.
Author Kurt Zeilenga
Last updated 2020-01-21 (Latest revision 2002-12-18)
RFC stream Legacy stream
Intended RFC status Informational
Formats
txt htmlized pdf bibtex bibxml
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3494 (Informational)
Action Holders
(None)
Telechat date (None)
Responsible AD Patrik Fältström
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-zeilenga-ldapv2-04 
A new Request for Comments is now available in online RFC libraries.

        RFC 3494

        Title:      Lightweight Directory Access Protocol version 2
                    (LDAPv2) to Historic Status
        Author(s):  K. Zeilenga
        Status:     Informational
        Date:       March 2003
        Mailbox:    Kurt@OpenLDAP.org
        Pages:      5
        Characters: 9225
        Obsoletes:  1484, 1485, 1487, 1488, 1777, 1778, 1779, 1781,
                    2559

        I-D Tag:    draft-zeilenga-ldapv2-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3494.txt

This document recommends the retirement of version 2 of the
Lightweight Directory Access Protocol (LDAPv2) and other dependent
specifications, and discusses the reasons for doing so.  This document
recommends RFC 1777, 1778, 1779, 1781, and 2559 (as well as documents
they superseded) be moved to Historic status.

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.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.