RFC 1777: Lightweight Directory Access Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3494.
Current document in this lineage: RFC 3494 — Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status; RFC 4510 — Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map; RFC 4511 — Lightweight Directory Access Protocol (LDAP): The Protocol; RFC 4512 — Lightweight Directory Access Protocol (LDAP): Directory Information Models; RFC 4513 — Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms; RFC 4514 — Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names; RFC 4515 — Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters; RFC 4516 — Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator; RFC 4517 — Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules; RFC 4519 — Lightweight Directory Access Protocol (LDAP): Schema for User Applications; RFC 4523 — Lightweight Directory Access Protocol (LDAP) Schema Definitions for X.509 Certificates
In plain English — editorial summary, not part of the RFC
The protocol described in this document is designed to provide access to the X.500 Directory while not incurring the resource requirements of the Directory Access Protocol (DAP).This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the X.500 Directory, and is intended to be a complement to the DAP itself. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1777
- Published
- March 1995
- Authors
- W. Yeong; T. Howes; S. Kille
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 22
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 35 RFCs, each formally replacing the one before it.
- RFC 1484 (1993)
- RFC 1485 (1993)
- RFC 1487 (1993)
- RFC 1488 (1993)
- RFC 1558 (1993)
- RFC 1777 (1995)
- RFC 1778 (1995)
- RFC 1779 (1995)
- RFC 1781 (1995)
- RFC 1959 (1996)
- RFC 1960 (1996)
- RFC 2251 (1997)
- RFC 2252 (1997)
- RFC 2253 (1997)
- RFC 2254 (1997)
- RFC 2255 (1997)
- RFC 2256 (1997)
- RFC 2559 (1999)
- RFC 2587 (1999)
- RFC 2829 (2000)
- RFC 2830 (2000)
- RFC 3377 (2002)
- RFC 3494 (2003)
- RFC 3674 (2003)
- RFC 3771 (2004)
- RFC 4510 (2006)
- RFC 4511 (2006)
- RFC 4512 (2006)
- RFC 4513 (2006)
- RFC 4514 (2006)
- RFC 4515 (2006)
- RFC 4516 (2006)
- RFC 4517 (2006)
- RFC 4519 (2006)
- RFC 4523 (2006) ✓
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 1778The String Representation of Standard Attribute SyntaxesObsoleted
March 1995
- RFC 1779A String Representation of Distinguished NamesObsoleted
March 1995
- RFC 1781Using the OSI Directory to Achieve User Friendly NamingObsoleted
March 1995
- RFC 1733Distributed Electronic Mail Models in IMAP4Current
December 1994
- RFC 1732IMAP4 Compatibility with IMAP2 and IMAP2bisCurrent
December 1994
- RFC 1823The LDAP Application Program InterfaceCurrent
August 1995
- RFC 1731IMAP4 Authentication MechanismsCurrent
December 1994
- RFC 1959An LDAP URL FormatObsoleted
June 1996
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?