TCP/IP is a large collection of different communication protocols based upon the two original protocols TCP and IP:
- TCP (Transmission Control Protocol) communication between applications
- UDP (User Datagram Protocol) simple communication between applications
- IP (Internet Protocol) communication between computers
- ICMP (Internet Control Message Protocol) for errors and statistics
- DHCP (Dynamic Host Configuration Protocol) for dynamic addressing
- HTTP (Hyper Text Transfer Protocol) web browser to server
- SNMP (Simple Network Management Protocol) administration of networks
- NTP (Network Time Protocol) synchronize the time between computers
- SMTP (Simple Mail Transfer Protocol) transmission of e-mails
- IMAP (Internet Message Access Protocol) storing and retrieving e-mails
- POP (Post Office Protocol) downloading e-mails
TCP Uses a Fixed Connection and IP is Connection-Less. When an IP packet is sent from a computer, it arrives at an IP router. The IP router is responsible for “routing” the packet to the correct destination, directly or via another router.
TCP/IP is TCP and IP working together. TCP takes care of the communication between your application software (i.e. your browser) and your network software. IP takes care of the communication with other computers. TCP is responsible for breaking data down into IP packets before they are sent, and for assembling the packets when they arrive. IP is responsible for sending the packets to the correct destination.
Each computer must have a unique 4 byte IP address. A domain name corresponds to an IP address and makes it easier to remember. It is translated by a DNS to an IP address.
A browser uses TCP/IP to access a server. A server uses TCP/IP to send HTML back to a browser. An e-mail program uses TCP/IP to connect to the Internet before sending and receiving e-mails using POP, SMTP and IMAP.
IP is at layer 3 in the OSI stack:
| 7.Application |
|
| 6.Presentation |
|
| 5.Session |
|
| 4.Transport |
TCP, UDP |
| 3.Network |
IP |
| 2.Datalink |
Ethernet |
| 1.Physical |
|
There are two sets of rules for subnetting TCP/IP networks. The original set of rules can be found in RFC 950, and the new set of rules can be found in RFC 1812.
A good analogy for IP addressing and packet forwarding (routing) is the snail mail analogy. Consider an IP packet to be an envelope containing data, and having an address on the front. Every TCP/IP-enabled network interface can be compared to a mailbox. Every mailbox (interface) has an IP address. The four bytes of an IP address can be compared to the state, city, street, and house number fields on the front of a snail mail envelope. A router in this analogy is a post office, that sorts and forwards mail based on the address on the envelope (packet header.) If the address is on the same street (based on the subnet mask,) the envelope (packet) is sent directly to the destination mailbox (interface) via local courier (Ethernet?). If the address is determined to be on another street, or in another city or state, the envelope (packet) is delivered via local courier (Ethernet?) to the street’s post office (router), where the postal workers (routing software) sort and forward mail based on established post office sorting procedures (routing tables.)
References:
http://www.w3schools.com/tcpip/tcpip_intro.asp
http://www.ipprimer.com/section.cfm
http://encyclopedia2.thefreedictionary.com/OSI+model
http://www.faqs.org/rfcs/rfc1812.html