A new Request for Comments is now available in online RFC libraries.


        RFC 1823:

        Title:      The LDAP Application Program Interface
        Author:     T. Howes & M. Smith
        Date:       August 1995
        Mailbox:    tim@umich.edu, mcs@umich.edu
        Pages:      22
        Characters: 41,081
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1823.txt


This document defines a C language application program interface to
the lightweight directory access protocol (LDAP). The LDAP API is
designed to be powerful, yet simple to use. It defines compatible
synchronous and asynchronous interfaces to LDAP to suit a wide variety
of applications.  This document gives a brief overview of the LDAP
model, then an overview of how the API is used by an application
program to obtain LDAP information.  The API calls are described in
detail, followed by an appendix that provides some example code
demonstrating the use of the API.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute