Professional Documents
Culture Documents
Unit 5 CN
Unit 5 CN
Application layer
DNS--Domain Name System:
This is primarily used for mapping host and e-mail destinations to IP addresses but can
also be used other purposes. DNS is defined in RFCs 1034 and 1035.
Working:-
To map a name onto an IP address, an application program calls a library
procedure called Resolver, passing it the name as a parameter.
The resolver sends a UDP packet to a local DNS server, which then looks up the
name and returns the IP address to the resolver, which then returns it to the caller.
Armed with the IP address, the program can then establish a TCP connection with
the destination, or send it UDP packets.
The DNS name space.
Resource Records.
Name Servers.
Domain names can be either absolute (ends with a period e.g. eng.sum.com) or
relative (doesn’t end with a period). Domain names are case sensitive and the component
names can be up to 63 characters long and full path names must not exceed 255
characters.
When a resolver has a query about a domain name, it passes the query to one of the local
name servers:
1. If the domain being sought falls under the jurisdiction of name server, it returns the
authoritative resource records ( that comes from the authority that manages the
record, and is always correct).
2. If the domain is remote and no information about the requested domain is available
locally the name server sends a query message to the top level name server for the
domain requested.
Eg: A resolver of flits.cs.vle.nl wants to know the IP address of the host
Linda.cs.yale.edu
Step 1: Resolver sends a query containing domain name sought the type and the class to
local name server, cs.vu.nl.
Step 2: Suppose local name server knows nothing about it, it asks few others near by
name servers. If none of them know, it sends a UDP packet to the server for edu-
server.net.
Step 3: This server knows nothing about Linda.cs.yale.edu or cs.yale.edu and so it
forwards the request to the name server for yale.edu.
Step 4: This one forwards the request to cs.yale.edu which must have authoritative
Resource records.
Step 5 to 8: The resource record requested works its way back in steps 5-8. This
query method is known as Recursive Query
3. When a query cannot be satisfied locally, the query fails but the name of the next
server along the line to try is returned.
Simple Network Management Protocol
SNMP - Version 1
SNMP - Version 2
SNMP - Version 3
SNMP was developed for use as a n/w management tool for N/W and internet
works operating TCP/IP. It includes the following key elements:
1. Management Station or Manager 3. Management Information Base
2. Agent 4. N/W Management Protocol
Management Station serves as interface for human N/W manager into network
Management system. It will have the following:
1. A set of management applications for data analysis fault recovery and so on.
2. An interface by which the n/w manager may monitor and control the n/w.
3. The capability of translation the n/w managers requirements into the actual
monitoring and control of remote elements in the n/w.
4. A data base of n/w management information extracted from the databases of
all the managed entities in the n/w.
Management Agent software equips key platforms such as hosts, Bridges, routers and
hubs so that they may be managed from a management station. The agent responds to
requests for information from a management station, responds to requests for actions
from management station, and may asynchronously provide management station with
important but unsolicited information.
To manage resources in the n/w, each resource is represented as an object (a data
variable that represents one aspect of managed agent). The collection of objects is
referred to as a Management Information Base (MIB). The MIB functions as a
collection of access points at the agent for management station. A management station
performs the monitoring function by retrieving the value of MIB objects.
The management station and agents are linked by a n/w management protocol.
The protocol used for the management of TCP/IP network is SNMP. Each of these
protocols includes the following key capabilities:
GET: Enables the management station to retrieve the value of objects at the
agent
SET: Enables the management station to set the value of objects at the agent
NOTIFY: Enables an agent to send unsolicited notifications to management
station of Significant events
SNMP – V1 Configuration:
Role of SNMP-V2 :
(b). Response-PDU:
PDU type Req-id Error-status Error-index Variable-bindings
(c). Get-Bulk-Request-PDU:
SNMP-V3: This defines an over all SNMP architecture and a set of security
capabilities .It provides 3 important services:
Authentication
Privacy Part of User-Based Security Model (USM)
Access Control Defined in View-Based Access Control Model (VACM)
(2). The User Agent: It is normally a program that accepts a variety of commands
for composing, receiving and replying to messages as well as for
manipulating mail boxes.
Sending E-mail: To do so, User must provide the messages, the destination address
and possibly some other parameters (Eg: the priority (or) security level). The message
can be produced with a free-standing text editor, a word processing program or
possibly with a text editor built into the user agent. The destination address must be in
a format that the user agent can deal with. Many user agents expect DNS address of
the form mailbox @ location.
Reading E-mail : When a user agent is started up, it will look at the user’s mailbox
for incoming mail before displaying anything on the screen. Then it may announce
the no. of messages in the mailbox or display a one-line summary of each one and
wait for a command. Each display line contains several fields(extracted from the
header of the corresponding message) like……..
Eg:
# Flags Bytes Sender Subject
Message Formats :
RFC 822 (SMTP)
RFC 1551 (MIME)
(1). RFC 822 :
Messages consist of a primitive envelope, some no. of header fields, a blank
line and then the message body. Each header field consists of a single line of ASCII text
containing the fieldname, a colon and a value. The principal header fields related to
message transport one :
After the headers, comes the message body. Users can put whatever they want
here.
(outgoing-mail)
(Incoming-mail)
Compression:
HTTP:
o HTTP stands for Hyper Text Transfer Protocol.
o It is a protocol used to access the data on the World Wide Web (www).
o The HTTP protocol can be used to transfer the data in the form of plain
text, hypertext, audio, video, and so on.
o This protocol is known as HyperText Transfer Protocol because of its
efficiency that allows us to use in a hypertext environment where there are
rapid jumps from one document to another document.
o HTTP is similar to the FTP as it also transfers the files from one host to
another host. But, HTTP is simpler than FTP as HTTP uses only one
connection, i.e., no control connection to transfer the files.
o HTTP is used to carry the data in the form of MIME-like format.
o HTTP is similar to SMTP as the data is transferred between client and
server. The HTTP differs from the SMTP in the way the messages are sent
from the client to the server and from server to the client. SMTP messages
are stored and forwarded while HTTP messages are delivered immediately.
Features of HTTP:
o Connectionless protocol: HTTP is a connectionless protocol. HTTP client
initiates a request and waits for a response from the server. When the
server receives the request, the server processes the request and sends
back the response to the HTTP client after which the client disconnects the
connection. The connection between client and server exist only during
the current request and response time only.
o Media independent: HTTP protocol is a media independent as data can
be sent as long as both the client and server know how to handle the data
content. It is required for both the client and server to specify the content
type in MIME-type header.
o Stateless: HTTP is a stateless protocol as both the client and server know
each other only during the current request. Due to this nature of the
protocol, both the client and server do not retain the information between
various requests of the web pages.
HTTP Transactions
The above figure shows the HTTP transaction between client and server. The
client initiates a transaction by sending a request message to the server. The
server replies to the request message by sending a response message.
Messages
HTTP messages are of two types: request and response. Both the message types
follow the same message format.
Request Message: The request message is sent by the client that consists of a
request line, headers, and sometimes a body.
Response Message: The response message is sent by the server to the client that
consists of a status line, headers, and sometimes a body.
Uniform Resource Locator (URL)
o A client that wants to access the document in an internet needs an address
and to facilitate the access of documents, the HTTP uses the concept of
Uniform Resource Locator (URL).
o The Uniform Resource Locator (URL) is a standard way of specifying any
kind of information on the internet.
o The URL defines four parts: method, host computer, port, and path.