Internet Protocol Suite

From Wikipedia, the free encyclopedia

Jump to: navigation, search

The Internet Protocol Suite (commonly known as TCP/IP) is the set of communications protocols used for the Internet and other similar networks. It is named from two of the most important protocols in it: the Transmission Control Protocol (TCP) and the Internet Protocol (IP), which were the first two networking protocols defined in this standard. Today's IP networking represents a synthesis of several developments that began to evolve in the 1960s and 1970s, namely the Internet and LANs (Local Area Networks), which emerged in the mid- to late-1980s, together with the advent of the World Wide Web in the early 1990s.

The Internet Protocol Suite, like many protocol suites, may 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 model consists of four layers (RFC 1122).[1][2] From lowest to highest, these are the Link Layer, the Internet Layer, the Transport Layer, and the Application Layer.

The Internet Protocol Suite
Application Layer
BGP · DHCP · DNS · FTP · GTP · HTTP · IMAP · IRC · Megaco · MGCP · NNTP · NTP · POP · RIP · RPC · RTP · RTSP · SDP · SIP · SMTP · SNMP · SOAP · SSH · Telnet · TLS/SSL · XMPP · (more)
Transport Layer
TCP · UDP · DCCP · SCTP · RSVP · ECN · (more)
Internet Layer
IP (IPv4, IPv6) · ICMP · ICMPv6 · IGMP · IPsec · (more)
Link Layer
ARP · RARP · NDP · OSPF · Tunnels (L2TP) · PPP · Media Access Control (Ethernet, MPLS, DSL, ISDN, FDDI) · Device Drivers · (more)
This box: view • talk • edit

Contents

[edit] History

The Internet Protocol Suite resulted from work done by Defense Advanced Research Projects Agency (DARPA) in the early 1970s. After building the pioneering ARPANET in 1969, 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 generation for the ARPANET.

By the summer of 1973, Kahn and Cerf had 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." There is even an implementation designed to run using homing pigeons, IP over Avian Carriers, documented in RFC 1149.[3][4]

