• ↑↓ pour naviguer
  • pour ouvrir
  • pour sélectionner
  • ⌘ ⌥ ↵ pour ouvrir dans un panneau
  • ←→ pour naviguer
  • esc pour rejeter
⌘ '
raccourcis clavier

The Problem

How do routers handle a packet that arrives faster than it can be sent out?

Formal Definition

Per Wikipedia: “Store-and-forward buffers the entire packet before forwarding, enabling error check and rate adaptation.”

Explanation

Like post office — clerk receives whole letter, checks address, then hands to next carrier, not letter-by-letter.

How It Works

  1. Packet arrives at input port
  2. Stored in buffer
  3. Checked for errors
  4. Routing table consulted
  5. Forwarded to output port

Visual Explanation

store_and_forward A Ingress B Buffer A->B step 1 C Egress B->C step 2

Semantic Network

semantic_store_and_forward THIS Store-and-Forward REL1 Related THIS--REL1 related REL2 Prereq THIS--REL2 builds from

Key Properties

  • Enables error detection
  • Needs memory for queue
  • Adds store delay
  • Contrasts with cut-through

Real-World Example

packet -> buffer -> lookup -> forward

Connections

Edge Cases & Gotchas

  • Buffer bloat — too much buffering adds latency
  • Assuming zero copy — actually copied