diagam , eaplan

theteem phyctea topolo98

laid o t
plugicasly
fow bate topoloas
mesh, ata,Busi Piag

() Mesh toploag:

tattor
Staton Station

tati em Station

device haadetli'cateo
- to othe denee.
poit poit
oy bl w two deves Cone to
we need nen-) physteal lie in Juiy
Couneeko Meh n Wodey
 ue gaueoke es thot ealh Coune chay
Adav: o delcateol
oon dot loa d,tuas otinotr
Lan ca
Mt bytHple deue.

teuplo aegioual
t e s houd eoked
e couveote d wy ote egtoval
ottie,
tuh

Stottan

eaeh denie Jhu deoicateo

detl Coutoley
pot-to -pornt lints owty
ujually elallee? hub

the CoroY ats as

es lape thon meel

A<tau topo og4
topolag to co et
2ach device eol o y rt

tiu make loy

tr
 (3)Bustope lay

Calole uel

Bu topo loay muti pot

aatt
a

Conetel to buy Cable

cowwerti
blw the devie, man celale
Cot
a

man Cabe to heat Coutat

mtaic
to asta
bw wwes bey calbee tton mesh )stattyploy
recunee Zolottm
Dihut
Dilt to adal conetim,

Stotto

Repeot

eaeh device hy
ng to poloy ee
de clr coteal to -pont
pot
tuo
with eny
 wtil rachs s erhvation
deie to dee

A datiey enty do stall ¬,

Rmey to po doay
Guly

Cau disahy a
Dis:
Type of Connection :

A network is two or more devices connected through links. A link is a communications pathway that
transfers data from one device to another.
There are two possible types of connections:

Point-to-Point -A point-to-point connection provides a dedicated link between two devices.The entire
capacity of the link is reserved for transmission between those two devices. Most point-to-point
connections use an actual length of wire or cable to connect the two ends, but other options, such as
microwave or satellite links, are also possible (see Figure a).
example-When we change television channels by infrared remote control, we are establishing apoint-
to-point connection between the remote control and the television’s control system.

Multipoint A multipoint (also called multidrop) connection is one in which more than two specific
devices share a single link (see Figure b)
a multipoint environment, the capacity of the channel is shared, either spatially or temporally.If several
devices can use the link simultaneously, it is a spatially shared connection. If users must take turns, it is
a timeshared connection.

2.With relevant diagrams, explain LAN,WAN and Internetwork

Local Area Network (LAN)
A local area network (LAN) is usually privately owned and connects some hosts in a single office, building, or
campus. Depending on the needs of an organization,
A LAN can be as simple as two PCs and a printer in someone’s home office, or it can extend throughout a
company and include audio and video devices.
Each host in a LAN has an identifier, an address, that uniquely defines the host in the LAN. A packet sent by a
host to another host carries both the source host’s and the destination host’s addresses.
Wide Area Network
A wide area network (WAN) is also an interconnection of devices capable of communication. However, it. We
see two distinct examples of WANs today: point-to-point WANs and switched WANs.
Point-to-Point WAN
A point-to-point WAN is a network that connects two communicating devices through a transmission media
(cable or air).

Switched WAN
A switched WAN is a network with more than two ends. A switched WAN, is used in the backbone of global
communication today. We can say that a switched WAN is a combination of several point-to-point WANs that
are connected by switches..

Internetwork
Today, it is very rare to see a LAN or a WAN in isolation; they are connected to one another. When two or more
networks are connected, they make an internetwork, or internet.
example- Assume that an organization has two offices, one on the east coast and the other on the west coast.
Each office has a LAN that allows all employees in the office to communicate with each other.

fig: An network made of two LAN and point-to-point dedicated WAN

When a host in the west coast office sends a message to another host in the same office, the router blocks the
message, but the switch directs the message to the destination. On the other hand, when a host on the west
coast sends a message to a host on the east coast, router R1 routes the packet to router R2, and the packet
reaches the destination. Figure shows another internet with several LANs and WANs connected. One of the
WANs is a switched WAN with fourswitches.

