Data Communictions and

Networking
Application Layer

Data Communictions and Networking

Introduction to Application Layer

It is the closest layer to the end user which means that the application
layer and end user can interact directly with the software application.
The application layer programs are based on client and servers.
The following are the functionalies of Application Layer:

Identifying communication partners:It identifies the availability of

communication partners for an application with data to transmit.
Determining resource availability:It determines whether sufficient
network resources are available for the requested communication.
Synchronizing Communication: All the communications occur
between the applications requires cooperation which is managed by
an application layer.

Data Communictions and Networking

Services of Application Layers

The Following are the Services of Application Layer :

Network Virtual terminal: An application layer allows a user to log

on to a remote host. To do so, the application creates a software
emulation of a terminal at the remote host. The user’s computer
talks to the software terminal, which in turn, talks to the host. The
remote host thinks that it is communicating with one of its own
terminals, so it allows the user to log on.

File Transfer, Access, and Management (FTAM): An application

allows a user to access files in a remote computer, to retrieve files
from a computer and to manage files in a remote computer.
FTAM defines a hierarchical virtual file in terms of file structure,
file attributes and the kind of operations performed on the files
and their attributes.

Data Communictions and Networking

Services of Application
Layers....
The Following are the Services of Application Layer :

Addressing: To obtain communication between client and server,

there is a need for addressing. When a client made a request to
the server, the request contains the server address and its own
address. The server response to the client request, the request
contains the destination address, i.e., client address. To achieve
this kind of addressing, DNS is used.

Mail Services: This layer provides Email forwarding and storage.

Directory Services: An application contains a distributed database

that provides access for global information about various objects
and services. Authentication: It authenticates the sender or
receiver’s message or both.

Data Communictions and Networking

Application Layer Architecture

It is designed by the application developer and defines how the

application should be structured over the various end systems.

Application architecture is of two types

Client-Server architecture : An application program running on the
local machine sends a request to another application program is
known as a client, and a program that serves a request is known as a
server. For example, when a web server receives a request from the
client host, it responds to the request to the client host.

Characteristics Of Client-server architecture:

Clients do not directly communicate with each other. For example, in
a web application, two browsers do not directly communicate with
each other.
A server is fixed, well-known address known as IP address because the
server is always on while the client can always contact the server by
sending a packet to the sender’s IP address.

Data Communictions and Networking

Merits of Client/Server Architecture

Advantages....!

Centralized: Centralized back-up is possible in client-server

networks, i.e., all the data is stored in a server.
Security: These networks are more secure as all the shared
resources are centrally administered.
Performance: The use of the dedicated server increases the speed
of sharing resources. This increases the performance of the
overall system.
Scalability: We can increase the number of clients and servers
separately, i.e., the new element can be added, or we can add a
new node in a network at any time.

Data Communictions and Networking

De-Merits of Client/Server Architecture

Dis-Advantages....!

Traffic Congestion is a big problem in Client/Server networks.

When a large number of clients send requests to the same
server may cause the problem of Traffic congestion.
It does not have a robustness of a network, i.e., when the server
is down, then the client requests cannot be met.
A client/server network is very decisive. Sometimes, regular
computer hardware does not serve a certain number of clients.
In such situations, specific hardware is required at the server
side to complete the work.
Sometimes the resources exist in the server but may not exist in
the client. For example, If the application is web, then we cannot
take the print out directly on printers without taking out the print
view window on the web.

Data Communictions and Networking

Application Layer Architecture

P2P (peer-to-peer) architecture : It has no dedicated server in a

data center. The peers are the computers which are not owned by the
service provider and resides in the homes, offices, schools, and
universities. The peers communicate with each other without passing
the information through a dedicated server, this architecture is known
as peer-to-peer architecture. The applications based on P2P
architecture includes file sharing and internet telephony.

Features of P2P
Self scalability: In a file sharing system, although each peer
generates a workload by requesting the files, each peer also adds a
service capacity by distributing the files to the peer.
Cost-effective: It is cost-effective as it does not require significant
server infrastructure and server bandwidth.

Data Communictions and Networking

TELNET

• TErminaL NETwork
• Although TELNET requires a logging name and
password, it is vulnerable to hacking because it
sends all data including the password in plaintext
(not encrypted). A hacker can eavesdrop and obtain
the logging name and password. Because of this
security issue, the use of TELNET has diminished in
favor of another protocol, Secure Shell (SSH),

Data Communictions and Networking

