Unit V

TRADITIONAL APPLICATIONS

Presentation by:
KAYTHRY P.
Assistant Professor,ECE
SSN College of Engineering
 Syllabus
• Traditional applications
• Electronic Mail
• SMTP – Simple Mail Transfer Protocol
• POP 3
• IMAP
• MIME
• HTTP – Hyper Text Transfer Protocol
• Web Services
• DNS – Domain Name System
• SNMP – Simple Network Management
Protocol
 Objectives
• At the end of this session, you can able
understand:
• What are network applications available today?
Application Layer
 Introduction
• Applications – that are
given to the END USER.
• Every application is
developed for a purpose
and have its own style of
working
Apps available
That’s is not ALL.
 Traditional Applications
• Among all the applications our study
focuses on 2 main traditional applications.
They are :

• Broadly speaking, both of these applications use

the request/reply paradigm—users send requests
to servers, which then respond accordingly.
 Traditional Applications
• It is important to distinguish between application
programs and application protocols.
• For example, the HyperText Transport Protocol
(HTTP) is an application protocol that is used to
retrieve Web pages from remote servers.
• There can be many different application programs
—that is, Web clients like Internet Explorer,
Chrome, Firefox —that provide users with a
different look and feel, but all of them use the
same HTTP protocol to communicate with Web
servers over the Internet.
 Distinguish between the Application Program and Application Protocols

• Example
 Traditional Applications
1. Each protocol reinvents the Simple Remote
procedure call (RPC) mechanism (it is called
simple because it only specifies the procedure,
format is taken care by companion protocol)
2. Each protocol will have a companion protocol
which defines the format of the contents
• Two very widely-used, standardized application
protocols:
– SMTP: Simple Mail Transfer Protocol is used to
exchange electronic mail.
– HTTP: HyperText Transport Protocol is used to
communicate between Web browsers and Web
 Traditional Applications
• This companion protocol specifies the format of the
information to be exchanged.
• Each protocol will have a companion protocol
 Traditional Applications
• Electronic Mail (SMTP, MIME, IMAP)
– Email is one of the oldest network applications
– It is important
– (1) to distinguish the user interface (i.e., your mail
reader) from the underlying message transfer
protocols (such as SMTP or IMAP – Internet
Message Access Protocol), and
– (2) to distinguish between this transfer protocol
and a companion protocol (RFC 822 and MIME-
Multi Purpose Internet Mail Extension) that
defines the format of the messages being
exchanged
 overview

• Application
• Application • Companion
Protocol:
Program: Protocol:
• Which is • Which specifies
• Which
available to the the RPC
specifies the
end user without mechanism to format of the
knowing any
fetch data that are to
knowledge
about the information be exchanged.
network. available at
remotely
Electronic Mail
 Traditional Applications – E-mail
• Electronic Mail
(SMTP, MIME,
IMAP)
• Message Format –
• This is the one of MIME
the oldest • Message Transfer –
applications. SMTP
• It is mandatory to
• Mail Reader – POP /
distinguish
between the User IMAP
Interface –
Transfer Protocols
– Companion
Protocol
Traditional Applications – E-mail
 Traditional Applications – E-mail
• Electronic Mail (SMTP, MIME, IMAP)
– Message Format :Message format is defined by the
companion protocols. Two majorly used protocols
are given below.
– RFC 822 - Standard for the format of ARPA
Internet text messages
• RFC 822 defines messages to have two parts: a
header and a body. Both parts are represented in
ASCII text
– MIME - Multipurpose Internet Mail Extensions.
•.
• Few headers are obtained by the user.
– Ex:
• TO address
• CC address Syntax:
• BCC address <Header Type> : <Header Value>
• Sub Text
• Few headers are added automatically by the
program
– Ex:
• From Address
• Mail Server
• Date and Time
 Traditional Applications – E-mail
• MIME : Multipurpose Internet Mail Extensions.
• This is an supplementary protocol that allows
Non ASCII data to be sent through E Mail
• This enabled the email to carry any type of
attachments like documents, pdf, image, etc.,
 Traditional Applications – E-mail
• Electronic Mail (SMTP, MIME, IMAP)
– Message Format
• The header is separated from the message body by a
blank line. Each header line contains a type and value
separated by a colon.
• Many of these header lines are familiar to users since
they are asked to fill them out when they compose an
email message.
• RFC 822 was extended in 1993 (and updated quite a few
times since then) to allow email messages to carry many
different types of data: audio, video, images, PDF
documents, and so on.
 Traditional Applications – E-mail
