A data-link layer unit that encapsulates one or more network-layer packets with link-specific headers and trailers (for example: link-layer addresses, length/type fields, and a frame check sequence) to define transmission boundaries, medium access control, and basic error detection for a single physical link.

Principle

Framing and link-local addressing allow each link’s devices to resolve delivery, medium access and error detection independently of network-layer routing and end-to-end semantics.

Demonstration

Illustrative scenario — Situation: A host sends an IP packet over an Ethernet segment. Recognition: The network interface card wraps the IP packet in an Ethernet frame, adding source/destination MAC addresses and an FCS trailer. Action: The frame is transmitted on the physical medium; switches forward or filter frames based on MAC addresses and check the FCS to detect transmission errors for that link. Consequence: The packet crosses the link with link-level delivery guarantees (best-effort with frame-level error detection); on the next hop the packet may be decapsulated and placed into a new frame appropriate to that link.

Misapplication

Assuming a frame persists unchanged across different link types or that frame headers convey end-to-end routing information. The error is taking link-local fields (MAC addresses, FCS) as global identifiers; frame boundaries and contents are generally recreated at each hop or when link technologies change.

Consequence

Correctly understood, frames provide per-link error detection, medium access control and addressing that optimize local delivery. Misuse—treating frames as end-to-end identifiers—can cause debugging mistakes, misconfigured forwarding rules, or failed interoperability across heterogeneous links.

Reversal

On point-to-point links, virtual circuits, or when tunneling/encapsulation is used, the local frame structure may be suppressed, converted, or encapsulated so that link-local framing is not the operative unit of end-to-end delivery.

Boundary

Clearly within: an IEEE 802.3 (Ethernet) frame with MAC addresses and FCS. Boundary case: PPP framing over a serial link where framing semantics differ but still delimit link transfers. Clearly outside: an application-level message or an IP packet that is not tied to a single physical link.

Semantic Tension

Local optimization versus end-to-end transparency: link-layer framing optimizes medium-specific performance and error control but introduces metadata and behaviors invisible to higher layers, complicating end-to-end reasoning.

Synthesis

A frame is the link-specific container that adapts network-layer payloads to a given medium: it defines the transmission unit, local addressing and error checks for a single hop, and is typically transient—recreated or transformed at each link boundary.