Re: Minutes from San Diego
Mark Kosters <[email protected]>
| Newsgroups | gmane.ietf.whois |
|---|---|
| Message-ID | <[email protected]> |
LDAP is one of the things we are experimenting with as well. We have tuned our software and can handle loads that are similar to the NSI registry. If you want, look at http://www.ldap.research.netsol.com/. We just recently announced the availability of a public domain whois -> ldap gateway for other registrars to want experiment with us but don't want to build a backend interface right away. We also have included a demo of access control (look at the different attributes that are displayed for a query issued by an anonymous user, an attorney, or the tech contact for a domain). Personally, I torn with LDAP. It has all this crufty X.500 stuff that it has to deal with. It would be much nicer to have a textual protocol that is xml based or even tagged as attribute/value pairs. On the other hand, LDAP offers some really nice features like ACL's, automatic navigation (via v3 referrals), structured attributes, and deployed LDAP clients on the desktop. IMHO, ACLs will be one of the things registries will need to confront to deal with the balance of privacy vs operational vs attorney issues. Mark On Fri, Jan 19, 2001 at 04:16:17PM +0100, Stig Venaas wrote: > We (well, NORID) plan to put the Whois data in an LDAP server, this is > one of the requirements though. We might try to implement this in Open- > LDAP. > > I think LDAP might be a good alternative, but we should probably write > up requirements first of all. > > Stig -- Mark Kosters [email protected] Verisign Applied Research PGP Key fingerprint = 1A 2A 92 F8 8E D3 47 F9 15 65 80 87 68 13 F6 48