3.With relevant diagrams, explain encapsulation and decapsulation in TCP/IP protocol suite.

Encapsulation and Decapsulation

One of the important concepts in protocol layering in the Internet is encapsulation/ decapsulation. Figure
shows this concept for the small internet
Figure show the encapsulation in the source host, decapsulation in the destination host, and
encapsulation and decapsulation in the router.
Encapsulation at the Source Host
 At the application layer, the data to be exchanged is referred to as a message. A message
normally does not contain any header or trailer, but if it does, we refer to the whole as the
message. The message is passed to the transport layer.
 The transport layer takes the message as the payload, the load that the transport layer should take
care of. It adds the transport layer header to the payload, which contains the identifiers of the
source and destination application programs that want to communicate plus some more
information that is needed for the end-to end delivery of the message, such as information
needed for flow, error control, or congestion control. The result is the transport- layer packet,
which is called the segment (in TCP) and the user datagram (in UDP). The transport layer then
passes the packet to the network layer.
 The network layer takes the transport-layer packet as data or payload and adds its own header to
the payload. The header contains the addresses of the source and destination hosts and some
more information used for error checking of the header, fragmentation information, and so on.
The result is the network-layer packet, called a datagram. The network layer then passes the
packet to the data link layer.
 The data-link layer takes the network-layer packet as data or payload and adds its own header,
which contains the link-layer addresses of the host or the next hop (the router). The result is the
link-layer packet, which is called a frame. The frame is passed to the physical layer for
transmission.
Decapsulation and Encapsulation at the Router
 At the router, we have both decapsulation and encapsulation because the router is connectedto
two or more links.
 After the set of bits are delivered to the data-link layer, this layer decapsulates the datagram from
the frame and passes it to the network layer.
 The network layer only inspects the source and destination addresses in the datagram header and
consults its forwarding table to find the next hop to which the datagram is to be delivered. The
contents of the datagram should not be changed by the network layer in the router unless there is
a need to fragment the datagram if it is too big to be passed through the next link. The datagram
is then passed to the data-link layer of the next link.
 The data-link layer of the next link encapsulates the datagram in a frame and passes it to the
physical layer for transmission.
Decapsulation at the Destination Host
 At the destination host, each layer only decapsulates the packet received, removes the
payload,and delivers the payload to the next-higher layer protocol until the message reaches the
application layer. It is necessary to say that decapsulation in the host involves error checking.
4.Explain circuit switched network and packet switched network in with a neat diagram.

Circuit-Switched Network:
In a circuit-switched network, a dedicated connection, called a circuit, is always availablebetween the two end
systems; the switch can only make it active or inactive(continuous communication between two telephone).
FIG shows a very simple switched network that connects four telephones to each end. We have used
telephone sets instead of computers asan end system because circuit switching was very common in
telephone networks in the past,

fig : Circuit-Switched Network

The thick line connecting two switches is a high-capacity communication line that can handle four voice
communications at the same time; the capacity can be shared between all pairs of telephone sets. The
switches used in this example have forwarding tasks but no storing capability.

Let us look at two cases.

In the first case, all telephone sets are busy; four people at one site are talking with four people at the other
site; the capacity of the thick line is fully used.
In the second case, only one telephone set at one side is connected to a telephone set at the other side; only
one-fourth of the capacity of the thick line is used. This means that a circuit- switched network is efficient only
when it is working at its full capacity; most of the time, it is inefficient because it is working at partial capacity.

Packet-Switched Network:
In a computer network, the communication between the two computers is done in blocks of data called
packets
This allows switches to function for both storing and forwarding because a packet is an independent entity that
can be stored and sent later. Fig shows a small packet-switched network that connects four computers at one
site to four computers at the other site.

fig: Packet-Switched Network

