RFC 1798: Connection-less Lightweight X.500 Directory Access Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3352.
Current version: RFC 3352 — Connection-less Lightweight Directory Access Protocol (CLDAP) to Historic Status
In plain English — editorial summary, not part of the RFC
The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC1798
- Published
- June 1995
- Authors
- A. Young
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 9
- Also known as
- —
- Obsoleted by:
- RFC 3352
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1971IPv6 Stateless Address AutoconfigurationObsoleted
August 1996
- RFC 1945Hypertext Transfer Protocol -- HTTP/1.0Current
May 1996
- RFC 2564Application Management MIBCurrent
May 1999
- RFC 2565Internet Printing Protocol/1.0: Encoding and TransportObsoleted
April 1999
- RFC 2566Internet Printing Protocol/1.0: Model and SemanticsObsoleted
April 1999
- RFC 2567Design Goals for an Internet Printing ProtocolCurrent
April 1999
- RFC 2568Rationale for the Structure of the Model and Protocol for the Internet Printing ProtocolCurrent
April 1999
- RFC 2569Mapping between LPD and IPP ProtocolsCurrent
April 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?