DOCSLIB.ORG

The Internet: Looking Back on How We Got Connected to the World

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Internet: Looking Back on How We Got Connected to the World FEDERAL COMMUNICATIONS COMMISSION et: The Intern How we g Back on Lookin e world cted to th got conne Summer 2004 Standards and Protocols: Making sure the Message the Birth of the Internet Gets Through • 1963—American Standard Code for While some may think primary owner of high- to link the Nation’s Information Interchange (ASCII) the Internet is a new powered computers, it scientists and engi- adopted. This was the first universal communication tool, its was in association with neers via a cross- standard to allow computers from history is remarkably simi- the Nation’s SAGE air- country computer different manufacturers to exchange lar to other areas of com- defense system that the network. A 1965 test data. munication: first sharing of computer of a wide area net- • 1969—Request for Comments power occurred. work (known as the • People had some- (RFC) first issued. The RFC is a “Experimental Net- thing to share; But early experiments in series of standards for computer net- work”) between MIT sharing the Nation’s com- working. RFC 1 detailed the operat- • Common languages and Stanford showed puting power didn’t sat- ing standards of ARPANET, the developed; and that such a nation- world’s first packet switching net- isfy all the growing • The common lan- wide network was work. Today there are nearly 4000 needs. So, researchers guages were trans- possible. RFC’s. mitted across physical working with DOD’s Ad- media. vanced Research Project Building upon this, • 1974—Transmission Control Proto- Agency (ARPA) built and other similar tests, col (TCP-RFC 793) proposed. This In Internet terms, the ele- upon the early 1960s in 1967 Lincoln Lab standard allowed network-to- ments to be shared were development of packet scientists working network connections. In 1978 the information and comput- switching theory and vi- with ARPA put for- Internet Protocol (IP-RFC 791) ing time, the common sions of a “Galactic Net- ward plans for con- joined TCP. Together, these languages were data work” to figure out a way necting most of the (continued on page 4) communications proto- cols, and phone circuits (continued on page 3) carried it all. FCC: A Long-Term INTEREST As computer use spread after WWII, it didn’t take • 1966—Computer I Notice of Inquiry. telecommunications services and long for people with lim- • 1973—Agency approves first applica- unregulated information services. ited computer access to tion for value-added carrier to pro- want to tap into the ex- • 1985—Computer III proceeding re- vide specialized communication ser- leased. cess capacity of those vices to computer users (Telenet). with computers. • 1998—FCC affirms that Internet Ser- • 1980—Computer II Final Order estab- vice Providers will continue to be Since, in the 1950s, the lishes distinction between regulated treated as “end users,” thus paying U. S. government was the lower access fees. (continued on page 3) 1970 1962 1964 1969 ALOHAnet, 1958 U.S. airlines ARPANET 1971 Galactic 1965 a packet net- 1st commercial launch 1st begins —1st Network U.S.’s 1st work that used @ symbol modem — commercial packet switch- proposed wide area radio waves for proposed for 300 bps time -sharing ing network network transmission, email of computers established with SABRE P AGE 2 T HE INTERNET: Broadband-AT-HOME: where the information superhighway speeds up Broadband Subscribers 14 A technology in operation for less automation, or even patient health than 10 years would not usually remotely through the Web. The Cable 12 qualify for historical treatment. high speed and high volume that 10 However, in the case of residential broadband offers could Cable broadband Internet access, the ex- also be used for bun- 8 plosive growth of this technology dled service where, Cable 6 may be rewriting all the rules re- for example, cable DSL garding the history of new tech- television, video-on- DSL 4 DSL In millions nologies. demand, voice, 2 data, and other Sat Sa S Begun in 1996, when Rogers Com- elli te ate 0 services are all te llite llite munications introduced the first offered over a single cable modem service in Canada, line. In truth, it is possible that many broadband encompasses several of the applications that will best Interestingly, these studies also find digital technologies (cable, satellite, exploit the technological capabili- that adults between the ages of 55 phone lines, power line, and wire- ties of broadband, while also cap- and 64 are more active adopters of less) that provide consumers inte- turing the imagination of consum- broadband than young adults. Re- grated access to voice, high-speed ers, have yet to be developed.” searchers don’t know if this is an (faster than 200 Kbps) data, video- indication of pricing issues or that on-demand, and interactive delivery But despite these many advantages, young people already accept services. as late as 1999, when the FCC is- broadband. But, it does indicate sued its first report on broadband, it that getting fast access to the Inter- The Congressional Research Service reported that "the consumer broad- net is no longer just a fad for the says that “broadband access, along band market is in the early stages of young. And, since broadband Inter- with the content and services it development.” net users tend to spend more time might enable, has and visit more pages online, access- the potential to But broad- ing the Internet via broadband is transform the band did also beginning to show up as an Internet—both The first attempt, in 1969, to connect not stay in alternative to entertainment alter- what it offers and computers at the first two ARPANET universities its early natives such as watching tv. how it is used. For stages for example, a two- crashed the system. On the second try the long. The Besides continuing growth in way, high-speed connection was made successfully and the Bandwidth broadband acceptance, new ways connection could Internet’s predecessor was begun. Report, of using and delivering broadband be used for based on are opening new vistas and creat- interactive Nielsen// ing new challenges. Ideas ranging applications such NetRatings from using electric lines as a broad- as online surveys, band transmission medium to plac- classrooms, showrooms, or health finds that between 2000 and 2001 ing long distance phone calls via clinics, where teacher and student broadband subscriptions rose over broadband may offer more services (or customer and salesperson, 50%; and, there was another 48% at lower prices—but, will also re- doctor and patient) can see and growth in 2003. Today, it is esti- quire flexible and creative thinking hear each other through their mated that over 27 million busi- about many of our traditional utility nesses and households (45% of computers. An “always on” and communication services. connection could be used to Internet households) use broad- band to access the Internet. monitor home security, home 1977 1981 1978 1979 Desktop 1973 The term 1979 IP protocol joins USENET personal Ethernet a “internetting” begins Emoticons 1982 TCP as common newsgroups computers local area net- to be used to de- Domain Name standard for -) -( grow from introduced work essential, scribe connections System created. net-to-net first suggested work at proposed between various by RFC 819 networks connections Duke University T HE INTERNET: LOOKING BACK PAGE 3 FCC: A Long-Term INTEREST (continued from page 1) • 1999—FCC releases Local Com- 2. Promote competition across • 2003—FCC hosts Voice over IP petition and Broadband Report different platforms for broad- Forum. and Order. band services. 3. Ensure that broadband ser- • 2002—FCC proceedings on vices exist in a minimal Internet Access over Cable and regulatory environment Internet Access over DSL find that promotes investment The ARPANET experienced its first virus in 1980. that these methods of Internet and innovation. This virus shut down the ARPANET for a short access are information services. These proceedings also set 4. Develop an analytical while. The first worm struck in 1988 and forth four guiding principles in framework that is consis- infected 10% of ARPANET hosts. regard to broadband: tent, to the extent possible, across multiple platforms. 1. Encourage the ubiquitous availability of broadband Internet access to all Ameri- cans. The birth of the internet (continued from page 1) Nation’s research computers over with different equipment and differ- mil, gov, edu, org), and phone circuits. This plan was car- ent operating systems—to talk to ried out in 1969 when the ARPA- each other some common lan- • Upgrades to the transmission NET, using 50 Kbps circuits, con- guage had to be developed. backbone. nected computers at four universi- But most of these improvements ties in California and Utah. The ARPANET initially used the Net- work Control Program (NCP) as this were known only to academics, But the commercial sector did not common transmission language. government employees, and gov- allow the ability to network com- However, in 1983 ARPANET ernment-sponsored researchers and puters to belong only to academics changed its common language to contractors until the late-1980s. and scientists for very long. By the Transmission Control Protocol/ The Internet we know today began 1974 the FCC had already ap- Internet Protocol (TCP/IP). TCP/IP to seem possible in 1989 when the proved three applications for what remains today’s most commonly first commercial email carriers (MCI were called “value-added carriers.” used protocol because of its reliabil- Mail and CompuServe) began busi- These organizations added equip- ity and proven track record. ness. That same year the first com- ment to leased transmission lines in mercial dial-up Internet Service Pro- order to provide services to com- Many additional improvements in vider (World Comes on Line) also puter users.
Load more

