[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: RFC 2255bis



Jim wrote

> The inclusion of all search constraints isn't only for referrals and
> search continuations. It would be nice to allow a client to construct
> an LDAP URL and to be able to convey various constraints.
> 

This in my opinion is where LDAP has got it wrong. It is generally a 
bad idea to use the same data construct for two different purposes. 
A referral does not serve the same purpose as a LDAP URL in 
general, and to use the same data construct for both is a bad idea. 
It leads to this messing up of features that Jim is proposing. (I tried 
to get this idea over in my old ID for knowledge references if I 
remember correctly <draft-ietf-ldapext-referral-01.txt> from March 
1998)

David

> It also is needed for future applications of the LDAP URL. Today, the
> iPlanet server allows one to construct a dynamic group using an LDAP
> URL. Because of today's limitations, alias dereferencing and size/time
> limits cannot be specified. In the future, there may be other types of
> attributes that wish to hold an LDAP URL for various reasons and it is
> limiting to not allow a full search operation to be expressed.
> 
> I believe the additional constraints can be added to the end of the
> URL as optional elements. This would not inherently add to the
> complexity of the LDAP URLs that people are used to seeing. It simply
> provides more consistency.
> 
> The alternative is to define a set of LDAP URL extensions that are
> used to specify the additional constraints. I'm willing to write that
> draft if it comes to that.
> 
> Jim
> 


***************************************************

David Chadwick
IS Institute, University of Salford, Salford M5 4WT
Tel +44 161 295 5351  Fax +44 161 745 8169
Mobile +44 790 167 0359
Email D.W.Chadwick@salford.ac.uk
Home Page  http://www.salford.ac.uk/its024/chadwick.htm
Understanding X.500  http://www.salford.ac.uk/its024/X500.htm
X.500/LDAP Seminars http://www.salford.ac.uk/its024/seminars.htm
Entrust key validation string MLJ9-DU5T-HV8J

***************************************************