Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site peora.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!petsd!peora!jer
From: jer@peora.UUCP (J. Eric Roskos)
Newsgroups: net.mail
Subject: Re: Mail addressing and routing
Message-ID: <1617@peora.UUCP>
Date: Wed, 11-Sep-85 09:03:09 EDT
Article-I.D.: peora.1617
Posted: Wed Sep 11 09:03:09 1985
Date-Received: Thu, 12-Sep-85 09:47:12 EDT
References: <644@adobe.UUCP> <169@graffiti.UUCP>
Organization: Perkin-Elmer SDC, Orlando, Fl.
Lines: 27

> If too much stuff is going through ut-sally, I get a nasty letter back &
> start sending stuff through ihnp4.  Or through someone else.  This way no-
> one NEEDS to take on an excess load.

> I don't expect anyone to pay any attention to me, since I'm just a
> lowly peon who can't afford a machine big enough to compile pathalias
> on... but in case anyone has got this far, consider it...

The scheme you have described is what I have been calling the "distributed
nameserver" scheme, which in MY "lowly peon" opinion, is the way to do it.
I disagree with the geographic sudomain scheme for cost reasons, but aside
from that, you have just described the routing string generated by a
nameserver when it routes a message to the next nameserver down the line.

PS - you don't have to compile pathalias on your machine to use the
approach we've been talking about.  I certainly don't have it on my PC (which
has only 1 500K and 1 1MB floppy disk... hardly enough for the pathalias
database!).
-- 
Shyy-Anzr:  J. Eric Roskos
UUCP: Ofc:  ..!{decvax,ucbvax,ihnp4}!vax135!petsd!peora!jer
     Home:  ..!{decvax,ucbvax,ihnp4}!vax135!petsd!peora!jerpc!jer
  US Mail:  MS 795; Perkin-Elmer SDC;
	    2486 Sand Lake Road, Orlando, FL 32809-7642

	"Nalgvzr gbzbeebj, gur cubar'yy evat, naq lbh'yy or ba lbhe jnl.
	 Onpx ubzr va Buvb, gurl jba'g oryvrir lbh..."