Summary of "Lec-27: Framing in Data Link Layer | Bit Stuffing vs Byte(Character) Stuffing"

Main Ideas / Concepts (Data Link Layer Framing)

Purpose of Framing in the Data Link Layer

• The data link layer must pack incoming bits into frames.
• To distinguish one frame from another, it uses a framing mechanism (typically delimiters).
• Terminology:
  • Network layer → packet
  • Data link layer → frame

Delimiter-Based Separation

• Framing uses start/end markers (“flags”) so the receiver can identify the boundaries of each frame.

---

Character-Oriented Framing (Character/Byte Stuffing)

Core Idea

• Use a flag delimiter at the start and end of the frame.
• The receiver takes everything between two flags as the data payload.
• Any flag-like value appearing inside the payload must be handled so the receiver doesn’t mistake it for a boundary.

Rule / Mechanism

• If the payload contains the flag character, the sender must escape it using an Escape character.
• Conceptual example:
  • Payload may look like: A flag C
  • Sender sends: Flag A ESC flag C Flag
    • Here, ESC indicates: “the next flag is part of data, not a delimiter.”

Receiver Behavior (Shared Rules)

• If the receiver encounters flag and then reaches the next flag:
  • If an ESC occurs before a flag, the receiver treats that flag as data (ignores it as a delimiter).
  • Without escaping, the receiver would interpret it incorrectly as a frame boundary.

Why Stuffing Is Needed

• Stuffing adds extra bytes/characters (e.g., extra ESC) so the receiver can correctly distinguish:
  • delimiter flags vs.
  • flag values that are actually part of the data

---

Bit-Oriented Framing (Bit Stuffing)

Core Idea

• Instead of stuffing entire characters/bytes, the sender stuffs bits based on a pattern associated with the start frame delimiter.
• Common rule described:
  • If the delimiter involves 0 followed by five 1s (i.e., 011111) at frame boundaries,
  • then the receiver must not confuse payload bits with delimiter bits.

Rule / Mechanism

• If the payload contains a sequence of five continuous 1s in a context where a delimiter-like pattern could be mistaken (specifically described as after 0):
  • Sender inserts a 0 after every occurrence of five consecutive 1s.
• This prevents the receiver from interpreting part of the payload as the sixth 1 that would complete the delimiter pattern.

Receiver Logic (Shared Rule)

• The receiver expects that:
  • If it sees 0 + five 1s + a sixth 1, that pattern indicates the delimiter region (header/boundary), not data.
• Stuffing ensures that pattern does not appear as-is inside the data.

---

Distinction: Character Stuffing vs Bit Stuffing

• Character-oriented (byte/character stuffing)
  • Stuff Escape + Flag when the payload contains the flag delimiter character.
• Bit-oriented (bit stuffing)
  • Stuff an extra 0 bit to break up delimiter-like sequences inside the payload bitstream.

---

Speaker / Sources

• Speaker: The video narrator/instructor (referred to as “I” / “Dear students…”) from the channel Gate Smashers.
• No other specific person or external source is identified in the subtitles.

Category

Educational

---

Share this summary

Share on X/Twitter Share on Facebook Share on LinkedIn Share on Reddit Share on WhatsApp Share on Telegram

---

Is the summary off?

If you think the summary is inaccurate, you can reprocess it with the latest model.

Reprocess summary

Video