> This gets to the heart of the matter. It is now 8 years later and RADB is > not catching on. But during the same time period some other UMich people > worked on a more general purpose directory service called LDAP and that > one is catching on. LDAP technology can be made to do the job that we need > done and instead of having to create tools from scratch we can leverage a > lot of commercial tools to deal with the core functions.
you are confusing an application service, radb, with an underlying store protocol, ldap. e.g., show me a routing db in ldap that has 10% the use of radb. by your reckoning, sql is the technology, as ripe, apnic, and many others use it as the *store* for their routing databases. randy