[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



> -----Original Message-----
> From: Dennis Glatting [mailto:dennis.glatting@software-munitions.com]
> Sent: Sunday, December 03, 2000 1:00 AM
> To: Patrik F=E4ltstr=F6m
> Cc: Randy Bush; Paul A Vixie; namedroppers
> Subject: Re: draft-ietf-dnsext-apl-rr-01.txt
>=20
>=20
> Patrik F=3DE4ltstr=3DF6m wrote:
> > At 14.35 -0800 00-12-02, Dennis Glatting wrote:
> >> But there is, isn't there? LDAP, as in, for example,=20
> ldap.cisco.com.
>=20
> > Ok, I have to take one step further down this slippery path:
> > Question: You want to know the phone number of "Eva Fr=3DF6lich". =
What
> > LDAP database do you search in?
>=20
> The same is true of DNS: which domain should you search? If you can't
> find something in DNS then how do you find it in LDAP, and visa =
versa?
> By pushing garbage from DNS to LDAP you at least have a hint of
> directory and database (the DAP part). DNS, it seems to me, is more =
of
> a locator service but people are trying to make it a database.
>=20
>=20

There is already a service that is used for user information and it =
does not
require any knowledge of containers or server location.  Finger is used =
to
retrieve user information based on email address.  DNS is supposed to =
be a
small, lightweight, quick program.  If we include a large amount of
information in the data for DNS, the resulting searches will become =
slower.



-------------------------------------
Mike Burns
net-linx Publishing Solutions - Ann Arbor
Senior Systems Engineer/
Systems Engineering Manager
ICQ#39636054
email: mike@nxps.com



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