A router in a packet-switched network has a queue that can store and forward the packet.

Example- Now assume that the capacity of the thick line is only twice the capacity of the data line connecting
the computers to the routers.
If only two computers (one at each site) need to communicate with each other, there is no waiting for the
packets. However, if packets arrive at one router when the thick line is already working at its full capacity, the
packets should be stored and forwarded in the order they arrived. The two simple examples show that a
packet-switched network is more efficient than a circuit switched network, but the packets may encounter
some delays.
5.Mention the differences between TCP/IP protocol suite and OSI model and explain why
OSI model has lack of success
When we compare the two models, we find that two layers, session and presentation, are missing from the
TCP/IP protocol suite. These two layers were not added to the TCP/IP protocolsuite after the publication of the
OSI model. The application layer in the suite is usually considered to be the combination of three layers in the
OSI model, as shown in Figure .

Two reasons were mentioned for this decision. First, TCP/IP has more than one transport-layer protocol. Some
of the functionalities of the session layer are available in some of the transport- layer protocols.

Second, the application layer is not only one piece of software. Many applications can be developed at this
layer. If some of the functionalities mentioned in the session and presentation layers are needed for a
particular application, they can be included in the development of that piece of software.

Lack of OSI Model’s Success:

When OSI model was introduced , many experts thought that the TCP/IP would fully be replaced but it was not
so due to following reasons:

1. OSI was completely functional and lot of time and money had been spent on TCP/IP Suite
2. Layers like Presentation and Session in OSI model did not have well defined protocols
3. For certain applications in Internet , the performance of OSI model was not very high.

6.With a neat diagram, explain significance of all layers in TCP/IP protocol suite.

Physical Layer
 Physical layer is responsible for carrying individual bits in a frame across the link. Although the physical
layer is the lowest level in the TCP/IP protocol suite, the communication between two devices at the
physical layer is still a logical communication because there is another, hidden layer, the transmission
media, under the physical layer.
 The following are the main responsibilities of the physical layer Definition of Hardware
Specifications, Encoding and Signalling, Data Transmission and Reception, Topology and Physical
Network Design
Data-link Layer
 Internet is made up of several links (LANs and WANs) connected by routers. The data-link layer is
responsible for taking the datagram and moving it across the link. (node to node communication)
 The link can be a wired LAN with a link-layer switch, a wireless LAN, a wired WAN, or a wireless WAN.
We can also have different protocols used with any link type.
 In each case, the data-link layer is responsible for moving the packet through the link. TCP/IP does not
define any specific protocol for the data-link layer.
  It supports all the standard and proprietary protocols. The data-link layer takes a datagram and
encapsulates it in a packet called a frame
Network Layer
 The network layer is responsible for creating a connection between the source computer and the
destination computer. The communication at the network layer is host-to-host. However, since there
can be several routers from the source to the destination, the routers in the path are responsible for
choosing the best route for each packet.
 The network layer is responsible packetizing and routing and forwarding the packet through possible
routes. others services are error and flow control, congestion control.
 The network layer in the Internet includes the main protocol, Internet Protocol (IP), that defines the
format of the packet, called a datagram at the network layer. IP also defines the format and the
structure of addresses used in this layer.
Transport Layer
 The logical connection at the transport layer is also end-to-end. The transport layer at the source host
gets the message from the application layer, encapsulates it in a transport layer packet (called a
segment or a user datagram in different protocols) and sends it, through the logical (imaginary)
connection, to the transport layer at the destination host.
 The transport layer is responsible for giving services to the application layer: to get a message from an
application program running on the source host and deliver it to the corresponding application program
on the destination host. (process to process communication)

There are more than one protocol in the transport layer:

 The main protocol, Transmission Control Protocol (TCP), is a connection-oriented protocol that first
establishes a logical connection between transport layers at two hosts before transferring data. It
creates a logical pipe between two TCPs for transferring a stream of bytes.
 User Datagram Protocol (UDP), is a connectionless protocol that transmits user datagrams without first
