[14] in Layered Athena
Re: Layered Athena Requirements
daemon@ATHENA.MIT.EDU (nschmidt@Athena.MIT.EDU)
Tue Mar 2 14:42:40 1993
From: nschmidt@Athena.MIT.EDU
To: Mark Rosenstein <mar@MIT.EDU>
Cc: layered-athena@Athena.MIT.EDU, nschmidt@Athena.MIT.EDU
In-Reply-To: Your message of Fri, 26 Feb 93 16:03:15 -0500.
Date: Tue, 02 Mar 93 14:15:49 EST
Hello Mark -
I think that the direction taken by your latest Athena Layering Requirements
document is right on target. One of the stickiest administrative questions
will be how we handle access to licensed third party software, as you point
out in section #8. Would it be possible to have an 11th subset, one that
costs money to be able to load, that enables that workstation to attach the
3rd party software lockers? I don't know if it's possible to do that on a
per machine (as contrasted with a per user) basis. If we had all of our
applications site-licensed to MIT, then this wouldn't be a problem. But we
are now starting to purchase licenses on some products for a limited number
of concurrent users, and therefore we can't afford to open access up to the
entire MIT community without in some way recovering the cost for the extra
licenses that we would have to purchase.
I am assuming in this that some private workstation owners only want access
to basic Athena services and are willing to pay only a base fee, while others
want access to the whole suite, including all the third party applications,
and are willing to pay extra for that.
Naomi
