new attributes for DSA objects

Paul-Andre Pays <Paul-Andre.Pays@inria.fr> Mon, 27 January 1992 12:19 UTC

Received: from nri.reston.va.us by NRI.NRI.Reston.VA.US id aa11740; 27 Jan 92 7:19 EST
Received: from bells.cs.ucl.ac.uk by NRI.NRI.Reston.VA.US id aa11715; 27 Jan 92 7:19 EST
Via: bells.cs.ucl.ac.uk; Mon, 27 Jan 1992 10:31:18 +0000
Received: from nsfnet-relay.ac.uk by sun.nsfnet-relay.ac.uk with Internet SMTP id <sg.10640-1@sun.nsfnet-relay.ac.uk>; Mon, 27 Jan 1992 10:13:55 +0000
Received: from [192.93.2.39] by vax.NSFnet-Relay.AC.UK via NSFnet with SMTP id aa03098; 27 Jan 92 9:49 GMT
Original-Received: from nuri.inria.fr by concorde.inria.fr, Mon, 27 Jan 92 10:54:39 +0100
PP-warning: Illegal Received field on preceding line
Original-Received: by nuri.inria.fr, Mon, 27 Jan 92 10:50:42 +0100
PP-warning: Illegal Received field on preceding line
Date: Mon, 27 Jan 92 10:50:42 +0100
From: Paul-Andre Pays <Paul-Andre.Pays@inria.fr>
Message-Id: <9201270950.AA00634@nuri.inria.fr>
To: osi-ds@cs.ucl.ac.uk
Subject: new attributes for DSA objects
Sender: pays@nuri.inria.fr


It is probably very late, but I forward a proposal
that could possibly be discussed by WG3

-- PAP





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

A proposal from Alain Zahm <zahm@osi.e3x.fr>  (from E3X):


DSA administration is of particular interest for users. Wether 99% of
the directory users will never administrate a server, all of them
will be interested by the QOS  their actual connection server is offering
them. So it seems that a DSA object well defined may help administrators
as well as users.

   The problem is :

      - standard doesn't take this problem in account

      - some administrative aspects may be implementation dependent


   On the other hand if nothing is done in this domain, a read request
concerning DSA entries may return unreadable useful information. So my
proposal is to specify in DSA entries the administrative limits they use
(size_limit, time_limit), by means of two attributes:

sizeLimit ATTRIBUTE
WITH ATTRIBUTE SYNTAX integerSyntax
SINGLE VALUE
::= -- oid no yet defined

timeLimit ATTRIBUTE
WITH ATTRIBUTE SYNTAX integerSyntax
SINGLE VALUE
::= -- oid no yet defined


Furthermore we have implemented a specific search feature concerning the
scope of expension. As it may be extremely costly, it seems to be
interesting to limit the number of DSAs towards which search may be
expanded. This is done through a specific attribute:

expandTo ATTRIBUTE
WITH ATTRIBUTE SYNTAX distinguishedNameSyntax -- a value contains the
                                              -- distinguished name of a DSA
                                              -- towards which a search
                                              -- operation may be expanded
MULTI VALUE
::= -- oid no yet defined


Of course this attribute is linked with one specific implementation, but as
you may see the knowledge of the value will lead the user to know how the
DSA works, and what kind of answer he may expect from this DSA


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