Additions to document archive
Paul Barker <P.Barker@cs.ucl.ac.uk> Fri, 29 October 1993 16:52 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06665;
29 Oct 93 12:52 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa06661;
29 Oct 93 12:52 EDT
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa15141;
29 Oct 93 12:52 EDT
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP
id <g.05198-0@haig.cs.ucl.ac.uk>; Fri, 29 Oct 1993 16:17:11 +0000
Received: from bunnahabhain.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP
id <g.02519-0@bells.cs.ucl.ac.uk>; Fri, 29 Oct 1993 16:17:02 +0000
To: osi-ds@cs.ucl.ac.uk
Subject: Additions to document archive
Date: Fri, 29 Oct 93 16:17:01 +0000
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Barker <P.Barker@cs.ucl.ac.uk>
Message-ID: <9310291252.aa15141@CNRI.Reston.VA.US>
Two recently published notes are now available by FTP from the osi-ds/ archive
at cs.ucl.ac.uk.
Paul
=================================================
OSI-DS 41
osi-ds-41-01.txt
Naming and Structuring Guidelines for X.500 Directory Pilots
Paul Barker
Steve Kille
Thomas Lenggenhager
October 1993
Abstract:
Deployment of a Directory will benefit from following certain
guidelines. This document defines a number of naming and
structuring guidelines focused on White Pages usage.
Alignment to these guidelines is recommended for directory pilots.
The final version of this document will replace RFC 1384.
OSI-DS 42
osi-ds-42-00.txt
Connection-less Lightweight Directory Access Protocol
Alan Young
October 1993
Abstract:
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 communica-
tion and it facilitates use of the directory in a manner analagous to
the DNS [6,7]. It is specifically targeted at simple lookup applica-
tions 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 [5].
The protocol specification draws heavily on that of LDAP.
------------------------------------------------------------------------
- Additions to document archive Paul Barker