LDAP Schema for Internet Mail
draft-srivastava-ldap-mail-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Daryl A. Huff , Anil Srivastava , Anil Srivastava , Ellen Siegel | ||
| Last updated | 1998-11-24 | ||
| 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
The use of directory services based on the Lightweight Directory Access Protocol (LDAP) [LDAP] is becoming increasingly popular for distributed and web-based services. Since most LDAP-based applications have developed their schemas independently, new application designers find themselves faced with the dilemma of how to interoperate with an already conflicting set of existing LDAP specifications. Today's Web-aware customers expect interoperability, so it is crucial to converge existing schema in a way that supports interoperability across arbitrary applications and vendors. In this spirit, we describe an LDAP schema for internet mail routing and delivery that is designed to be modular and to support a common core for sharing user state across an arbitrary set of applications.
Authors
Daryl A. Huff
Anil Srivastava
Anil Srivastava
Ellen Siegel
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)