Re: interworking issues

[Paul Barker <[e-mail]>]

> 3. the time-outs are very different and in some case don't even allow
>  for retrieving entries with larger content (eg. X.509 certificates)
>  especially when a X.25 link has to be used for reaching the leaf DSA.
>  they need to be short, but not that short
> 
My view is that timeouts should be as long as the patience of the user,
possibly within some very large maximum.

> 5. many clients algorithm for searches will not give good results
>   because they insist on searching filters which are not allowed
>     eg. UserId is NOT searchable for legal reasons in most french DSA
> 
This is a problem.  I favour some sort of search guide approach, where
organisations can identify the type of searches that are allowed beneath a
node.  This allows the best of both worlds: complicated filters if you want
them and they are supported, and the knowledge of what simple filters will
work as a lowest common denominator strategy.

> 7. some clients have strange behaviours preventing interop
>    this may come from the search filter see above
>    this also come from non-conformance (or Quipu proprietary features)
>    -- this seems to be the case of "de" (at least the publicly
>    available DUA at ULCC)

I wish you wouldn't say things like this (about DE) without some sort of 
supporting evidence.  DE doesn't use quipu object classes in filters.  It does
ask for the quipu attribute masterDSA when reading country entries, so that
it can use a modified search algorithm (more use of read and list) when
querying countries which do not use the Quipu distribution model.  Your
comments of two/three years ago prompted this change.
> 
> 8. there is still a severe lack of consistency for the respective use
>   of chaining vs referals
>   -> performance tend to mandate referals (at least in the higher
>     part of the hierrachy)

I am planning to examine this point very soon for some research I am doing.
My hunch is the the opposite of your assumption.

>   -> clients seems to be neraly completely unaware of loops
>   and of loop-detection code in such configurations.
> 
An argument for chaining, putting such complexity in DSAs, and having to 
get it right once, rather than in every DUI.
> 

> but let me terminate with the MOST SERIOUS one : conformance
> 

Inasmuch as this means that we all have to speak the same protocol, I agree.
Whether we should be looking for slavish conformance to a model which 
many of us doubt is THE way forward is another matter.  I suppose my fear
amounts to a feeling that conformance to strict X.500 will be one step
forward for Quipu (and anyone interoperating with it), but two steps back 
towards something of baroque complexity.

Paul