Lightweight Directory Access Protocol
draft-ietf-asid-ldapv2-protocol-00
Document | Type |
Expired Internet-Draft
(asid WG)
Expired & archived
|
|
---|---|---|---|
Authors | Steve Kille , Wengyik Yeong , Tim Howes | ||
Last updated | 1996-05-14 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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 protocol described in this document is designed to provide access to the X.500 Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the X.500 Directory, and is intended to be a complement to the DAP itself. Key aspects of LDAP are - Protocol elements are carried directly over TCP or other transport, bypassing much of the session/presentation overhead. - Many protocol data elements are encoding as ordinary strings (e.g., Distinguished Names). - A lightweight BER encoding is used to encode all protocol elements.
Authors
Steve Kille
Wengyik Yeong
Tim Howes
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)