📄 rfc1359.txt
字号:
(206) 562-3000
ehood@nwnet.net
NETTF [Page 19]
RFC 1359 Connecting to the Internet August 1992
NYSERnet
Jim Luckett
NYSERNET INC
111 College Place
Room 3-211
Syracuse, New York 13244
(315) 443-4120
luckett@nysernet.org
Fax: (315) 425-7518
OARnet
Alison A. Brown
Ohio Supercomputer Center
1224 Kinnear Road
Columbus, Ohio 43085
(614) 292-9248
alison@osc.edu
Fax: (614) 292-7168
Onet
Eugene Siciunas
4 Bancroft Ave., Rm. 116
University of Toronto
Toronto
Ontario M5S 1A1
Canada
(416) 978-5058
eugene@vm.utcs.utoronto.ca
Fax: (416) 978-6620
PREPnet
Thomas W. Bajzek
530 North Neville Street
Pittsburgh, PA 15213
(412) 268-7870
twb+@andrew.cmu.edu
Fax: (412) 268-7875
PSCnet
Eugene F. Hastings, II
Pittsburgh Supercomputing Center
4400 5th Avenue
Pittsburgh, PA 15213
(412) 268-4960
hastings@psc.edu
Fax: (412) 268-5832
NETTF [Page 20]
RFC 1359 Connecting to the Internet August 1992
PSINet
William L. Schrader
President & CEO
11800 Sunrise Valley Drive
Suite 1100
Reston, VA 22091
(703) 620-6651
wls@psi.com
Fax: (703) 620-4586
SDSCnet
E. Paul Love, Jr.
San Diego Supercomputer Center
P.O. Box 85608
San Diego, CA 92186-9784
(619) 534-5043
loveep@sdsc.edu
Fax: (619) 514-5152
Sesquinet
Farrell Gerbode
Office of Networking and
Computing Systems
Rice University
Houston, TX 77251-1892
(713) 527-4988
farrell@rice.edu
FAX: (713) 527-6099
SURAnet
Jack Hahn
1353 Computer Science Center
University of Maryland
College Park, Maryland 20742-2411
(301) 454-5434
hahn@umd5.umd.edu
THEnet
Tracy LaQuey Parker
Computation Center
University of Texas
Austin, TX 78712
(512) 471-5046
tracy@utexas.edu
NETTF [Page 21]
RFC 1359 Connecting to the Internet August 1992
VERnet
James A. Jokl
VERnet
Academic Computing Center
Gilmer Hall
University of Virginia
Charlottesville, VA 22903
jaj@boole.acc.virginia.edu
Westnet
Pat Burns
UCC
601 S. Howes, 6th Floor South
Colorado State University
Fort Collins, CO 80523
(303) 491-7260
pburns@yuma.ACNS.ColoState.EDU
Fax: (303) 491-2293
8. Appendix B. NSFNet Backbone Services Acceptable Use Policy
THE NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY - released
February 1992
GENERAL PRINCIPLE:
(1) NSFNET Backbone services are provided to support open research
and education in and among US research and instructional
institutions, plus research arms of for-profit firms when
engaged in open scholarly communication and research. Use for
other purposes is not acceptable.
SPECIFICALLY ACCEPTABLE USES:
(2) Communication with foreign researchers and educators in
connection with research or instruction, as long as any network
that the foreign user employs for such communication provides
reciprocal access to US researchers and educators.
(3) Communication and exchange for professional development, to
maintain currency, or to debate issues in a field or subfield of
knowledge.
(4) Use for disciplinary-society, university-association,
government-advisory, or standards activities related to the
user's research and instructional activities.
NETTF [Page 22]
RFC 1359 Connecting to the Internet August 1992
(5) Use in applying for or administering grants or contracts for
research or instruction, but not for other fundraising or public
relations activities.
(6) Any other administrative communications or activities in direct
support of research and instruction.
(7) Announcements of new products or services for use in research or
instruction, but not advertising of any kind.
(8) Any traffic originating from a network of another member agency
of the Federal Networking Council if the traffic meets the
acceptable use policy of that agency.
(9) Communication incidental to otherwise acceptable use, except for
illegal or specifically unacceptable use.
UNACCEPTABLE USES:
(10) Use for for-profit activities (consulting for pay, sales or
administration of campus stores, sale of tickets to sports
events, and so on) or use by for-profit institutions unless
covered by the General Principle or as a specifically acceptable
use.
(11) Extensive use for private or personal business.
This statement applies to use of the NSFNET Backbone only. NSF
expects that connecting networks will formulate their own use
policies. The NSF Division of Networking and Communications Research
and Infrastructure will resolve any questions about this Policy or
its interpretation.
9. References
[1] Holbrook, P., and J. Reynolds, Editors, "Site Security
Handbook", FYI 8, RFC 1244, CICNet, USC/Information Sciences
Institute, July 1991.
[2] Internet Activities Board, "Ethics and the Internet", RFC 1087,
IAB, January 1989.
[3] Comer, Douglas, "Internetworking with TCP/IP: Principles,
Protocols, and Architectures", Second Edition, Prentice Hall,
Englewood Cliffs, N.J, 1991.
[4] Libes, D., "Choosing a Name for Your Computer", FYI 5, RFC 1178,
Integrated Systems Group/NIST, August 1990.
NETTF [Page 23]
RFC 1359 Connecting to the Internet August 1992
10. Security Considerations
Institutions who wish to connect to the Internet should be aware that
the Internet network is, by nature, and open network. As such,
connecting institutions must make sure that security mechanisms are
in force on their own campus network to ensure that unauthorized or
inappropriate use of campus resources is not exploited by either the
internal campus or by the external Internet community. Moreover, it
is incumbent on the institution to ensure that the campus community
is aware of the proper use of the Internet. The institution bears
the responsibility to educate its users on the appropriate use of
campus systems within the context of proper and ethical use of the
Internet.
An assessment of security on the campus network prior to connecting
to the Internet should ensure that all required security patches are
installed on all campus connected systems as well as on the campus
network. Systems with sensitive data or information should be
physically secure as well as up to date with software security
patches. In so far as possible, network addressable devices should
be secure. Changes to these devices should only be effected by
authorized network management personnel to avoid potential security
risks.
For more information on security issues, refer to FYI 8, RFC 1244,
"Site Security Handbook" [1].
In summary, it is only the cooperation and attention of each
connecting institution on the Internet to security issues that will
ensure the security of the Internet as a whole.
11. Authors' Addresses
ACM SIGUCCS Networking Taskforce
E-Mail discussion list: nettf@comet.cit.cornell.edu
Martyne M. Hallgren, Chairman
Cornell University
143 Caldwell Hall
Ithaca, NY
Phone: (607) 255-5510
EMail: martyne@nr-tech.cit.cornell.edu
Jack Pope
University of San Diego
San Diego, CA
NETTF [Page 24]
RFC 1359 Connecting to the Internet August 1992
Pat Smith
MERIT, Inc.
Ann Arbor, MI
John Cordani
Eastern Michigan University
Ypsilanti, MI
Steven Sather
University of California, Los Angeles
Los Angeles, CA
Joyce McGowan
University of Arkansas
Fayetteville, Arkansas
NETTF [Page 25]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -