Notes from our 10/21 meeting

Attending were Bill, Brian, Marine, Oliver, and Naomi

We spent a majority of the meeting going over Oliver's proposal
(which in turn had been built on Thomas' suggestions from last
week), which is as follows (slightly ammended from his original to
include what came out of our discussion):

A.  DEFINITIONS

* MIT - for the purposes of licensing and deployment, is anyone
with a valid MIT kerberos principal (and therefore the ability to
get AFS tokens).  this is a broad definition, but it is the same
one used by the certificate server, necx, and MIT site-licensed
software distribution.

* Athena Workstation - for the purposes of licensing and
deployment, is any machine running at least these essential Athena
services: Kerberos, Hesiod, and AFS as prodvided by an Athena
Release

* Machine Administered by MIT's Athena Computing Environment - any
Athena Workstation (as defined above) which appears in the Athena
billing database

B. CLASSES OF 3PARTYSW

Class I: licensed to "MIT."  system:authuser access control can be
used for software located in AFS.  certificates can be used for
download of motif and transcript packages.

Class II:  licensed to "Athena" and "Athena Workstations." 
system:authuser access control can be used to restrict access
(install in AFS and never distributed as packages)

Class III: licensed to "Machines Administered by MIT's Athena
Computing Environment."  Restricted by belonging to a list of
machines, identical to the list in the Athena billing database.

Class IV:  licensed by a specific number of concurrent users. 
Restricted in the same way ad Class III machines, not because of
legal license restrictions, but rather to enable us to recover our
costs for adding additional licenses as our population of users
expands.

C.  FEES (proposed - no student fees collected)

* admin fee - 
	Full install machines - paid by depts and labs
	Layered machines - no fee

* triage/reinstall fee -
	Full install machines - paid by depts and labs
	Layered machines - no fee

* SW fee -
	Full install machines - paid by depts and labs
	Layered machines - those that want to run Class III and IV
		software pay this fee
	Students are in the database, but their fee is 0

* HW maintenance - Brian will make a proposal about what he'd like
to see for both Full Install and Layered machines

NOTE:  There has historically never been a portion of the Athena
fees that goes to infrastructure of servers, bug fixes, OLC
consulting, etc.  We anticipate that adding Linux/Athena and
Layered Linux/Athena will not change this.

Suggestion about how we might control access to Class III and
Class IV software: use a version of the wrapper that does not use
encryption, to speed up startup time (Q: why do we use encryption
in the first place?)

Suggestion about how we might manage the list of machines with
access to Class III and Class IV software - in addition to the
possibilities of AFS groups (development work would be needed by
Ops to enable this) or the software wrapper, might use a Moira
flag.  

Questions that remain:

1.  What fees should be charged for Standard and Layered Linux
Athena?  We need to balance cost recovery with guiding people to
the appropriate product. 

2.  What is the $ impact of putting out Layered Linux Athena.

3.  What is the best mechanism for restricting access to software
for machines on the list?

4.  What is a simple, automated way for machines to be registered
to be on the list?

We'll pick up the discussion here at next week's meeting -

Thursday, Oct 28, 3:30 - 5:00 PM, N42-203