creating a logical connection. In UDP, each user datagram is an independent entity without being related
to the previous or the next one (the meaning of the term connectionless).
Application Layer
 As Figure shows, the logical connection between the two application layers is end to-end. The two
application layers exchange messages between each other as though there were a bridge between the
two layers.
 However, communication is done through all the layers.
 Communication at the application layer is between two processes (two programs running at this layer).
To communicate, a process sends a request to the other process and receives a response. Process-to-
process communication is the duty of the application layer
The application layer in the Internet includes many predefined protocols.

 The Hypertext Transfer Protocol (HTTP) is a vehicle for accessing the World Wide Web(WWW).
 The Simple Mail Transfer Protocol (SMTP) is the main protocol used in electronic mail (e-mail)
service.
 The File Transfer Protocol (FTP) is used for transferring files from one host to another.
 The Terminal Network (TELNET) and Secure Shell (SSH) are used for accessing a site remotely.
7.Compare connectionless and connection-oriented protocols in transport layer.

S.NO Connection-oriented Service Connection-less Service

Connection-oriented service is related to the Connection-less service is related to the

1. telephone system. postal system.

Connection-oriented service is preferred by Connection-less Service is preferred by

2. long and steady communication. bursty communication.

Connection-less Service is not

Connection-oriented Service is necessary.
3. compulsory.

4. Connection-oriented Service is feasible. Connection-less Service is not feasible.

In connection-oriented Service, Congestion In connection-less Service, Congestion

5. is not possible. is possible.

Connection-oriented Service gives the Connection-less Service does not give

6. guarantee of reliability. a guarantee of reliability.

In connection-oriented Service, Packets In connection-less Service, Packets do

7. follow the same route. not follow the same route.

Connection-oriented services require a Connection-less Service requires a

8. bandwidth of a high range. bandwidth of low range.

9. Ex: TCP (Transmission Control Protocol) Ex: UDP (User Datagram Protocol)

9.Explain TCP connection establishment using three way handshaking.

Three-Way Handshaking:
 The connection establishment in TCP is called three-way handshaking.
 In our example, an application program, called the client, wants to make a connection with
another application program, called the server, using TCP as the transport-layer protocol.
 The process starts with the server. The server program tells its TCP that it is ready to accept a
connection.
 This request is called a passive open. Although the server TCP is ready to accept a connection
from any machine in the world, it cannot make the connection itself.
 The client program issues a request for an active open. A client that wishes to connect to an
open server tells its TCP to connect to a particular server.
 TCP can now start the three-way handshaking process, as shown in Figure
 To show the process we use timelines. Each segment has values for all its header fields and
perhaps for some of its option fields too. We show only the few fields necessary to understand
each phase.
 We show the sequence number, the acknowledgment number, the control flags (only those that
are set), and window size if relevant. The three steps in this phase are as follows.

1. The client sends the first segment, a SYN segment, in which only the SYN flag is set. This
segment is for synchronization of sequence numbers. The client in our example chooses a
random number as the first sequence number and sends this number to the server. This sequence
number is called the initial sequence number (ISN). Note that this segment does not contain an
acknowledgment number. It does not define the window size either; a window size definition
makes sense only when a segment includes an acknowledgment. The segment can also include
some options that we discuss later in the chapter. Note that the SYN segment is a control
segment and carries no data. However, it consumes one sequence number because it needs to be
acknowledged. We can say that the SYN segment carries one imaginary byte.
A SYN segment cannot carry data, but it consumes one sequence number.

2. The server sends the second segment, a SYN + ACK segment with two flag bits set as: SYN and
ACK. This segment has a dual purpose. First, it is a SYN segment for communication in the
other direction. The server uses this segment to initialize a sequence number for numbering the
bytes sent from the server to the client. The server also acknowledges the receipt of the SYN
segment from the client by setting the ACK flag and displaying the next sequence number it
expects to receive from the client. Because the segment contains an acknowledgment, it also
needs to define the receive window size, rwnd (to be used by the client), as we will see in the
flow control section. Since this segment is playing the role of a SYN segment, it needs to be
acknowledged. It, therefore, consumes one sequence number.
A SYN 1 ACK segment cannot carry data, but it does consume one sequence number.

