Information about Internet Protocol Suite
The Internet protocol suite is the set of communications protocols that implement the protocol stack on which the Internet and most commercial networks run. It has also been referred to as the TCP/IP protocol suite, which is named after two of the most important protocols in it: the Transmission Control Protocol (TCP) and the Internet Protocol (IP), which were also the first two networking protocols defined. Today's IP networking represents a synthesis of two developments that began in the 1970s, namely LANs (Local Area Networks) and the Internet, both of which have revolutionized computing.
The Internet Protocol suite—like many protocol suites—can be viewed as a set of layers. Each layer solves a set of problems involving the transmission of data, and provides a well-defined service to the upper layer protocols based on using services from some lower layers. Upper layers are logically closer to the user and deal with more abstract data, relying on lower layer protocols to translate data into forms that can eventually be physically transmitted. The TCP/IP reference model consists of four layers.[1]
By the summer of 1973, Kahn and Cerf had soon worked out a fundamental reformulation, where the differences between network protocols were hidden by using a common internetwork protocol, and instead of the network being responsible for reliability, as in the ARPANET, the hosts became responsible. (Cerf credits Hubert Zimmerman and Louis Pouzin [designer of the CYCLADES network] with important influences on this design.)
With the role of the network reduced to the bare minimum, it became possible to join almost any networks together, no matter what their characteristics were, thereby solving Kahn's initial problem. (One popular saying has it that TCP/IP, the eventual product of Cerf and Kahn's work, will run over "two tin cans and a string", and it has in fact been implemented using homing pigeons, as specified in RFC1149 [2] an the implementation documented in [3].)
A computer called a router (a name changed from gateway to avoid confusion with other types of gateway) is provided with an interface to each network, and forwards packets back and forth between them. Requirements for routers are defined in RFC1812 [4].
The idea was worked out in more detailed form by Cerf's networking research group at Stanford in the 1973–74 period, resulting in the first TCP specification, [5]. (The early networking work at Xerox PARC, which produced the PARC Universal Packet protocol suite, much of which was , was also a significant technical influence; people moved between the two.)
DARPA then contracted with BBN Technologies, Stanford University, and the University College London to develop operational versions of the protocol on different hardware platforms. Four versions were developed: TCP v1, TCP v2, a split into TCP v3 and IP v3 in the spring of 1978, and then stability with TCP/IP v4 — the standard protocol still in use on the Internet today.
In 1975, a two-network TCP/IP communications test was performed between Stanford and University College London (UCL). In November, 1977, a three-network TCP/IP test was conducted between the U.S., UK, and Norway. Between 1978 and 1983, several other TCP/IP prototypes were developed at multiple research centres. A full switchover to TCP/IP on the ARPANET took place January 1, 1983.[6]
In March 1982, the US Department of Defense made TCP/IP the standard for all military computer networking.[7] In 1985, the Internet Architecture Board held a three day workshop on TCP/IP for the computer industry, attended by 250 vendor representatives, helping popularize the protocol and leading to its increasing commercial use.
On November 92005 Kahn and Cerf were presented with the Presidential Medal of Freedom for their contribution to American culture.[3]
The IP suite uses encapsulation to provide abstraction of protocols and services. Generally a protocol at a higher level uses a protocol at a lower level to help accomplish its aims. The Internet protocol stack has never been altered, by the IETF, from the four layers defined in RFC 1122. The IETF makes no effort to follow the seven-layer OSI model and does not refer to it in standards-track protocol specifications and other architectural documents.
Some textbooks have attempted to map the Internet Protocol suite model onto the seven layer OSI Model. The mapping often splits the Internet Protocol suite's Network access layer into a Data link layer on top of a Physical layer, and the Internet layer is mapped to the OSI's Network layer. These textbooks are secondary sources that contravene the intent of RFC1122 and other IETF primary sources. The IETF has repeatedly stated that Internet protocol and architecture development is not intended to be OSI-compliant.
Unique implementations include Lightweight TCP/IP, an open source stack designed for embedded systems and KA9Q NOS, a stack and associated protocols for amateur packet radio systems and personal computers connected via serial lines.
..... Click the link for more information.
The Internet Protocol suite—like many protocol suites—can be viewed as a set of layers. Each layer solves a set of problems involving the transmission of data, and provides a well-defined service to the upper layer protocols based on using services from some lower layers. Upper layers are logically closer to the user and deal with more abstract data, relying on lower layer protocols to translate data into forms that can eventually be physically transmitted. The TCP/IP reference model consists of four layers.[1]
History
The Internet protocol suite came from work done by DARPA in the early 1970s. After building the pioneering ARPANET, DARPA started work on a number of other data transmission technologies. In 1972, Robert E. Kahn was hired at the DARPA Information Processing Technology Office, where he worked on both satellite packet networks and ground-based radio packet networks, and recognized the value of being able to communicate across them. In the spring of 1973, Vinton Cerf, the developer of the existing ARPANET Network Control Program (NCP) protocol, joined Kahn to work on open-architecture interconnection models with the goal of designing the next protocol for the ARPANET.By the summer of 1973, Kahn and Cerf had soon worked out a fundamental reformulation, where the differences between network protocols were hidden by using a common internetwork protocol, and instead of the network being responsible for reliability, as in the ARPANET, the hosts became responsible. (Cerf credits Hubert Zimmerman and Louis Pouzin [designer of the CYCLADES network] with important influences on this design.)
With the role of the network reduced to the bare minimum, it became possible to join almost any networks together, no matter what their characteristics were, thereby solving Kahn's initial problem. (One popular saying has it that TCP/IP, the eventual product of Cerf and Kahn's work, will run over "two tin cans and a string", and it has in fact been implemented using homing pigeons, as specified in RFC1149 [2] an the implementation documented in [3].)
A computer called a router (a name changed from gateway to avoid confusion with other types of gateway) is provided with an interface to each network, and forwards packets back and forth between them. Requirements for routers are defined in RFC1812 [4].
The idea was worked out in more detailed form by Cerf's networking research group at Stanford in the 1973–74 period, resulting in the first TCP specification, [5]. (The early networking work at Xerox PARC, which produced the PARC Universal Packet protocol suite, much of which was , was also a significant technical influence; people moved between the two.)
DARPA then contracted with BBN Technologies, Stanford University, and the University College London to develop operational versions of the protocol on different hardware platforms. Four versions were developed: TCP v1, TCP v2, a split into TCP v3 and IP v3 in the spring of 1978, and then stability with TCP/IP v4 — the standard protocol still in use on the Internet today.
In 1975, a two-network TCP/IP communications test was performed between Stanford and University College London (UCL). In November, 1977, a three-network TCP/IP test was conducted between the U.S., UK, and Norway. Between 1978 and 1983, several other TCP/IP prototypes were developed at multiple research centres. A full switchover to TCP/IP on the ARPANET took place January 1, 1983.[6]
In March 1982, the US Department of Defense made TCP/IP the standard for all military computer networking.[7] In 1985, the Internet Architecture Board held a three day workshop on TCP/IP for the computer industry, attended by 250 vendor representatives, helping popularize the protocol and leading to its increasing commercial use.
On November 92005 Kahn and Cerf were presented with the Presidential Medal of Freedom for their contribution to American culture.[3]
Layers in the Internet Protocol suite
) IP suite stack showing the physical network connection of two hosts via two routers and the corresponding layers used at each hop |
)
The IP suite uses encapsulation to provide abstraction of protocols and services. Generally a protocol at a higher level uses a protocol at a lower level to help accomplish its aims. The Internet protocol stack has never been altered, by the IETF, from the four layers defined in RFC 1122. The IETF makes no effort to follow the seven-layer OSI model and does not refer to it in standards-track protocol specifications and other architectural documents.
| 4. Application | DNS, TFTP, TLS/SSL, FTP, Gopher, HTTP, IMAP, IRC, NNTP, POP3, SIP, SMTP, SNMP, SSH, TELNET, ECHO, BitTorrent, RTP, PNRP, rlogin, ENRP |
|---|---|
| Routing protocols like BGP, which for a variety of reasons run over TCP, may also be considered part of the application or network layer. | |
| 3. Transport | TCP, UDP, DCCP, SCTP, IL, RUDP |
| 2. Internet | Routing protocols like OSPF, which run over IP, are also to be considered part of the network layer, as they provide path selection. ICMP and IGMP run over IP and are considered part of the network layer, as they provide control information. |
| IP (IPv4, IPv6) | |
| ARP and RARP operate underneath IP but above the link layer so they belong somewhere in between. | |
| 1. Network access | Ethernet, Wi-Fi, token ring, PPP, SLIP, FDDI, ATM, Frame Relay, SMDS |
Some textbooks have attempted to map the Internet Protocol suite model onto the seven layer OSI Model. The mapping often splits the Internet Protocol suite's Network access layer into a Data link layer on top of a Physical layer, and the Internet layer is mapped to the OSI's Network layer. These textbooks are secondary sources that contravene the intent of RFC1122 and other IETF primary sources. The IETF has repeatedly stated that Internet protocol and architecture development is not intended to be OSI-compliant.
Implementations
Today, most commercial operating systems include and install the TCP/IP stack by default. For most users, there is no need to look for implementations. TCP/IP is included in all commercial Unix systems, Mac OS X, and all free-software Unix-like systems such as Linux distributions and BSD systems, as well as Microsoft Windows.Unique implementations include Lightweight TCP/IP, an open source stack designed for embedded systems and KA9Q NOS, a stack and associated protocols for amateur packet radio systems and personal computers connected via serial lines.
See also
Notes
1. ^ R. Braden (October 1989). RFC 1122: Requirements for Internet Hosts—Communication Layers. Information Sciences Institute (ISI) at University of Southern California. Retrieved on 2007-09-15.
2. ^ [http:www.isi.edu/in-notes/rfc1149.txt A Standard for the Transmission of IP Datagrams on Avian Carriers]RFC1149,D.Weitzmann, April 1, 1990
3. ^ The informal report from the RFC 1149 event.Bergen Linux User Group,April 2001
4. ^ Requirements for IP RoutersRFC1812, F. Baker, June 1995
5. ^ Specification of Internet Transmission Control Protocol,RFC675, V.Cerf et al, December 1974
6. ^ Internet History
7. ^ Ronda Hauben. From the ARPANET to the Internet. TCP Digest (UUCP). Retrieved on 2007-07-05.
2. ^ [http:www.isi.edu/in-notes/rfc1149.txt A Standard for the Transmission of IP Datagrams on Avian Carriers]RFC1149,D.Weitzmann, April 1, 1990
3. ^ The informal report from the RFC 1149 event.Bergen Linux User Group,April 2001
4. ^ Requirements for IP RoutersRFC1812, F. Baker, June 1995
5. ^ Specification of Internet Transmission Control Protocol,RFC675, V.Cerf et al, December 1974
6. ^ Internet History
7. ^ Ronda Hauben. From the ARPANET to the Internet. TCP Digest (UUCP). Retrieved on 2007-07-05.
References
- Internet History -- Pages on Robert Kahn, Vinton Cerf, and TCP/IP (reviewed by Cerf and Kahn).
- Forouzan, Behrouz A. (2003). TCP/IP Protocol Suite, 2nd, McGraw-Hill. ISBN 0-07-246060-1|.
Further reading
- Andrew S. Tanenbaum. Computer Networks. ISBN 0-13-066102-3
- Douglas E. Comer. Internetworking with TCP/IP - Principles, Protocols and Architecture. ISBN 86-7991-142-9
- Joseph G. Davies and Thomas F. Lee. Microsoft Windows Server 2003 TCP/IP Protocols and Services. ISBN 0-7356-1291-9
- Craig Hunt TCP/IP Network Administration. O'Reilly (1998) ISBN 1-56592-322-7
- W. Richard Stevens. The Protocols (TCP/IP Illustrated, Volume 1). Addison-Wesley Professional; 1st edition (December 31, 1993). ISBN 0-201-63346-9
- Ian McLean. Windows(R) 2000 TCP/IP Black Book ISBN 1-57610-687-X
External links
- RFC 675 - Specification of Internet Transmission Control Program, December 1974 Version
- TCP/IP State Transition Diagram (PDF)
- RFC 1180 A TCP/IP Tutorial - from the Internet Engineering Task Force (January 1991)
- TCP/IP FAQ
- The TCP/IP Guide - A comprehensive look at the protocols and the procedures/processes involved
- A Study of the ARPANET TCP/IP Digest
- TCP/IP Sequence Diagrams
- The Internet in Practice
- TCP/IP - Directory & Informational Resource
- Daryl's TCP/IP Primer - Intro to TCP/IP LAN administration, conversational style
- Introduction to TCP/IP
computing protocols, see Protocol (computing). For protocols on two-way voice communications, see Voice procedure. For other meanings of the word protocol, see Protocol.
..... Click the link for more information.
..... Click the link for more information.
A protocol stack (sometimes communications stack) is a particular software implementation of a computer networking protocol suite. The terms are often used interchangeably.
..... Click the link for more information.
..... Click the link for more information.
Internet is a worldwide, publicly accessible series of interconnected computer networks that transmit data by packet switching using the standard Internet Protocol (IP). It is a "network of networks" that consists of millions of smaller domestic, academic, business, and government
..... Click the link for more information.
..... Click the link for more information.
A protocol stack (sometimes communications stack) is a particular software implementation of a computer networking protocol suite. The terms are often used interchangeably.
..... Click the link for more information.
..... Click the link for more information.
The Transmission Control Protocol (TCP) is one of the core protocols of the Internet protocol suite. TCP provides reliable, in-order delivery of a stream of bytes, making it suitable for applications like file transfer and e-mail.
..... Click the link for more information.
..... Click the link for more information.
Internet protocol may refer to:
..... Click the link for more information.
- The Internet Protocol, a data-oriented protocol used for communicating data across a packet-switched internetwork
- The Internet protocol suite, a set of communications protocols that implement the protocol stack on which the Internet runs
..... Click the link for more information.
In computer networking, the upper layer protocol (ULP) refers to the more abstract protocol when performing encapsulation. It contrasts with lower layer protocol which refers to the more specific protocol.
..... Click the link for more information.
..... Click the link for more information.
In computer networking, the lower layer protocol (LLP) refers to the more specific protocol when performing encapsulation. It contrasts with upper layer protocol which refers to the more abstract protocol.
..... Click the link for more information.
..... Click the link for more information.
The TCP/IP model or Internet reference model, sometimes called the DoD model (DoD, Department of Defense) ARPANET reference model, is a layered abstract description for communications and computer network protocol design.
..... Click the link for more information.
..... Click the link for more information.
Defense Advanced Research Projects Agency
Agency overview
Formed 1958
Employees 240
Annual Budget $3.2 billion
Agency Executive Anthony J. Tether, Director
Website
www.darpa.
..... Click the link for more information.
Agency overview
Formed 1958
Employees 240
Annual Budget $3.2 billion
Agency Executive Anthony J. Tether, Director
Website
www.darpa.
..... Click the link for more information.
The ARPANET, developed by DARPA of the United States Department of Defense, was the world's first operational packet switching network, and the predecessor of the global Internet.
..... Click the link for more information.
..... Click the link for more information.
Robert E. Kahn
Born November 23 1938
Nationality USA
Field Computer Science
..... Click the link for more information.
Born November 23 1938
Nationality USA
Field Computer Science
..... Click the link for more information.
The Information Processing Technology Office is an agency of the Defense Advanced Research Projects Agency whose stated mission is:
..... Click the link for more information.
[To] create a new generation of computational and information systems that possess capabilities far beyond those of current
..... Click the link for more information.
Vinton Gray Cerf
Born May 23 1943
New Haven, Connecticut
..... Click the link for more information.
Born May 23 1943
New Haven, Connecticut
..... Click the link for more information.
Network Control Program (NCP) provided the middle layers of the protocol stack running on an ARPANET host computer. (Sometimes the abbreviation NCP is mistakenly expanded to Network Control Protocol, but this term is not found in the contemporary documentation.
..... Click the link for more information.
..... Click the link for more information.
In networking, a communications protocol or network protocol is the specification of a set of rules for a particular type of communication.
Multiple protocols often describe different aspects of a single communication.
..... Click the link for more information.
Multiple protocols often describe different aspects of a single communication.
..... Click the link for more information.
In 1991, Hubert Zimmerman was awarded the SIGCOMM Award for "20 years of leadership in the development of computer networking and the advancement of international standardization".
..... Click the link for more information.
..... Click the link for more information.
Louis Pouzin, (1931 - ) born in Chantenay-Saint-Imbert (Nièvre), France, invented the datagram and designed the first packet communications network, CYCLADES. He also created the first forms of command-line interface.
..... Click the link for more information.
..... Click the link for more information.
The CYCLADES packet switching network was an influential French network system in the early 1970s, similar to the ARPANET.
The CYCLADES network was the first to make the hosts responsible for the reliable delivery of data, rather than the network itself, using unreliable
..... Click the link for more information.
The CYCLADES network was the first to make the hosts responsible for the reliable delivery of data, rather than the network itself, using unreliable
..... Click the link for more information.
IP over Avian Carriers (IPoAC) is a humorous proposal to carry Internet Protocol (IP) traffic by birds such as homing pigeons. IP over Avian Carriers was initially described in RFC 1149, an April 1 RFC issued by the Internet Engineering Task Force written by D.
..... Click the link for more information.
..... Click the link for more information.
A gateway, in computer networking technology, is a node that serves as an entrance to another network, and vice-versa. Gateways are most commonly used to transfer data between private networks and the Internet.
..... Click the link for more information.
..... Click the link for more information.
..... Click the link for more information.
PARC (Palo Alto Research Center, Inc.), formerly Xerox PARC, is a research and development company in Palo Alto, California that began as a division of Xerox Corporation. It was founded in 1970, and incorporated as a wholly owned subsidiary of Xerox in 2002.
..... Click the link for more information.
..... Click the link for more information.
The PARC Universal Packet (commonly abbreviated to PUP, although the original documents usually use Pup) was one of the two earliest internetwork protocol suites; it was created by researchers at Xerox PARC in the mid-1970s.
..... Click the link for more information.
..... Click the link for more information.
BBN Technologies (originally Bolt Beranek and Newman) is a high-technology company that provides research and development services. BBN is based next to Fresh Pond in Cambridge, Massachusetts, USA.
..... Click the link for more information.
..... Click the link for more information.
Leland Stanford Junior University, commonly known as Stanford University or simply Stanford, is a private university located approximately 37 miles (60 kilometers) southeast of San Francisco and approximately 20 miles (32 km) northwest of San Jose in Stanford,
..... Click the link for more information.
..... Click the link for more information.
University College London, commonly known as UCL, is the oldest multi-faculty constituent college of the University of London, one of the two original founding colleges, and the first British University to be founded on a non-religious basis.
..... Click the link for more information.
..... Click the link for more information.
January 1 is the 1st day of the year (2nd in leap years) in the Gregorian calendar. There are 0 days remaining. The preceding day is December 31 of the previous year.
..... Click the link for more information.
..... Click the link for more information.
19th century - 20th century - 21st century
1950s 1960s 1970s - 1980s - 1990s 2000s 2010s
1980 1981 1982 - 1983 - 1984 1985 1986
Year 1983 (MCMLXXXIII
..... Click the link for more information.
1950s 1960s 1970s - 1980s - 1990s 2000s 2010s
1980 1981 1982 - 1983 - 1984 1985 1986
Year 1983 (MCMLXXXIII
..... Click the link for more information.
The Internet Architecture Board (IAB) is the committee charged with oversight of the technical and engineering development of the Internet by the Internet Society (ISOC).
..... Click the link for more information.
..... Click the link for more information.
This article is copied from an article on Wikipedia.org - the free encyclopedia created and edited by online user community. The text was not checked or edited by anyone on our staff. Although the vast majority of the wikipedia encyclopedia articles provide accurate and timely information please do not assume the accuracy of any particular article. This article is distributed under the terms of GNU Free Documentation License.
Herod_Archelaus
