EVOPEDIA

← all systems · see it in The System

OSI model (the Basic Reference Model for Open Systems Interconnection, ISO/IEC 7498-1 | ITU-T X.200)

The purpose of this Reference Model of Open Systems Interconnection is to provide a common basis for the coordination of standards development for the purpose of systems interconnection, while allowing existing standards to be placed into perspective within the overall Reference Model. ... The resulting architecture with seven layers, illustrated in Figure 11, obeys the principles in 6.2 a) and b).

Properties published scienceour proposal

Sourced fields, and our own readings.

born at1978 (provisional model, SC16/N34, March 1978)
born precisionmonth
boundaryInside: the abstract architecture (layers, entities, services, service access points, protocols, data units, management and the principles for drawing layers) as written in ISO/IEC 7498 / X.200 and its parts, and as people hold and use it. Outside: the real systems and their internal working ('OSI is concerned only with the interconnection of systems'), the service and protocol standards written to it (which can be implemented; the model 'cannot be implemented'), and the rival models.
nested levelBuilt from seven layers and the elements of layer operation; embedded in ISO's and ITU-T's standards work and in the field's teaching. The highest of three levels of abstraction in the OSI scheme, above service and protocol specifications.
scaletechnological

Measures (24) published science

layers in the reference model7 layers
principles used to choose the layers13 principles (1980 list)
drafting time of the model in SC1618 months
experts contributing to the modelmore than 100 experts
characteristic clock: initial development of the reference model2.5 years
characteristic clock: Draft Proposed Standards from SC16around 2 per year (1983)
the wait: a whole service data unit before passingone complete SDU per connection
revision interval: IS 7498 to the revised joint text1983 to 1 July 1994 dates
US federal OSI procurement mandate in forceAugust 1990 (GOSIP v1 published August 1988); abandoned by NIST in 1994 dates
IETF rough consensus (the rival process)80 to 90 percent agreement
IETF participants protesting the IAB's CLNP proposal, July 1992approximately 700 participants
layers in the ARPANET Reference Model (rival)3 (one mandatory) layers
payload share of a TCP ack carried as IP over ATM40 of 106 bytes (the source: '37% payload (TCP Ack size)')
IP over ATM overhead on a DS3 lineabout 31 percent of 44.736 Mbps
payload share of a full Ethernet frame after TCP/IPv4 headers1460 of 1500 bytes of the Ethernet data field (the IP datagram), not of the frame
OSI connection-mode transport classes5 (TP0-TP4) classes
EvoArch hourglass resemblance H at round 100 (median)almost 95 percent
span over which the protocol hourglass emerged30-40 years
change in quiz score after analogical role-play+8 percentage points (n = 10, single group, eight questions)
DS3 physical-layer toll: PLCP overhead4.032 Mbps of 44.736
DS3 cell-layer toll: per-cell headers3.840 Mbps of 44.736
DS3 adaptation-layer toll: SNAP header and padding5.900 Mbps of 44.736
first revision interval: IS 7498 to Addendum 1 (connectionless)spring 1983 to 15 July 1987 dates
EvoArch layers for the TCP/IP stack6 layers (application protocols at 5, applications at 6)

Open contentions (6) open contention

Where sources or readings disagree. Both stay on the map.

Cross-scale patterns seen here (21) our proposal

Shapes that recur when the same kind of problem is solved at different scales, and how each shows in OSI model (the Basic Reference Model for Open Systems Interconnection, ISO/IEC 7498-1 | ITU-T X.200). Each links to every other system that shows it.

Valence: what it trades, and with whom (9) published science

Each exchange with a neighbour, read from both sides: who gains, who pays, and what carries it.

Partners and parts published science

Built from / builds (10)

Sits inside / holds (3)

expressed by (18)

floor filled by (20)

represents (2)

Kinds (10)

Notes published science

Layers

The ways it takes in its world, where they meet, and how it acts back, each from L1 (where it meets the world) up.

mental representation: the seven-layer model as engineers, teachers and learners hold and use it

  1. L1: Networks as people meet them: invisible, layered processes
  2. L2: Learning the seven layers: lecture, analogy (the postal letter), role-play
  3. L3: A shared vocabulary: protocols of other suites named by OSI layer (TCP and UDP 'layer 4')
  4. L4: Working by layer: troubleshooting, and cross-layer designs that reach across layers
  5. L5: Security architecture by layer
  6. L6: Extensions above the seven: the user (layer 8), money and politics (layers 8-9)
  7. L7: The reference for teaching and documentation, outliving its protocols

