Scribd
Upload
50 views

Application Layer Introduction

The application layer is the topmost layer in the OSI and TCP/IP models. It includes protocols that are directly used by users like web browsers, email clients, and file transfer programs. Application layer protocols can operate using either a peer-to-peer or client-server model and common examples include HTTP, SMTP, FTP, and Telnet. These protocols define message formats and interactions between applications on different systems to enable communication and data transfer.

Uploaded by

Vivek Bhatt
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
50 views

Application Layer Introduction

The application layer is the topmost layer in the OSI and TCP/IP models. It includes protocols that are directly used by users like web browsers, email clients, and file transfer programs. Application layer protocols can operate using either a peer-to-peer or client-server model and common examples include HTTP, SMTP, FTP, and Telnet. These protocols define message formats and interactions between applications on different systems to enable communication and data transfer.

Uploaded by

Vivek Bhatt
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Application Layer Protocols

•Application layer is the topmost layer in OSI


and TCP/IP layered model.
•. This layer is for applications which are
involved in communication system.
•A user may or may not directly interacts with
the applications. Application layer is
where the actual communication is initiated
and reflects.
•. it does not serve any other layers.
•Application layer takes the help of Transport
and all layers below it to communicate or
transfer its data to the remote host.
•When an application layer protocol wants to
communicate with its peer application layer
protocol on remote host, it hands over the data
or information to the Transport layer. The
transport layer does the rest with the help of all
the lay
•Not every user application can be put into
Application Layer except those applications
which interact with the communication system.
For example, designing software or texteditor
cannot be considered as application layer
programs.
•On the other hand, when we use a Web
Browser, which is actually using Hyper Text
Transfer Protocol (HTTP) to interact with the
network, HTTP is Application Layer
protocol
•Irrespective of which software you use, it is
the protocol which is considered at Application
Layer used by that software.
•DNS is a protocol which helps user
application protocols such as HTTP to
accomplish its work.
Two remote application processes can
communicate mainly in two different fashions:
 Peer-to-peer: Both remote processes are
executing at same level and they
exchange data using some shared resource.
 Client-Server: One remote process acts as a
Client and requests some resource from
another application process acting as Server.
In client-server model, any process can act as
Server or Client. It is not the type of
machine, size of the machine, or its computing
power which makes it server.
•A system can act as Server and Client simultaneously
•Two processes in client-server model can interact in various ways:
 Sockets
 Remote Procedure Calls (RPC)

•There are several protocols which work for users in Application


Layer. Application
layer protocols can be broadly divided into two categories:
 Protocols which are used by users. For example, eMail.
 Protocols which help and support protocols used by users. For
example, DNS.
The Internet Architecture

Application layer

Transport layer / Layer 4

Network layer

Link layer

Physical layer
Application vs application protocol
• Application protocol: ”specs” of a particular
application.
• Applications implementing the same protocol
can interact with each other despite different
implementations
• Not all network applications have open
network protocols
Anatomy of an Application
• protocol
Types of messages (e.g., requests and responses)

• Message syntax (e.g., fields, and how to delineate)

• Semantics of the fields (i.e., meaning of the


information)

• Rules for when and how a process sends


messages

• Platform and programming language


independent
Anatomy of a content-rich application-layer protocol
1. A companion protocol that specifies the data format

2. A protocol that describes the interactions between two end


systems

• Examples
– HTTP and HTML
– SMTP and RFC 2822 (Internet Text Messages), and Multipurpose
Internet Mail Extensions (MIME)

• Simpler protocols may specify both data format and


interactions in one protocol
– Eg. DNS
• Request/response
• The record has a simple format
– Telnet
– FTP
Sample application
protocols: HTTP
• Client sends a request with method, URL, and meta-
data

• Server applies the request to the resource and returns


the response, including meta-data

• Single TCP connection for control and data


Telnet
• Client simply relays user keystrokes to the server

• Server simply relays any output to the client

• TCP connection persists for duration of the login


session

• Network Virtual Terminal (NVT) format for


transmitting ASCII data, and control information
(e.g., End-of-Line delimiter)
FTP
• Client connects to remote machine, “logs in”, and
issues commands for transferring files to/from
the account

• Server responds to commands and transfers files

• Separate TCP connections for control and data

• Control connection uses the same NVT format as


Telnet

You might also like