The 

TCP/IP model is a description framework for computer network protocols created in the

1970s by DARPA, an agency of the United States Department of Defense. It evolved
fromARPANET, which was the world's first wide area network and a predecessor of
the Internet. The TCP/IP Model is sometimes called the Internet Model or the DoD Model.

The TCP/IP model, or Internet Protocol Suite, describes a set of general design guidelines
and implementations of specific networking protocols to enable computers to communicate
over a network. TCP/IP provides end-to-end connectivity specifying how data should be
formatted, addressed, transmitted, routed and received at the destination. Protocols exist for
a variety of different types of communication services between computers.

TCP/IP, sometimes referred to as the Internet model, has four abstraction layers as defined

in RFC 1122. This layer architecture is often compared with the seven-layer OSI Reference
Model; using terms such as Internet reference model, incorrectly, however, because it is
descriptive while the OSI Reference Model was intended to be prescriptive, hence being a
reference model.

The TCP/IP model and related protocols are maintained by the Internet Engineering Task
Force (IETF).

TCP vs UDP
The flow of traffic across the Internet is on the basis of protocols which are TCP
(Transmission Control Protocol) and UDP (User Datagram Protocol).

While TCP is more popular across the Internet, the UDP cannot be rendered completely
redundant. TCP allows error correction but UDP does not. In the case of UDP, there is a
guarantee of the data delivery at the download or addresse point. This is made possible by
‘flow control’ which determines the requirement for resending data. Flow control also checks
and stops the transmission of data unless previous packets have been successfully delivered.
This is based on the process in which the client can request a resending of a particular packet
from the server until the entire packet has been received as in its original form.

UDP is also common but it cannot be relied upon for sending important data like secure files,
important webpages etc. It is used mostly for streaming media including audio and video.
UDP is faster than TCP and media players work best with it. There is no flow control or error
correction but the speed is far greater so despite streaming media not being of high quality, it
can be viewed properly with UDP.

TCP is safer as compared to UDP as the latter serves as an adequate cover for viruses. TCP
also has a complicated frame structure. In case of UDP, the operating system has to do very
little work to translate the data.

UDP is connection less while TCP is connection-oriented which requires the latter protocal to
establish full connection between the receiver and the sender. The connection needs to be
closed after the transfer is complete to free up system resources that were being used by the
protocol. UDP requires no authorization and is okay for free-floating dissemination of data.

What is the difference between UDP and TCP

internet protocols?
by VI VE K G IT E on MAY 15, 2007 · 14 C OMME NT S

Q. Can you explain the difference between UDP and TCP internet protocol (IP) traffic and
its usage with an example?
A. Transmission Control Protocol (TCP) and User Datagram Protocol (UDP)is a
transportation protocol that is one of the core protocols of the Internet protocol suite. Both
TCP and UDP work at transport layer TCP/IP model and both have very different usage.

Difference between TCP and UDP

TCP
Reliability: TCP is connection-oriented
protocol. When a file or message send it
will get delivered unless connections fails.
If connection lost, the server will request
UDP
Reliability: UDP is connectionless
protocol. When you a send a data or
message, you don't know if it'll get there,
it could get lost on the way. There may be
the lost part. There is no corruption while corruption while transferring a message.
transferring a message.
Ordered: If you send two messages along a Ordered: If you send two messages out,
connection, one after the other, you know you don't know what order they'll arrive in
the first message will get there first. You i.e. no ordered
don't have to worry about data arriving in
the wrong order.
Heavyweight: - when the low level parts of Lightweight: No ordering of messages, no
the TCP "stream" arrive in the wrong order, tracking connections, etc. It's just fire and
resend requests have to be sent, and all the forget! This means it's a lot quicker, and
out of sequence parts have to be put back the network card / OS have to do very
together, so requires a bit of work to piece little work to translate the data back from
together. the packets.
Streaming: Data is read as a "stream," with Datagrams: Packets are sent individually
nothing distinguishing where one packet and are guaranteed to be whole if they
ends and another begins. There may be arrive. One packet per one read call.
multiple packets per read call.
Examples: World Wide Web (Apache TCP Examples: Domain Name System (DNS
port 80), e-mail (SMTP TCP port 25 UDP port 53), streaming media
Postfix MTA), File Transfer Protocol (FTP applications such as IPTV or movies,
port 21) and Secure Shell (OpenSSH port Voice over IP (VoIP), Trivial File
22) etc. Transfer Protocol (TFTP) and online
multiplayer games etc