IT Employment

General discussion


TCP and IP

By isaaclau ·
TCP works on Transport Layer
Ip works on Network Layer

Transport Layer provide reliable connection-oriented connection between host.

However....Network Layer provide "Best effort" delievery. Connectionless(packet -switched) ,

Why there are no conflict between these system....
so which connection will take over...TCp or IP???

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Think of it this way.

by LordInfidel In reply to TCP and IP

Look at how your mail get's delivered.

When it's at the Post office (application layer) it is sorted and prepared for transport (presentation layer)

It is then given to the mail carrier and is put on the truck (transport layer ie tcp). Depending on the type of package he/she is delivering will depend on when it will be delivered on if it will require a signature.

The mail carrier then drives around and looks at each piece of mail and reads the address (Network Layer ie IP). This is where the piece of mail will be delivered.

Now here is where your confusion comes in. The Transport layer is not just TCP. It is also UDP or ICMP. TCP will basically be like a package that needs to be signed for, UDP will be a normal piece of mail, ICMP is kind of like bulk mail (kind of in the gray area).

These layers work together and correspond to the same layer on the other side of the connection.

Packets go up the chain and back down again. But while they are doing that, they talk to their counterpart on the other side of the connection.

Collapse -

A book that you really need is

by LordInfidel In reply to TCP and IP

The Protocols (TCP/IP Illustrated, Volume 1)&vol 2**82306

The connectionless connection is UDP. That is the best effort. Think of the transport layer not as TCP but as the delivery method (tcp,udp,icmp)

IP is protocols and addressing; http, ssl, ftp, dns, telnet, ssh, etc.

Collapse -

IP is on the application layer???

by VNCoder In reply to A book that you really ne ...

G'day LordInfidel,
Are you sure IP deals with specific application protocol???
Thinking in term of the OSI Reference Model for ease of understanding, IP is BELOW the Application layer. So IP DOES NOT deal with http, ssl, ftp, telnet, etc.

TCP/IP is a name given to the collection (or suite) of networking protocols that have been used to construct the global Internet. The protocols are also referred to as the DoD (dee-oh-dee) or Arpanet protocol suite because their early development was funded by the Advanced Research Projects Agency (ARPA) of the US Department of Defense (DoD).

The TCP/IP name is taken from two of the fundamental protocols in the collection, IP and TCP. Other core protocols in the suite are UDP and ICMP. These protocols work together to provide a basic networking framework that is used by many different application protocols, each tuned to achieving a particular goal.

Internet Protocol (IP) is the central, unifying protocol in the TCP/IP suite. It provides the basic delivery mechanism for packets of data sent between all systems on an internet, regardless of whether the systems are in the same room or on opposite sides of the world. All other protocols in the TCP/IP suite depend on IP tocarry out the fundamental function of moving packets across the internet.

You will need a whole chapter or even a book or two to cover TCP/IP.

Collapse -

Your right.... Had a brain fart

by LordInfidel In reply to IP is on the application ...

In my quest for explaining it, I f***d up.

Thanx for correcting me......

What I *Really* should of said was....

IP is a connectionless protocol. It does not attempt to gurantee delivery. It's job is to determine the souce/destination IP, *Protocol that is use, Checksum and the TTL.

I starred *protocol because this is where I had the brainFart. IP will look at the port/protocol and make the determination of where to send it to at the Transport Layer, be it TCP or UDP.

It is then the transport layers responsiblity for delivery confirmation or in the case of UDP lack of it.

Now at the router it is a little different. The router will not care about the protocol that is being used.

BUT---Big But--- *some Routers can look at the ToS and protocol fields to do basic filtering.

<You will need a whole chapter or even a book or two to cover TCP/IP>

Which is why I reccomended the tcp/ip illustrated.

If you are out of the basic level, then I strongly reccommend TCP/IP Network Administration from O'reilly. I beleive it is up to version 3.

Thanx again for correcting me.

Related Discussions

Related Forums