CS382/EE475: Spring 2022-2023 Quiz 2 - SET 1

Zartash Uzmi

Quiz Number 2 – Solutions

Closed Book; Closed Notes; Time Given=15 minutes (Feb 14, 2023)

“I certify that I have neither received nor given unpermitted aid on this examination and that I have
reported all such incidents observed by me in which unpermitted aid is given.”

Name Signature Student ID

Provide brief and precise answers. Final answers are required; no credit otherwise.

Question 1: True/False. Indicate True (T) or False (F) and provide reason in one short phrase.

a) Layer 2 switches are not required to implement Network Layer. [ T / F ]

Remark: Layer 2 switches are only used for local delivery for which the Physical and Data Link Layers
are sufficient.

b) Providing reliability within a single hop will never increase the end-2-end loss rate. [ T / F ]
Remark: Providing reliability “inside” the network will decrease the overall end-2-end loss rate.

c) Fate Sharing principle says that the state needed by an entity is stored at a third-party server. [ T / F ]
Remark: Fate Sharing principle implies co-locating the state with the entity that needs it.

d) In a recent instance, Pakistan Telecom Authority (PTA) had to block the entire Wikipedia site (instead
of just the offending page). They could have blocked just the offending page if everyone were using HTTP
instead of HTTPS. [ T / F ]
Remark: HTTP would have allowed deep packet inspection (DPI) into the application layer data
(including the page URL) and that packet could have been dropped only for the offending pages.

e) TCP provides reliability but UDP does not. [ T / F ]

Remark: UDP provides non-reliable best-effort service while TCP endpoints provide reliability.

Question 2: HTTP Delays. One-sided propagation delay of 150 milliseconds exists between a client
machine and a server machine. Client requests from the server, using HTTP through a browser, a small base
HTML file (thus, you can neglect its transmission time). Embedded/referenced objects, if any, can only be
requested AFTER the base HTML file is received. In each of the following cases, estimate the minimum
time elapsed between providing the URL to the browser and displaying the complete file in the browser.

a) The base HTML file has no embedded objects. We use non-persistent HTTP (HTTP/1.0) on a single
(i.e., no concurrent) TCP connection.

Solution: 2 × 150 (for TCP handshake) + 2 × 150 (for HTTP request/response) = 600ms
Note: This estimate neglects file transmission delay as specified in the question.

b) The base HTML file has no embedded objects. We use persistent (but not pipelined) HTTP on a single
(i.e., no concurrent) TCP connection.

Solution: 600ms (same as HTTP/1.0)

c) The base HTML file has no embedded objects. We use persistent (and pipelined) HTTP (http/1.1) on a
single (i.e., no concurrent) TCP connection.

Solution: 600ms (same as HTTP/1.0 as there is no embedded object)

d) The base HTML file has no embedded objects. We use HTTP and can open no more than 3 concurrent
TCP connections.

Solution: 600ms (same as HTTP/1.0 as there is no embedded object)

e) Base HTML file has 5 embedded objects, which are tiny (hence, neglect transmission time). We use
non-persistent HTTP (HTTP/1.0) on a single (i.e., no concurrent) TCP connection.

Solution: 2 × 150 (for TCP handshake) + 2 × 150 (for HTTP request/response) = 600ms for base file and
then also for each embedded object, making a total of 3600ms.

f ) Base HTML file has 5 embedded objects, which are tiny (hence, neglect transmission time). We use
persistent (but not pipelined) HTTP on a single (i.e., no concurrent) TCP connection.

Solution: 600ms for the base HTML file and then 2×150 (for HTTP request/response for EACH embedded
object), bringing a total of 2100ms.

g) Base HTML file has 5 embedded objects, which are tiny (hence, neglect transmission time). We use
persistent (and pipelined) HTTP (HTTP/1.1) on a single (i.e., no concurrent) TCP connection.

Solution: 600ms for the base HTML file and then 2 × 150 (for HTTP request/response for ALL tiny
embedded objects), bringing a total of 900ms.

h) Base HTML file has 5 embedded objects, each object is 200kB (kilobytes) and the download link speed
is 10Mbps (Megabits per second). We use persistent (and pipelined) HTTP (HTTP/1.1) on a single (i.e.,
no concurrent) TCP connection.

Solution: 600ms for the base HTML file and then 2 × 150 (for HTTP request/response for all embedded
3
×8
objects) followed by 200×10
10×106 = 160ms for each embedded object, bringing a total of 1700ms.
CS382/EE475: Spring 2022-2023 Quiz 2 - SET 2
Zartash Uzmi