the OSI reference model as its users draw it: seven layers from the physical medium to the application (reader's view)

  1. L1: Physical layer: the mechanical, electrical, functional and procedural means for bit transmission over physical media (the media themselves are sometimes called a (0) layer)
  2. L2: Data link layer: data-link connections over physical connections; detects and possibly corrects physical-layer errors
  3. L3: Network layer: routing and relaying across subnetworks in tandem or parallel; may split messages too large for a link
  4. L4: Transport layer: transparent, end-to-end transfer between end systems, optimizing the network service at minimum cost
  5. L5: Session layer: organizing and synchronizing dialogue between presentation entities
  6. L6: Presentation layer: common representation of data, syntax independence for applications
  7. L7: Application layer: application entities, the sole access of application processes (people, programs, machines) to the OSI environment

the boardroom (shared floors)

  1. L5: ISO TC97/SC16 (Open Systems Interconnection) and its working group on architecture, with the CCITT rapporteur's group: where contributions, comments and liaison texts converge
  2. L6: The reference model text: ISO 7498 / X.200 and its parts (security, naming and addressing, management), the definitions every OSI standard must use
  3. L7: The field that holds and uses the model: standards developers, governments, network engineers, teachers and security architects; the shared reference for teaching and documentation

way in: CCITT's work (public data networks, X.25, the rapporteur's group on a layered model)

  1. L1: Public data networks adopting X.25 in the late 1970s
  2. L2: Existing CCITT physical and network-level standards (X.21, V.24, V.35; X.25 level 3)
  3. L3: The CCITT Rapporteur's Group on a layered model for public data network services recognises the model
  4. L4: Collaborative drafting with ISO/IEC to one identical text

way in: Critiques and rival theories of layering

  1. L1: Implementers find strict layering imperfect and break it creatively
  2. L2: Written critiques: 'That violates Layering!' (1982); 'Layering Considered Harmful' (2002)
  3. L3: Named principles about where functions belong: the end-to-end argument
  4. L4: Cross-layer design and its cautions
  5. L5: Rival architectures: recursive layers (RINA) against a fixed five-layer internet model
  6. L6: Formal theories of layering: optimization decomposition; evolutionary models (EvoArch)

way in: Data units arriving at an open system (the flow the model describes)

  1. L1: Bits over physical connections
  2. L2: Frames checked: errors detected and possibly corrected
  3. L3: Network: routed and relayed across subnetworks
  4. L4: Transport: end to end between end systems
  5. L5: Session: dialogue organized and synchronized
  6. L6: Presentation: common representation of data
  7. L7: Application entity: the application process's only access

way in: Existing networks and network architectures (ARPANET, CYCLADES, NPL, EIN; vendors' SNA and DECnet; X.25)

  1. L1: Running packet networks and vendors' installed networks
  2. L2: Each maker's own 'network architecture' of conventions
  3. L3: Published proposals entered as SC16 documents (INWG 96.1 transport as SC16/N24; IFIP virtual terminal as SC16/N23)
  4. L4: Principle e): boundaries where past experience has shown success

way in: Learners and practitioners (classroom, troubleshooting, the 'layer 8' talk)

  1. L1: Networks whose processes are invisible to people
  2. L2: A lecture and a role-play seen and heard by students
  3. L3: The postal-service analogy maps the seven layers to sending a letter
  4. L4: Understanding measured by quiz
  5. L5: Layer numbers used in practitioners' talk and troubleshooting
  6. L6: The model extended in jokes and politics: layer 8 user, layer 9 politics

way in: National member bodies and their experts (contributions, comments, ballots)

  1. L1: More than 100 experts from many countries and international organizations
  2. L2: Written contributions merged into the text
  3. L3: National positions: delegates acting for national firms
  4. L4: Ballots and comment rounds on DP and DIS

way in: New transmission technology and modes (fibre, LANs, datagram and connectionless service, ISDN)

  1. L1: New physical media such as fibre optics
  2. L2: Local area networks on broadcast media
  3. L3: Connectionless (datagram) operation
  4. L4: Outstanding architectural issues listed for further work

