Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!GIPSI.GIPSI.FR!philipp
From: philipp@GIPSI.GIPSI.FR (Philippe Prindeville)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: BIND bug list
Message-ID: <9005311516.AA09617@Gipsi.Gipsi.Fr>
Date: 31 May 90 17:16:50 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 17

The resolver shouldn't be a system call (since it is session layer),
but at the same time it shouldn't be linked into every applicaton,
since you might want to upgrade it or add functionality.  Really,
the best thing to do is to RPC to a local resolver daemon that can
do things like measure which servers give timely responses, and
which ones are south.  Also, things like address sorting based on
policy constraints could be done there also.

If this sounds like ypbind to you, Don't Panic.  I'm not advocating
yellow pages.  Just saying there should be more thread/RPC type
design in UNIX.

It would be nice if the IAB would say type-X RPC (XDR, etc) will be
the official protocol of the Internet, so we could get on with the
design of system servers...

-Philip