Protocol stack: Difference between revisions

Revision as of 00:21, 7 July 2025

Latest revision as of 06:34, 28 July 2025

(2 intermediate revisions by 2 users not shown)

Line 35:

A request on computer ''A'' to send a chunk of data to ''C'' is taken by the upper protocol, which (through whatever means) knows that ''C'' is reachable through ''B''. It, therefore, instructs the wireless protocol to transmit the data packet to ''B''. On this computer, the lower layer handlers will pass the packet up to the inter-network protocol, which, on recognizing that ''B'' is not the final destination, will again invoke lower-level functions. This time, the cable protocol is used to send the data to ''C''. There, the received packet is again passed to the upper protocol, which (with ''C'' being the destination) will pass it on to a higher protocol or application on ''C''.

In practical implementation, protocol stacks are often divided into three major sections: media, transport, and applications. A particular [[operating system]] or platform will often have two well-defined software interfaces: one between the media and transport layers, and one between the transport layers and applications. The media-to-transport interface defines how transport protocol software makes uhttps://github.com/account_verifications?return_to=%2Flogin%2Foauth%2Fauthorize%3Fclient_id%3DIv1.a72902e7053ea8aa%26new_signup%3Dtrue%26scope%3Dread%253Auser%252Cuser%253Aemail%26state%3DeyJvcmlnaW4iOiJodHRwczpcL1wvd29yZHByZXNzLmNvbSIsInV4X21vZGUiOiJyZWRpcmVjdCIsInJlZGlyZWN0X3VyaSI6Imh0dHBzOlwvXC93b3JkcHJlc3MuY29tXC9tZVwvc2VjdXJpdHlcL3NvY2lhbC1sb2dpbiIsIm5vbmNlIjoiODc4Y2NjMjBlMyJ9seuse of particular media and hardware types and is associated with a [[device driver]]. For example, this interface level would define how [[TCP/IP]] transport software would talk to the [[network interface controller]]. Examples of these interfaces include [[Open Data-Link Interface|ODI]] and [[Network Driver Interface Specification|NDIS]] in the [[Microsoft Windows]] and [[DOS]] environment. The application-to-transport interface defines how application programs make use of the transport layers. For example, this interface level would define how a [[web browser]] program would talk to TCP/IP transport software. Examples of these interfaces include [[Berkeley sockets]] and System V [[STREAMS]] in [[Unix-like]] environments, and [[Winsock]] for Microsoft Windows.

==Examples==