RFC 2596: Use of Language Codes in LDAP
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3866.
Current version: RFC 3866 — Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP)
In plain English — editorial summary, not part of the RFC
This document describes how language codes are carried in LDAP and are to be interpreted by LDAP servers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2596
- Published
- May 1999
- Authors
- M. Wahl; T. Howes
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 9
- Also known as
- —
- Obsoleted by:
- RFC 3866
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 2696LDAP Control Extension for Simple Paged Results ManipulationCurrent
September 1999
- RFC 2820Access Control Requirements for LDAPCurrent
May 2000
- RFC 2829Authentication Methods for LDAPObsoleted
May 2000
- RFC 2927MIME Directory Profile for LDAP SchemaCurrent
September 2000
- RFC 2256A Summary of the X.500(96) User Schema for use with LDAPv3Obsoleted
December 1997
- RFC 2255The LDAP URL FormatObsoleted
December 1997
- RFC 2164Use of an X.500/LDAP directory to support MIXER address mappingCurrent
January 1998
- RFC 1960A String Representation of LDAP Search FiltersObsoleted
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?