way in: Security needs and threats on the communication path

  1. L1: The communications path between end systems
  2. L2: Commercial users' need to transfer data securely
  3. L3: Security services (peer entity authentication, confidentiality, integrity, non-repudiation, traffic flow confidentiality)
  4. L4: Security layering principles decide placement

way in: The rival's running practice: TCP/IP networks, their running code and the market

  1. L1: TCP/IP in widespread use on multi-vendor networks
  2. L2: Running code: multiple interoperable implementations before standardization
  3. L3: A descriptive rival reference model (the ARPANET Reference Model, three layers)
  4. L4: Comparisons: the US National Research Council study of TCP against TP-4 (asked 1983, reported 1985)
  5. L5: Procurement policy met by administrators who kept TCP/IP
  6. L6: The market tips (the World Wide Web)

way out: Coordinating standards: layer service definitions and protocols written to the model

  1. L1: Published documents (ITU-T X-series; ISO/IEC standards)
  2. L4: Layer standards: e.g. the connection-mode transport protocol in five classes, TP0 to TP4 (X.224)
  3. L5: TC97 adopts SC16's recommendations to start protocol projects (end of 1979)
  4. L6: Compliance and consistency statements required of other standards

way out: Designs placed by layer (and cross-layer designs)

  1. L1: Implemented on links and hosts
  2. L4: Protocols placed in a layer; cross-layer schemes reach across
  3. L7: Designers reason by layer

way out: Government profiles and procurement mandates (GOSIP)

  1. L1: Purchases by federal agencies
  2. L5: GOSIP version 1 published August 1988; required from August 1990
  3. L7: Governments endorse OSI

way out: Layer talk: naming problems and devices by layer number

  1. L1: Spoken among people
  2. L4: Troubleshooting placed by layer (a 'layer 8 issue')
  3. L7: Layer numbers as the shared vocabulary

way out: Security placed by layer (X.800 / ISO 7498-2)

  1. L1: Protected traffic on the medium
  2. L3: Encryption at the network layer (IPsec); MACsec at the data link layer (layer 2) is booked beside it
  3. L6: Security services allocated to layers

way out: Teaching the seven layers

  1. L1: Students enact the layers as sender and receiver groups
  2. L3: A lecture and the postal analogy
  3. L7: The model in curricula

way out: The OSI protocol suite on the wires (X.400, X.500, IS-IS lasting)

  1. L1: Signals on the medium
  2. L3: IS-IS routing at the network layer
  3. L7: Application protocols X.400 (messaging) and X.500 (directory)

written record: the reference model as a standard (ISO 7498 / ITU-T X.200 and its parts)

  1. L1: Contributions and working documents from experts and member bodies (SC16 N-documents)
  2. L2: SC16 and its architecture working group draft the model: 18 months, seven layers, transmitted to TC97 in July 1979
  3. L3: Ballots: Draft Proposal (late 1980), Draft International Standard (spring 1982) after two rounds of comments
  4. L4: International Standard ISO 7498 (spring 1983); merged with CCITT's text and published 1984 as ISO 7498 and X.200; revised joint text approved 1 July 1994
  5. L5: The family of parts: basic model, security architecture, naming and addressing, management
  6. L6: Three levels of abstraction and compliance: architecture, then service and protocol specifications that must be consistent with it
  7. L7: Purpose: a common basis for coordinating standards development, and a frame within which teams work independently

Sources (30) published science

