Re: A tool for getting information out of the Quipu logfiles

[[e-mail]]

> > 
> > let me just point out that what is probably considered as
> > 0% reachability may probably in some case just
> > reflect the inability for your DSA to "interwork" with
> > some other implementations or operational modes.
> > 
> 
> 0% reachability is just 0% reachability, that is neither of these
> 6 DSAs ( all Quipu DSAs as PAP so rightly points out ) has been able 
> to make a connection to this other DSA.
> 
> Reachability does not include any operations between the DSAs
> besides the initial connection.

Well possibly I was too fast at interpreting your results
however I have some suspicion about many existing products
which start by a search  and Class=dSA in order to get
the different Dsas Acces Point when they are returned referals
(which as announced is what has been choosen and implemented
on the french master, all searches -except base object scope-
with base object C=FR will return referals ans will not be chained
whereas searches on a lower base object will be chained if needed.

> 
> Now, if the interworking between QuipuDSAs and DSAs of other origin is
> so bad that they can not even make a connection, then we really are in
> big trouble.


YES we are in big trouble
and I would appreciate QIPU specialists
to give their opinion on the subject
to announce when the QUipu internal model will change
  in order to provide interworking with non Quipu
to explain how they see the migration from old-quipus to new-ones
   an particularly the problem with public versions...

Avoiding the deal with this issue is clearly riding fast with closed
eyes right into a big concrete wall
The sooner it will at last be taken into account the highest
the probablility to save X.500 future

The only alternative would be to have the internet to standardize
on Quipu model and not on X500 but this woeld be another big problem

Please experts do comment!

-- PAP