Re: Anti Capitalism?

[Simon Higgs <simon@higgs.com>]

At 1:02 PM -0800 1/3/97, bmanning@ISI.EDU wrote:

> > > 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? ;).
> >
>
> 	When did this list become "redefine existing DNS capabilities".
>

When someone suggested the registry holds all the data in DNS - 'coz
DNS can't do it right now.

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

What's the RFC on reverse mapping the whois data from within the DNS hierarchy?

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

So who keeps the records?

These are all key points for the IAHC to provide a fix and not a kludge.

Regards,

Simon

--
If at first you don't succeed, skydiving is not for you.