Quiz Number 2 – Solutions

Closed Book; Closed Notes; Time Given=15 minutes (Feb 14, 2023)

“I certify that I have neither received nor given unpermitted aid on this examination and that I have
reported all such incidents observed by me in which unpermitted aid is given.”

Signature

Name Student ID

Provide brief and precise answers. Final answers are required; no credit otherwise.

Question 1: True/False. Indicate True (T) or False (F) and provide reason in one short phrase.

a) In a recent instance, Pakistan Telecom Authority (PTA) had to block the entire Wikipedia site (instead
of just the offending page). They could have blocked just the offending page if everyone were using HTTP
instead of HTTPS. [ T / F ]
Remark: HTTP would have allowed deep packet inspection (DPI) into the application layer data
(including the page URL) and that packet could have been dropped only for the offending pages.

b) Providing reliability within a single hop will never increase the end-2-end loss rate. [ T / F ]
Remark: Providing reliability “inside” the network will decrease the overall end-2-end loss rate.

c) Fate Sharing principle says that the state needed by an entity is stored at a third-party server. [ T / F ]
Remark: Fate Sharing principle implies co-locating the state with the entity that needs it.

d) UDP provides reliability but TCP does not. [ T / F ]

Remark: UDP provides non-reliable best-effort service while TCP endpoints provide reliability.

e) Layer 2 switches are not required to implement Network Layer. [ T / F ]

Remark: Layer 2 switches are only used for local delivery for which the Physical and Data Link Layers
are sufficient.

Question 2: HTTP Delays. One-sided propagation delay of 200 milliseconds exists between a client
machine and a server machine. Client requests from the server, using HTTP through a browser, a small base
HTML file (thus, you can neglect its transmission time). Embedded/referenced objects, if any, can only be
requested AFTER the base HTML file is received. In each of the following cases, estimate the minimum
time elapsed between providing the URL to the browser and displaying the complete file in the browser.

a) The base HTML file has no embedded objects. We use non-persistent HTTP (HTTP/1.0) on a single
(i.e., no concurrent) TCP connection.

Solution: 2 × 200 (for TCP handshake) + 2 × 200 (for HTTP request/response) = 800ms
Note: This estimate neglects file transmission delay as specified in the question.

b) The base HTML file has no embedded objects. We use persistent (but not pipelined) HTTP on a single
(i.e., no concurrent) TCP connection.

Solution: 800ms (same as HTTP/1.0)

c) The base HTML file has no embedded objects. We use persistent (and pipelined) HTTP (http/1.1) on a
single (i.e., no concurrent) TCP connection.

Solution: 800ms (same as HTTP/1.0 as there is no embedded object)

d) The base HTML file has no embedded objects. We use HTTP and can open no more than 3 concurrent
TCP connections.

Solution: 800ms (same as HTTP/1.0 as there is no embedded object)

e) Base HTML file has 3 embedded objects, which are tiny (hence, neglect transmission time). We use
non-persistent HTTP (HTTP/1.0) on a single (i.e., no concurrent) TCP connection.

Solution: 2 × 200 (for TCP handshake) + 2 × 200 (for HTTP request/response) = 800ms for base file and
then also for each embedded object, making a total of 3200ms.

f ) Base HTML file has 3 embedded objects, which are tiny (hence, neglect transmission time). We use
persistent (but not pipelined) HTTP on a single (i.e., no concurrent) TCP connection.

Solution: 800ms for the base HTML file and then 2×200 (for HTTP request/response for EACH embedded
object), bringing a total of 2000ms.

g) Base HTML file has 3 embedded objects, which are tiny (hence, neglect transmission time). We use
persistent (and pipelined) HTTP (HTTP/1.1) on a single (i.e., no concurrent) TCP connection.

Solution: 800ms for the base HTML file and then 2 × 200 (for HTTP request/response for ALL tiny
embedded objects), bringing a total of 1200ms.

h) Base HTML file has 3 embedded objects, each object is 200kB (kilobytes) and the download link speed
is 10Mbps (Megabits per second). We use persistent (and pipelined) HTTP (HTTP/1.1) on a single (i.e.,
no concurrent) TCP connection.

Solution: 800ms for the base HTML file and then 2 × 200 (for HTTP request/response for all embedded
3
×8
objects) followed by 200×10
10×106 = 160ms for each embedded object, bringing a total of 1680ms.
CS382/EE475: Spring 2022-2023 Quiz 2 - SET 3
Zartash Uzmi

