Re: Anti Capitalism?

[bmanning@ISI.EDU]

> > Actually, I wouldn't.  Putting the data in DNS is to support one
> > purpose:  finding a person to fix a problem when DNS doesn't work.
> > As a privacy advocate, I see no reason to facilitate people finding
> > every system I might be the contact for, for example.  Or is that
> > what you meant by a "reverse map"?
> >
> 
> That means there'll be DNS crawlers. And everyone was wigging out last
> year over the existing load... 8-(
> 
> Actually, the most useful feature would be geographic mapping within
> DNS for any host record. It's a feature request (GPS-DNS anyone?  ;).
> The other stuff is usefull from a white pages perspective.
> 
> >
> > Dump the zone, grep for TXT fields with the appropriate headers (eg
> > "Contact-id: KC125", and build a database from it.  This was Paul
> > Vixie's idea about how to support a white-pages directory service.
> > He imagined several competing directory service organizations doing
> > it.
> >
> 
> I still don't see why this couldn't be built into DNS. It's no
> different from creating in-addr.arpa records. You just need to ensure
> the hierarchy is built properly to support it (ObjectDNS anyone? ;).
> 
> Regards,
> 
> Simon
> 
> --
> If at first you don't succeed, skydiving is not for you.
> 

	When did this list become "redefine existing DNS capabilities".

	All the facilities that you crave are defined and there are
	even a few implementations.

	This kicker is that you can't -force- your downstreams  
	to add these records.


--bill