3. The client sends the third segment. This is just an ACK segment. It acknowledges the receipt of
the second segment with the ACK flag and acknowledgment number field. Note that the ACK
segment does not consume any sequence numbers if it does not carry data, but some
implementations allow this third segment in the connection phase to carry the first chunk of data
 from the client. In this case, the segment consumes as many sequence numbers as the number of
data bytes.
An ACK segment, if carrying no data, consumes no sequence number.

10.Explain UDP services along with the neat diagram of Pseudoheader for checksum.

UDP Services
Process-to-Process Communication
UDP provides process-to-process communication using socket addresses, a combination of IP addresses
and port numbers.

Connectionless Services
 UDP provides a connectionless service. This means that each user datagram sent by UDP is an
independent datagram.
 There is no relationship between the different user datagrams even if they are coming from the
same source process and going to the same destination program. The user datagrams are not
numbered.
 Also, unlike TCP, there is no connection establishment and no connection termination. This
means that each user datagram can travel on a different path.
 One of the ramifications of being connectionless is that the process that uses UDP cannot send a
stream of data to UDP and expect UDP to chop them into different, related user datagrams.
 Instead, each request must be small enough to fit into one user datagram. Only those processes
sending short messages, messages less than 65,507 bytes (65,535 minus 8 bytes for the UDP
header and minus 20 bytes for the IP header), can use UDP.

Flow Control
 UDP is a simple protocol. There is no flow control, and hence no window mechanism.
 The receiver may overflow with incoming messages.
 The lack of flow control means that the process using UDP should provide for this service, if
needed.

Error Control
 There is no error control mechanism in UDP except for the checksum.
 This means that the sender does not know if a message has been lost or duplicated.
 When the receiver detects an error through the checksum, the user datagram is silently discarded.
 The lack of error control means that the process using UDP should provide for this service, if
needed.

Checksum
 UDP checksum calculation includes three sections: a pseudoheader, the UDP header, and the
data coming from the application layer.
 The pseudoheader is the part of the header of the IP packet in which the user datagram is to be
encapsulated with some fields filled with 0s (see Figure).
 If the checksum does not include the pseudoheader, a user datagram may arrive safe and sound.
However, if the IP header is corrupted, it may be delivered to the wrong host.
 The protocol field is added to ensure that the packet belongs to UDP, and not to TCP.
 The value of the protocol field for UDP is 17. If this value is changed during transmission, the
checksum calculation at the receiver will detect it and UDP drops the packet. It is not delivered
to the wrong protocol.
 Pseudoheader for checksum calculation

11.Describe sending and receving buffers in TCP and explain how the segments are created from
the bytes in the buffers.

Sending and Receiving Buffers

 Because the sending and the receiving processes may not necessarily write or read data at the
same rate, TCP needs buffers for storage.
 There are two buffers, the sending buffer and the receiving buffer, one for each direction.
 One way to implement a buffer is to use a circular array of 1-byte locations as shown in Figure.
 For simplicity, we have shown two buffers of 20 bytes each; normally the buffers are hundreds
or thousands of bytes, depending on the implementation.
 We also show the buffers as the same size, which is not always the case. The figure shows the
movement of the data in one direction.
 At the sender, the buffer has three types of chambers. The white section contains empty
chambers that can be filled by the sending process (producer).
 The coloured area holds bytes that have been sent but not yet acknowledged. The TCP sender
keeps these bytes in the buffer until it receives an acknowledgment.
 The shaded area contains bytes to be sent by the sending TCP. This could be due to the