Recommended publications
  • 2606 A. Panitz BCP: 32 June 1999 Category: Best Current Practice
    Network Working Group D. Eastlake Request for Comments: 2606 A. Panitz BCP: 32 June 1999 Category: Best Current Practice Reserved Top Level DNS Names Status of this Memo This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. Abstract To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented. Table of Contents 1. Introduction............................................1 2. TLDs for Testing, & Documentation Examples..............2 3. Reserved Example Second Level Domain Names..............2 4. IANA Considerations.....................................3 5. Security Considerations.................................3 References.................................................3 Authors' Addresses.........................................4 Full Copyright Statement...................................5 1. Introduction The global Internet Domain Name System is documented in [RFC 1034, 1035, 1591] and numerous additional Requests for Comment. It defines a tree of names starting with root, ".", immediately below which are top level domain names such as ".com" and ".us". Below top level domain names there are normally additional levels of names. Eastlake & Panitz Best Current Practice [Page 1] RFC 2606 Reserved Top Level DNS Names June 1999 2. TLDs for Testing, & Documentation Examples There is a need for top level domain (TLD) names that can be used for creating names which, without fear of conflicts with current or future actual TLD names in the global DNS, can be used for private testing of existing DNS related code, examples in documentation, DNS related experimentation, invalid DNS names, or other similar uses.
    [Show full text]
  • Network Working Group J. Postel Request for Comments: 820 J. Vernon January 1983 Obsoletes Rfcs
    Network Working Group J. Postel Request for Comments: 820 J. Vernon January 1983 Obsoletes RFCs: 790, 776, 770, 762, 758, 755, 750, 739, 604, 503, 433, 349 Obsoletes IENs: 127, 117, 93 ASSIGNED NUMBERS This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This RFC will be updated periodically, and in any case current information can be obtained from Jon Postel. The assignment of numbers is also handled by Jon, subject to the agreement between DARPA/IPTO and DDN/PMO about number allocation, documented in Appendix A of this RFC. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, or network number please contact Jon to receive a number assignment. Jon Postel USC - Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90291 phone: (213) 822-1511 ARPANET mail: POSTEL@ISIF The ARPANET community is making the transition form the ARPANET to the ARPA Internet. This has been characterized as the NCP/TCP transition [63], although many other the protocols are involved, too. The working documents for the new Internet environment have been collected by the Network Information Center (NIC) in a book entitled the "Internet Protocol Transition Workbook" [62]. Most of the protocols mentioned here are documented in the RFC series of notes. The more prominent and more generally used are documented in the "Internet Protocol Transition Workbook" or in the old "Protocol Handbook" [17] prepared by the NIC. Some of the items listed are undocumented.
    [Show full text]
  • Network Working Group J. Reynolds Request for Comments: 923 J
    Network Working Group J. Reynolds Request for Comments: 923 J. Postel ISI Obsoletes RFCs: 900, 870, 820, October 1984 790, 776, 770, 762, 758, 755, 750, 739, 604, 503, 433, 349 Obsoletes IENs: 127, 117, 93 ASSIGNED NUMBERS Status of this Memo This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. Distribution of this memo is unlimited. Introduction This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This RFC will be updated periodically, and in any case current information can be obtained from Joyce Reynolds. The assignment of numbers is also handled by Joyce. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, network number, etc., please contact Joyce to receive a number assignment. Joyce Reynolds USC - Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90292-6695 Phone: (213) 822-1511 ARPA mail: [email protected] Most of the protocols mentioned here are documented in the RFC series of notes. The more prominent and more generally used are documented in the "Internet Protocol Transition Workbook" [33] or in the old "ARPANET Protocol Handbook" [34] prepared by the NIC. Some of the items listed are undocumented. Further information on protocols can be found in the memo "Official ARPA-Internet Protocols" [89]. In all cases the name and mailbox of the responsible individual is indicated. In the lists that follow, a bracketed entry, e.g., [nn,iii], at the right hand margin of the page indicates a reference for the listed protocol, where the number ("nn") cites the document and the letters ("iii") cites the person.
    [Show full text]
  • Growth of the Internet
    Growth of the Internet K. G. Coffman and A. M. Odlyzko AT&T Labs - Research [email protected], [email protected] Preliminary version, July 6, 2001 Abstract The Internet is the main cause of the recent explosion of activity in optical fiber telecommunica- tions. The high growth rates observed on the Internet, and the popular perception that growth rates were even higher, led to an upsurge in research, development, and investment in telecommunications. The telecom crash of 2000 occurred when investors realized that transmission capacity in place and under construction greatly exceeded actual traffic demand. This chapter discusses the growth of the Internet and compares it with that of other communication services. Internet traffic is growing, approximately doubling each year. There are reasonable arguments that it will continue to grow at this rate for the rest of this decade. If this happens, then in a few years, we may have a rough balance between supply and demand. Growth of the Internet K. G. Coffman and A. M. Odlyzko AT&T Labs - Research [email protected], [email protected] 1. Introduction Optical fiber communications was initially developed for the voice phone system. The feverish level of activity that we have experienced since the late 1990s, though, was caused primarily by the rapidly rising demand for Internet connectivity. The Internet has been growing at unprecedented rates. Moreover, because it is versatile and penetrates deeply into the economy, it is affecting all of society, and therefore has attracted inordinate amounts of public attention. The aim of this chapter is to summarize the current state of knowledge about the growth rates of the Internet, with special attention paid to the implications for fiber optic transmission.
    [Show full text]
  • 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.
    [Show full text]
  • Network Working Group N. Freed Request for Comments: 2049 Innosoft Obsoletes: 1521, 1522, 1590 N
    Network Working Group N. Freed Request for Comments: 2049 Innosoft Obsoletes: 1521, 1522, 1590 N. Borenstein Category: Standards Track First Virtual November 1996 Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract STD 11, RFC 822, defines a message representation protocol specifying considerable detail about US-ASCII message headers, and leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for (1) textual message bodies in character sets other than US-ASCII, (2) an extensible set of different formats for non-textual message bodies, (3) multi-part message bodies, and (4) textual header information in character sets other than US-ASCII. These documents are based on earlier work documented in RFC 934, STD 11, and RFC 1049, but extends and revises them. Because RFC 822 said so little about message bodies, these documents are largely orthogonal to (rather than a revision of) RFC 822. The initial document in this set, RFC 2045, specifies the various headers used to describe the structure of MIME messages. The second document defines the general structure of the MIME media typing system and defines an initial set of media types.
    [Show full text]
  • Multimedia, Internet, On-Line
    Section IV: Multimedia, the Internet, and On-Line Services High-End Digital Video Applications Larry Amiot Electronic and Computing Technologies Division Argonne National Laboratory The emphasis of this paper is on the high-end applications Internet and Intranet that are driving digital video. The research with which I am involved at Argonne National Laboratory is not done on dig- The packet video networks which currently support many ital video per se, but rather on how the research applications applications such as file transfer, Mbone video (talking at the laboratory drive its requirements for digital video. The heads), and World Wide Web browsing are limiting for high- paper will define what digital video is, what some of its com- quality video because of the low throughput one can achieve ponents are, and then discuss a few applications that are dri- via the Internet or intranets. Examples of national packet ving the development of these components. The focus will be switched networks developed in the last several years include on what digital video means to individuals in the research the National Science Foundation Network (NSFNet). The and education community. Department of Energy had its own network called ESNET, and the National Aeronautics and Space Administration The Digital Video Environment (NASA) had a network as well. Recently, the NSFNet was de- commissioned, and commercial interests are now starting to In 1996, a group of people from several universities in the fill that void. Research and education communities are find- Midwest and from Argonne formed a Video Working Group. ing, however, that this new commercial Internet is too re- This body tried to define the areas of digital video of impor- stricting and does not meet their throughput requirements; it tance to their institutions.
    [Show full text]
  • Before the FEDERAL COMMUNICATIONS COMMISSION Washington, D.C
    Before the FEDERAL COMMUNICATIONS COMMISSION Washington, D.C. 20554 In the Maller of ) ) Global Crossing Limited and Level 3 ) Communications, Inc., Application for ) Consent to Transfer Control ofAuthority to ) Provide Global facilities-Based and Global ) IB Docket No. I 1-78 Resale International Telecommunications ) Services and ofDomestic Common Carrier ) Transmission Lines, Pursuant to Section 214 ) of the Communications Act, as Amended ) ) Level 3 Communications, Inc., Petition for ) Declaratory Ruling Under Section 31 0(b)(4) ) Ofthe Communications Act of 1934, as ) AJnended ) DECLARATION OF MARCELLUS NIXON I. My name is Marcellus I ixon. I am the Director ofIP Network Planning at XO Communications, LLC. (XO). My business address is 13865 Sunrise Valley Drive, Hcrndon, VA 20171. 2. I have bcen employed at XO since 2002, initially as an IP Network Engineer. I have been in my current position as Dircctor ofIP Network Planning since 2008. My career with IP nctworks began in the US Army. I have also held networking positions with the NASD and internet MCT. I hold a Bachelor ofInterdisciplinary Studies from the University of Virginia. 3. In my current position, I am responsible for all strategic aspects of IP network planning, and I am the peering coordinator for XO. In that capacity, I manage relationships with other Tier I and lower tier Internet Backbone Providers (lI3Ps), including detennining wbere peering occurs, evaluating network arcbitecture needs such as capacity requirements, routing requirements, and the impact of technological changes on the peering arrangement. I also am responsible for negotiating interconnection (peering) agreements. To date, I have negotiated on behalf ofXO forty-seven (47) peering agreements.
    [Show full text]
  • Networking and the Internet
    Networking and Today’s lecture the Internet History of the Internet How the Internet works Lecture 4 – COMPSCI111/111G S2 2018 Network protocols The telephone WWII and the Cold War 1876: first successful bi-directional Computer technology played an important role transmission of clear speech in code-breaking during WW2 by Alexander Bell and Thomas Watson Cold War between US and USSR led to a technology and arms race Peaked with the launch of Sputnik in 1957 1958: Advanced Research Projects Agency (ARPA) 1940: first successful transmission established of digital data through over telegraph wires by George Stibitz April 1969: construction of ARPANET begins, a packet-switching network Circuit-switching network Packet-switching network Nodes are connected physically via a central Data is broken into packets, which are then sent node on the best route in the network Used by the telephone network Each node on the route sends the packet onto its next destination, avoiding congested or broken Originally, switchboard operators had to nodes manually connect phone calls, today this is done electronically B A ARPANET ARPANET in 1977 October 1969: ARPANET is completed with four nodes 1973: Norway connects to ARPANET via satellite, followed by London via a terrestrial link ARPANET ARPANET to the Internet 1983: TCP/IP implemented in ARPANET Networks similar to ARPANET sprang up around the USA and in other countries 1990: ARPANET is formally decommissioned 1984: domain name system (DNS) implemented 1985: NSFNET was established 1989: Waikato University connects to NSFNET 1991: World Wide Web (WWW) created at CERN (European Organization for Nuclear Research) by Tim Berners-Lee 1995: NSFNET is retired WWW vs Internet Internet growth The Internet is a global system of interconnected computer networks.
    [Show full text]
  • Design of a Lan-Based Voice Over Ip (Voip) Telephone System
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by KhartoumSpace DESIGN OF A LAN-BASED VOICE OVER IP (VOIP) TELEPHONE SYSTEM A thesis submitted to the University of Khartoum in partial fulfillment of the requirement for the degree of MSC in Communication & Information Systems BY HASSAN SULEIMAN ABDALLA OMER B.SC of Electrical Engineering (2000) University of Khartoum Supervisor Dr. MOHAMMED ALI HAMAD ABBAS Faculty of Engineering & Architecture Department of Electrical & Electronics Engineering SEPTEMBER 2009 ﺑﺴﻢ اﷲ اﻟﺮﺣﻤﻦ اﻟﺮﺣﻴﻢ ﺻﺪق اﷲ اﻟﻌﻈﻴﻢ iii ACKNOWLEDGEMENTS First I would like to thanks my supervisor Dr. Mohammed Ali Hamad Abbas, because this research project would not have been possible without his support and guidance; so I take this opportunity to offer him my gratitude for his patience ,support and guidance . Special thanks to the Department of Electrical and Electronics Engineering University Of Khartoum for their facilities, also I would like to convey my thanks to the staff member of MSc program for their help and to all my colleges in the MSc program. It is with great affection and appreciation that I acknowledge my indebtedness to my parents for their understanding & endless love. H.Suleiman iv Abstract The objective of this study was to design a program to transmit voice conversations over data network using the internet protocol –Voice Over IP (VOIP). JAVA programming language was used to design the client-server model, codec and socket interfaces. The design was fully explained as to its input, processing and output. The test of the designed voice over IP model was successful, although some delay in receiving the conversation was noticed.
    [Show full text]
  • How Constructing the DNS Shaped Internet Governance
    A Service of Leibniz-Informationszentrum econstor Wirtschaft Leibniz Information Centre Make Your Publications Visible. zbw for Economics Malcic, Steven Article The problem of future users: how constructing the DNS shaped internet governance Internet Policy Review Provided in Cooperation with: Alexander von Humboldt Institute for Internet and Society (HIIG), Berlin Suggested Citation: Malcic, Steven (2016) : The problem of future users: how constructing the DNS shaped internet governance, Internet Policy Review, ISSN 2197-6775, Alexander von Humboldt Institute for Internet and Society, Berlin, Vol. 5, Iss. 3, pp. 1-13, http://dx.doi.org/10.14763/2016.3.434 This Version is available at: http://hdl.handle.net/10419/214028 Standard-Nutzungsbedingungen: Terms of use: Die Dokumente auf EconStor dürfen zu eigenen wissenschaftlichen Documents in EconStor may be saved and copied for your Zwecken und zum Privatgebrauch gespeichert und kopiert werden. personal and scholarly purposes. Sie dürfen die Dokumente nicht für öffentliche oder kommerzielle You are not to copy documents for public or commercial Zwecke vervielfältigen, öffentlich ausstellen, öffentlich zugänglich purposes, to exhibit the documents publicly, to make them machen, vertreiben oder anderweitig nutzen. publicly available on the internet, or to distribute or otherwise use the documents in public. Sofern die Verfasser die Dokumente unter Open-Content-Lizenzen (insbesondere CC-Lizenzen) zur Verfügung gestellt haben sollten, If the documents have been made available under an Open gelten
    [Show full text]
  • Network Working Group J. Postel Request for Comments: 959 J. Reynolds ISI Obsoletes RFC: 765 (IEN 149) October 1985
    Network Working Group J. Postel Request for Comments: 959 J. Reynolds ISI Obsoletes RFC: 765 (IEN 149) October 1985 FILE TRANSFER PROTOCOL (FTP) Status of this Memo This memo is the official specification of the File Transfer Protocol (FTP). Distribution of this memo is unlimited. The following new optional commands are included in this edition of the specification: CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU (Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD (Print Directory), and SYST (System). Note that this specification is compatible with the previous edition. 1. INTRODUCTION The objectives of FTP are 1) to promote sharing of files (computer programs and/or data), 2) to encourage indirect or implicit (via programs) use of remote computers, 3) to shield a user from variations in file storage systems among hosts, and 4) to transfer data reliably and efficiently. FTP, though usable directly by a user at a terminal, is designed mainly for use by programs. The attempt in this specification is to satisfy the diverse needs of users of maxi-hosts, mini-hosts, personal workstations, and TACs, with a simple, and easily implemented protocol design. This paper assumes knowledge of the Transmission Control Protocol (TCP) [2] and the Telnet Protocol [3]. These documents are contained in the ARPA-Internet protocol handbook [1]. 2. OVERVIEW In this section, the history, the terminology, and the FTP model are discussed. The terms defined in this section are only those that have special significance in FTP. Some of the terminology is very specific to the FTP model; some readers may wish to turn to the section on the FTP model while reviewing the terminology.
    [Show full text]