Understanding the OSI Reference Model: Protocols at Each Layer

at

protocols at each layer of OSI model



The OSI (Open Systems Interconnection) reference model is a conceptual framework used to understand network interactions in seven distinct layers. Each layer has specific protocols that facilitate communication and data exchange. Let’s dive into the OSI model and explore the protocols that operate at each layer.

Application layer

It’s responsible for providing an interface for the user to interact with application services or network services. Ex-Web browser (HTTP), Telne


Presentation layer

It’s responsible for defining a standard format to the data. The major functions described at this layer are: -

Encoding-Decoding Ex- AVI-(video), WAV-(voice), JPEG (graphite), ASCII (text) Encryption-Decryption

Session layer

It’s responsible for establishing, maintaining, and terminating the sessions. Session ID is used to identify a session or interaction.

Ex-Remote procedural call, Apple talk session protocol.



Transport Layer

It provides data delivery mechanism between applications in the network. Transport layer is the major function layer In OSI layer

Identifying service

Multiplexing&De-multiplexing Segmentation, Error correction, flow control Transport layer protocols?

The protocols which takes care of data transport at transport layer are TCP/UDP


Difference between UDP & TCP.



Network Layer
It provides logical addressing path determination (routing)

The protocols that work in this layer are: -Routed Protocol, Routing Protocol Routed Protocols→Used to carry user data between data.

Routing Protocols→used performs path determinisation routing.

Data link layer

It provides communication with network layer.

Mac (media access control) it provides reliable transit of data across a physical link.

Physical layer

It defines the electrical, mechanical functional specification for communication between the network devices.


#OSI #layers #network #tcp #udp
Read more
Labels:
Subscribe to: Posts (Atom)

Featured Post

Day 41 — BGP Confederations: Sub-AS Design, External View and Migration

1. Opening Confederations are another way to scale BGP inside a large administrative domain. They divide the domain into member autonomous systems while presenting a single confederation identifier to external peers. They are powerful, but their operational model is more complex than simply 'using private ASNs inside.' The engineering goal is not to memorize another BGP command. It is to understand what information each speaker is allowed to propagate, what path information can be hidden, and what failure domain is created by the chosen control-plane architecture . 2. Concept and standards behavior RFC 5065 defines AS_CONFED_SEQUENCE and AS_CONFED_SET and how member-AS relationships are represented. Confederation external sessions have eBGP-like properties inside the confederation, while the confederation is presented externally as one AS. Modern guidance must also account for the fact that RFC 9774 prohibits new origination of AS_SET/AS_CONFED_SET in ordinary aggregation c...