policies.html 3.52 KB
Newer Older
Jay Lepreau's avatar
Jay Lepreau committed
1 2
<html>
<head>
Jay Lepreau's avatar
Jay Lepreau committed
3
	<title>emulab.net - Administrative Policies</title>
4
	<link rel='stylesheet' href='tbstyle-plain.css' type='text/css'>
Jay Lepreau's avatar
Jay Lepreau committed
5 6 7
</head>
<body>

8
<center>
Jay Lepreau's avatar
Jay Lepreau committed
9
<h1>Administrative Policies</h1>
10 11 12 13 14
</center>

Most any legitimate research/experimental use is allowed, including
use by companies.  Of course, when demand exceeds supply we will have
to assign priorities to projects, but the hardware base will be expanding.
Jay Lepreau's avatar
Jay Lepreau committed
15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56

<h2>Acceptable Use, Allocation Priority, Reporting, Governance, Disclaimer</h2>

Our current and anticipated policies follow.  We expect these to
evolve as experience demands, and we are open to constructive
suggestions concerning them.

<h3>Acceptable Use</h3>
In principle, almost any research or experimental use of the testbed
by experimenters that have a need for it is appropriate.
<p>
"Abuse" of the facility or its other users, in any form, will of course
result in termination of access.  Abuse includes using the facility
for other than a project's stated purpose.

<h3>Allocation Priority</h3>

When the testbed become oversubscribed we will be allocating its
resources based on some function-- currently vague but in roughly
this order-- of
perceived research value and broader impact,
the testbed's uniqueness as a suitable platform for the research,
novelty as a testbed application,
resources required (typically: number of nodes),
experimenters' contribution to testbed software development,
experimenters' lack of access to other appropriate facilities,
sponsorship by our primary sponsors (currently NSF and Cisco),
educational value,
affiliation with an academic institution,
whether the project is funded/peer-reviewed,
and for commercial users, their willingness to help defray costs, i.e., pay.
<p>

Many development-oriented commercial experiments and evaluations will
be allowed, but low priority.


<h3>Reporting</h3>

In order to assess the testbed's impact and report to our sponsors, we
simply require notice of all publications or patents to which the testbed
contributed.  Formal acknowledgement in such publications is required
57 58 59 60 61 62 63 64 65 66
as well. Something like the following:

<blockquote>
"We blah blah blah ... 
emulab.net, the Utah Network Emulation Testbed,
which is primarily supported by NSF grant ANI-00-82493 and Cisco Systems."
</blockquote>

<p>
Finally, we will be soliciting feedback and suggestions from
Jay Lepreau's avatar
Jay Lepreau committed
67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87
our users.

<h3>Governance</h3>

An administrative board, including representatives from our major
sponsors, will be involved in setting broad policy and have review
authority.  Typically, a small executive committee composed of members
from the University of Utah Flux research group will decide most
resource allocation issues.
<p>
A Technical Advisory Board is also being formed, containing distinguished
members of the network and distributed systems research communities.

<h3>Disclaimer</h3>

We are providing broad access to the testbed in the hopes that it will
be useful, but we do so WITHOUT ANY WARRANTY; without even the implied
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
<p>

We disclaim all liability from errors in results or security breaches
Jay Lepreau's avatar
Jay Lepreau committed
88 89 90 91 92
resulting from emulab's use.  The system is currently at
"beta" level but is constantly undergoing rapid development, so
significant amounts of code are always new.
We are making an effort to provide inter-project security, but users
must realize that high security is unlikely in i) such a new and rapidly
93 94 95
evolving system, ii) where users have such complete control over
hardware and software resources, and iii) in such a public facility
that will attract attack.