• Electronic Mail (SMTP, MIME, IMAP)
– Message Format
• MIME consists of three basic pieces.
– The first piece is a collection of header lines that
augment the original set defined by RFC 822.
• These header lines describe, in various ways, the data MIME
mainly consists of 5 header:
• MIME - Version
• Content type – type of data contained in the message
• Content transfer encoding – how the data in the message body
is encoded
• Content ID – message ID
• Content Description – human readable description
MIME Headers
Traditional Applications – E-mail
–The second piece is definitions for a
set of content types (and subtypes). For
example, MIME defines two different
still image types, denoted image/gif
and image/jpeg, each with the obvious
meaning.
–The third piece is a way to encode the
various data types so they can be
shipped in an ASCII email message.
 Traditional Applications – E-mail
– Message Transfer – SMTP,POP,IMAP
• For many years, the majority of email was moved
from host to host using only SMTP (Simple Mail
Transfer Protocol).
• While SMTP continues to play a central role.
• IMAP (Internet Message Access Protocol) and
POP (Post Office Protocol) being two other
important protocols for retrieving mail messages.
 Traditional Applications – E-mail -SMTP
• The actual mail transfer is done through the Mail Transfer
Agents (
MTA).
• The protocol that defines the MTA Client and Server is
called SMTP.
• SMTP is used 2 Times
– Between sender and mail server.
– Between 2 mail servers.
Traditional Applications – E-mail -SMTP
• Electronic Mail (SMTP, MIME, IMAP)
– Message Transfer
• The MTA on a sender’s machine establishes an
SMTP/TCP connection to the MTA on the
recipient’s mail server, in many cases the mail
traverses one or more mail gateways on its route
from the sender’s host to the receiver’s host.
• Like the end hosts, these gateways also run a
message transfer agent process.
 Traditional Applications – E-mail
• Electronic Mail (SMTP, MIME, IMAP)
– Mail Reader
• The final step is for the user to actually retrieve his or
her messages from the mailbox, read them, reply to
them, and possibly save a copy for future reference.
• The user performs all these actions by interacting with a
mail reader.
• This mail reader was originally just a program running
on the same machine as the user’s mailbox.
Message Reader / Message Access
 Traditional Applications – E-mail
• Electronic Mail (SMTP, MIME, IMAP)
– Mail Reader:
– SMPT is not involved in the third stage because SMTP
is a Push Protocol. It pushes the message from the client
to the server.
– The third stage need the Pull Protocol. The client must
pull message from the server.
– Two of the popularly used message access agents are
POP3 and IMAP
• Today, most often the user accesses his or her
mailbox from a remote machine using yet another
protocol, such as the Post Office Protocol (POP) or
the Internet Message Access Protocol (IMAP).
 Traditional Applications – E-mail
• Electronic Mail (SMTP, MIME, IMAP)
– Mail Reader
• IMAP is similar to SMTP in many ways.
• It is a client/server protocol running over TCP,
where the client (running on the user’s desktop
machine) issues commands in the form of
<CRLF>-terminated ASCII text lines and the
mail server (running on the machine that
maintains the user’s mailbox) responds in-kind.
• The exchange begins with the client
authenticating him or herself, and identifying
the mailbox he or she wants to access.
 Traditional Applications – E-mail -
POP 33(POP 3)
• Post Office Protocol Version
• Client POP 3 will be installed in the recipient’s
computer and the server POP 3 is installed at the server.
• Message access will be initiated when the user wants to
download the mail from the server.
• POP 3 have 2 modes
– Delete Mode
• In this mode, the mail is deleted from the mailbox
after each retrieval.
– Keep Mode
• In this mode, the mail is kept is the personal
computer for future access.
Exchange of Commands and Responses in POP 3
 Traditional Applications – E-mail -
• IMAP
Internet Mail Access Protocol, Version 4
• IMAP 4 is similar to the POP 3 but with added
features.
• The features are:
– A user can check the email header prior to
downloading.
– A user can search the content of the email for a
specific string
– A user can download partial email due to bandwidth
constraints.
– User can create delete or rename mail boxes
– User can create hierarchy of mail boxes.
POP 3 Vs IMAP 4
Video Presentation on E - Mail
 Summary
• E-mail
• SMTP
• MIME
• IMAP
• POP