Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site mit-hermes.ARPA
Path: utzoo!linus!philabs!cmcl2!harvard!think!mit-eddie!mit-hermes!dms
From: dms@mit-hermes.ARPA (David M. Siegel)
Newsgroups: net.mail
Subject: Re: The TRUTH about .UUCP
Message-ID: <2504@mit-hermes.ARPA>
Date: Mon, 7-Oct-85 09:43:19 EDT
Article-I.D.: mit-herm.2504
Posted: Mon Oct  7 09:43:19 1985
Date-Received: Wed, 9-Oct-85 06:36:00 EDT
Organization: The MIT AI Lab, Cambridge, MA
Lines: 25


   From: henry@utzoo.UUCP (Henry Spencer)
   Keywords: sponge leech freeloader domains routing_overhead

   The problem is not so much the additional overhead of doing routing, but
   the additional volume of traffic that such strategies cause.  The creed
   of the domainists is that sites should determine more direct paths (how?)
   and remember them, to speed traffic and avoid overloading central sites.
   What the creed does not supply is the strong incentives that would be
   necessary to actually convince people to do this, when it's so much easier
   to just freeload a little more on the central sites.  

Maybe the "domain servers" would just supply path information back to
the requestor. With this approach, the requestors would have incentive
to cache address information (to speed up mail xfers). Granted, the
overall mail transfer speed might go down (but not by much of the
order of host polling and caching protocols were done right). This is
like the way the internet is doing domaining. The domain servers give
a name and pass back an address (really a path). 


-Dave
-- 
					Arpa:	dms@mit-hermes.arpa
					Usenet:	mit-eddie!mit-hermes!dms