RFC 3673: Lightweight Directory Access Protocol version 3 (LDAPv3): All Operational Attributes
In plain English — editorial summary, not part of the RFC
The Lightweight Directory Access Protocol (LDAP) supports a mechanism for requesting the return of all user attributes but not all operational attributes. This document describes an LDAP extension which clients may use to request the return of all operational attributes.
Document record
- Document ID
- RFC3673
- Published
- December 2003
- Authors
- K. Zeilenga
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3676The Text/Plain Format and DelSp ParametersCurrent
February 2004
- RFC 2976The SIP INFO MethodObsoleted
October 2000
- RFC 4685Atom Threading ExtensionsCurrent
September 2006
- RFC 2520NHRP with Mobile NHCsCurrent
February 1999
- RFC 2227Simple Hit-Metering and Usage-Limiting for HTTPCurrent
October 1997
- RFC 1976PPP for Data Compression in Data Circuit-Terminating Equipment (DCE)Current
August 1996
- RFC 5497Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)Current
March 2009
- RFC 5587Extended Generic Security Service Mechanism Inquiry APIsCurrent
July 2009
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?