Question regarding TCP/IP

[Sunner]

Why are IP and TCP so often lumped together as if they were somehow mutually inclusive?
Take for example the "Local Area Connection" properties dialogue under WinNT.
"Internet Protocol (TCP/IP)".

WTF is up with that? Why not just call it "Internet Protocol", I don't see anything TCP specific in there, I guess maybe WINS uses TCP(I have no idea really), DNS can use TCP or UDP, and so forth.

Might as well call it "Internet Protocol (TCP/ICMP/UDP/ESP/Yadayadayada/IP)".

Oh well, you get my point I'm sure
So, again, why is TCP so special?

 

[spidey07]

well they are kinda lumped together to call the entire family tcp/ip.

TCP really is at the heart of internet communications and very important to why its so successful.

 

[Sunner]

Originally posted by: spidey07
well they are kinda lumped together to call the entire family tcp/ip.

TCP really is at the heart of internet communications and very important to why its so successful.

Yeah, figured it was something like that, just wanted to know if there was actually some kind of "real" reason why.
Basically just something that's bugged me(yes, I do get bugged by the little things) ever since I learned the difference between TCP, UDP, etc

 

[Apathetic]

Here's a link to the OSI model for networking. Basically, IP is a "layer 3" (network) protocal and TCP is a "layer 4" (transport) protocol. Each layer has different responsibilities.

Here's a Wikipedia link for more information.

Dave

 

[spidey07]

tcp/ip actually came from the department of defense model, not the OSI.



that's mainly what you don't see session and presentation layers in the core of the TCP/IP suite.

 

[JackMDS]

As with all other communications protocol, TCP/IP is composed of layers:

IP - is responsible for moving packet of data from node to node. IP forwards each packet based on a four byte destination address (the IP number). The Internet authorities assign ranges of numbers to different organizations. The organizations assign groups of their numbers to departments. IP operates on gateway machines that move data from department to organization to region and then around the world.
TCP - is responsible for verifying the correct delivery of data from client to server. Data can be lost in the intermediate network. TCP adds support to detect errors or lost data and to trigger retransmission until the data is correctly and completely received.
Sockets - is a name given to the package of subroutines that provide access to TCP/IP on most systems.

The above is Quote from: Text<a target=_blank class=ftalternatingbarlinklarge href="http://pclt.cis.yale.edu/pclt/COMM/TCPIP.HTM">http://pclt.cis.yale.edu/pclt/COMM/TCPIP.HTM</a>

:sun:

 

[WiseOldDude]

TCP/IP defines a suite of protocols. If you say TCP or IP you are refering to a specific protocol, not the suite which includes, UDP, FTP, Telnet, SMNP,SNMP, HTTP, ARP, RARP, and others

 

[Sunner]

Originally posted by: Apathetic
Here's a link to the OSI model for networking. Basically, IP is a "layer 3" (network) protocal and TCP is a "layer 4" (transport) protocol. Each layer has different responsibilities.

Here's a Wikipedia link for more information.

Dave

Yeah I know, that's pretty much why I've wondered why they were lumped together.