ACP 133 Common Content and LDAP
draft-dally-acp133-and-ldap-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kathy Dally | ||
| Last updated | 2000-09-25 | ||
| 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
In Allied Communications Publication (ACP) 133 [1], an X.500 directory user schema, called Common Content, is specified for the Allied Directory. In order to enable Lightweight Directory Access Protocol (LDAP) access to the Allied Directory and to enable the general use by others of elements from the Common Content, this document specifies the encoding of the Common Content using the LDAP notation from Request for Comments (RFC) 2252 [2].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)