version of June 4, 2005
Due to the large set of projects supported by the HPWREN program,
it is unrealistic to utilize the network in an uncontrolled manner.
In order to continue to support and protect good science, education
and crisis response activities, it is critical that connected
collaborators understand that HPWREN's resources are limited, and
are careful about the load they impose on the network, as well as
onto the (rather small) support staff. Because of our shared
infrastructure situation, HPWREN users must follow these usage
conditions. If the usage conditions are changed, we will make an
attempt to inform HPWREN users; however, it is also your responsibility
to periodically read this agreement - as non-compliance may result
in immediate network disconnect.
- HPWREN collaborators need to have an understanding that HPWREN
is a collaborative research program, and not a generic and paid
for service. It is critical that each collaborator read,
understand, and follow the rules outlined on the first page of
(especially Acknowledgments and Disclaimer), and this document.
- All IP address use (including a connected host machine) must
be centrally coordinated, with IP addresses assigned by HPWREN
staff once an IP request form is received. These forms are
available by request from HPWREN staff. Uncoordinated picking
of IP addresses is reason for a permanent disconnect. For short
duration uses (such as a laptop for a few hours), most sites
support DHCP for automatic IP address assignments. DHCPed addresses
are not permitted for permanent use.
- For each machine the HPWREN staff requires a statement about
anticipated bandwidth use (e.g., in kilobits per second), and
their characteristics (bursty, continuous, ....). Is the
requirements change over time, a revised statement needs to be
provided. The IP address request form includes fields for such
- A block diagram of the complete site setup connected
to HPWREN has to be provided to HPWREN staff within no more than
a week of the IP request.
- A host/site connect requester commits to using HPWREN bandwidth
efficiently in a non-wasteful way (i.e., taking any reasonable
steps to minimize unnecessary bandwidth use). For example, no
video (bandwidth hog) permitted unless someone actually watches
it, and even then for limited durations only.
- Uncoordinated NAT or VPN devices are discouraged, as they
make network trouble shooting harder. An uncoordinated NAT/VPN
site may not receive trouble shooting support from the HPWREN
team, and will possibly be disconnected if it appears to causes
problems to HPWREN. An example of problems VPNs may create are
capabilities to reach HPWREN-internal addresses from outside
HPWREN, which may result in immediate disconnect if such is
perceived as possibly happening.
- A HPWREN collaborator must understand and acknowledges that
the HPWREN connection is not permitted to be used just as a cost
saving method, but only to connect applications that are reasonably
unrealistic to connect via other means.
- No network backdoor connection is allowed. If there is an
alternative means to connect, do not connect to HPWREN in addition,
as it could make network management very difficult. Revocable
exceptions may be made by the HPWREN PI at his discretion in
writing, if there is a good reason, and the activity is very
carefully and continuously coordinated. If such exception is
granted, and there is an assumption of a problem, the connection
will be discontinued if no response is received to a clarification
request within at most 24 clock-hours. If the backdoor connection
appears to cause significant problems, the site may be immediately
- An HPWREN collaborator must understand that the security of
the equipment and privacy of the traffic is the responsibility
of the user. The HPWREN team cannot be held responsible for
security or privacy. If privacy is an issue, use end-end encryption.
- An HPWREN collaborator needs to attend the annual
users meetings. Those meetings are to provide information to
everyone about the collaborative activities, and to provide input
as a group to the HPWREN team about future goals, objectives,
and implementations that the HPWREN program should consider to
- While the HPWREN program is currently funded out of an
NSF award, that may not always be the case, and everyone needs
to understand that over time it may be necessary for collaborators
to help support the infrastructure. Some projects have already
started to carry at least some of their incremental cost.
- HPWREN collaborators are strongly encouraged to from time to
time provide text and images for short updates on the HPWREN
news web site at:
http://hpwren.ucsd.edu/news/. Please contact the HPWREN PI
if you would like to submit such materials.
- An HPWREN user must understand that violating rules or not
operating in a cooperative spirit with the HPWREN team may result
in immediate disconnect.