TELNET - Local versus Remote Logging

Data Communictions and Networking

TELNET - Network Virtual Terminal (NVT)

Data Communictions and Networking

TELNET- Embedding

• TELNET uses only one TCP connection.

The server uses the well-known port 23,
and the client uses an ephemeral port.
• The same connection is used for sending
both data and control characters.

Data Communictions and Networking

DNS : Domain Name Space

An application layer protocol defines how the application processes

running on different systems, pass the messages to each other.
DNS stands for Domain Name System.
DNS is a directory service that provides a mapping between the
name of a host on the network and its numerical address.
DNS is required for the functioning of the internet. Each node in a
tree has a domain name, and a full domain name is a sequence of
symbols specified by dots.
DNS is a service that translates the domain name into IP addresses.
This allows the users of networks to utilize user-friendly names when
looking for other hosts instead of remembering the IP addresses.
For Example, Suppose the FTP site at EduSoft had an IP address of
132.147.165.50, most people would reach this site by specifying
ftp.EduSoft.com. Therefore, the domain name is more reliable than IP
address

Data Communictions and Networking

DNS : Domain Name Space

DNS is a TCP/IP protocol used on different platforms. its space

is divided into three different sections: generic domains, country
domains, and inverse domain.

Data Communictions and Networking

DNS : Domain Name Space

Generic Domain :
It defines the registered hosts according to their generic behavior.
Each node in a tree defines the domain name, which is an index to
the DNS database.
It uses three-character labels, and these labels describe the
organization type.
Example : .com (Commercial Orgnizations), .edu (Educational
institutions), .gov (Government institutions) and Soon...
Country Domain : The format of country domain is same as a
generic domain, but it uses two-character country
abbreviations (e.g., .us for the United States) in place of three
character organizational abbreviations.
Inverse Domain : It is used for mapping an address to a name.
When the server has received a request from the client, and the
server contains the files of only authorized clients. To determine
whether the client is on the authorized list or not, it sends a query
to the DNS server and ask for mapping an address to the name.

Data Communictions and Networking

Example : Generic Domains

Data Communictions and Networking

Example : Country Domains

Data Communictions and Networking

Example : Inverse Domains

Data Communictions and Networking

DNS : Domain Name Space
Working of DNS :
DNS is a client/server network communication protocol.
DNS clients send requests to the server while DNS servers
send responses to the client.
Client requests contain a name which is converted into an IP
address known as a forward DNS lookups while requests containing
an IP address which is converted into a name known as reverse
DNS lookups.
DNS implements a distributed database to store the name of all
the hosts available on the internet.
If a client like a web browser sends a request containing a
hostname, then a piece of software such as DNS resolver sends a
request to the DNS server to obtain the IP address of a hostname.
If DNS server does not contain the IP address associated with a
hostname, then it forwards the request to another DNS server. If
IP address has arrived at the resolver, which in turn completes the
request over the internet protocol.

Data Communictions and Networking

Example - DNS Works

Data Communictions and Networking

Example - Domain Name Space

Data Communictions and Networking

Example - Domain Name Space

Data Communictions and Networking

Example - Domain Name Space

Data Communictions and Networking

Domain Name Space -RESOLUTION

Mapping a name to an address is called name-address resolution.

DNS is designed as a client-server application. A host that needs to map an
address to a name or a name to an address calls a DNS client called a
resolver.
The resolver accesses the closest DNS server with a mapping request.
If the server has the information, it satisfies the resolver; otherwise, it
either refers the resolver to other servers or asks other servers to provide
the information.
After the resolver receives the mapping, it interprets the response to see if
it is a real resolution or an error, and finally delivers the result to the
process that requested it.
A resolution can be either recursive or iterative.

Data Communictions and Networking

Domain Name Space -RESOLUTION

Data Communictions and Networking

 Domain Name Space -RESOLUTION

• The IP address is now sent back to the top-level DNS server (event 5), then
back to the root server (event 6), then back to the ISP DNS server, which
may cache it for the future queries (event 7), and finally back to the source
host (event 8).

Data Communictions and Networking

 Domain Name Space -RESOLUTION

