Originally posted by: spidey07
Originally posted by: Pepsi90919
a protocol is a mutual way of communicating. tcp/ip is a suite of protocols on layer 3 and 4.
A little more than a mutual way of communicating. Each protocol has its own layer - a set of rules that must be followed...a "protocol" if you will.
Etherent is a protocol. ATM is a protocol. SONET is a protocol. POS is a protocol. At the end of the day it does mean "mutual way of communicating", but there are many other layers than that.
Generally when saying "TCP/IP" you are referring to the entire protocol suite witch encompasses the application layer as well - the HTTP, the SMTP, the TFTP, the ICMP, the H.323, the Oracle, the SMB, the BGP, the OSPF, the PIM and on and on. All of this can be found in the RFCs or a protocol map.
Although from a strict standpoind TCP and IP operate at layers 4 and 3 respectively the nomenclature of "TCP/IP" is used to include all that is the Internet Protocol. A predefined set of rules of operation and predefined layers and bit boundaries. It is this layered approach that makes TCP/IP so extensible regardless of the underlying layer1/2 procotols such as PPP, Frame-Relay, ATM, POS, Sonet, HDLC, Token Ring, FDDI, 1000 Base-T, etc.
But careful, sometimes people don't obey the rules *cough* microsoft *cough* and prefer to do things their way.