slowness of the receiving process or to congestion in the network.
 After the bytes in the coloured chambers are acknowledged, the chambers are recycled and
available for use by the sending process. This is why we show a circular buffer.
 The operation of the buffer at the receiver is simpler. The circular buffer is divided into two
areas (shown as white and coloured).
 The white area contains empty chambers to be filled by bytes received from the network. The
coloured sections contain received bytes that can be read by the receiving process.
 When a byte is read by the receiving process, the chamber is recycled and added to the pool of
empty chambers.
Fig. Sending and receiving buffers
12.Explain the architecture and format of electronic mail.
Architecture
To explain the architecture of e-mail, we give a common scenario, as shown in Figure. Another
possibility is the case in which Alice or Bob is directly connected to the corresponding mail server, in
which LAN or WAN connection is not required.

 In the common scenario, the sender and the receiver of the e-mail, Alice and Bob respectively,
are connected via a LAN or a WAN to two mail servers.
 The administrator has created one mailbox for each user where the received messages are stored.
 A mailbox is part of a server hard drive, a special file with permission restrictions. Only the
owner of the mailbox has access to it.
 The administrator has also created a queue (spool) to store messages waiting to be sent.
 A simple e-mail from Alice to Bob takes nine different steps, as shown in the figure.
 Alice and Bob use three different agents: a user agent (UA), a message transfer agent (MTA),
and a message access agent (MAA).
 When Alice needs to send a message to Bob, she runs a UA program to prepare the message and
send it to her mail server.
 The mail server at her site uses a queue (spool) to store messages waiting to be sent. The
message, however, needs to be sent through the Internet from Alice’s site to Bob’s site using an
MTA.
 Here two message transfer agents are needed: one client and one server.
 Like most client-server programs on the Internet, the server needs to run all the time because it
does not know when a client will ask for a connection.
 The client, on the other hand, can be triggered by the system when there is a message in the
queue to be sent.
 The user agent at the Bob site allows Bob to read the received message. Bob later uses an MAA
client to retrieve the message from an MAA server running on the second server.
 There are two important points we need to emphasize here. First, Bob cannot bypass the mail
server and use the MTA server directly.
 To use the MTA server directly, Bob would need to run the MTA server all the time because he
does not know when a message will arrive.
 This implies that Bob must keep his computer on all the time if he is connected to his system
through a LAN.
 If he is connected through a WAN, he must keep the connection up all the time. Neither of these
situations is feasible today.
  Second, note that Bob needs another pair of client-server programs: message access programs.
 This is because an MTA client-server program is a push program: the client pushes the message
to the server. Bob needs a pull program. The client needs to pull the message from the server.

Format
1. Sending Mail
To send mail, the user, through the UA, creates mail that looks very similar to postal mail. It has an
envelope and a message (see Figure). The envelope usually contains the sender address, the receiver
address, and other information. The message contains the header and the body. The header of the
message defines the sender, the receiver, the subject of the message, and some other information. The
body of the message contains the actual information to be read by the recipient.

2. Receiving Mail
The user agent is triggered by the user (or a timer). If a user has mail, the UA informs the user with a
notice. If the user is ready to read the mail, a list is displayed in which each line contains a summary of
the information about a particular message in the mailbox. The summary usually includes the sender
mail address, the subject, and the time the mail was sent or received. The user can select any of the
messages and display its contents on the screen.

3. Addresses
To deliver mail, a mail handling system must use an addressing system with unique addresses. In the
Internet, the address consists of two parts: a local part and a domain name, separated by an @ sign (see
Figure). The local part defines the name of a special file, called the user mailbox, where all the mail
received for a user is stored for retrieval by the message access agent. The second part of the address is
the domain name. An organization usually selects one or more hosts to receive and send e-mail; they are
sometimes called mail servers or exchangers. The domain name assigned to each mail exchanger either
comes from the DNS database or is a logical name (for example, the name of the organization).
4. Mailing List or Group List
Electronic mail allows one name, an alias, to represent several different e-mail addresses; this is called a
mailing list. Every time a message is to be sent, the system checks the recipient’s name against the alias
database; if there is a mailing list for the defined alias, separate messages, one for each entry in the list,
must be prepared and handed to the MTA.