• The application program on the source host calls the DNS resolver (client) to
find the IP address of the destination host.
• The resolver, which does not know this address, sends the query to the local
DNS server (for example, dns.anet.com) (EVENT 1)
• Assume that this server does not know the IP address of the destination
host either. It sends the query to a root DNS server, whose IP address is
supposed to be known to this local DNS server (event 2).
• Root servers do not normally keep the mapping between names and IP
addresses, but a root server should at least know about one server at each
top level domain (in this case, a server responsible for com domain).
• The query is sent to this top-level-domain server (event 3).
• We assume that this server does not know the name-address mapping of
this specific destination, but it knows the IP address of the local DNS server
in the McGraw-Hill company (for example, dns.mcgraw-hill.com).
• The query is sent to this server (event 4), which knows the IP address of the
destination host.

Data Communictions and Networking

DNS – ITERATIVE RESOLUTION

Data Communictions and Networking

 DNS ITERATIVE RESOLUTION

• In iterative resolution, each server that does not know the mapping sends
the IP address of the next server back to the one that requested it.
• Normally the iterative resolution takes place between two local servers; the
original resolver gets the final answer from the local server.
• Note that the messages shown by events 2, 4, and 6 contain the same
query. However, the message shown by event 3 contains the IP address of
the top-level domain server, the message shown by event 5 contains the IP
address of the McGraw-Hill local DNS server, and the message shown by
event 7 contains the IP address of the destination.
• When the Anet local DNS server receives the IP address of the destination,
it sends it to the resolver (event 8).

Data Communictions and Networking

 DNS- CACHING

• Each time a server receives a query for a name that is not in its domain, it
needs to search its database for a server IP address. Reduction of this search
time would increase efficiency.
• DNS handles this with a mechanism called caching. When a server asks for a
mapping from another server and receives the response, it stores this
information in its cache memory before sending it to the client.
• If the same or another client asks for the same mapping, it can check its
cache memory and resolve the problem.
• Caching speeds up resolution, but it can also be problematic. If a server
caches a mapping for a long time, it may send an outdated mapping to the
client. To counter this, two techniques are used.
• First, the authoritative server always adds information to the mapping
called time to live (TTL). It defines the time in seconds that the receiving
server can cache the information. After that time, the mapping is invalid and
any query must be sent again to the authoritative server.
• Second, DNS requires that each server keep a TTL counter for each mapping
it caches. The cache memory must be searched periodically and those
mappings with an expired TTL must be purged.
Data Communictions and Networking
File Transfer Protocol

FTP stands forFileTransferProtocol.

FTP is a standard internet protocol provided by TCP/IP used for
transmitting the files from one host to another.
It is mainly used for transferring the web page files from their creator to
the computer that acts as a server for other computers on the internet.
It is also used for downloading the files to computer from other
servers.

Objectives of FTP :
It provides the sharing of files.
It is used to encourage the use of remote computers.
It transfers the data more reliably and efficiently.

Data Communictions and Networking

Why FTP?

Although transferring files from one system to another is very simple

and straightforward, but sometimes it can cause problems.
Two systems may have different file conventions.
Two systems may have different ways to represent text and
data. Two systems may have different directory structures.

Solution:
FTP protocol overcomes these problems by establishing two
connections between hosts. One connection is used for data transfer,
and another connection is used for the control connection.

Data Communictions and Networking

Mechanism of FTP

FTP is an application layer protocol which moves files between

local and remote file systems.
It runs on the top of TCP, like HTTP.
To transfer a file, 2 TCP connections are used by FTP in
parallel: Control connection and Data connection.

Data Communictions and Networking

Mechanism of FTP

The above figure shows the basic model of the FTP.

The FTP client has three components: the user
interface, control process, and data transfer process.
The server has two components: the server control process and
the server data transfer process.

Data Communictions and Networking

Connections in FTP

Control Connection(Port : 21): It uses very simple rules for

communication. Through this, we can transfer a line of command/response
at a time. It is made between the control processes and remains connected
during the entire interactive FTP session.

Data Connection(Port : 20): It uses very complex rules as data types

may vary. It is made between data transfer processes. It opens when a
command comes for transferring the files and closes when the file is
transferred.

Data Communictions and Networking

FTP - Clients

It is a program that implements a FTP to transfer files between

two hosts on the internet.
It allows a user to connect to a remote host and upload or
download the files.
It has a set of commands, used to connect to a host, transfer
the files, and close the connection.
This GUI based FTP client makes the file transfer very easy and
also does not require to remember the FTP commands.

Data Communictions and Networking

Control Connections in FTP

Using the control

connection

Data Communictions and Networking

Data Connections in FTP

Using the Data

connection

Data Communictions and Networking