Quiz Number 2 – Solutions

Closed Book; Closed Notes; Time Given=15 minutes (Feb 14, 2023)

“I certify that I have neither received nor given unpermitted aid on this examination and that I have
reported all such incidents observed by me in which unpermitted aid is given.”

Signature

Name Student ID

Provide brief and precise answers. Final answers are required; no credit otherwise.

Question 1: True/False. Indicate True (T) or False (F) and provide reason in one short phrase.

a) Fate Sharing principle says that the state needed by an entity is stored at a third-party server. [ T / F ]
Remark: Fate Sharing principle implies co-locating the state with the entity that needs it.

b) Layer 2 switches are not required to implement Network Layer. [ T / F ]

Remark: Layer 2 switches are only used for local delivery for which the Physical and Data Link Layers
are sufficient.

c) In a recent instance, Pakistan Telecom Authority (PTA) had to block the entire Wikipedia site (instead
of just the offending page). They could have blocked just the offending page if everyone were using HTTP
instead of HTTPS. [ T / F ]
Remark: HTTP would have allowed deep packet inspection (DPI) into the application layer data
(including the page URL) and that packet could have been dropped only for the offending pages.

d) TCP provides reliability but UDP does not. [ T / F ]

Remark: UDP provides non-reliable best-effort service while TCP endpoints provide reliability.

e) Providing reliability within a single hop will never increase the end-2-end loss rate. [ T / F ]
Remark: Providing reliability “inside” the network will decrease the overall end-2-end loss rate.

Question 2: HTTP Delays. One-sided propagation delay of 250 milliseconds exists between a client
machine and a server machine. Client requests from the server, using HTTP through a browser, a small base
HTML file (thus, you can neglect its transmission time). Embedded/referenced objects, if any, can only be
requested AFTER the base HTML file is received. In each of the following cases, estimate the minimum
time elapsed between providing the URL to the browser and displaying the complete file in the browser.

a) The base HTML file has no embedded objects. We use non-persistent HTTP (HTTP/1.0) on a single
(i.e., no concurrent) TCP connection.

Solution: 2 × 250 (for TCP handshake) + 2 × 250 (for HTTP request/response) = 1000ms
Note: This estimate neglects file transmission delay as specified in the question.

b) The base HTML file has no embedded objects. We use persistent (but not pipelined) HTTP on a single
(i.e., no concurrent) TCP connection.

Solution: 1000ms (same as HTTP/1.0)

c) The base HTML file has no embedded objects. We use persistent (and pipelined) HTTP (http/1.1) on a
single (i.e., no concurrent) TCP connection.

Solution: 1000ms (same as HTTP/1.0 as there is no embedded object)

d) The base HTML file has no embedded objects. We use HTTP and can open no more than 3 concurrent
TCP connections.

Solution: 1000ms (same as HTTP/1.0 as there is no embedded object)

e) Base HTML file has 4 embedded objects, which are tiny (hence, neglect transmission time). We use
non-persistent HTTP (HTTP/1.0) on a single (i.e., no concurrent) TCP connection.

Solution: 2 × 250 (for TCP handshake) + 2 × 250 (for HTTP request/response) = 1000ms for base file and
then also for each embedded object, making a total of 5000ms.

f ) Base HTML file has 4 embedded objects, which are tiny (hence, neglect transmission time). We use
persistent (but not pipelined) HTTP on a single (i.e., no concurrent) TCP connection.

Solution: 1000ms for the base HTML file and then 2×250 (for HTTP request/response for EACH embedded
object), bringing a total of 3000ms.

g) Base HTML file has 4 embedded objects, which are tiny (hence, neglect transmission time). We use
persistent (and pipelined) HTTP (HTTP/1.1) on a single (i.e., no concurrent) TCP connection.

Solution: 1000ms for the base HTML file and then 2 × 250 (for HTTP request/response for ALL tiny
embedded objects), bringing a total of 1500ms.

h) Base HTML file has 4 embedded objects, each object is 200kB (kilobytes) and the download link speed
is 10Mbps (Megabits per second). We use persistent (and pipelined) HTTP (HTTP/1.1) on a single (i.e.,
no concurrent) TCP connection.

Solution: 1000ms for the base HTML file and then 2 × 250 (for HTTP request/response for all embedded
3
×8
objects) followed by 200×10
10×106 = 160ms for each embedded object, bringing a total of 2140ms.