8.Illustrate with the flow diagram, why the size of the send window must be less than 2 m in Go
Back N protocol and analyse.
Send Window Size
 We can now show why the size of the send window must be less than 2 𝑚. As an example, we
choose m = 2, which means the size of the window can be 2 𝑚 − 1, or 3.
 Figure compares a window size of 3 against a window size of 4. If the size of the window is 3
(less than 2𝑚) and all three acknowledgments are lost, the only timer expires, and all three
packets are resent.
 The receiver is now expecting packet 3, not packet 0, so the duplicate packet is correctly
discarded. On the other hand, if the size of the window is 4 (equal to 22 ) and all
acknowledgments are lost, the sender will send a duplicate of packet 0.
 However, this time the window of the receiver expects to receive packet 0 (in the next cycle),
so it accepts packet 0, not as a duplicate, but as the first packet in the next cycle. This is an
error.
 This shows that the size of the send window must be less than 2m

Send window size for Go-Back-N

16.Illustrate with the flow diagram, why the size of the sender and receiver window can be atmost
one half of 2m in Selective repeat protocol and analyse.

Window Sizes
 We can now show why the size of the sender and receiver windows can be at most one-half of
2𝑚. For an example, we choose m = 2, which means the size of the window is 2𝑚/2 or 2(𝑚−1)= 2.
 Figure compares a window size of 2 with a window size of 3. If the size of the window is 2 and
all acknowledgments are lost, the timer for packet 0 expires and packet 0 is resent.
 However, the window of the receiver is now expecting packet 2, not packet 0, so this duplicate
packet is correctly discarded (the sequence number 0 is not in the window).
  When the size of the window is 3 and all acknowledgments are lost, the sender sends a duplicate
of packet 0.
 This time, the window of the receiver expects to receive packet 0 (0 is part of the window), so it
accepts packet 0, not as a duplicate, but as a packet in the next cycle. This is clearly an error.

Selective-Repeat, window size

14.Explain World wide web and web documents with a neat diagram
World Wide Web

 The WWW today is a distributed client-server service, in which a client using a browser can
access a service using a server.
 The service provided is distributed over many locations called sites. Each site holds one or more
web pages.
 Each web page can contain some links to other web pages in the same or other sites. A web page
can be simple or composite.
 A simple web page has no links to other web pages; a composite web page has one or more links
to other web pages. Each web page is a file with a name and address.

Web Documents
The documents in the WWW can be grouped into three broad categories: static, dynamic, and active.
Static Documents
 Static documents are fixed-content documents that are created and stored in a server. The client
can get a copy of the document only.
 The contents of the file are determined when the file is created, not when it is used. Of course,
the contents in the server can be changed, but the user cannot change them.
Dynamic Documents
 A dynamic document is created by a web server whenever a browser requests the document.
 When a request arrives, the web server runs an application program or a script that creates the
dynamic document.
 The server returns the result of the program or script as a response to the browser that requested
the document
Active Documents
 For many applications, we need a program or a script to be run at the client site. These are called
active documents.
 For example, suppose we want to run a program that creates animated graphics on the screen or a
program that interacts with the user.
17.With a neat diagram explain FTP.
FTP: File Transfer Protocol
 File Transfer Protocol (FTP) is the standard protocol provided by TCP/IP for copying a file from
one host to another.
 Although transferring files from one system to another seems simple and straightforward, some
problems must be dealt with first.
 For example, two systems may use different file name conventions. Two systems may have
different ways to represent data. Two systems may have different directory structures.
 All of these problems have been solved by FTP in a very simple and elegant approach. Although
