LDAPv3: All Operational Attributes
draft-zeilenga-ldapv3bis-opattrs-06
| Document | Type |
Expired Internet-Draft
(individual in app area)
Expired & archived
|
|
|---|---|---|---|
| Author | Kurt Zeilenga | ||
| Last updated | 2015-10-14 (Latest revision 2001-04-02) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Patrik Fältström | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
X.500 [X.500] provides a mechanism for clients to request all operational attributes be returned with entries provided in response to a search operation. This mechanism is often used by clients to discover which operatinal attributes are present in an entry. LDAP [RFC2251] does not provide a similar mechanism to clients.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)