Content deleted Content added
mNo edit summary |
|||
Line 41:
IBM, AT&T and DEC were the first major corporations to adopt TCP/IP, this despite having competing [[proprietary protocol]]s. In IBM, from 1984, [[Barry Appelman]]'s group did TCP/IP development. They navigated the corporate politics to get a stream of TCP/IP products for various IBM systems, including [[MVS]], [[VM (operating system)|VM]], and [[OS/2]]. At the same time, several smaller companies, such as [[FTP Software]] and the [[Wollongong Group]], began offering TCP/IP stacks for [[DOS]] and [[Microsoft Windows]].<ref name="TtEPm">{{cite web| url = http://support.microsoft.com/kb/108007| title = Using Wollongong TCP/IP with Windows for Workgroups 3.11| website=Microsoft Support| archive-url=https://web.archive.org/web/20120112105314/http://support.microsoft.com/kb/108007| archive-date = 12 January 2012| url-status=dead}}</ref> The first [[VM/CMS]] TCP/IP stack came from the University of Wisconsin.<ref name="BZHnU">{{cite web|url=http://www.weblab.isti.cnr.it/education/ssfs/lezioni/slides/archives/cern.htm|title=A Short History of Internet Protocols at CERN|access-date=12 September 2016|archive-url=https://web.archive.org/web/20161110200124/http://www.weblab.isti.cnr.it/education/ssfs/lezioni/slides/archives/cern.htm|archive-date=10 November 2016|url-status=dead}}</ref>
Some programmers are notable for early TCP/IP stack implementations. Jay Elinsky and Oleg Vishnepolsky of IBM Research wrote software for VM/CMS and OS/2, respectively.<ref>''An Introduction to Computer Networks''. Stanford University, CS144, Fall 2012, pp. 21–22. Available at: <nowiki>https://kirils.org/skype/stuff/pdf/2012/An_Introduction_to_Computer_Networksweek_one.pdf</nowiki></ref> In 1984, Donald Gillies at MIT wrote a ''ntcp'' multi-connection TCP which runs atop the IP/PacketDriver layer maintained by John Romkey at MIT in 1983–84. Romkey leveraged this TCP in 1986 when FTP Software was founded.<ref name="j7VeG">{{cite web |title= Desktop TCP/IP at middle age |last1= Baker |first1= Steven |last2= Gillies |first2= Donald W |url= http://www.ece.ubc.ca/~gillies/9802net.html |access-date= September 9, 2016 |archive-date= August 21, 2015 |archive-url= https://web.archive.org/web/20150821010509/http://www.ece.ubc.ca/~gillies/9802net.html |url-status= dead }}</ref><ref name="vss61">{{cite web|url=http://www.romkey.com/about/|title=About|last=Romkey|first=John|date=17 February 2011|access-date=12 September 2016|archive-date=November 5, 2011|archive-url=https://web.archive.org/web/20111105074443/http://www.romkey.com/about/|url-status=live}}</ref> Starting in 1985, Phil Karn created a multi-connection TCP application for ham radio systems (KA9Q TCP).<ref name="vCamZ">Phil Karn, ''KA9Q TCP Download Website''</ref>
The spread of TCP/IP was fueled further in June 1989, when the [[University of California, Berkeley]] agreed to place the TCP/IP code developed for [[BSD UNIX]] into the public ___domain. Various corporate vendors, including IBM, included this code in commercial TCP/IP software releases. For Windows 3.1, the dominant PC operating system among consumers in the first half of the 1990s, Peter Tattam's release of the [[Trumpet Winsock]] TCP/IP stack was key to bringing the Internet to home users. Trumpet Winsock allowed TCP/IP operations over a serial connection ([[Serial_Line_Internet Protocol|SLIP]] or [[Point-to-Point Protocol|PPP]]). The typical home PC of the time had an external Hayes-compatible modem connected via an RS-232 port with an [[8250]] or [[16550]] UART which required this type of stack. Later, Microsoft would release their own TCP/IP add-on stack for [[Windows for Workgroups]] 3.11 and a native stack in Windows 95. These events helped cement TCP/IP's dominance over other protocols on Microsoft-based networks, which included IBM's [[Systems Network Architecture]] (SNA), and on other platforms such as [[Digital Equipment Corporation]]'s [[DECnet]], [[Open Systems Interconnection]] (OSI), and [[Xerox Network Systems]] (XNS).
| |||