Re: DNS vs. non-DNS Data (was Re: Signature at parent (draft-ietf-dnsop-parent-sig-00.txt))

["Eric A. Hall" <[e-mail]>]

Robert Elz wrote:

> Personally, I have no problem with storing almost any kind of data in
> the DNS

I'm sure you didn't mean the example I'm about to give but I am taking the
bait anyway. :)

The problem with being too liberal wrt DNS data is that it dillutes the
effectiveness of the lookup service.

If for example under the "anything goes" principle somebody defines the
dreaded My-MP3-Files RR which returns records for every MP3 cataloged on a
specific server, it is possible for thousands of RRs to be returned.
However, those answers will also get returned whenever the associated
domain name is queried with a qtype=*

Ergo, everytime sendmail tries to enumerate the RRs for a destination
domain name, it would get overloaded with My-MP3-Files RRs, which would
either dillute or completely destroy the usability of DNS for simple
lookup functions.

That's maybe an exaggeration, but maybe it isn't, and really it will all
depend on how liberal the line is drawn. I advocate hard-liner positioning
in this matter. Heck it might even be worth a policy thing, no RRs get
approved without passing through DNSEXT first.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/


to unsubscribe send a message to [e-mail] with
the word 'unsubscribe' in a single line as the message text body.