RFC 3876: Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3)
In plain English — editorial summary, not part of the RFC
This document describes a control for the Lightweight Directory Access Protocol version 3 that is used to return a subset of attribute values from an entry. Specifically, only those values that match a "values return" filter. Without support for this control, a client must retrieve all of an attribute's values and search for specific values locally. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3876
- Published
- September 2004
- Authors
- D. Chadwick; S. Mullan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3928Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP)Current
October 2004
- RFC 2891LDAP Control Extension for Server Side Sorting of Search ResultsCurrent
August 2000
- RFC 2739Calendar Attributes for vCard and LDAPUpdated
January 2000
- RFC 2649An LDAP Control and Schema for Holding Operation SignaturesCurrent
August 1999
- RFC 2247Using Domains in LDAP/X.500 Distinguished NamesUpdated
January 1998
- RFC 3866Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP)Current
July 2004
- RFC 3909Lightweight Directory Access Protocol (LDAP) Cancel OperationCurrent
October 2004
- RFC 3727ASN.1 Module Definition for the LDAP and X.500 Component Matching RulesCurrent
February 2004
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?