ITU-T Recommendation X.200 (07/94) | ISO/IEC 7498-1:1994, Information technology - Open Systems Interconnection - Basic Reference Model: The basic model (ITU, 1994; identical text to ISO/IEC 7498-1; read in full from the ITU's free PDF)
Day J.D., Zimmermann H. (1983) The OSI reference model. Proceedings of the IEEE 71(12):1334-1340. doi:10.1109/PROC.1983.12775 (read in full from an open course copy, OCR text) (behind its links)
Russell A.L. (2006) 'Rough Consensus and Running Code' and the Internet-OSI Standards War. IEEE Annals of the History of Computing 28(3):48-61. doi:10.1109/MAHC.2006.42 (read in full from an open course copy) (behind its links)
Kawadia V., Kumar P.R. (2005) A cautionary perspective on cross-layer design. IEEE Wireless Communications 12(1):3-11. doi:10.1109/MWC.2005.1404568 (behind its links)
Akhshabi, S. & Dovrolis, C. The Evolution of Layered Protocol Stacks Leads to an Hourglass-Shaped Architecture (extended version of the ACM SIGCOMM 2011 paper; read via fetch summary) (behind its links)
OSI model (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
ITU-T Recommendation X.800 (03/91) Security architecture for Open Systems Interconnection for CCITT applications (technically aligned with ISO 7498-2; sections 1, 5.2 and 6.1 read) (behind its links)
Zimmermann H. (1980) OSI Reference Model - The ISO Model of Architecture for Open Systems Interconnection. IEEE Transactions on Communications 28(4):425-432. doi:10.1109/TCOM.1980.1094702 (read in full from an open course copy, OCR text) (behind its links)
Padlipsky M.A. (1982) A Perspective on the ARPANET Reference Model. RFC 871 (sections: the layering axiom and the comparison with the ISO model) (behind its links)
RFC 3439, Some Internet Architectural Guidelines and Philosophy (2002) (behind its links)
Akhshabi S., Sarda S., Dovrolis C., Yi S. (2014) An explanatory evo-devo model for the developmental hourglass. F1000Research 3:156. doi:10.12688/f1000research.4583.2 (sections: abstract, the results comparing the transcriptome age index with the model, discussion, methods data sources) (behind its links)
Oyebisi D. (2026) Analogical role-play for teaching the OSI model in undergraduate computing education. Discover Education. doi:10.1007/s44217-026-02154-w (behind its links)
ISO 7498:1984/Addendum 1:1987, Connectionless-mode transmission (sections: front matter and introduction 0.1, from the publisher's free preview) (behind its links)
OSI protocols (Wikipedia, via Wikimedia Enterprise; abstract) (behind its links)
Layer 8 (Wikipedia, via Wikimedia Enterprise; the article carries a primary-sources tag) (behind its links)
RFC 1122, Requirements for Internet Hosts: Communication Layers (1989) (behind its links)
Saltzer J.H., Reed D.P., Clark D.D. (1984) End-to-end arguments in system design. ACM Transactions on Computer Systems 2(4):277-288. doi:10.1145/357401.357402 (behind its links)
Vrijders S. et al. incl. Day J. (2020) ARCFIRE: Experimentation with the Recursive InterNetwork Architecture. Computers 9(3):59. doi:10.3390/computers9030059 (sections: introduction and design comparison table) (behind its links)
Chiang M., Low S.H., Calderbank A.R., Doyle J.C. (2007) Layering as Optimization Decomposition: A Mathematical Theory of Network Architectures. Proceedings of the IEEE 95(1):255-312. doi:10.1109/JPROC.2006.887322 (behind its links)
Srivastava V., Motani M. (2005) Cross-layer design: a survey and the road ahead. IEEE Communications Magazine 43(12):112-119. doi:10.1109/MCOM.2005.1561928 (behind its links)
ITU-T Recommendation X.290 (04/95) OSI conformance testing methodology and framework: General concepts (sections: summary and introduction) (behind its links)
ITU-T Recommendation X.210 (11/93) | ISO/IEC 10731, OSI Basic Reference Model: Conventions for the definition of OSI services (sections: definitions of primitives, 6.3) (behind its links)
Honda M. et al. (2011) Is it still possible to extend TCP? ACM Internet Measurement Conference 2011. doi:10.1145/2068816.2068834 (behind its links)
Doyle, J. & Csete, M. 2011, Architecture, constraints, and behavior, PNAS (in-press author copy; read via fetch summary) (behind its links)
Protocol Wars (Wikipedia, rev 1380571779, 2026-10-16, via Wikimedia Enterprise; read by section) (behind its links)
Cooper D. et al. (2008) Internet X.509 Public Key Infrastructure Certificate and CRL Profile. RFC 5280 (sections: abstract, 4.1) (behind its links)
Wireshark Wiki: ATN (Aeronautical Telecommunication Networks) (a technical wiki page, not research literature; read in full) (behind its links)
Dijkstra E.W. (1968) The structure of the 'THE'-multiprogramming system. Communications of the ACM 11(5):341-346. doi:10.1145/363095.363143 (sections: abstract and System Hierarchy) (behind its links)
ITU-T Recommendation I.320 (11/93) ISDN protocol reference model (sections: 2.1 relationship with the X.200-series) (behind its links)
ITU-T Recommendation X.901 (08/97) | ISO/IEC 10746-1, Open Distributed Processing - Reference Model: Overview (sections: summary and source) (behind its links)