OSI-DS 33 and 34 - DUA and DSA Metrics

Steve Hardcastle-Kille <S.Kille@isode.com> Wed, 10 June 1992 22:34 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa08468; 10 Jun 92 18:34 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa06348; 10 Jun 92 18:33 EDT
Received: from bells.cs.ucl.ac.uk by NRI.Reston.VA.US id aa06342; 10 Jun 92 18:33 EDT
Received: from glenlivet.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id <g.03731-0@bells.cs.ucl.ac.uk>; Wed, 10 Jun 1992 21:38:00 +0100
From: Steve Hardcastle-Kille <S.Kille@isode.com>
To: osi-ds@cs.ucl.ac.uk
Subject: OSI-DS 33 and 34 - DUA and DSA Metrics
Phone: +44-71-223-4062
Date: Wed, 10 Jun 92 21:37:23 +0100
Message-ID: <3225.708208643@UK.AC.UCL.CS>
Sender: S.Kille@cs.ucl.ac.uk

Two new OSI-DS notes are available.   Please send comments.



OSI-DS 33
osi-ds-33-00.ps
osi-ds-33-00.txt
	DUA Metrics
	P. Barker
	June 1992
   This is a part of a PARADISE Deliverable.
The note defines a set of criteria by which a
DUA implementation, or more precisely a
Directory user interface, may be judged.
Particular issues covered include terminal
requirements; style of interface; target user;
default object classes and attribute types; use
of DAP; error handling.
   The intention is that the replies to the
questions posed describe the DUA / user
interface fairly fully.  Some of the questions
will yield answers which are purely
descriptive; others, however, are intended to
yield answers which give some measure of the
utility of the DUA. The marks awarded for a DUA
in each particular area should give a good
indication of the DUA's capabilities, and its
suitability for various tasks.
   It should be noted that the focus of this
document is very much on ``white pages'' DUAs.
this is a reflection of the current information
base.  Nevertheless much of the document will
be applicable to DUAs developed for other types
of Directory usage.



OSI-DS 34
osi-ds-34-00.ps
osi-ds-34-00.txt
	DSA Metrics
	P. Barker
	S.E. Hardcastle-Kille
	June 1992
       This is a part of a PARADISE Deliverable.
    The note defines a set of criteria by which a
    DSA implementation may be judged.  Particular
    issues covered include conformance to
    standards; performance; demonstrated
    interoperability.
       The intention is that the replies to the
    questions posed describe the DSA fairly fully.
    Some of the questions will yield answers which
    are purely descriptive; others, however, are
    intended to yield answers which give some
    measure of the utility of the DSA. The marks
    awarded for a DSA in each particular area
    should give a good indication of the DSA's
    capabilities, and its suitability for
    particular uses.



------------------------------------------------------------------------




The following topics  may be obtained from the info-server
using a request in the form:
        request: osi-ds
        topic: <one of topics the below>

For example:

From: Joe.Soap@somedomain
To: info-server@cs.ucl.ac.uk
Subject: Anything you like

request: osi-ds
topic: scope.txt	


Files are available in Text, Postscript or both.   
    FILENAME.txt for plain text format
    FILENAME.ps  for postscript

Note that not all the files are available in all the formats.

All documents are numbered, in the form OSI-DS nnn or
 OSI-DS-MINUTES nnn

The files are also available by FTP, NIFTP, and  FTAM.

FTP to CS.UCL.AC.UK, username anonymous and your own name as password
		cd osi-ds; 

FTAM to bells, computer science, university college london, gb 
   username = anon, no password

NIFTP to uk.ac.ucl.cs, binary mode, username  =  guest,
     password  =  (Your  mail address in the form user@site)
     filenames should be prepended with <OSI-DS> (Note that the
     angle brackets and capital letters are vital)