Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site uwmacc.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!uwvax!uwmacc!darling
From: darling@uwmacc.UUCP (Jean Darling)
Newsgroups: net.mail.headers
Subject: Re: SMTP source verification.
Message-ID: <1370@uwmacc.UUCP>
Date: Tue, 6-Aug-85 18:22:50 EDT
Article-I.D.: uwmacc.1370
Posted: Tue Aug  6 18:22:50 1985
Date-Received: Fri, 9-Aug-85 02:23:07 EDT
References: <337@brl-tgr.ARPA>
Organization: UWisconsin-Madison Academic Comp Center
Lines: 27

We are bringing up a local TCP/IP network connecting a heterogeneous 
bunch of operating systems.  One of the things we want our network
to do for us is allow certain peripheral output devices (plotter, photo-
typesetter, laser printer, etc) to be shareable by any authorized user
on the network (under our administration, they have to pay!).

We expect to have some sort of global authorization system which would
contain network ids and passwords.  We will need some kind of global 
queues for these devices as well.  We are beginning the process of designing
some network servers to do this sort of thing, but we'd prefer not to
re-invent the wheel.

The authentication problem comes up for PC users of the network; we
*think* that having a network password would protect us fairly well, and
perhaps would take care of making sure the right PC user is collecting
the right mail.  Perhaps we would have to use the encryption scheme
to make sure someone wasn't pretending to be the authorization server.

[How feasible is it to try to treat some local IP addresses like ports,
available to PCs on a first-come first-served basis?  (These addresses
could only be known locally...users from outside would have to mail to
the gateway nameserver machine.)]

Please help clear away the fog.  Any comments, suggestions, or pointers
to references will be welcomed.

Jean Darling