RFC 3383: Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4520.
Current version: RFC 4520 — Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)
In plain English — editorial summary, not part of the RFC
This document provides procedures for registering extensible elements of LDAP (Lightweight Directory Access Protocol). The document also provides guidelines to IANA (Internet Assigned Numbers Authority) describing conditions under which new values can be assigned
Document record
- Document ID
- RFC3383
- Published
- September 2002
- Authors
- K. Zeilenga
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- app
- Pages
- 23
- Also known as
- —
- Obsoleted by:
- RFC 4520
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 2350Expectations for Computer Security Incident ResponseCurrent
June 1998
- RFC 5767User-Agent-Driven Privacy Mechanism for SIPCurrent
April 2010
- RFC 6271Requirements for SIP-Based Session PeeringCurrent
June 2011
- RFC 8085UDP Usage GuidelinesUpdated
March 2017
- RFC 3382Internet Printing Protocol (IPP): The 'collection' attribute syntaxObsoleted
October 2002
- RFC 3384Lightweight Directory Access Protocol (version 3) Replication RequirementsCurrent
October 2002
- RFC 3381Internet Printing Protocol (IPP): Job Progress AttributesObsoleted
October 2002
- RFC 3380Internet Printing Protocol (IPP): Job and Printer Set OperationsCurrent
October 2002
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?