idnits 2.17.1 draft-zeilenga-ldapv2-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3494 5 Title: Lightweight Directory Access Protocol version 2 6 (LDAPv2) to Historic Status 7 Author(s): K. Zeilenga 8 Status: Informational 9 Date: March 2003 10 Mailbox: Kurt@OpenLDAP.org 11 Pages: 5 12 Characters: 9225 13 Obsoletes: 1484, 1485, 1487, 1488, 1777, 1778, 1779, 1781, 14 2559 16 I-D Tag: draft-zeilenga-ldapv2-04.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3494.txt 20 This document recommends the retirement of version 2 of the 21 Lightweight Directory Access Protocol (LDAPv2) and other dependent 22 specifications, and discusses the reasons for doing so. This document 23 recommends RFC 1777, 1778, 1779, 1781, and 2559 (as well as documents 24 they superseded) be moved to Historic status. 26 This memo provides information for the Internet community. It does 27 not specify an Internet standard of any kind. Distribution of this 28 memo is unlimited. 30 This announcement is sent to the IETF list and the RFC-DIST list. 31 Requests to be added to or deleted from the IETF distribution list 32 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 33 added to or deleted from the RFC-DIST distribution list should 34 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 36 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 37 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 38 help: ways_to_get_rfcs. For example: 40 To: rfc-info@RFC-EDITOR.ORG 41 Subject: getting rfcs 43 help: ways_to_get_rfcs 45 Requests for special distribution should be addressed to either the 46 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 47 specifically noted otherwise on the RFC itself, all RFCs are for 48 unlimited distribution.echo 49 Submissions for Requests for Comments should be sent to 50 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 51 Authors, for further information.