[go: up one dir, main page]
Scribd
Upload
7 views4 pages

01100110

The document explains the reasoning behind various networking concepts and calculations related to RTT estimation, MSS calculation, propagation and transmission delays, HTTP packet analysis, TCP segment details, and DNS responses. It includes specific examples and formulas to illustrate how to derive values such as estimated RTT, effective MSS, and delays. Each section is designed to enhance understanding of the underlying principles and practical applications in networking.

Uploaded by

delumgahakotuwa678
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views4 pages

01100110

The document explains the reasoning behind various networking concepts and calculations related to RTT estimation, MSS calculation, propagation and transmission delays, HTTP packet analysis, TCP segment details, and DNS responses. It includes specific examples and formulas to illustrate how to derive values such as estimated RTT, effective MSS, and delays. Each section is designed to enhance understanding of the underlying principles and practical applications in networking.

Uploaded by

delumgahakotuwa678
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Absolutely!

Let’s go through each answer and explain the reasoning behind it so you
understand why we’re doing what we’re doing—not just the final result.

✅ EXPLAINED ANSWERS – IT31013 FINAL EXAM STRUCTURE

🕒 1. RTT Estimation

Q: Estimated RTT = 120 ms, Sample RTT = 150 ms, α = 0.25. What’s the new RTT?

📘 Explanation:
We’re using Exponential Weighted Moving Average (EWMA) to smooth out RTT fluctuations.
The formula is:

New Estimated RTT=(1−α)×Old RTT+α×New Sample RTT\text{New Estimated RTT} = (1 - \


alpha) \times \text{Old RTT} + \alpha \times \text{New Sample RTT}

So:

=(1−0.25)×120+0.25×150=90+37.5=127.5 ms= (1 - 0.25) \times 120 + 0.25 \times 150 = 90 +


37.5 = \boxed{127.5 \text{ ms}}

📌 Why?
This helps TCP gradually adjust RTT rather than overreacting to spikes.

🕒 2. RTT Table-Based Estimation

We calculate the RTT for each segment by subtracting Sent Time from ACK Received Time.

Segment RTT (ms)

1 150

2 124

3 165

4 178

5 153

Then, use the EWMA again, this time with α = 0.35.

📘 For Segment 2:
=0.65×150+0.35×124=140.9 ms= 0.65 \times 150 + 0.35 \times 124 = 140.9 \text{ ms}

Repeat for each segment. Final result after Segment 5 is:

157.14 ms⇒Smooth average RTT\boxed{157.14 \text{ ms}} \Rightarrow \text{Smooth average


RTT}

📦 3. MSS Calculation

Given:

 MTU = 1500 bytes

 IPv6 header = 40 bytes

 TCP header = 20 bytes

 Sender MSS = 1440, Receiver MSS = 1050

 File size = 24,000 bytes

a. Effective MSS?

✅ TCP uses the smaller of the two advertised values:

1050 bytes\boxed{1050 \text{ bytes}}

b. How many full segments?

Each segment carries 1050 bytes of data:

240001050=22.86⇒22 full segments\frac{24000}{1050} = 22.86 \Rightarrow \boxed{22 \


text{ full segments}}

c. Remaining data in last segment:

24000−(22×1050)=900⇒900 bytes24000 - (22 \times 1050) = 900 \Rightarrow \boxed{900 \


text{ bytes}}

🚀 4. Propagation Delay

Distance = 10,678,000 meters


Speed = 1.75×108 m/s1.75 \times 10^8 \text{ m/s}

Delay=DistanceSpeed=106780001.75×108=0.0610457 seconds\text{Delay} = \frac{\


text{Distance}}{\text{Speed}} = \frac{10678000}{1.75 \times 10^8} = 0.0610457 \text{ seconds}
Convert to nanoseconds:

0.0610457×109=61,046,000 ns0.0610457 \times 10^9 = \boxed{61,046,000 \text{ ns}}

📌 Why?
Propagation delay is only about distance and speed—nothing to do with file size.

💾 5. Transmission Delay

File = 7 GB = 56 Gb (multiply by 8), Bandwidth = 800 Mbps

Delay=56000800=70 seconds=70000 ms\text{Delay} = \frac{56000}{800} = \boxed{70 \


text{ seconds}} = \boxed{70000 \text{ ms}}

📌 Why?
This is how long it takes to push all bits onto the wire—not how long they take to reach the
other end.

🌐 6. HTTP Packet Analysis

i. GET requests
Two GETs seen in the capture = \boxed{2}

ii. HTTP Version

HTTP/

∗StatusCodes∗∗−∗∗100∗∗:Continuesending(notanerror)
1.1⇒Allows∗∗persistentconnections∗∗(reusethesameTCPconnectionformultiplerequests)iii.∗

−∗∗200∗∗:Success−∗∗404∗∗:Pagenotfoundiv.∗∗ServerIPAddress∗∗\[128.119.245.12\
boxed{HTTP/1.1} \Rightarrow Allows **persistent connections** (reuse the same TCP
connection for multiple requests) iii. **Status Codes** - **100**: Continue sending (not an
error) - **200**: Success - **404**: Page not found iv. **Server IP Address** \[ \
boxed{128.119.245.12}

This is the web server replying to the GET.

🧵 7. TCP Segment Details

i. IP Addresses:

 Source = 172.19.2.146
 Destination = 8.8.8.8 (Google DNS)

ii. Window size:

 Base: 512

 Scaling factor: 256

512×256=131072 bytes512 \times 256 = \boxed{131072 \text{ bytes}}

Shows how much data the receiver can handle without ACK.

iii. Flags:

 FIN: “I’m done sending.”

 ACK: “I received your last packet.”

📌 Why?
Flags are used to manage TCP’s stateful connection lifecycle.

🌐 8. DNS Response

i. Port Numbers:

 Port 53 → Standard for DNS servers

 Port 63487 → Random high port from the client (used to match the response to the
request)

ii. DNS Answer: The client asked for the IP of gaia.cs.umass.edu, and the server replied:

128.119.245.12\boxed{128.119.245.12}

📌 Why?
This is how domain names are resolved to IPs using DNS.

Would you like me to prepare this in a document format or slide deck too?

You might also like