A computer called a router (a name changed from gateway to avoid confusion with other types of gateways) is provided with an interface to each network, and forwards packets back and forth between them. Requirements for routers are defined in (Request for Comments 1812).[5]

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 (Request for Comments 675) [6]. (The early networking work at Xerox PARC, which produced the PARC Universal Packet protocol suite, much of which existed around the same period of time, 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 sites in the US, UK, and Norway. Several other TCP/IP prototypes were developed at multiple research centers between 1978 and 1983. The migration of the ARPANET to TCP/IP was officially completed on January 1, 1983 when the new protocols were permanently activated.[7]

In March 1982, the US Department of Defense declared TCP/IP as the standard for all military computer networking.[8] In 1985, the Internet Architecture Board held a three day workshop on TCP/IP for the computer industry, attended by 250 vendor representatives, promoting the protocol and leading to its increasing commercial use.

Kahn and Cerf were honored with the Presidential Medal of Freedom on November 9, 2005 for their contribution to American culture.

[edit] Layers in the Internet Protocol Suite

[edit] The concept of layers

The TCP/IP suite uses encapsulation to provide abstraction of protocols and services. Such encapsulation usually is aligned with the division of the protocol suite into layers of general functionality. In general, an application (the highest level of the model) uses a set of protocols to send its data down the layers, being further encapsulated at each level.

This may be illustrated by an example network scenario, in which two Internet host computers communicate across local network boundaries constituted by their internetworking gateways (routers).

TCP/IP stack operating on two hosts connected via two routers and the corresponding layers used at each hop
Encapsulation of application data descending through the protocol stack.

The functional groups of protocols and methods are the Application Layer, the Transport Layer, the Internet Layer, and the Link Layer (RFC 1122). It should be noted that this model was not intended to be a rigid reference model into which new protocols have to fit in order to be accepted as a standard.

The following table provides some examples of the protocols grouped in their respective layers.

Application DNS, TFTP, TLS/SSL, FTP, Gopher, HTTP, IMAP, IRC, NNTP, POP3, SIP, SMTP,SMPP, SNMP, SSH, Telnet, Echo, RTP, PNRP, rlogin, ENRP
Routing protocols like BGP and RIP which run over TCP/UDP, may also be considered part of the Internet Layer.
Transport TCP, UDP, DCCP, SCTP, IL, RUDP, RSVP
Internet IP (IPv4, IPv6) ICMP, IGMP, and ICMPv6
OSPF for IPv4 was initially considered IP layer protocol since it runs per IP-subnet, but has been placed on the Link since RFC 2740.
Link ARP, RARP, OSPF (IPv4/IPv6), IS-IS, NDP

[edit] Layer names and number of layers in the literature

The following table shows the layer names and the number of layers in the TCP/IP model as presented in university course textbooks about computer networking in use today.

RFC 1122, Kurose[9] Forouzan [10] Comer[11], Kozierok[12] Stallings[13] Tanenbaum[14] Cisco Academy[15] Arpanet Reference Model 1982 (RFC 871)
Four layers Five layers Five layers Five layers Four layers Four layers Three layers
Application Application Application Application Application Application Application/Process
Transport Transport Transport Host-to-host or transport Transport Transport Host-to-host
Internet Network Internet Internet Internet Internetwork
Link Data link Data link (Network interface) Network access Host-to-network Network interface Network interface
Physical (Hardware) Physical

These textbooks are secondary sources that may contravene the intent of RFC 1122 and other IETF primary sources[16].

Different authors have interpreted the RFCs differently regarding whether the Link Layer (and the four-layer TCP/IP model) covers physical layer issues or a "hardware layer" is assumed below the link layer. Some authors have tried to use other names for the Link Layer, such as Network interface layer, in effort to avoid confusion with the Data Link Layer of the seven-layer OSI model. Others have attempted to map the Internet Protocol model onto the seven-layer OSI Model. The mapping often results in a model with five layers, wherein the Link Layer is split into a Data Link Layer on top of a Physical Layer. In literature with a bottom-up approach to computer networking, in which physical layer issues are emphasized, the use of the OSI reference model is sometimes preferred.

The Internet Layer is usually directly mapped to the OSI's Network Layer. At the top of the hierarchy, the Transport Layer is always mapped directly into OSI Layer 4 of the same name. OSIs Application Layer, Presentation Layer, and Session Layer are collapsed into TCP/IP's Application Layer. As a result, these efforts result in either a four- or five-layer scheme with a variety of layer names. This has caused considerable confusion in the application of these models. Other authors dispense with rigid pedagogy[17] focusing instead on functionality and behavior.

The Internet protocol stack has never been altered by the Internet Engineering Task Force (IETF) from the four layers defined in RFC 1122. The IETF makes no effort to follow the seven-layer OSI model although RFCs sometimes refer to it. The IETF has repeatedly stated[citation needed] that Internet protocol and architecture development is not intended to be OSI-compliant.

RFC 3439, addressing Internet architecture, contains a section entitled: "Layering Considered Harmful".[16]

[edit] Implementations

Most operating systems in use today, including all consumer-targeted systems, include a TCP/IP implementation.

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.

[edit] See also

[edit] References

  1. ^ RFC 1122, Requirements for Internet Hosts -- Communication Layers, R. Braden (ed.), October 1989
  2. ^ RFC 1123, Requirements for Internet Hosts -- Application and Support, R. Braden (ed.), October 1989
  3. ^ D. Weitzmann (April 1990). [http:www.isi.edu/in-notes/rfc1149.txt "A Standard for the Transmission of IP Datagrams on Avian Carriers"]. Internet Engineering Task Force. http:www.isi.edu/in-notes/rfc1149.txt. Retrieved on 2007-11-20. 
  4. ^ Bergen Linux User Group (April 2001). "The informal report from the RFC 1149 event". http://www.blug.linux.no/rfc1149/writeup.html. 
  5. ^ F. Baker (June 1995). "Requirements for IP Routers". http://www.isi.edu/in-notes/rfc1812.txt. 
  6. ^ V.Cerf et al (December 1974). "Specification of Internet Transmission Control Protocol". http://www.ietf.org/rfc/rfc0675.txt. 
  7. ^ Internet History
  8. ^ Ronda Hauben. "From the ARPANET to the Internet". TCP Digest (UUCP). http://www.columbia.edu/~rh120/other/tcpdigest_paper.txt. Retrieved on 2007-07-05. 
  9. ^ James F. Kurose, Keith W. Ross, Computer Networking: A Top-Down Approach, 2007, ISBN 0321497708
  10. ^ Behrouz A. Forouzan, Data Communications and Networking
  11. ^ Douglas E. Comer, Internetworking with TCP/IP: Principles, Protocols and Architecture, Pearson Prentice Hall 2005, ISBN 0131876716
  12. ^ Charles M. Kozierok, "The TCP/IP Guide", No Starch Press 2005
  13. ^ William Stallings, Data and Computer Communications, Prentice Hall 2006, ISBN 0132433109
  14. ^ Andrew S. Tanenbaum, Computer Networks, Prentice Hall 2002, ISBN 0130661023
  15. ^ Mark Dye, Mark A. Dye, Wendell, Network Fundamentals: CCNA Exploration Companion Guide, 2007, ISBN 1587132087
  16. ^ a b R. Bush; D. Meyer (December 2002), Some Internet Architectural Guidelines and Philosophy, Internet Engineering Task Force, http://www.isi.edu/in-notes/rfc3439.txt, retrieved on 2007-11-20 
  17. ^ IP Fundamentals: What Everyone Needs to Know About Addressing and Routing, T. Maufer, Computer Networks, Prentice Hall 1999, ISBN 0130661023

[edit] Further reading

[edit] External links

Retrieved from "http://en.wikipedia.org/wiki/Internet_Protocol_Suite"
Personal tools