Re: draft-ietf-dnsext-apl-rr-01.txt

[Patrik Fältström <paf@cisco.com>]

At 14.35 -0800 00-12-02, Dennis Glatting wrote:
>But there is, isn't there? LDAP, as in, for example, ldap.cisco.com.

Ok, I have to take one step further down this slippery path:

Question: You want to know the phone number of "Eva Fr=F6lich". What 
LDAP database do you search in?

Even if you want to know more about "paf@cisco.com", what LDAP 
database do you go to, what query do you issue, and what schema do 
you use? What base DN is the record in?

=46urther, even if you know "/C=3DSE/O=3DCisco/CN=3DPatrik Faltstrom", what 
LDAP server do you go to?

Answer:
LDAP doesn't work globally because of the lack of indexing (only 
strict hierarchies like DNS exists, and works) and noone have been 
able to create "the root" which should work as the root nameservers. 
If this root existed, you should still only be able to query for 
records if you knew the DN. Now, the DN is both the location and 
unique identity of a record which is what I call "overloading the DN 
with information". If a record moves from one server to another one, 
the DN changes. Because of this, I as a person can not have one DN 
for the rest of my life as a unique identifier for my record.

So, as LDAP only handle the same kind of lookups as DNS (hierarichal 
when you happen to know the global unique identifier), is slower and 
doesn't have root servers in the world, people look instead at DNS as 
it works.



But, as I said, this discussion need a bar.

     paf


-- 


to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.