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

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

At 09.12 -0800 00-12-03, Eric A. Hall wrote:
>This is a problem for every federated namespace. BUT just because the
>problem is the same for all of them does not mean that you might as well
>use DNS. DNS has many other problems in addition to this one which make it
>even more unsuitable, not equally unsuitable.

I agree completely. I am not arguing _for_ DNS. I just explain why 
people want to use it.

>Tell me how you will index partial elements of a value in DNS? If I want
>to find all of the email addresses which contain "ehsco.com" how do I
>search for this? How do I setup the backend? This specific functionality
>is not defined nor is it even feasible with DNS. It is well suited to LDAP
>however.

It is not well suited in LDAP either, as you might have referrals 
(like in DNS), but no server-server protocol which transfer the index 
which is needed.

>Second: how do you define per-RR ACLs in DNS? If I want to publish my work
>phone to all anonymous agents, my cell phone to fellow employees, and my
>home/emergency info to my family, how do I do this in DNS?

This exists in LDAP, given that the bind operations succeedes, and 
you agree with the server on what bind mechanisms you want to use.

>DNS is a crap directory.

I have not claimed that DNS makes searches possible. What I claim is 
that lookup (which you do in DNS) work crap in LDAP because of lack 
of root server, LDAP doesn't give searches etc etc.

    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.