we can transfer files using HTTP, FTP is a better choice to transfer large files or to transfer files
using different formats.
 Figure shows the basic model of FTP.

 The client has three components: the user interface, the client control process, and the client data
transfer process.
 The server has two components: the server control process and the server data transfer process.
 The control connection is made between the control processes. The data connection is made
between the data transfer processes.
 Separation of commands and data transfer makes FTP more efficient. The control connection
uses very simple rules of communication.
 We need to transfer only a line of command or a line of response at a time. The data connection,
on the other hand, needs more complex rules due to the variety of data types transferred.

18.Explain application layer paradigms.

Application-Layer Paradigms
 To use the Internet, we need two application programs to interact with each other: one running
on a computer somewhere in the world, the other running on another computer somewhere else
in the world.
 The two programs need to send messages to each other through the Internet infrastructure.
 Two paradigms have been developed during the lifetime of the Internet to answer this question:
the client-server paradigm and the peer-to-peer paradigm
Traditional Paradigm: Client-Server
 The traditional paradigm is called the client-server paradigm. It was the most popular paradigm
until a few years ago.
 In this paradigm, the service provider is an application program, called the server process; it runs
continuously, waiting for another application program, called the client process, to make a
connection through the Internet and ask for service.
 There are normally some server processes that can provide a specific type of service, but there
are many clients that request service from any of these server processes.
  The server process must be running all the time; the client process is started when the client
needs to receive service. The client-server paradigm is similar to some available services out of
the territory of the Internet.

For example, a telephone directory center in any area can be thought of as a server; a subscriber that
calls and asks for a specific telephone number can be thought of as a client.

New Paradigm: Peer-to-Peer

 A new paradigm, called the peer-to-peer paradigm (often abbreviated P2P paradigm) has
emerged to respond to the needs of some new applications.
 In this paradigm, there is no need for a server process to be running all the time and waiting for
the client processes to connect.
 The responsibility is shared between peers. A computer connected to the Internet can provide
service at one time and receive service at another time.
 A computer can even provide and receive services at the same time. Figure shows an example of
communication in this paradigm.
20. Explain Local verses remote logging in TELNET.

Local versus Remote Logging

 When a user logs into a local system, it is called local logging. As a user types at a terminal or at
a workstation running a terminal emulator, the keystrokes are accepted by the terminal driver.
 The terminal driver passes the characters to the operating system. The operating system, in turn,
interprets the combination of characters and invokes the desired application program or utility.
 When a user wants to access an application program or utility located on a remote machine, she
performs remote logging. Here the TELNET client and server programs come into use.
 The user sends the keystrokes to the terminal driver where the local operating system accepts the
characters but does not interpret them.
 The characters are sent to the TELNET client, which transforms the characters into a universal
character set called Network Virtual Terminal (NVT) characters and delivers them to the local
TCP/IP stack.
 The commands or text, in NVT form, travel through the Internet and arrive at the TCP/IP stack at
the remote machine.
 Here the characters are delivered to the operating system and passed to the TELNET server,
which changes the characters to the corresponding characters understandable by the remote
computer.
 The characters cannot be passed directly to the operating system because the remote operating
system is not designed to receive characters from a TELNET server; it is designed to receive
characters from a terminal driver.
 The solution is to add a piece of software called a pseudo terminal driver, which pretends that the
characters are coming from a terminal. The operating system then passes the characters to the
appropriate application program.
21. Explain Persistent and non-persistent connections in HTTP.

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

Persistent Connections
 HTTP version 1.1 specifies a persistent connection by default. In a persistent connection, the
server leaves the connection open for more requests after sending a response
 The server can close the connection at the request of a client or if a time-out has been reached.
The sender usually sends the length of the data with each response.
 There are some occasions when the sender does not know the length of the data. This is the case
when a document is created dynamically or actively.
 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.
Example
Figure shows the same scenario as in previous example, but using a persistent connection. Only one
connection establishment and connection termination are used, but the request for the image is sent
separately