Control/Data Connections in FTP

Using theControlconnection

Using theDataconnection

Data Communictions and Networking

Communication over data connection

File Type
FTP can transfer one of the following file types across the data
connection: ASCII file, EBCDIC file, or image file.
Data Structure
file structure,
record structure,
page structure.
Transmission Mode
stream mode,
block mode,
compressed mode.
File Transfer
retrieving a file (server to client),
storing a file (client to server),
directory listing (server to client).
Control/Data Connections in FTP

Using theCommandprocessing

Using theFile Transfer

Data Communictions and Networking

Commands in FTP...!

Access Commandsin FTP

Data Format Commandsin FTP

Data Communictions and Networking

Commands in FTP...!

File Management Commandsin FTP

Port Defining Commandsin FTP

Data Communictions and Networking

Commands in FTP...!

File Transfer Commandsin FTP

Miscellaneous Commandsin FTP

Data Communictions and Networking

Commands in FTP...!

Response Commandsin FTP

Data Communictions and Networking

Commands in FTP...!

Response Commandsin FTP

Data Communictions and Networking

Example : Retrieve List of Items in Directory

Data Communictions and Networking

Example : Actual FTP Sessions

FTP Sessions

The colored lines show the responses from the server control connection;
The black lines show the commands sent by the client.
The lines in white with black background show data transfer.

Data Communictions and Networking

Advantages of FTP

Speed: One of the biggest advantages of FTP is speed. The FTP

is one of the fastest way to transfer the files from one computer
to another computer.

Efficient: It is more efficient as we do not need to complete all

the operations to get the entire file.

Security: To access the FTP server, we need to login with the

username and password. Therefore, we can say that FTP is more
secure.

Back & forth movement: FTP allows us to transfer the files back
and forth. Suppose you are a manager of the company, you send
some information to all the employees, and they all send
information back on the same server.

Data Communictions and Networking

Disadvantages of FTP

The standard requirement of the industry is that all the FTP

transmissions should be encrypted. However, not all the FTP
providers are equal and not all the providers offer encryption. So, we
will have to look out for the FTP providers that provides
encryption.

FTP serves two operations, i.e., to send and receive large files on a
network. However, the size limit of the file is 2GB that can be
sent. It also doesn’t allow you to run simultaneous transfers to
multiple receivers.

Passwords and file contents are sent in clear text that allows
unwanted eavesdropping. So, it is quite possible that attackers
can carry out the brute force attack by trying to guess the FTP
password.

It is not compatible with every system.

Data Communictions and Networking

SNMP : Simple Network
Management Protocol

Data Communictions and Networking

SNMP - Simple Network Management Protocol

SNMP stands for Simple Network Management Protocol.

It is an application–layer protocol defined by the
Internet Architecture Board (IAB).
It is a part of Transmission Control Protocol⁄Internet
Protocol (TCP⁄IP) protocol suite.
SNMP is one of the widely accepted protocols to manage
and monitor network elements.
It comes with bundle of network elements called SNMP
agents, which enables and configures to communicate with
the network management system (NMS).
SNMP is a framework used for managing devices on the
internet.
It provides a set of operations for monitoring and managing
the internet.

Data Communictions and Networking

SNMP Concept

SNMP has two components Manager and Agent.

The Manager is a host that controls and monitors a set of
Agents such as routers.
It monitors the devices made by different manufacturers
and installed on different physical networks.
It is used in a heterogeneous network made of different LANs
and WANs connected by routers or gateways.
Data Communictions and Networking
SNMP Managers and Agents

A manager is a host that runs the SNMP client program while

the agent is a router that runs the SNMP server program.

Management of the internet is achieved through simple

interaction between a manager and agent.

The agent is used to keep the information in a database while the

manager is used to access the values in the database. For example,
a router can store the appropriate variables such as a number of
packets received and forwarded while the manager can compare
these variables to determine whether the router is congested or
not.

Agents can also contribute to the management process. A

server program on the agent checks the environment, if
something goes wrong, the agent sends a warning message to
the manager.

Data Communictions and Networking

SNMP Managers and Agents

In other words, management with SNMP is based on

three basic ideas:
1. A manager checks an agent by requesting
information that reflects the behavior of the agent.
2. A manager forces an agent to perform a task by
resetting values in the agent database.
3. An agent contributes to the management process by
warning the manager of an unusual situation

Data Communictions and Networking

Management Components

Management is not achieved only through the SNMP protocol

