RFC 1359
Connecting to the Internet - What Connecting Institutions Should Anticipate
RFC 1359: Connecting to the Internet 🎀 What Connecting Institutions Should Anticipate 🦋
- RFC number: 1359, filed as FYI 16 🌸
- Group: Network Working Group 🧚
- Organization: ACM SIGUCCS Networking Taskforce, so bestie, this is a community doc 🫶
- Category: It's an FYI, so it's giving information for the Internet community. It does not specify an Internet standard 💅
- Date: August 1992 📅
- Obsoletes: Nothing listed in the header 🙈
- Updates: Nothing listed in the header ✨
The authors' addresses are in Section 11 (we'll get there, I promise 💖).
Status of this Memo
okay so this memo is for information only for the Internet community. It is not an Internet standard 📘 Distribution is unlimited, so share it with everyone 💜
Abstract
this FYI RFC lays out the big issues an institution should think about when deciding on and setting up a campus connection to the Internet 🌐
to keep things clear, it includes some specific details. The doc is aimed at U.S. academic institutions that haven't connected yet 🎓
BUT the issues with specific info can be generalized for any organization that wants to join the worldwide Internet community ✨ Those orgs will need to get the correct, detailed info from their local or national IP service providers. This doc can also be used as an evaluation checklist for orgs that are already connected ✅
Readers are expected to have general familiarity with networking concepts and terminology. No pressure, but you should know your stuff 😌
Table of Contents 📑
1. Acknowledgements.............................................. 2
2. Introduction.................................................. 2
3. Initial Planning/Pre-Internet Installation Phase............... 4
3.1 Ask the Vital Question...................................... 4
3.2 Reasons Why to Participate................................... 5
3.3 Connection Options........................................... 6
3.4 Connection Service Providers................................. 7
3.5 Sample Questions for Connection Services Providers........... 8
3.5.1 Sample Questions........................................... 8
3.6 Cost Assessment.............................................. 9
4. Initial Implementation and Startup Phase....................... 10
4.1 Policy Issues................................................ 10
4.2 Connection to the Mid-level Network.......................... 11
4.3 IP Addresses and Domain Names................................ 11
4.4 Technical Issues............................................. 12
4.5 Support...................................................... 12
4.6 Training..................................................... 13
4.7 Promotion.................................................... 13
5. Full Production/Maintenance................................... 13
5.1 Technical Issues............................................. 14
5.2 Human Factors................................................ 14
6. Evaluation Strategies......................................... 15
7. Appendix A. Partial List of IP Service Providers.............. 16
8. Appendix B. NSFNet Backbone Services Acceptable Use Policy.... 22
9. References.................................................... 23
10. Security Considerations....................................... 24
11. Authors' Addresses............................................ 241. Acknowledgements 🫶
this doc was made by the ACM SIGUCCS Networking Taskforce. NETTF was created in 1989 under the direction of Martyne Hallgren, with the approval and support of the SIGUCCS Executive Board 👑
the Networking Taskforce exists to do a few iconic things: raise awareness and understanding of the Internet, share information and research on how the Internet is developed and used, promote innovative and appropriate use of Internet resources, and start and encourage cooperation between SIGUCCS members and other orgs with similar goals in networking, like the Internet Engineering Task Force (IETF) 🤝
2. Introduction 🌈
the Internet is a world-wide network of networks, with gateways linking orgs in North and South America, Europe, the Pacific Basin, and other countries not previously included 🗺️ The orgs are administratively independent from each other, and there is no central, worldwide, technical control point. Still, working together, they've built what looks to a user like one single virtual network that spans the globe 🌍
the networks all use a common suite of networking protocols, TCP/IP. That shared protocol stuff, plus shared network functionality and interoperability, is what makes them look like a seamless, integrated virtual network, irregardless of the underlying heterogeneity of the computer hardware or communications transport underneath 💅
yes, the doc really says "irregardless." we are not going to fix it, we are just going to look at it 💀
the most basic functions are electronic mail, access to remote computational and informational facilities, and file transfer 📬 The networking protocols were first deployed in the late 1960's in the United States. For several years, they were only used for very specific research activities and in some computer science departments 🧑🔬
then in 1985, at a meeting of National Science Foundation networking specialists and higher education reps, a new national data networking backbone using these protocols was outlined 🔥 It acted as a catalyst for dramatic changes in data networking technologies and usage. Iconic behavior 👑
the NSFNet backbone was originally conceived to connect the six national supercomputing centers that had been established. Over the years, the backbone and its associated mid-level networks grew dramatically 📈 The networks built for mission- and discipline-specific uses also grew dramatically. Because of the common technology, they could be connected together, which increased their reach and, as a result, their usefulness to the user community, with very little additional expense 🤑 The end result is a robust technology that supports the higher education and research community. Its continued development and growth are essential to keeping excellence in education and research alive 🎓💖
use of the Internet has steadily and dramatically grown over the past years. More and more sites have connected 🌱 Each site may have more and more uses for the network as existing users expand and new users are added, which results in exponential growth of network traffic 📊 But even more dramatic are the explosions in growth from innovative applications 🚀 Networks are having a dramatic effect on everything from libraries to elementary schools, from sharing expensive scientific instruments to using databases to access atmospheric data, to electronic publishing and interpersonal collaborations building "workplaces without walls" 🧚
the number of connected orgs is constantly growing ✨ Right now, the orgs connecting through the Internet include universities and colleges, research laboratories (government and private), libraries, specialized scientific centers, state agencies, K-12 (Kindergarten-12th Grade) organizations, individuals, and individual research labs 🏫 But no matter what kind of org it is, they all have the same need to understand what it means to connect to the Internet 🫶
an institution must anticipate and prepare for four critical phases in deploying an Internet connection 🎯 The list of issues in this document isn't exhaustive. Instead, the info should alert decision makers to the major concerns they should address during the different phases of network deployment 📋
as each issue is discussed, both soft and hard cost items will be identified, and both must be considered when figuring out the real cost of deploying an Internet connection 💸 Hard costs are the ones that create invoices. They include new circuits or phone lines, the purchase of modems or csu's and routers, network membership dues, and upgrades to existing hardware to make it network compatible 🧾 Soft costs are harder to quantify but no less important 🥹 They include training and education of staff, faculty, and students; modifications to support staffing and structure; and deploying new network applications or services, such as FTP servers, centralized electronic mail services, or campus-wide information systems 💻 Soft costs also come with benefits that can easily be seen as people investment and organizational investment 🌟
the four phases of an Internet connection deployment are:
- A. Initial planning/Pre-Internet installation phase 🗓️
- B. Initial Implementation and Startup phase 🛠️
- C. Full Production/Maintenance phase 🔧
- D. Evaluation/Upgrade phase 🔄
3. Initial Planning/Pre-Internet Installation Phase 🧠
3.1. Ask the Vital Question 💭
first things first, an institution must address the question, "What does my community/institution gain from participating in the Internet community?" This is the main question, bestie, so don't skip it 👑
commercial and non-profit education and research institutions rightfully spend a great deal of high-level effort defining their mission and goals 🎯 Any introduction of new technology (especially one involving new modes and methodologies of communication) should be assessed in light of the institution's own mission and goals, as well as the wants and needs of the user community it serves 🫶
following that, and as part of this evaluation, key decision makers at the highest levels of the organization will need info not just on the cost of connecting, but more importantly on the purpose and scope of participating in the Internet 📊 The decision to participate takes the strong commitment of senior administration AND the support and endorsement of the general institutional community 🙌 For an educational institution, it is critical to have the support and active interest of the faculty 🎓 This decision will also involve a campus wide needs assessment to figure out the interest and support of the campus community 💜
3.2 Reasons Why to Participate 💖
okay bestie, so getting an Internet connection can unlock a whole campus-wide plan for using information technology that you might literally never reach otherwise 🫶. It's hard to put a number on these perks, but they still need to go into the justification process ✨. Lots of institutions already did this and are very likely already connected 🎀. An interested institution might want to chat with a nearby, connected organization to see what benefit they've gotten from it 👀. An institution looking at a connection for the first time must decide if a major reason is simply to participate in a technology that has already proven itself as being important to education. More importantly, it may be a requirement now to compete with peer organizations 💅.
This is especially important when recruiting new faculty and students 🧚. New faculty will want to keep up their research and academic collaborations, which may need resources the institution can't afford. Those resources can be made available through the network 🌈. So a university or college may be able to recruit students and offer a new curriculum that demands access to resources only available through the network. The potential gain in prestige, research participation, and dollars is well worth the investment 🔥.
Many universities have also discovered economic efficiencies 🦋. A lot of subscription services used to require a dedicated and expensive access method. More and more of these services are now accessible through the Internet, and this trend will undoubtedly continue as more and more commercial companies make their services available 💜. The subscription fee may not change, but the cost of the dedicated connection can be used to finance an Internet connection instead. Not only will the service be more available, but the underlying access medium can be used for multiple functions 🍓.
Libraries, many of which already have automated catalogs, are looking at new applications to handle the glut of information, shrinking dollars, and limited shelf space 📚. Electronic journals, image-based text, and publishing on demand are all being evaluated for the digital library ✨. Universities are also automating and integrating a bunch of activities and giving students and staff access through a campus network. At some universities, students can register for classes, check their grades, and look at their bill from their dorm room instead of suffering through long lines 😭. Some universities are also able to stay in touch with their alumni through a variety of online information resources 🌸.
NSFNet was first created to give access to five national supercomputer centers. Those centers still provide researchers with leading-edge computational technologies to support research in a variety of areas, from black holes to pollution in the L.A. basin 🌌. Today, researchers and students have access to a broad range of computational, informational, and scientific instrumentation that can be used remotely, with no loss of productivity 🔬. For some organizations, this means they can now recruit faculty with research requirements they could never afford themselves 👑. It also means access to research funding 💰. At the same time, it opens the door for faculty and students to pick their next institution for reasons other than the hardware currently owned 🫶.
3.3 Connection Options 🌷
There are a variety of connection options, and factors besides cost can be used to pick the right option or series of options 💭. These factors include the size and projected use (traffic) of the connection, plus the nature of the use and the purpose of the enterprise driving the effort 📈.
There are three basic categories of IP service connection available right now 💖. All three support essentially the same set of functions. They support a variety of line speeds, which affects the total capacity of the connection, and they'll run on a variety of hardware platforms 🖥️. Performance depends on the line speed, the hardware and software used, and the use itself ✨.
The three basic connection categories are:
- a) dedicated connection
- b) dialup connection
- c) dialup access to a connection service
A dedicated connection requires a dedicated, point-to-point telecommunications circuit and an IP router (a dedicated networking device) linking the organization to the Internet 🔗. Line speeds range from 9.6 Kb to 45 Mb, with the most common connection speeds being 56Kb and 1.54 Mb 🏎️. A dedicated connection most commonly connects to a campus-wide network with several hosts and workstations 🏫.
A dialup connection requires a workstation, which may or may not be dedicated to networking, with appropriate networking software and an attached modem 📞. It uses a regular phone line. When a network connection is needed, the workstation is used to establish a connection over the modem and phone line. At the end of use, the connection is broken 👋. Line speeds range from 9.6Kb to 56Kb, with lower speeds being most common 🐢. It can be used to connect a single workstation or a LAN. However, if it's used to connect a LAN, the workstation must provide some routing functionality 🧭.
Several IP service providers offer dialup access to a connection service 📲. This kind of service only provides remote login capabilities or other limited functions. You call a local phone number and get set up in a single function environment. A terminal emulator is used from a MAC or a PC 💻. The service can support speeds from 2.4Kb - 19.2 Kb. Providers usually charge a flat-rate connection fee instead of a connection fee plus traffic charge 🎀.
As each type of connection alternative is examined, the organization must consider the technical evolution and cost projections 🔮. The appropriate campus agency (usually an information or telecommunications area) should inventory the existing campus networking 📋. For organizations that already have a campus network, the inventory will be super valuable input for developing a short and long term technology evolution strategy 🌟.
If a campus network doesn't exist yet, developing a campus networking strategy may end up upgrading technology throughout the whole campus 🚀. Either way, the question of how to get network connectivity to the workstations in faculty and staff desks, large user rooms, residence halls, libraries, and campus stores must eventually be addressed 🙈.
A connection to the Internet doesn't always mean building a campus-wide network 🌱. In some cases, it may be appropriate for only a small segment of the organization's community to have access to the Internet. Often, organizations use this as a way to introduce the technology to a small group of enthusiastic customers who become champions in their own right 🏆.
3.4 Connection Service Providers 🌐
There are several organizations, both not-for-profit and commercial, that now offer connectivity services to the Internet 💼. Refer to Appendix A for a partial list 📝.
There's no hard and fast rule about who an organization should approach for a connection 🤷♀️. Historically, academic institutions have tended to become members of the closest mid-level network 🎓. The best approach, given the growing number of IP service providers, is to consider all the providers that offer services in the region. Then consider the variety and quality of services offered within the framework of the organization's requirements, and make an informed decision based on that information 🧠✨.
3.5 Sample Questions for Connection Services Providers 💬
It's honestly hard to know what questions to ask when you're evaluating different service providers 😵💫. The following set of questions is a starting point for any discussion with an IP service provider 🫶.
3.5.1 Sample Questions
- a) What connection services do they offer? Please describe in detail (i.e., until you understand what they are talking about).
- b) What is the cost?
- c) What is included in the cost?
- the circuit cost (installation and monthly charge)
- the router (cost of onsite router, cost of offsite router)
- hardware/software
- maintenance, of what??
- membership fee
- d) Is there any other kind of charge not included in the upfront cost?
- e) What are their support services?
- NOC?
- NIC?
- What do they mean by either organization?
- f) Do they fix the router when it's broken?
- g) Do they require 24 hour access to the physical location?
- h) Do they require an onsite person be available to them to assist in problem diagnosis?
- i) What training is available? Is it included in above cost??
- j) Do they have an acceptable use policy?
- k) Is there an annual meeting?
- l) Do they have dedicated (i.e., full time), professional staff?
- m) Are there limitations to connecting to other parts of the Internet (i.e., can you everywhere you need to get?)?
- n) To whom else do they provide service?
- references?
If any of this information is confidential, consider finding another service provider 🚩💅.
3.6 Cost Assessment 💸
okay so bestie, an org thinking about plugging into the Internet has to look past the cute little physical connection and the startup costs 🥺 they also need to budget for the whole support infrastructure that comes after, like the ongoing care and feeding of a campus-wide network. at some universities that network might only carry data, but at lots of universities and other orgs it has to grow to handle data, voice, and video as the apps and requirements keep expanding 📞🎥
the Internet gives you access to a huge pile of resources and functions and services that might not have existed locally before, and that's giving main character energy 🌟 but your support staff will need education and training so they can support and train the faculty, other staff, and students on the new tech and resources. this training might mean a strategic glow-up for how the campus networking info services are set up and deployed. the costs of these added-value services should be planned for ahead of time, no cap 💅
more usage on the campus network means more demands on the existing network tech staff 😩 and areas of the institution that weren't in data networking yet are going to want in 🙋♀️ not every one of these can be exactly priced out, but they still have to be anticipated and built into campus planning for an Internet connection ✨ think libraries, dorms, student services, and data depositories 📚
the Internet connection is basically the spark for a campus-wide plan for using info tech that might have otherwise been out of reach 🔥 the benefits can be hard to put a number on, but they absolutely have to go into the justification process 💖 one big perk is access to expensive scientific instruments, like computational services (i.e., massively parallel supercomputers) or particle accelerators 🧪 so the org gets to use those facilities without buying one, which makes it an effective recruiting tool for bright young PHD's who need that kind of resource 🎓🫶
4. Initial Implementation and Startup Phase 🚀
once the institution decides to connect to the Internet, a bunch of tasks should get underway ✨ roughly speaking they cover policy, process definition, education, promotion, technical stuff, and fiscal issues 💰 several of these should get handled at the same time, periodt 🙌
4.1. Policy Issues 📜
the campus community should come up with guidelines for acceptable use of the network 🛡️ these guidelines cover the rules for the campus net, and now they also stretch to appropriate use of the Internet itself 🌐 the appropriate use policy has to include policies the Internet community has already developed 🤝 NSF has an acceptable use policy that applies to the backbone networks they provide, so check out Appendix B 👀 each of the mid-level networks, plus other orgs running their own backbones, has its own acceptable use policy, and those might not match NSF's at all 😬 it's important to know what's limited and what isn't before you connect and start using various networks 💯
writing an acceptable use policy protects the institution, and it's also a super good chance to set up campus guidelines for privacy and security around computing in general 🔐 stuff like what data is available on the network, how that data should properly be used, who is allowed to use it, and copyright and attribution requirements for FTP-able documents all deserve a look 📄
the ethical guidelines around using and possibly misusing software and data banks on the Internet have to be carefully written and shared across the whole institution, and they need to get into the hands of faculty, staff, and students 📣 people have already done a lot of work on good references you can use to guide these policies 📚 check out FYI 8, RFC 1244, "Site Security Handbook" [1] 🙌
to make the most of the Internet community as a whole, the campus community has to learn proper etiquette on the network 🌸 that covers things like managing big files, data compression, and using email efficiently 📧 see RFC 1087, "Ethics and the Internet" [2] 💜
4.2. Connection to the Mid-level Network 🔌
by this point the org should know what kind of connection it wants and which service provider it'll be working with 🤓 there are specific technical details that have to be handled in the first deployment, including evaluating hardware and software 🖥️ the mid-level network or the institution providing the connection is often an amazing resource for teaming up with the on-campus group to pick the best configuration 🫶 it's vital to figure out before this point exactly what the org will need to buy, and what will come as part of a fee-based service 💳 (go back to the sample set of questions if you need a refresher 💅)
4.3. IP Addresses and Domain Names 🏷️
every org connecting to the network must have a unique identifier, and this is called the campus IP network address 🆔 most orgs also get a domain name on top of that numerical identifier 💅 it's through the numerical address and the domain name that the org's hosts become known across the Internet 🌍
an org has to register with the authority that assigns IP addresses and with the one that handles domain names 📝 the IP address is assigned by the Internet Address Naming Authority (IANA) 🦋 the domain name gets picked by the org itself 🎀 a domain name is basically just a character string that maps to the IP address, and it's way easier for humans to remember than a random set of numbers 🧠 a tutorial on IP addresses and domain names is beyond the scope of this doc, but if you want the deep dive, check out Doug Comer's textbook, "Internetworking with TCP/IP: Principles, Protocols, and Architectures" [3] 📖 (see also FYI 5, RFC 1178, "Choosing a Name for Your Computer" [4] 💻)
there are different classes of Internet addresses, and each one matches the number of hosts an org expects to connect to its networks 📊 so the campus should think carefully about how its own network will grow before applying for the right class of membership 🌱 the IP service provider is a great source of advice for picking a membership class 🙋♀️
registration for IP addresses and domain names costs nothing right now 🤑
the procedure for applying for an IP address and domain name should be explained, and the IP service provider often hands it over to the connecting org 📋
4.4. Technical Issues 🛠️
the installation itself should cause as little disruption to the campus network as possible 🙏 to make that happen, the org should put together a complete plan of action, which would include the following steps (some may happen at the same time, some may be done by the service provider, and the list isn't exhaustive 🫠):
a) order, install, test circuit or phone line
b) IP address and domain name registration
c) hardware purchasing/delivery
d) routing configurations/reconfig campus network
e) bring up router, test end-to-end connectivity
f) make available to campus4.5. Support 🤝
honestly the most challenging part of the initial deployment is how much the network tech and network info services teams have to reorient themselves 😵💫 there are added responsibilities for network management, plus extra network info services to support the connection 📈 cognizant administrators have to recognize these added tasks, plan for them, and budget for them 💸 admin also has to make sure the duties of the tech and network info services staff are clearly split up, so nobody duplicates work or ends up in a fight 🙅♀️
while the network is going up, educating the user community is critical 🎓 that includes making documentation about basic Internet info and specific campus resources, plus details on remote resources (library catalogs, information servers, etc) and how to use them 📚
a lot of orgs have already made excellent documentation and are happy to share it 🥰 they usually just want attribution in return for distribution rights, and those are for educational purposes only 🙏
4.6. Training 🎀
networking problems that end-users run into are often caused by misinformation or campus-specific configurations, not by problems at the mid-level or backbone 🙈 investing in staff and user training and documentation at the start of the network deployment is an investment that pays off big time in the long run 💰✨
user training is critical, but depending on the size of the campus, it's impossible to expect support staff to train users one by one 😭 so it's smart to build and promote a hierarchy of support personnel, where the central support staff trains the trainers, who then go out and support their own groups of users 🧚
the most critical course for users covers local info on the basic functions of the network: electronic mail, file transfer, and remote login 💌 good documentation helps the network get used successfully 📖 documentation should be clear, concise, and to the point ✂️ during training, make sure to address the most commonly asked questions first 🙋♀️
4.7. Promotion 📣
a network is only as successful as its users say it is 💅 from day one, the network has to be presented to them as a useful tool 🛠️ promotion through newsletters and other appropriate communication vehicles is a required activity, no debate 📰 an active promotion strategy lets an org set user expectations about service and performance, which matters a lot for a networking staff that's still learning 🥹
faculty involvement from the very beginning is vital 👑 it's important to earn their support and build on it 💜 whether that's through faculty advisory committees or direct contact with individuals, their feedback and support can be a healthy measure of success 🌈
5. Full Production/Maintenance 🌟
as the campus community makes the Internet part of its usual routine, the people responsible for the campus network and the Internet connection have to ensure accessibility, reliability, and relative ease of use 🔧 this ongoing maturation of the network is a vital service to the user community 💖
as the network becomes a crucial tool in the user community's daily routine, the interface between the operations, information, and user services staffs and the end users becomes even more important 🫶 responding to end-user problems with courtesy, and taking responsibility for resolving the end-user concern (as opposed to just the actual technical problem), builds a working environment of trust and partnership 🦋✨
5.1. Operation Services 🔧
okay so ops is where the magic keeps happening 💅 there's gonna be hardware and software support, which means updating and maintaining compatible software revisions, planned replacement and maintenance of communications hardware so it can make use of new technology, and routine network operations center activities 🫶 that includes IP number administration, monitoring the network to figure out its usage patterns, optimal routing, and continuous and accurate updates of known problems, plus trouble shooting the problem areas of the campus net 🔍 the network staff will have to maintain the campus routing tables, and if the site serves as a backbone site, it may have to maintain tables for its designated area too 🗺️
ngl the ops team and the engineering team need to be besties 👯♀️ keeping a close relationship between them is super important. the operations staff must have a quick inroad to engineering so the user community gets quick responses whenever problems get reported 🏃♀️💨
how big all this gets depends on the size of the campus network and how much responsibility the campus has for its Internet connection. honestly the responsibilities only grow in scale and importance as the institution comes to rely on the network and its access to the Internet 📈 it's giving main character growth arc 🌱
5.2. Information and User Services 📚
the education, training and promotion stuff that goes with the network keeps going, but it matures in both scope and level of network expertise 🎓 documentation efforts keep going too. docs get refined and reviewed periodically for accuracy and completeness 📝 but individual consultation will change as network users get more sophisticated and experienced. the more consulting and info services show up on the network itself, the more the network info staff will probably end up doing "training the trainers" 🧑🏫 or running one-on-one help sessions with faculty and researchers who are doing collaborative research over the network 🤝
promotion has to keep going too 📣 it needs to involve new faculty and staff, promote and advertise major campus network activities and projects, and highlight new services and projects available on the Internet ✨ that can look like a campus newsletter or periodic seminars on network services 🗞️ and honestly it's a necessary and crucial part of recruiting new and innovative uses of the Internet, which is what justifies continued development and investment 💜
6. Evaluation Strategies 🔬
okay so a system as complex and everywhere as the campus data network needs periodic review and evaluation 🧐 the campus network is the primary access point to the larger Internet community, so evaluation strategies have to include analyses of how and where the Internet gets used the most, and how campus data flows might optimize that traffic 🚦
evaluating network statistics gives key info on how the network gets used and who's using it 📊 and that has to lead to assessment mechanisms that gauge user satisfaction with the network and the tools used to access it 🥰 at the base level there are the tools built into the network protocol itself, like Telnet, FTP, and SMTP mail. they give everyone fundamental access to the Internet 🔌 but as campus use of the network and the Internet matures, the campus community itself will build on those tools to make special "campus customized" tools 🛠️ network services should evaluate user needs and, where it makes sense, design user friendly interface mechanisms that are especially suited to special campus area needs 💖
⚠️ bestie listen up: quantitative methods of evaluation are important, but they can not replace qualitative methods. if end-users are unhappy, and problems keep getting reported even though the statistics and technical monitors show few errors, organizations have to recognize that serious problems do exist and take immediate action to resolve them 🚨
the use of the Internet itself, and its impact on campus research and instruction goals, must be reviewed and evaluated 🧪 introducing new technology inevitably involves reorientation and new means of communication 🔄 this should benefit the campus community as a whole, but new technologies may leave some segments of the community feeling disoriented 🥺 a careful evaluation of the impact should figure out not only which areas of campus benefit from Internet participation, but also which areas are not benefitting from the new technology 🔍 planning strategies should give special attention to the areas that aren't making use of network resources, so those areas become aware of the potential benefits and get training in using the network 🎀
in summary, universities, schools, colleges and institutions in the Internet community must incorporate a mechanism to evaluate both the hidden benefits and the hidden costs of that participation 🦋✨
7. Appendix A. Partial List of U.S. IP Service Providers ✨
okay so this appendix is basically a little contact book 📇 of US IP service providers. these are the folks you'd call about connecting to the network. it's a partial list, so it's not every single provider out there, but it's giving very helpful vibes 💖
ANS
Joel Maloff
Vice President - Client Services
Advanced Network and Services
2901 Hubbard Rd.
Ann Arbor, MI 48105
(313) 663-7610
maloff@nis.ans.net
BARRNET
William Yundt
Pine Hall Rm. 115
Stanford, CA 94305-4122
(415) 723-3104
gd.why@forsythe.stanford.edu
Fax: (415) 723-0010
CERFnet
Susan Estrada
San Diego Supercomputer Center
P.O. Box 85608
San Diego, CA 92186-9784
(619) 534-5067
estradas@sdsc.edu
Fax: (619) 534-5167
CICnet
Michael Staman
President
ITI Building
2901 Hubbard Drive Pod G
Ann Arbor, MI 48105
staman@cic.net
(313) 998-6101
Fax: (313) 998-6105
Colorado Supernet
Ken Harmon
CSM Computing Center
Colorado School Mines
1500 Illinois
Golden, Colorado 80401
(303) 273-3471
kharmon@csn.org
Fax: (303) 273-3475
CONCERT
Joe Ragland
CONCERT (Communications for NC
Education, Research, and Technology)
P.O. Box 12889
3021 Cornwallis Road
Research Triangle Park, NC 27709
(919) 248-1404
jrr@concert.net
Fax: (919) 248-1405
CREN
Jim Conklin
EDUCOM
1112 16th Street NW
Washington D.C. 20036
(202) 872-4200
conklin@bitnic.bitnet
Fax: (202) 872-4318
CSUNET
Chris Taylor
Manager, Network Technology
Office of the Chancellor
Information Resources and Technology
P.O. Box 3842
Seal Beach, CA 90740-7842
(213) 985-9669
chris@calstate.edu
Fax: (213) 985-9400
JVNCnet
Sergio Heker
6 von Neumann Hall
Princeton University
Princeton, NJ 08544
(609) 258-2411
heker@jvnc.net
Fax: (609) 258-2424
LOS NETTOS
Ann Cooper
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, Ca 90292
(310) 822-1511
Fax: (310) 823-6714
Merit
Eric Aupperle
Merit Network
2200 Bonisteel Blvd.
Ann Arbor, MI 48109-2112
(313) 764-9423
ema@merit.edu
Fax: (313) 747-3745
MIDnet
Dale Finkelson
29 WSEC
University of Nebraska
Lincoln, NE 68588
(402) 472-5032
dmf@westie.unl.edu
Fax: (402) 472-5280
MRNET
Dennis Fazio
Executive Director
The Minnesota Regional Network
511 11th Avenue South, Box 212
Minneapolis, Minnesota 55415
(612) 342-2570
dfazio@MR.NET
Fax: (612) 344-1716
NCAR
Joseph H. Choy
P.O. Box 3000
Boulder, CO 80307-3000
(303) 497-1222
choy@ncar.ucar.edu
Fax: (303) 497-1137
NEARnet
John Rugo
Accounts Manager
BBN Systems and Technologies
10 Moulton Street
Cambridge, MA 02138
(617) 873-2935
jrugo@nic.near.net
NETILLINOIS
Ed Krol
University of Illinois
Computing Services Office
1304 W. Springfield
Urbana, IL 61801
(217) 333-7886
e-krol@uiuc.edu
NevadaNet
University of Nevada System
Computing Services
4505 Maryland Pkwy
Las Vegas, NV 89154
(702) 739-3557
NorthWestNet
Eric S. Hood
Executive Director
NorthWestNet
2435 233rd Place NE
Redmond, WA 98053
(206) 562-3000
ehood@nwnet.net
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
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
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-22938. Appendix B. NSFNET Backbone Services Acceptable Use Policy 🎀
this one is the rulebook for the NSFNET Backbone 📜 it's dated February 1992, and it's giving very clear boundaries about who gets to use the backbone and for what. honestly it's kind of iconic 💅
THE NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY - released February 1992
General Principle:
(1) okay so the NSFNET Backbone is there to support open research and education between US research and teaching institutions, plus the research arms of for-profit firms when they're doing open scholarly communication and research. using it for anything else is not acceptable 🚫
Specifically Acceptable Uses:
(2) talking with foreign researchers and educators about research or teaching is totally fine 🌍 as long as the network the foreign user is on gives reciprocal access to US researchers and educators.
(3) communication and exchange for professional development, to stay current, or to debate issues in a field or subfield of knowledge 🧠
(4) use for disciplinary-society, university-association, government-advisory, or standards activities that connect to the user's research and instructional activities 🤝
(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 coming from a network of another member agency of the Federal Networking Council, if that traffic meets the acceptable use policy of that agency 🫶
(9) communication that's incidental to otherwise acceptable use, except for illegal or specifically unacceptable use 🌸
Unacceptable Uses:
(10) 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 it's covered by the General Principle or counts 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.
10. Security Considerations 🔐
okay this part is SO important bestie, so listen up 👂 any institution that wants to connect to the Internet needs to know that the Internet is, by nature, an open network 🌐 which means connecting institutions have to make sure their own campus network has security mechanisms in place. the goal is that unauthorized or inappropriate use of campus resources can't get exploited, whether by someone inside the campus or by the wider Internet community 😭 the institution is also responsible for making sure the campus community knows how to use the Internet properly. basically, the institution has to teach its users how to use campus systems in a proper and ethical way within the context of the Internet 🫶
before connecting to the Internet, the campus network should be assessed for security. that assessment should make sure all required security patches are installed on every campus-connected system, and on the campus network itself ✅ systems with sensitive data should be physically secure and kept up to date with software security patches 🔒 as far as possible, network-addressable devices should be secure too. and changes to these devices should only be made by authorized network management personnel, so we don't invite security risks 🚨
for more on security issues, check out FYI 8, RFC 1244, "Site Security Handbook" [1] 📖
and honestly the big takeaway is this: the Internet as a whole only stays secure if every connecting institution pays attention to security and cooperates on it 💜 we're all in this together, fr fr 🌈
11. Authors' Addresses ✨
Okay bestie, this is the squad that wrote the thing 💖 Let's meet them 🫶
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
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
That's the whole crew, the end of the doc, and honestly they're iconic for keeping the Internet running 🌈✨ 💅
📦 where this page comes from
- ietf: rfc1359 1992-08
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms