This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| ISO/OSI model | |
|---|---|
| Name | ISO/OSI model |
| Caption | Layered architecture of the ISO/OSI model |
| Developer | International Organization for Standardization |
| Introduced | 1984 |
ISO/OSI model The ISO/OSI model is a conceptual framework for understanding and designing interoperable network systems introduced by the International Organization for Standardization, related institutions such as the International Electrotechnical Commission and influential in organizations like the International Telecommunication Union. It provided a seven-layered taxonomy that informed the work of standards bodies including the Institute of Electrical and Electronics Engineers, European Telecommunications Standards Institute, and corporate stakeholders such as IBM, Xerox, Hewlett-Packard, and Cisco Systems. The model shaped research at universities like Massachusetts Institute of Technology, Stanford University, and University of California, Berkeley and influenced protocols deployed by industry consortia including the Internet Engineering Task Force and the World Wide Web Consortium.
The ISO/OSI model divides network functions into seven abstract layers to promote interoperability among systems produced by AT&T Corporation, Bell Labs, Digital Equipment Corporation, and other vendors. It served as a pedagogical and design tool used in curricula at institutions such as Princeton University and California Institute of Technology, and informed government procurement standards in agencies like the National Institute of Standards and Technology and the European Union. The framework is frequently cited alongside models and projects from DARPA, ARPANET, and research efforts at Bell Labs that preceded the commercialization of packet switching.
The seven layers—from physical to application—are conceptually distinct entities that map to technologies developed by companies and laboratories such as Western Electric, Motorola, Intel Corporation, and Nokia. The Physical layer aligns with hardware specifications produced by IEEE 802 working groups and influenced standards like those from ITU-T and manufacturers including Cisco Systems and Juniper Networks. The Data Link layer interacts with media access controls standardized by IEEE 802.3 and IEEE 802.11, with implementations in products by Broadcom Corporation and Qualcomm. The Network layer encompasses addressing and routing concepts advanced in research at Carnegie Mellon University and protocols later standardized by the IETF and deployed by backbone providers such as AT&T and Verizon Communications. The Transport layer relates to reliable delivery mechanisms explored in projects like X.25 and formalized in protocols used by Microsoft Corporation and Apple Inc.. The Session, Presentation, and Application layers influenced application frameworks and services offered by enterprises such as Oracle Corporation, SAP SE, IBM middleware, and web innovators including CERN and Tim Berners-Lee's World Wide Web team.
Standards work tied to the model was coordinated by bodies like ISO, ITU-T, IETF, and the IEEE. Protocol suites and specifications—ranging from link-layer standards like Ethernet and Token Ring to network-layer designs from X.25 and routing protocols studied at Cisco Systems—were discussed in working groups connected to ANSI and regional bodies such as ETSI. The model influenced documentation practices exemplified in RFC series managed by the IETF and the formal approvals seen in ISO/IEC joint publications. Vendors such as Sun Microsystems, Oracle Corporation, and Microsoft produced application-layer protocols and APIs that mapped to the top layers in vendor interoperability initiatives coordinated at trade associations like IEEE Communications Society.
Adoption varied across administrations, corporations, and academic projects: major telecommunication operators including BT Group, Deutsche Telekom, and Nippon Telegraph and Telephone referenced the model in network planning, while computing firms like IBM, HP, Dell Technologies, and Cisco Systems implemented protocol stacks inspired by its abstractions. Research testbeds at institutions such as MIT, Stanford University, and University of Cambridge validated layered designs, and large-scale deployments by cloud providers such as Amazon Web Services and Google reflected evolved architectures that trace conceptual lineage to the ISO/OSI separation of concerns.
Comparisons frequently involve the DARPA-funded TCP/IP architecture and its documentation in the RFC series produced by the IETF; debates engaged stakeholders including Vint Cerf-affiliated projects, Jon Postel's editorial work, and corporate implementers at Sun Microsystems and Microsoft Corporation. The TCP/IP model’s four-layer simplification was driven by pragmatic deployments in networks like ARPANET and commercial internets managed by carriers such as Sprint Corporation and Verizon Communications, contrasting with the ISO/OSI model’s formal standardization through ISO committees and national standards bodies like BSI and AFNOR.
The model originated from standardization efforts in the 1970s and early 1980s involving ISO, CCITT (now ITU-T), and national delegations from organizations including ANSI and DIN. Key corporate participants included Xerox, IBM, and Digital Equipment Corporation, with technical influences from projects at Bell Labs, BBN Technologies, and academic groups at University College London and Cambridge University. The model was promulgated in international standards and debated at conferences such as IFIP and workshops organized by IEEE and regional agencies like ETSI.
Critics from operational communities including practitioners at IETF and implementers at Cisco Systems argued that the ISO/OSI model was overly prescriptive for operational internetworking, citing the rapid, pragmatic evolution of TCP/IP stacks in environments run by ARPA contractors and companies like Sun Microsystems. Other limitations highlighted by technology historians at institutions such as Harvard University and University of Oxford point to the model’s abstraction gaps when applied to modern virtualized systems managed by VMware, Microsoft Azure, and Amazon Web Services, and its limited direct mapping to emerging paradigms advanced by consortia like Open Networking Foundation and standards efforts at 3GPP.
Category:Network architecture