but also the use of other protocols that can cooperate with the
SNMP protocol.
Management is achieved through the use of the other two
protocols: SMI (Structure of management information) and
MIB(management information base).
Management is a combination of SMI, MIB, and SNMP. All
these three protocols such as abstract syntax notation 1 and
basic encoding rules .

Data Communictions and Networking

Management Components...!

SMI: It is a component used in network management. It defines

the type of data that can be stored in an object and show how to
encode the data for the transmission over a network.
MIB: Each agent has its own MIB, which is a collection of all the
objects that the manager can manage. MIB is categorized into
eight groups: system, interface, address translation, ip, icmp, tcp,
udp, and egp. These groups are under the mib object.

Data Communictions and Networking

Management Components...!

SNMP Messages: It defines five types of messages:

GetRequest, GetNextRequest, SetRequest, GetResponse, and
Trap.

Data Communictions and Networking

Management
Componenets...!
GetRequest:

SNMP manager sends this message to request data from the

SNMP agent. It is simply used to retrieve data from SNMP
agents.
In response to this, the SNMP agent responds with the requested
value through a response message.

GetNextRequest:
This message can be sent to discover what data is available on an
SNMP agent. The SNMP manager can request data continuously
until no more data is left. In this way, the SNMP manager can take
knowledge of all the available data on SNMP agents.

GetBulkRequest:

This message is used to retrieve large data at once by the SNMP

manager from the SNMP agent. It is introduced in SNMPv2c.
Data Communictions and Networking
 SetRequest:
It is sent from a manager to the agent to set a value in a variable.

GetResponse:
It is sent from an agent to the manager in response to the GetRequest
and GetNextRequest message.
This message contains the value of a variable requested by the
manager. When sent in response to Get messages, it will contain the
data requested. When sent in response to the Set message, it will contain
the newly set value as confirmation that the value has been set.

Trap: The Trap message is sent from an agent to the manager to report
an event. For example, if the agent is rebooted, then it informs the
manager as well as sends the time of rebooting.
WWW ARCHITECTURE

• The WWW today is a distributed client/server service, in

which a client using a browser can access a service using a
server. However, the service provided is distributed over
many locations called sites.
• Each site holds one or more web pages
• Each web page is a file with a name and address.
HTTP
 The protocols that are used to transfer hypertext between two
computers is known as HyperText Transfer Protocol.
 HTTP provides standard between a web browser and web server to
establish communication.
 It is set of rules for transferring data from one computer to another.
Data such as text, images, and other multimedia files are shared on
the World Wide Web.
 It is an application protocol which is used for distributed,
collaborative, hypermedia information systems
Architecture of WWW
Web Client(Browser)

Controller -receives input from the keyboard or the mouse and uses
the client programs to access the document
Interpreters -to display the document on the screen
Web Servers
 The web page is stored at the server. Each
time a request arrives, the corresponding
document is sent to the client.
Uniform Resource Locator (URL)
 WEB DOCUMENTS

The documents in the WWW can be grouped into

three broad categories: static, dynamic, and active.
The category is based on the time at which the
contents of the document are determined.

Types:
Static Documents
Dynamic Documents
Active Documents
Static document
Dynamic document using CGI
Dynamic document using server-site script
Note

Dynamic documents are sometimes

referred to as server-site dynamic
documents.
Active document using Java applet
Active document using client-site script
Note

Active documents are sometimes

referred to as client-site dynamic
documents.
 HTTP
The Hypertext Transfer Protocol (HTTP) is a
protocol used mainly to access data on the World
Wide Web. HTTP functions as a combination of FTP
and SMTP.

Topics discussed in this section:

HTTP Transaction
Persistent Versus Nonpersistent Connection
Note

HTTP uses the services of TCP on well-

known port 80.
HTTP transaction
Nonpersistent versus Persistent Connections
 Nonpersistent Connections
 In a nonpersistent connection, one TCP connection
is made for each request/response.
 The following lists the steps in this strategy:
 1. The client opens a TCP connection and sends a
request.
 2. The server sends the response and closes the
connection.
 3. The client reads the data until it encounters an
end-of-file marker; it then closes the connection.
Nonpersistent versus Persistent Connections
 Nonpersistent Connections
 In this strategy, if a file contains links to N
different pictures in different files (all located on
the same server), the connection must be
opened and closed N + 1 times. The
nonpersistent strategy imposes high overhead on
the server because the server needs N + 1
different buffers each time a connection is
opened.
Nonpersistent versus Persistent Connections
Nonpersistent versus Persistent Connections
 Persistent Connections
 This is the case when a document is created
