CS 6551 - unit 5 PPT

1. RMK College of Engineering and Technology
CS 6551
Computer Networks
Department
of
Electronics and Communication Engineering

2. Unit 5
Application Layer
Prepared by
Jai Ganesh S
Asst.Professor - ECE

3. 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

4. Application Layer

5. Introduction
• Applications – that are given to the END
USER.
• Every application is developed for a purpose
and have its own style of working

6. Apps available

7. That’s is not ALL.

8. Traditional Applications
• Among all the applications our study focuses on 2 main traditional
applications. They are :

9. Reason for Traditional Applications
• We call these application as traditional application because they existed
since the early days of computer networks.

10. Before starting the Topic…
• There are 3 general points that have to be made clear.
1. Distinguish between the Application Program and Application Protocols
2. 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)
3. Each protocol will have a companion protocol which defines the format of the contents.

11. Distinguish between the Application Program and Application
Protocols
• example

12. Each protocol reinvents the Simple Remote procedure call (RPC)
mechanism
• Remote Procedure Call (RPC) is a protocol that one program can use to request a
service from a program located in another computer in a network without having
to understand network details. (A procedure call is also sometimes known as a
function call or a subroutine call.)
• RPC uses the client/server model.

13. RPC Mechanism

14. • Most of the application programs works on Query – Respond Principle.
• This RPC specifies, which mechanism to be followed to fetch information
from the source.

15. Each protocol will have a companion protocol
• This companion protocol specifies the format of the information to be
exchanged.

16. overview
• Application Program:
• Which is available to the end user
without knowing any knowledge
about the network.
• Application Protocol:
• Which specifies the RPC
mechanism to fetch information
available at remotely located
systems.
• Companion Protocol:
• Which specifies the format
of the data that are to be
exchanged.

18. Electronic Mail

19. E - Mail
• This is the one of the oldest applications.
• It is mandatory to distinguish between the User Interface – Transfer
Protocols – Companion Protocol

20. What happens when you press
Send Button
EMAIL CLIENT
MIME
EMAIL CLIENT

21. E - Mail
• Message Format – MIME
• Message Transfer – SMTP
• Mail Reader – POP / IMAP

22. Format of an E Mail

23. 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
• MIME - Multipurpose Internet Mail Extensions.

24. RFC 822
• This defines 2 parts
• Header
• Body

25. • Few headers are obtained by the user.
• Ex:
• TO address
• CC address
• BCC address
• Sub Text
• Few headers are added automatically by the program
• Ex:
• From Address
• Mail Server
• Date and Time
Syntax:
<Header Type> : <Header Value>

26. 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.,

27. MIME Headers
• MIME mainly consists of 5 header:
• MIME - Version
• Content type
• Content transfer encoding
• Content ID
• Content Description

28. MIME Headers

29. Data types and subtypes in MIME

30. Content Transfer Encoding

32. Message Transfer

33. Introduction
• Once the mails are composed they are transferred to the destination using
Mail Transfer Protocols.
• Some of the popular Mail Transfer Protocols are
• SMTP – Simple Mail Transfer Protocol
• POP – Post Office Protocol
• IMAP – Internet Message Access Protocol

34. SMTP
• The actual mail transfer is done through the Mail Transfer Agents.
• 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.

35. • SMTP simply defines how commands and responses must be sent back
and forth.

36. SMTP Commands

37. SMTP Responses

38. Connection Establishment

39. Mail Transfer

40. Connection Termination

41. Message Reader / Message Access

42. Introduction
• 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

43. POP 3
• Post Office Protocol Version 3 (POP 3)
• 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.

44. Modes of POP 3
• 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.

45. Exchange of Commands and Responses in POP 3

46. IMAP 4
• 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.

47. POP 3 Vs IMAP 4

48. My Official Account – POP 3 Setting

49. My Official account - IMAP Settings

50. MY Personal Account

51. Video Presentation on E - Mail

52. End
of
E - Mail

53. World Wide Web - WWW

54. Introduction
• The WWW is a repository of information
linked together from points all over the
world.
• The original goal of the web was to find a way to organize and retrieve information about
hyper linked documents.
• WWW uses HTTP Protocol to access the webpages on the internet. (Will be discussed
shortly)

55. WWW Architecture

56. Clients (Browsers)
1. Controller – Receives i/p from keyboard / mouse and uses the client program to access the documents.
2. Client protocol – This can be of any protocol discussed before like FTP, HTTP Etc.,
3. Interpreters – This can be any interpreter like java, Flash or HTML to display the appropriate content
CLIENT
(BROWSERS)
 There are variety of browsers available that interprets and displays
a web document.
 Every client consists of three parts

57. Clients (Browsers)

58. Server
• The webpage is stored at the server
• Each time the request is received the corresponding document
is sent to the client.
• The server can be more efficient by enabling “Multithreading”
(Answering Multiple requests)

59. URL – Uniform Resource Locator
• When a page needs to be accessed it must have a address.
• HTTP uses locators to access the webpages available at widely distributed areas.
• URL is a standard for specifying any kind of information on the internet.
• URL defines 4 Important things:

60. Example URL

61. HTTP – Hyper Text Transfer Protocol

62. Introduction
• The Hyper Text Transfer Protocol (HTTP) is mainly used to access the data on the
world wide web.
• HTTP is the combination of FTP and SMTP.
• It is like FTP because it uses TCP Connection.
• It is like SMTP because data transferred between the server and client looks like
SMTP messages.

63. HTTP Transaction
• The client initiates the transaction by sending a request message and the
server replies through an response message.

64. Formats of Request and Response Messages

65. Request Line and Status Line

66. Request Type

67. Status Code
• This field indicates the status of the request through codes.
• Codes in the range of
• 100  informational
• 200  Successful Request
• 300  Redirect the client to another URL
• 400  Error at client
• 500  Error at server

68. Status Codes and their Phrases

69. Contd..

70. Header
• The format of the header is shown in the figure.
• The request header and Response header have different values.

71. Request Header

72. Response Header

73. End
of
HTTP

74. Web Services

75. End
of
Web Services

76. Domain Name System - DNS

77. End
of
DNS

78. Simple Network Management Protocol - SNMP

79. End
of
SNMP