Use of Aliases within LDAP
draft-byrne-ldap-alias-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ellen Stokes , Debbie Byrne , Ludovic Poitou | ||
| Last updated | 1998-04-22 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes the suggested behavior for aliases for LDAPv3 and above to improve LDAP server interoperability . The key words 'MUST', 'SHOULD', and 'MAY' used in this document are to be interpreted as described in [Bradner97].
Authors
Ellen Stokes
Debbie Byrne
Ludovic Poitou
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)