dynamically or actively.
 In these cases, the server informs the client that the
length is not known and closes the connection after
sending the data so the client knows that the end of
the data has been reached.
 Time and resources are saved using persistent
connections. Only one set of buffers and variables
needs to be set for the connection at each site. The
round trip time for connection establishment and
connection termination is saved
Nonpersistent versus Persistent Connections
Request and response messages
Request and status lines
Request Methods
Request Header names
Response Status codes
Status codes (continued)
Header format
General headers
Response Header Names
 Example

This example retrieves a document. We use the GET

method to retrieve an image with the path /usr/bin/image1.
The request line shows the method (GET), the URL, and
the HTTP version (1.1). The header has two lines that show
that the client can accept images in the GIF or JPEG
format. The request does not have a body. The response
message contains the status line and four lines of header.
The header lines define the date, server, content encoding
(MIME version, which will be described in electronic mail),
and length of the document. The body of the document
follows the header.
Example
 Example

In this example, the client wants to send a web

page to be posted on the server. We use the PUT
method. The request line shows the method
(PUT), URL, and HTTP version (1.1). There are
four lines of headers. The request body contains
the web page to be posted. The response
message contains the status line and four lines
of headers. The created document, which is a
CGI document, is included as the body.
Example
 Example

HTTP uses ASCII characters. A client can directly

connect to a server using TELNET, which logs into port
80 (see next slide). The next three lines show that the
connection is successful. We then type three lines. The
first shows the request line (GET method), the second is
the header (defining the host), the third is a blank,
terminating the request. The server response is seven
lines starting with the status line. The blank line at the
end terminates the server response. The file of 14,230
lines is received after the blank line (not shown here).
The last line is the output by the client.
Example (continued)
Note

HTTP version 1.1 specifies a persistent

connection by default.
 SMTP-SIMPLE MAIL
TRANSFER PROTOCOL

McGraw-Hill © The McGraw-Hill Companies, Inc., 2000

 ELECTRONIC MAIL

One of the most popular Internet services is

electronic mail (e-mail). The designers of the Internet
probably never imagined the popularity of this
application program. Its architecture consists of
several components that we discuss in this chapter.

Topics discussed in this section:

Architecture
User Agent
Message Transfer Agent: SMTP
Message Access Agent: POP and IMAP
Web-Based Mail
First scenario in electronic mail
Note

When the sender and the receiver of an

e-mail are on the same system,
we need only two user agents.
Second scenario in electronic mail
Note

When the sender and the receiver of an

e-mail are on different systems, we
need two UAs and a pair of
MTAs (client and server).
Third scenario in electronic mail
Note

When the sender is connected to the

mail server via a LAN or a WAN,
we need two UAs and two pairs
of MTAs (client and server).
Fourth scenario in electronic mail
Push versus pull in electronic email
Note

When both sender and receiver are

connected to the mail server via
a LAN or a WAN, we need two
UAs, two pairs of MTAs
and a pair of MAAs.
This is the most common situation
today.
Services of user agent
Note

Some examples of command-driven

user agents are mail, pine,
and elm.
Note

Some examples of GUI-based user

agents are Eudora, Outlook, Gmail and
Netscape.
Format of an e-mail
E-mail address
Phases of
Mail
Transfer
MIME
MIME header
Data types and subtypes in MIME
Content-transfer-encoding
SMTP range
Commands and responses
Command format
Commands
Responses
Responses (continued)
 Example

Let us see how we can directly use SMTP to send an

e-mail and simulate the commands and responses we
described in this section. We use TELNET to log into
port 25 (the well-known port for SMTP). We then use the
commands directly to send an e-mail. In this example,
[email protected] is sending an e-mail to himself.
The first few lines show TELNET trying to connect to
the Adelphia mail server. After connection, we can type
the SMTP commands and then receive the responses, as
shown on the next slide. Note that we have added, for
clarification, some comment lines, designated by the “=”
signs. These lines are not part of the e-mail procedure.
 Example (continued)

$ telnet mail.adelphia.net 25
Trying 68.168.78.100 . . .
Connected to mail.adelphia.net (68.168.78.100).
Example (continued)
Example (continued)
POP3 and IMAP4
The exchange of commands and responses in POP3
Thank
s

Data Communictions and Networking