RFC 4518: Lightweight Directory Access Protocol (LDAP): Internationalized String Preparation
In plain English — editorial summary, not part of the RFC
The previous Lightweight Directory Access Protocol (LDAP) technical specifications did not precisely define how character string matching is to be performed. This led to a number of usability and interoperability problems. This document defines string preparation algorithms for character-based matching rules defined for use in LDAP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4518
- Published
- June 2006
- Authors
- K. Zeilenga
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4519Lightweight Directory Access Protocol (LDAP): Schema for User ApplicationsCurrent
June 2006
- RFC 4517Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching RulesCurrent
June 2006
- RFC 4516Lightweight Directory Access Protocol (LDAP): Uniform Resource LocatorCurrent
June 2006
- RFC 4520Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)Current
June 2006
- RFC 4515Lightweight Directory Access Protocol (LDAP): String Representation of Search FiltersCurrent
June 2006
- RFC 4514Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished NamesCurrent
June 2006
- RFC 4513Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security MechanismsUpdated
June 2006
- RFC 4512Lightweight Directory Access Protocol (LDAP): Directory Information ModelsCurrent
June 2006
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?