Standards and Concepts

👉 Think of TCP/IP like a delivery system (Amazon / Swiggy style 🚚) that decides:

• How data is created
• How it is packed
• How it travels
• How it is delivered correctly

Without TCP/IP → Internet cannot work at all ❌

1. Your phone creates a request
2. Data is broken into small packets
3. Packets travel through routers on the internet
4. Google’s server receives and understands the request
5. Google sends the response back (page loads)

👉 All of this works because of the TCP/IP model ✅

Layer No.	Layer Name	What It Does
4️⃣	Application	What the user uses
3️⃣	Transport	How data is delivered
2️⃣	Internet	IP address & routing
1️⃣	Network Access	Physical sending of data

Closest layer to the user. Allows apps and software to use the network.

Common Protocols:

• HTTP / HTTPS → Websites
• FTP → File transfer
• SMTP → Sending emails
• DNS → Name → IP conversion

🧠 Example:
Typing https://youtube.com
👉 Application layer understands: “User wants a website”

• TCP → Reliable, safe, slower
• UDP → Fast, no guarantee

🎥 Watching YouTube → UDP (speed matters)
🏦 Online banking → TCP (accuracy matters)

---

Exam Trick:
TCP = Reliable
UDP = Fast

Handles IP addresses and routing.

Main Protocol: IP

Example:

• Your IP → 192.168.1.10
• Google IP → 142.250.182.14

👉 Internet layer decides the best path 🌍

Responsible for physical data transmission.

Examples:

• Ethernet cable
• Wi-Fi
• Network Interface Card (NIC)

Data becomes:
⚡ Electrical signals (cable)
📡 Radio waves (Wi-Fi)

📤 Sending Device
Application → Transport → Internet → Network Access

📥 Receiving Device
Network Access → Internet → Transport → Application

📌 Same layers, reverse direction

🧠 One-Line Memory Trick (Exam GOLD 🥇)

“Application creates data, Transport delivers it, Internet routes it, Network sends it.”

📌 It is not a real protocol
📌 It is a learning + troubleshooting model

💡 Think like this:

TCP/IP → How the internet actually works
OSI → How humans understand and fix network problems

You must answer questions like:

• ❓ Is the cable faulty?
• ❓ Is IP missing?
• ❓ Is the application down?

👉 The OSI model helps you find EXACTLY where the problem is.

Layer No.	Layer Name	Easy Meaning
7️⃣	Application	What the user uses
6️⃣	Presentation	Format & security
5️⃣	Session	Connection control
4️⃣	Transport	Reliable delivery
3️⃣	Network	IP & routing
2️⃣	Data Link	MAC & switching
1️⃣	Physical	Cables & signals

👉 All People Seem To Need Data Processing

• Application
• Presentation
• Session
• Transport
• Network
• Data Link
• Physical

📌 This trick is VERY popular in exams and interviews.

Direct interaction with user applications.

Examples:

• Web browser (Chrome)
• Email client (Gmail, Outlook)

Protocols:

• HTTP / HTTPS
• FTP
• SMTP
• DNS

🧠 Problem Example:
❌ Website not opening
✔ First check Application layer

Handles:

• Data formatting
• Encryption & decryption
• Compression

🧠 Examples:

• HTTPS encryption 🔐
• JPEG, PNG images
• MP4 videos

📌 Data unreadable → Presentation layer issue

Manages:

• Session start
• Session maintenance
• Session termination

🧠 Examples:

• Staying logged into a website
• Session timeout after inactivity

📌 Connection drops repeatedly → Session layer problem

Handles:

• End-to-end delivery
• Error correction
• Flow control

Protocols:

• TCP → Reliable, safe
• UDP → Fast, no guarantee

🧠 Examples:

• File download → TCP
• Video streaming → UDP

📌 CCST Tip:
TCP = Reliable
UDP = Fast

Handles:

• IP addressing
• Routing between networks

Protocol: IP (IPv4 / IPv6)

🧠 Examples:

• No IP address
• Router not working

👉 Network layer problem

Handles:

• MAC addressing
• Switching
• Error detection (frames)

Devices:

• Switch
• Network Interface Card (NIC)

🧠 Examples:

• Switch port disabled
• MAC address issue

👉 Data Link layer problem

Handles physical transmission using:

• Electrical signals
• Optical signals
• Radio waves

Examples:

• Ethernet cable
• Fiber cable
• Wi-Fi signals

🧠 Examples:

• Cable unplugged ❌
• No Wi-Fi signal ❌

👉 Physical layer issue

Support engineers usually check Bottom → Top:

1️⃣ Check cable
2️⃣ Check switch
3️⃣ Check IP
4️⃣ Check service

