Protocol Development and the Evolution of Communication Standards

For digital communication to occur, systems must agree on a set of rules known as protocols. These protocols are typically expressed through algorithms and data structures. To ensure that these rules work across different hardware and operating systems, developers use portable programming languages. When specifications are independent of the source, the result is wider interoperability, allowing diverse systems to communicate seamlessly.

The creation of protocol standards usually involves the support of a standards organization. These bodies initiate the standardization process, and members voluntarily agree to adhere to the results. Because these members often control significant market shares, or because governments enforce standards to protect public interest, obtaining official approval is critical for a protocol's success.

[ไม่มีภาพประกอบ]

Key Facts

• Standardization prevents the proliferation of incompatible protocol variants.
• De facto standards are protocols that dominate a market without formal standardization.
• The OSI Model provides a seven-layer framework to define network responsibilities.
• IETF manages Internet protocols using a "rough consensus and running code" approach.
• Peer entities are corresponding layers on different systems that communicate using specific protocols.

The Critical Need for Protocol Standards

The danger of lacking standards is illustrated by the history of IBM's Binary Synchronous Communications (BSC). Originally a link-level protocol for connecting two nodes, BSC was later used in multinode networks, revealing significant flaws. Without a central standard, various manufacturers created their own incompatible enhancements—sometimes deliberately to lock users into their own ecosystem. This resulted in over 50 different variants of the original bi-sync protocol.

In some instances, protocols achieve market dominance without formal approval; these are called de facto standards. While common in niche or monopolized markets, they can be used to stifle competition. However, there are positive examples, such as the Linux operating system, which remains open and invites competition despite its de facto status.

Global Standards Organizations

Several key organizations manage the development of communication protocols to ensure impartiality and future-proof research:

• ISO (International Organization for Standardization): Develops broad international standards.
• ITU (International Telecommunication Union): Focuses on the public switched telephone network (PSTN) and radio systems.
• IEEE (Institute of Electrical and Electronics Engineers): Controls many electronics industry protocols for consumer and commercial devices.
• IETF (Internet Engineering Task Force): Maintains the protocols that power the Internet.
• W3C (World Wide Web Consortium): Produces standards for Web technologies.
• NMEA: Provides standards specifically for marine electronics.

Coordination between these bodies is essential. Without it, the industry risks incompatible definitions or conflicting interpretations of messages, such as failing to maintain monotone decreasing time-to-live values, which could lead to stable routing loops.

The Standardization Process

Using the ISO as an example, the process begins with a sub-committee workgroup. This group issues working drafts and discussion documents to provoke feedback from interested parties. After a period of debate, modification, and compromise, the proposal evolves from a draft into a draft international standard, and finally, an international standard. These standards are periodically reissued to fix deficiencies and adapt to new technological views.

The OSI Model Framework

Drawing lessons from ARPANET, the predecessor of the Internet, the Open Systems Interconnection (OSI) model was created. This framework prevents overlapping functionality by clearly defining the responsibilities of a protocol at different levels.

In this model, systems are connected by a physical medium. Each layer provides services to the layer above it by utilizing the layer below. Communication between layers happens via a service access point (interface). While protocol standards define how peer entities at the same layer communicate, service standards define the interaction between adjacent layers.

The Seven Layers of the OSI Model

1. Physical Layer: Handles electrical characteristics, transmission techniques, and physical connection maintenance.
2. Data Link Layer: Manages data link connections, detects and corrects physical layer errors, and handles flow control.
3. Network Layer: Responsible for setup, maintenance, and release of network paths, routing, relay functions, and congestion control.
4. Transport Layer: Ensures reliable, transparent, and cost-effective data transfer, supporting the multiplexing of connections.
5. Session Layer: Manages session connections, data exchange, interaction management, and resynchronization.
6. Presentation Layer: Handles syntax negotiation, data transformations, compression, and encryption.
7. Application Layer: Provides services directly to application processes, including partner identification, authentication, and data integrity procedures.

Common Protocols by OSI Layer

Layer	Examples
Application	HTTP, FTP, SMTP, DNS, SSH, DHCP
Presentation	TLS, PGP, ASCII, MIME
Session	NetBIOS, RTP, SOCKS, PPTP
Transport	TCP, UDP, SCTP, QUIC
Network	IP (IPv4/IPv6), ICMP, IPsec, IGMP
Data Link	Ethernet (IEEE 802), PPP, ATM, Frame Relay
Physical	USB, Bluetooth, RS-232, DSL

Evolution: OSI vs. TCP/IP

The RM/OSI model was originally designed for connection-oriented networks, which are better suited for wide area networks (WANs). This is why it includes a session layer. In contrast, the TCP/IP scheme assumes a connectionless network, which is more efficient for local area networks (LANs).

Because the Internet required immediate solutions, the IETF developed its own process based on "rough consensus and running code" (as described in RFC 2026). Over time, the RM/OSI model expanded to include connectionless services, allowing both TCP and IP to eventually become international standards.

Frequently Asked Questions

What is the difference between a protocol standard and a de facto standard?

A protocol standard is formally approved by a recognized standards organization (like ISO or IEEE), whereas a de facto standard gains market dominance through widespread use without a formal standardization process.

Why is the OSI model useful for network design?

The OSI model provides a structured framework that prevents overlapping functionality and clearly defines the responsibilities of each layer, making it easier to develop future-proof and interoperable protocols.

What is a service access point in the OSI model?

A service access point is the interface through which a layer communicates with the layer immediately above it to provide necessary services.

How does the IETF's standardization process differ from the ISO's?

While the ISO uses a formal process of sub-committees and draft proposals, the IETF historically relied on a more pragmatic approach described as "rough consensus and running code."

What happened to the BSC protocol that highlighted the need for standards?

Because BSC lacked standardization, different manufacturers created over 50 incompatible variants, some of which were designed specifically to prevent users from switching to competing hardware.