A shared contract
Interoperability starts with an agreement.
A standard describes behavior precisely enough that independent systems can connect: message formats, states, timing, addressing, error handling, and the meaning of each field. It does not require every device to use the same hardware or code.
Standards can be published by formal organizations, developed by an industry group, or adopted through widespread practice. Their value is the boundary they make predictable.
Name the layers of the idea
Standard, protocol, implementation
Standard
The documented contract: formats, procedures, constraints, and expected behavior.
Protocol
The communication rules used by participants to exchange messages and change state.
Implementation
The hardware or software that applies those rules on a real network.
Interoperability
The observable result: independent implementations can communicate as intended.
A few landmarks
Different standards answer different questions.
Ethernet · IEEE 802.3
Defines widely used wired local-network behavior, including frame formats and access to the medium.
Wi-Fi · IEEE 802.11
Defines wireless local-network communication, radio access procedures, and frame behavior.
HDLC · ISO/IEC 13239
Describes bit-oriented framing and link control for point-to-point and other data links.
Internet protocols · IETF RFCs
Specify the interoperable rules of the Internet family, including IP, TCP, DNS, and HTTP.
Frame Relay
Provided a simpler virtual-circuit WAN service after X.25, with less recovery work inside the network.
ATM
Used fixed-size cells and virtual circuits to combine traffic classes with predictable handling.
MPLS
Uses labels inside provider networks to select forwarding paths, separate VPN contexts, and engineer traffic treatment.
Packet switching
Shares links among independently addressed data units instead of reserving a permanent circuit for every conversation.
Historical case study
X.25 turned a public network into a packet service.
X.25 was a family of ITU-T recommendations for connecting customer equipment to a public packet-switched network. It was designed for links that could be noisy or unreliable, so the network offered substantial error detection, acknowledgements, and flow control.
The customer side is the ETTD (equipement terminal de traitement de donnees, or DTE). The provider side is the ETCD (equipement de terminaison de circuit de donnees, or DCE). The ETTD requests access and exchanges X.25 packets; the ETCD presents the network interface and provides access to the provider's packet-switched service.
A connection could use a virtual circuit: the network associated packets with a logical connection and forwarded them through an agreed path or state. The packets still shared the provider infrastructure, but the customer experienced a managed conversation rather than an isolated physical circuit.
Read the units on the wire
A LAPB frame carries an X.25 packet.
X.25 is easier to understand when its two nested structures are separated. LAPB, derived from HDLC, frames one hop and supplies link-level sequencing and error detection. Its information field carries the X.25 packet used by the packet layer.
LAPB frame
Flag, address, control, information, and frame check sequence protect the local data-link exchange.
GFI
The General Format Identifier describes packet-header format and related options.
LCGN + LCN
The logical channel group and channel number identify the virtual-circuit context at the interface.
Packet type
The packet-type field distinguishes call setup, data transfer, clearing, flow control, and other procedures.
OSI transport standard
X.224 defines a connection-oriented transport exchange.
X.224, also published as ISO 8073, defines the OSI transport protocol. It provides procedures for opening a transport connection, transferring data, and closing the connection. The protocol exchanges TPDUs (Transport Protocol Data Units), not X.25 packets or LAPB frames.
In the historical stack discussed here, X.224 belongs above the X.25 packet layer. X.25 moves packets through the provider network, while X.224 organizes an end-to-end transport conversation between transport entities.
CR
Connection Request starts a transport connection attempt.
CC
Connection Confirm accepts the transport connection.
DT
Data Transfer carries transport user data.
DR
Disconnect Request begins an orderly release.
Read the history correctly
Old standards explain design tradeoffs.
X.25 added recovery where its links and services needed it. Later technologies often moved more responsibility to endpoints and used faster, simpler forwarding in the network. Comparing them teaches a general lesson: reliability, state, cost, delay, and simplicity can be placed at different boundaries.
When studying any network standard, ask four questions: who publishes it, which boundary it defines, what failures it handles, and which parts are left to an implementation.
Knowledge check
Test your standards model
Answer twelve questions. The answer order changes each time.