📌 This saves TIME and avoids confusion.

🎯 Final One-Line Summary (Remember This 💡)

OSI Model helps you understand WHERE the network problem is, layer by layer.

⭐ CCST GOLD LINE (VERY IMPORTANT)

Packets are used by routers (IP)
Frames are used by switches (MAC)

👉 This one line alone answers many CCST exam questions.

📌 Packets are used when data needs to:

• Travel between different networks
• Be routed using IP addresses

• ✅ Source IP address
• ✅ Destination IP address
• ✅ Actual data (payload)

You send a message from:
Your laptop → Google server

Packets created:

• From IP: 192.168.1.10
• To IP: 142.250.182.14

👉 Routers read packets, not frames
Because routers work with IP addresses.

📌 Frames are used for:

• Communication inside the same network (LAN)
• Delivery from one device to the next

• ✅ Source MAC address
• ✅ Destination MAC address
• ✅ The packet inside it

👉 Yes 😄 A packet is wrapped inside a frame

Inside your home:

• Laptop → Wi-Fi Router
• Router → Switch

Frames use MAC addresses like:
00:1A:2B:3C:4D:5E

👉 Switches read frames, not packets

Feature	Packet	Frame
OSI Layer	Layer 3 (Network)	Layer 2 (Data Link)
Address Type	IP Address	MAC Address
Used by	Routers	Switches
Scope	Between networks	Within same network
Contains	Data	Packet + MAC info

1️⃣ Application creates data
2️⃣ Transport layer breaks data
3️⃣ Network layer creates packet (IP)
4️⃣ Data Link layer wraps packet into frame (MAC)
5️⃣ Physical layer sends bits (0s & 1s)

👉 This process is called encapsulation

🖥️ End Device (PC / Phone)
• Creates packet
• Wraps it inside a frame

🔀 Switch
• Looks only at MAC address
• Forwards frame
• ❌ Does NOT care about IP

🌐 Router
• Removes old frame
• Reads packet (IP)
• Decides next path
• Creates new frame for next network

📌 Frame changes at every hop
📌 Packet usually stays the same

❌ Problem: Internet not working

Symptom	Likely Issue
Switch light OFF	Frame / Layer 2 issue
No IP address	Packet / Layer 3 issue
Can ping IP but website not loading	Application layer issue

👉 OSI + Packet/Frame knowledge = fast troubleshooting 🚀

🧠 Memory Trick (Easy Recall)

Frame = Local delivery (MAC)
Packet = Global delivery (IP)

⭐ CCST GOLD LINE (Remember This!)

IP = Who (device)
MAC = Which hardware
Port = Which application

👉 If you remember this one line, half of addressing questions are solved ✅

❌ House address
❌ Flat number
❌ Person name

• IP finds the device
• MAC finds the hardware on local network
• Port finds the application

🧠 Think of IP as a home address 🏠

IPv4: 192.168.1.10
IPv6: 2001:db8::1

• Private IP → Inside LAN (home / office)
• Public IP → On the internet

Your laptop IP → 192.168.1.10
Google server IP → 142.250.182.14

👉 Routers use IP addresses to route packets 🌐

🧠 Think of MAC as a fingerprint 🆔

00:1A:2B:3C:4D:5E

• Fixed to NIC (Network Interface Card)
• Works inside the local network (LAN)
• Used by switches

Inside your home:
Laptop → Router → Switch

Communication happens using MAC addresses (frames)
👉 Switches read MAC, not IP

🧠 Think of port as a room number in a house 🚪

Service	Port
HTTP	80
HTTPS	443
FTP	21
SSH	22
SMTP	25
DNS	53

You open:
https://google.com

Behind the scenes:
IP → Google server
Port → 443 (HTTPS)

👉 Same server, different apps → different ports

When you open a website:

IP Address → Finds the device (server)
MAC Address → Finds device in local network
Port Number → Finds the correct application

Destination IP → 142.250.182.14
Destination Port → 443
Destination MAC → Router’s MAC (local hop)

Feature	IP Address	MAC Address	Port Number
OSI Layer	Layer 3	Layer 2	Layer 4
Identifies	Device	Hardware	Application
Used by	Routers	Switches	TCP / UDP
Scope	Global	Local (LAN)	Application level
Changes?	Yes (DHCP)	No (mostly)	No

Problem	Likely Cause
No internet, no IP	IP addressing issue
Devices not visible in LAN	MAC / Layer 2 issue
Website opens, email not working	Port issue

🧠 Final Memory Trick (Don’t Forget!)

IP = Where the device is
MAC = Which device it is
Port = Which app it is