The Internet Development Process: Observations and Reflections
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Leased-Line Replacement
Leased-Line REPLACEMENT Utilizing gigabit wireless links to provide fiber-like performance at significant savings compared to leased lines. WHITE PAPER Leased-Line Replacement T1 (1.5 Mbps) line is not enough capacity to handle the need, four T1s When considering high-bandwidth connections between locations, the are ordered from the telco at a monthly rate of $500 each ($2,000 per thinking used to be that the only way to get service was to pick up the month). This twelve month commitment also requires a startup fee of phone, call the Local Exchange Carrier (LEC) and order a circuit. As long $1,000 to cover equipment and provisioning of the circuits. This amounts as the startup costs and monthly recurring charges were within the IT to $25,000 for the one year lease to provide a 6 Mbps connection budget, and the IT manager and business administrators were content between the corporate headquarters and the satellite office. with the level of service provided, writing a monthly check to the LEC was not a problem. If troubles were encountered with the service, a In the second scenario, a DS3 leased line is used to connect a school’s phone call to the provider was all that was necessary to resolve the LAN to the district office backbone three miles away. Services such as problem. voice, data, Internet access, and classroom video are transported over the circuit. To establish service, the local carrier requires a startup fee Businesses relying on leased lines find a wide range of performance of $3,000 that covers the cost of edge devices, as well as installation options tailored to suit their needs, from T1/E1 (1.5/2 Mbps), multiple and commissioning. -
How Did They Get to the Moon Without Powerpoint?
How Did They Get to the Moon Without PowerPoint? Mordechai (Moti) Ben-Ari Department of Science Teaching Weizmann Institute of Science [email protected] Keynote speech at the Finnish Computer Science Society, May, 2003. 1 Developing a Technology The invention of writing, however, was the invention of an entirely new Let me start with a description of one of my first technology.[3, p. 9] full-time jobs: There is something to be said for this definition: I developed a technology for data min- do you remember those old movies that show “typ- ing in order to consolidate enterprise- ing pools,” where rows and rows of people, usually customer relations. women, sat pecking away at keyboards all day? Since I held that job in the early 1970s, clearly I would not have described my work in this terminol- ogy! What I actually did was: I wrote a program that read the system log, computed usage of CPU time and printed reports so that the users could be billed. My point in this talk is that hi-tech in general and computer science in particular did not begin in the 1990s, but that we have been doing it for decades. I believe that today’s students are being fed a lot of marketing propaganda to the contrary, and that they Well, things haven’t changed all that much! have completely lost a historical perspective of our discipline. I further believe that we have a respon- sibility as educators to downgrade the hype and to give our students a firm background in the scientific and engineering principles of computer science. -
The Internet Development Process Stockholm October 2010
The Internet development Process Stockholm October 2010 Pål Spilling What I would talk about? • The main Norwegian contributions • Competitions between alternatives • Did Norway benefit from its participation? • Some observations and reflections • Conclusion A historical timeline 1981/82 TCP/IP accepted standard for US 1993 Web browser Mosaic Defence became available 1980 TCP/IP fully 2000 developed 1975 Start of the Internet Project; 1974 Preliminary specificaons of TCP 1977 First 3 – network Demonstration Mid 1973 ARPANET covers US, Hawaii, FFI Kjeller, and UCL London 1950 1955 ‐1960, End 1968 Ideas of resource Start of the ARPANET sharing networks project Norway and UK on ARPANET 1973 London o SATNET o Kjeller Norwegian Contributions • SATNET development – Simulations – Performance measurements • Internet performance measurements • Packet speech experiments over the Internet • Improved PRNET protocol architecture Competitions between alternatives • X.25 (ITU) • ISO standards (committee work) • DECNET (proprietary) • IBM (proprietary) • TCP/IP demonstrated its usefullness i 1977 accepted as a standard for US defence Norwegian benefits • Enabled me to create a small Norwegian internet • Got access to UNIX, with TCP/IP and user services integrated • Gave research scientists early exposure to internet and its services • Early curriculum in computer communications; Oslo University Observations and reflections • Norwegian Arpanet Committee; dissolved itself due to lack of interest • IP address space too small for todays use • TCP split in -
Rulemaking: 1999-10 FSOR Emission Standards and Test Procedures
State of California Environmental Protection Agency AIR RESOURCES BOARD EMISSION STANDARDS AND TEST PROCEDURES FOR NEW 2001 AND LATER MODEL YEAR SPARK-IGNITION MARINE ENGINES FINAL STATEMENT OF REASONS October 1999 State of California AIR RESOURCES BOARD Final Statement of Reasons for Rulemaking, Including Summary of Comments and Agency Response PUBLIC HEARING TO CONSIDER THE ADOPTION OF EMISSION STANDARDS AND TEST PROCEDURES FOR NEW 2001 AND LATER MODEL YEAR SPARK-IGNITION MARINE ENGINES Public Hearing Date: December 10, 1998 Agenda Item No.: 98-14-2 I. INTRODUCTION AND BACKGROUND ........................................................................................ 3 II. SUMMARY OF PUBLIC COMMENTS AND AGENCY RESPONSES – COMMENTS PRIOR TO OR AT THE HEARING .................................................................................................................. 7 A. EMISSION STANDARDS ................................................................................................................... 7 1. Adequacy of National Standards............................................................................................. 7 2. Lead Time ................................................................................................................................. 8 3. Technological Feasibility ........................................................................................................ 13 a. Technological Feasibility of California-specific Standards ..............................................................13 -
1117 M. Stahl Obsoletes Rfcs: 1062, 1020, 997, 990, 960, 943, M
Network Working Group S. Romano Request for Comments: 1117 M. Stahl Obsoletes RFCs: 1062, 1020, 997, 990, 960, 943, M. Recker 923, 900, 870, 820, 790, 776, 770, 762, SRI-NIC 758, 755, 750, 739, 604, 503, 433, 349 August 1989 Obsoletes IENs: 127, 117, 93 INTERNET NUMBERS Status of this Memo This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community. Distribution of this memo is unlimited. Introduction This Network Working Group Request for Comments documents the currently assigned network numbers and gateway autonomous systems. This RFC will be updated periodically, and in any case current information can be obtained from Hostmaster at the DDN Network Information Center (NIC). Hostmaster DDN Network Information Center SRI International 333 Ravenswood Avenue Menlo Park, California 94025 Phone: 1-800-235-3155 Network mail: [email protected] Most of the protocols used in the Internet are documented in the RFC series of notes. Some of the items listed are undocumented. Further information on protocols can be found in the memo "Official Internet Protocols" [40]. The more prominent and more generally used are documented in the "DDN Protocol Handbook" [17] prepared by the NIC. Other collections of older or obsolete protocols are contained in the "Internet Protocol Transition Workbook" [18], or in the "ARPANET Protocol Transition Handbook" [19]. For further information on ordering the complete 1985 DDN Protocol Handbook, contact the Hostmaster. Also, the Internet Activities Board (IAB) publishes the "IAB Official Protocol Standards" [52], which describes the state of standardization of protocols used in the Internet. -
The Internet Development Process: Observations and Reflections Pål Spilling
The Internet Development Process: Observations and Reflections Pål Spilling To cite this version: Pål Spilling. The Internet Development Process: Observations and Reflections. 3rd History of Nordic Computing (HiNC), Oct 2010, Stockholm, Sweden. pp.297-304, 10.1007/978-3-642-23315-9_33. hal- 01564646 HAL Id: hal-01564646 https://hal.inria.fr/hal-01564646 Submitted on 19 Jul 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License The Internet Development Process: Observations and Reflections Pål Spilling University Graduate Center (UNIK), Kjeller, Norway [email protected] Abstract. Based on the experience of being part of the team that developed the internet, the author will look back and provide a history of the Norwegian participation. The author will attempt to answer a number of questions such as why was The Norwegian Defense Research Establishment (FFI) invited to participate in the development process, what did Norway contribute to in the project, and what did Norway benefit from its participation? Keywords: ARPANET, DARPA, Ethernet, Internet, PRNET 1 A Short Historical Résumé The development of the internet went through two main phases. -
Digital Subscriber Lines and Cable Modems Digital Subscriber Lines and Cable Modems
Digital Subscriber Lines and Cable Modems Digital Subscriber Lines and Cable Modems Paul Sabatino, [email protected] This paper details the impact of new advances in residential broadband networking, including ADSL, HDSL, VDSL, RADSL, cable modems. History as well as future trends of these technologies are also addressed. OtherReports on Recent Advances in Networking Back to Raj Jain's Home Page Table of Contents ● 1. Introduction ● 2. DSL Technologies ❍ 2.1 ADSL ■ 2.1.1 Competing Standards ■ 2.1.2 Trends ❍ 2.2 HDSL ❍ 2.3 SDSL ❍ 2.4 VDSL ❍ 2.5 RADSL ❍ 2.6 DSL Comparison Chart ● 3. Cable Modems ❍ 3.1 IEEE 802.14 ❍ 3.2 Model of Operation ● 4. Future Trends ❍ 4.1 Current Trials ● 5. Summary ● 6. Glossary ● 7. References http://www.cis.ohio-state.edu/~jain/cis788-97/rbb/index.htm (1 of 14) [2/7/2000 10:59:54 AM] Digital Subscriber Lines and Cable Modems 1. Introduction The widespread use of the Internet and especially the World Wide Web have opened up a need for high bandwidth network services that can be brought directly to subscriber's homes. These services would provide the needed bandwidth to surf the web at lightning fast speeds and allow new technologies such as video conferencing and video on demand. Currently, Digital Subscriber Line (DSL) and Cable modem technologies look to be the most cost effective and practical methods of delivering broadband network services to the masses. <-- Back to Table of Contents 2. DSL Technologies Digital Subscriber Line A Digital Subscriber Line makes use of the current copper infrastructure to supply broadband services. -
Assignment #4: Big−O, Sorting, Tables, History − Soln
Assignment #4: Big−O, Sorting, Tables, History − Soln 1. Consider the following code fragment: for (int pass = 1; pass <= 10; pass++) { for (int index = 0; index < k; index += 10) { for (int count = 0; count < index; count++) { do_something(); } } } Assuming that the execution time of do_something() is independent of k, what is the most accurate description of the worst case run−time for this algorithm? a) O(1) b) O(k ) c) O(k log(k) ) 2 d) O(k ) ← 3 e) O(k ) Briefly explain your reason for choosing this answer. The outer loop executes (10+1-1)/1=10 times, and the middle loop executes (k-0)/10 = k/10 times for each execution of the outer loop. The innermost loop executes no times at first, then once, then twice, until k-1 times the last time that the middle loop executes, and the body runs O(1) time. Thus the run time is 10*(0+1+2+?+k- 1)*O(1) = O(k2). 2. Consider the following code fragment: for (int pass = 1; pass <= k; pass++) { for (int index = 0; index < 100*k; index += k) { do_something(); } } Assuming that the execution time of do_something() is O(log(k) ), what is the most accurate description of the worst case run−time for this algorithm? f) O(log(k) ) g) O(k ) h) O(k log(k) ) ← 2 i) O(k ) 2 j) O(k log(k) ) Briefly explain your reason for choosing this answer. The outer loop is executed (k+1-1)/1 = k times, the inner loop is exectuted (100k-0)/k = 100 times, and the innermost block takes time O(log(k)). -
On-Demand Routing in Multi-Hop Wireless Mobile Ad Hoc Networks
Available Online at www.ijcsmc.com International Journal of Computer Science and Mobile Computing A Monthly Journal of Computer Science and Information Technology ISSN 2320–088X IJCSMC, Vol. 2, Issue. 7, July 2013, pg.317 – 321 RESEARCH ARTICLE ON-DEMAND ROUTING IN MULTI-HOP WIRELESS MOBILE AD HOC NETWORKS P. Umamaheswari 1, K. Ranjith singh 2 1Periyar University, TamilNadu, India 2Professor of PGP College, TamilNadu, India 1 [email protected]; 2 [email protected] Abstract— An ad hoc network is a collection of wireless mobile nodes dynamically forming a temporary network without the use of any preexisting network infrastructure or centralized administration. Routing protocols used in ad hoc networks must automatically adjust to environments that can vary between the extremes of high mobility with low bandwidth, and low mobility with high bandwidth. This thesis argues that such protocols must operate in an on-demand fashion and that they must carefully limit the number of nodes required to react to a given topology change in the network. I have embodied these two principles in a routing protocol called Dynamic Source Routing (DSR). As a result of its unique design, the protocol adapts quickly to routing changes when node movement is frequent, yet requires little or no overhead during periods in which nodes move less frequently. By presenting a detailed analysis of DSR’s behavior in a variety of situations, this thesis generalizes the lessons learned from DSR so that they can be applied to the many other new routing protocols that have adopted the basic DSR framework. The thesis proves the practicality of the DSR protocol through performance results collected from a full-scale 8 node tested, and it demonstrates several methodologies for experimenting with protocols and applications in an ad hoc network environment, including the emulation of ad hoc networks. -
Core Magazine February 2002
FEBRUARY 2002 CORE 3.1 A PUBLICATION OF THE COMPUTER HISTORY MUSEUM WWW.COMPUTERHISTORY.ORG PAGE 1 February 2002 OUR ACTIONS TODAY COREA publication of the Computer History3.1 Museum IN THIS MISSION ISSUE TO PRESERVE AND PRESENT FOR POSTERITY THE ARTIFACTS AND STORIES OF THE INFORMATION AGE INSIDE FRONT COVER VISION OUR ACTIONS TODAY The achievements of tomorrow must be was an outstanding success, and I simply doesn’t exist anywhere else in TO EXPLORE THE COMPUTING REVOLUTION AND ITS John C Toole rooted in the actions we take today. hope you caught the impact of these the world. With your sustained help, our IMPACT ON THE HUMAN EXPERIENCE Many exciting and important events announcements that have heightened actions have been able to speak much 2 THE SRI VAN AND COMPUTER have happened since our last CORE awareness of our enterprise in the louder than words, and it is my goal to INTERNETWORKING publication, and they have been community. I’m very grateful to Harry see that we are able to follow through Don Nielson carefully chosen to strategically shape McDonald (director of NASA Ames), Len on our dreams! EXECUTIVE STAFF where we will be in five years. Shustek (chairman of our Board of 7 John C Toole David Miller Trustees), Donna Dubinsky (Museum This issue of CORE is loaded with THE SRI VAN AND EARLY PACKET SPEECH EXECUTIVE DIRECTOR & CEO VICE PRESIDENT OF DEVELOPMENT 2 Don Nielson First, let me officially introduce our Trustee and CEO of Handspring), and technical content and information about Karen Mathews Mike Williams new name and logo to everyone who Bill Campbell (chairman of Intuit) who our organization—from a wonderful EXECUTIVE VICE PRESIDENT HEAD CURATOR 8 has not seen them before. -
I: the Conception
Excerpt from: Mayo, Keenan and Newcomb, Peter. “How the Web Was Won,” Vanity Fair, July 2008. I: The Conception Paul Baran, an electrical engineer, conceived one of the Internet’s building blocks—packet switching— while working at the Rand Corporation around 1960. Packet switching breaks data into chunks, or “packets,” and lets each one take its own path to a destination, where they are re-assembled (rather than sending everything along the same path, as a traditional telephone circuit does). A similar idea was proposed independently in Britain by Donald Davies. Later in his career, Baran would pioneer the airport metal detector. Paul Baran: It was necessary to have a strategic system that could withstand a first attack and then be able to return the favor in kind. The problem was that we didn’t have a survivable communications system, and so Soviet missiles aimed at U.S. missiles would take out the entire telephone- communication system. At that time the Strategic Air Command had just two forms of communication. One was the U.S. telephone system, or an overlay of that, and the other was high-frequency or shortwave radio. So that left us with the interesting situation of saying, Well, why do the communications fail when the bombs were aimed, not at the cities, but just at the strategic forces? And the answer was that the collateral damage was sufficient to knock out a telephone system that was highly centralized. Well, then, let’s not make it centralized. Let’s spread it out so that we can have other paths to get around the damage. -
Glossary of Communications Terms for Relay Engineers
Glossary of Communications Terms For Relay Engineers A Working Group Report from the H14 WG Of the H – Relaying Communications Subcommittee May 2008 Participants Roger Ray, Chairman Ray Young, Vice Chairman Marc Benou Oscar Bolado Jim Huddelston Stan Klein Ken Martin John Miller Tim Phillippe Mark Simon Mal Swanson Disclaimer This document has been prepared in order to give the Protective Relay Engineer an insight and understanding of communication terms that they may encounter in their work. It is not meant to be a substitute for or replace the IEEE Dictionary. Glossary of Communications Terms For Relay Engineers AAL - ATM Adaptation Layer The standards layer that allows multiple applications to have data converted to and from the ATM cell. A protocol used that translates higher layer services into the size and format of an ATM cell. ACCUNET Switched 56 An AT&T digital service providing switched (dialup) digital service at 56 Kbps. ACCUNET T1.5 An AT&T tariffed data oriented digital service that provides leased end-to-end customer premises terminated T-1 links. ACCUNET T1.5 Reserved A disaster recovery service whereby a switched 1.544 Mbps link is available between COs and is activated when AT&T is notified of the T-1 link failure. ACCUNET T45 An AT&T tariffed service that provides 45 Mbps, DS3 service which can carry 28 T-1 connections (672 voice channels). ACD - Automatic Call Distributor A telephone facility that manages incoming calls and handles them based on the number called and an associated database of handling instructions. ADPCM - Adaptive Differential Pulse Code Modulation A speech coding method which uses fewer bits than the traditional PCM (Pulse Code Modulation).