Understanding the TCP/IP Protocol Stack
Understanding the TCP/IP Protocol Stack
TCP/IP was developed and demonstrated for the first time in1972by theDepartment of
Defenseof theUnited Statesrunning it onARPANET, a wide area network of
said department.
TheOSI model, on the other hand, was proposed as a theoretical approach and also as
a first phase in the evolution of thecomputer networks. Therefore, theOSI model
it is easier to understand, but the TCP/IP model is the one that is actually used. It is helpful
understand theOSI modelbefore knowing TCP/IP, since the same principles apply,
but they are easier to understand in theOSI model.
History of the TCP/IP Protocol
The Internet Protocol Suite was the result of the work carried out by the
Defense Advanced Research Projects Agency (DARPA for short)
English) toearly 70sAfter the construction of the pioneerARPANETin1969
DARPA began working on a large number of data transmission technologies. In
1972Robert E. Kahnhe was hired by the Office of Processing Techniques
DARPA information, where he worked in communicationpackagesforsatelliteand for
radio waves, acknowledged the important value of communication in these two ways. In the
spring of 1973,Vint Cerfdeveloper of the ARPANET protocol, Network Control
Program(NPC) joined Kahn with the aim of creating an open architecture of
interconnection and thus design the new generation of ARPANET protocols.
For the summer of1973, Kahn and Cerf had achieved a fundamental remodeling,
where the differences between network protocols were hidden using aProtocol of
communicationsand moreover, the network ceased to be responsible for the reliability of the
communication, as it happened in ARPANET, was thehostthe responsible. Cerf acknowledged the
merit ofHubert ZimmermanyLouis Pouzincreators of thered CYCLADESbecause of his/her
the work was greatly influenced by the design of this network.
With the role that networks played in the communication process reduced to a minimum, it
it became a real possibility to communicate different networks, regardless of the characteristics
that they had. There is a popular saying about the TCP/IP protocol, which was the product
final developed by Cerf and Kahn, which states that this protocol will end up working
even between 'two cans connected by a string'. In fact, there is even an implementation
usingmessenger pigeons, IP about messenger pigeons, which is documented inRFC
1149. .
A computer called a router (a name that was later changed to gateway, door
of link, to avoid confusion with other types ofGateway) is equipped with a
interface for each network, and sendsDatagramsround trip between them. The requirements for
these routers are defined in theRFC 1812.
This idea was implemented in a more detailed way by the research group.
what Cerf had inStanfordduring the period from 1973 to 1974, resulting in the
first TCP specification (Request for Comments 675,Then DARPA was
hired byBBN Technologies, theStanford University, and theUniversity College of
Londonto develop operational versions of the protocol on different platforms of
hardware. Four different versions were developed: TCP v1, TCP v2, a third
divided into two TCP v3 and IP v3 in the spring of 1978, and then the version was stabilized
TCP/IP v4 - the standard protocol that is still used on the Internet.
In1975the first communication test between two networks with protocols was carried out
TCP/IP between Stanford University and University CollegeLondon(UCL). In
1977Another communication test was conducted using a TCP/IP protocol between three networks.
different locations inUnited States, United KingdomyNorway. Varios prototipos
different TCP/IP protocols were developed in multiple research centers among
the years1978y1983The complete network migrationARPANETto the TCP/IP protocol
officially concluded on the dayJanuary 1of1983when the protocols were activated
permanently.
The TCP/IP suite is designed for routing and has a very high degree of reliability.
it is suitable for large and medium networks, as well as in enterprise networks. It is used for
world level to connect toInternetand web servers. It is compatible with the
standard tools to analyze network performance.
One drawback of TCP/IP is that it is more difficult to configure and maintain than
NetBEUIoIPX/SPX; it is also somewhat slower on networks with a medium traffic volume
lower. However, it can be faster on networks with a large traffic volume where
we need to route a large number of frames.