🚀 go-pugleaf

	Well, looks like this one was able to be replied to.  Good.

	So how about if some diligent persons on the Internet implement
and debug name servers, and then pass the source to other sites?  With
any luck, the (already overworked) sys.admins will be able to bring it
up without too much trouble; not nearly as much as having to implement it
all themselves, which admittedly is quite a task.  I suspect that there
are enough sites short of manpower to keep this thing from getting off
the ground on schedule.  Am I right, or are there [research community]
hosts that just don't *want* to convert?

	For now, of course, the undesirable '%' kludge *must* be used.
It's nice that Cal is so far ahead of the game that they've had domains
working locally for years.  But as we've seen you can't force it on the
Internet, even if it should be out there and working weeks ago (according
to RFC 921).  Is it possible for those who are with it to help out those
behind?  If we could do this it might even convince the DDN people that
it can be done smoothly, and that our national defense systems won't be
out to lunch for a month cause nobody can look up hosts  ;-)  Of course
there are serious problems to be worked out (some local ones which you
pointed out, and others)...

	I know that research community is stuck in the middle, it's
not their fault, etc. etc.  How can we help get this worked out?  We
don't need any more finger pointing, name calling, or blame shifting.
We do need working electronic communication networks.

			      --      jad      --
			         John A Dilley

----------