idnits 2.17.1 draft-zeilenga-cldap-02.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 3352 5 Title: Connection-less Lightweight Directory Access 6 Protocol (CLDAP) to Historic Status 7 Author(s): K. Zeilenga 8 Status: Informational 9 Date: March 2003 10 Mailbox: Kurt@OpenLDAP.org 11 Pages: 4 12 Characters: 7265 13 Obsoletes: 1798 15 I-D Tag: draft-zeilenga-cldap-02.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3352.txt 19 The Connection-less Lightweight Directory Access Protocol (CLDAP) 20 technical specification, RFC 1798, was published in 1995 as a Proposed 21 Standard. This document discusses the reasons why the CLDAP technical 22 specification has not been furthered on the Standard Track. This 23 document recommends that RFC 1798 be moved to Historic status. 25 This memo provides information for the Internet community. It does 26 not specify an Internet standard of any kind. Distribution of this 27 memo is unlimited. 29 This announcement is sent to the IETF list and the RFC-DIST list. 30 Requests to be added to or deleted from the IETF distribution list 31 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 32 added to or deleted from the RFC-DIST distribution list should 33 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 35 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 36 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 37 help: ways_to_get_rfcs. For example: 39 To: rfc-info@RFC-EDITOR.ORG 40 Subject: getting rfcs 42 help: ways_to_get_rfcs 44 Requests for special distribution should be addressed to either the 45 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 46 specifically noted otherwise on the RFC itself, all RFCs are for 47 unlimited distribution.echo 48 Submissions for Requests for Comments should be sent to 49 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 50 Authors, for further information.