🚀 go-pugleaf

In <1991May22.081251.1026@uunet.uu.net> asp@uunet.uu.net (Andrew Partan) writes:

>[stuff deleted]

>If someone can write some software that can distinguish between
>	customer!customer-node!user
>and
>	customer!non-customer-node!user
>for all customers w/o us having to keep a database of interior customer
>nodes, then we will consider running it.

>Until that point, we would rather use one of our operators to do the
>ftping of files.

Simple.  Require that all uunet customers enlist in the domain process.  Or,
to enforce that, allow the service to be available only to customers that have
enrolled in the domain system.  UUNET should know about domain names of its
customers, and customers should operate all nodes under their domain (ie, no 
organization "is supposed" to have more than one domain name).  Now, if a 
customer had a neighboring site for which it wished to allow anon-ftp requests
from the neighbor site to uunet (ie, customer agrees to let neighbor send 
requests "via" customer's account (ieie, customer will pass teh request and
subsequently pay for return responses)), then customer could notify uunet of
the domain of customer's neighbor as being legal for requesting via customer's
uunet channel.  

This is very much the case with me as I have a telebit and
900+ megs of online space here at Jobsoft.  I share the uunet service (ie, 
split costs) with a public access node here (that I co-admin), RaiderNet
Public Access, which has its own domain, RAIDERNET.COM.  My domain is 
JOBSOFT.COM.  UUNET should immediately (from my account info) know I am
a uunet customer.  Now, I would like for the RaiderNet system to be able to 
use the uunet ftp service without having to reside under my domain.  I would
send a letter to uunet!postmaster from my 'root' account giving authorization
for requests from the RaiderNet.COM domain to be honored as I have agreed to 
pay for them.  

This is not at all out of the question as when any node that
is not a uunet customer wants to setup a domain name using uunet as their
forwarder, they must obviously have their traffic routed through some site
that is a uunet customer.  UUNET's policy requires permission granted from 
the uunet customer's root account giving authorization for the non-uunet
site to route traffic via the uunet customer's site.  This is good as the 
uunet's customer is acknowledging he will pay for that traffic, both ways.
The non-uunet site might then start pumping up mail volumes, at the uunet
customer's expense.  But, as in my case, that has been arranged for.  So, 
when dealing with a uunet anon-ftp service, the senerio is essentially the
same (to a certain degree).  

Also, maintaining a database of domain names would be a lot more logical
than individual site names!  Also, is an organization (such as JobSoft) 
that were a uunet customer added several new unix stations, if uunet's 
authorization were based on domain names, no new arrangements would have
to be made, provided the organization kept the policy of all mail nodes 
being setup under that organization's domain name.  On the contrary, it 
would be quite a bit of work on both sides if individual nodes had to be
registered.  You might could use an organization map entry, but since when
are they really accurate?  Besides, the domain system has been preached to
us for years, why not put it to some additional use?

Just some thoughts.

Mark.

-- 
Mark J. Bailey, N4XHX                              _______/====X11====\_______
USMAIL: 511 Memorial Blvd., Murfreesboro, TN 37129 |         JobSoft         |
VOICE:  +1 615 893 0098                            | Design & Development Co.|
UUCP:   ...!uunet!mjbtn!mjb, ...!raider!mjbtn!mjb  |  Murfreesboro, TN  USA  |
DOMAIN: mjb@mjbtn.JOBSOFT.COM      CIS: 76314,160  ---------------------------
<KA9Q-UNIX-USERS Mailing List-Subscribe: ka9q-unix-requests@mjbtn.jobsoft.com>