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


        RFC 1798:

        Title:      Connection-less Lightweight Directory Access
                    Protocol 
        Author:     A. Young
        Date:       June 1995
        Mailbox:    A.Young@isode.com
        Pages:      9
        Characters: 18,548
        Updates/Obsoletes:  none

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


The protocol described in this document is designed to provide access
to the Directory while not incurring the resource requirements of the
Directory Access Protocol (DAP).  In particular, it is aimed at
avoiding the elapsed time that is associated with connection-oriented
communication and it facilitates use of the Directory in a manner
analagous to the DNS (Domain Name Service).  It is specifically
targeted at simple lookup applications that require to read a small
number of attribute values from a single entry.  It is intended to be
a complement to DAP and LDAP (Lightweight Directory Access Protocol).
The protocol specification draws heavily on that of LDAP.  This memo
was initiated in the [now defunct] OSI Directory Services Working
Group and completed by the Access and Synchronization of the Internet
Directories Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  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-REQUEST@NIC.DDN.MIL.

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