application layer protocols and web communication short notes

Summary: DNS and Web Request Sequencing Checklist

.checklist { list-style: none; padding: 0; margin: 1rem 0 0 0; } .checklist li { display: flex; align-items: flex-start; gap: 0.75rem; margin-bottom: 0.75rem; padding: 0.75rem; background: color-mix(in srgb, var(--color-primary) 5%, var(--color-bg)); border-radius: 0.5rem; border: 1px solid var(--color-border); color: var(--color-text); line-height: 1.5; } .check-box { flex-shrink: 0; width: 1.25rem; height: 1.25rem; border: 2px solid var(--color-primary); border-radius: 0.25rem; display: flex; align-items: center; justify-content: center; margin-top: 0.1rem; } .check-box svg { width: 100%; height: 100%; stroke: var(--color-primary); } .checklist li strong { color: var(--color-text); } Summary: DNS and Web Request Sequencing Checklist Rapid Revision Checklist DNS Default: Assume iterative resolution and empty caches unless specified. DNS Pairs: Full resolution from host = 4 pairs (Host to Local, Local to Root, Local to TLD, Local to Auth). Resolver-only = 3 pairs. TCP Handshake: Strictly SYN, then SYN-ACK, then ACK. Takes 1 RTT. Application Layer: HTTP GET can only be sent after the TCP handshake is complete. Directionality: "Leaving the computer" means excluding DNS Response and TCP SYN-ACK. Protocol Mapping: DNS uses UDP (port 53). HTTP uses TCP (port 80). HTTPS uses TCP (port 443).

Quick Reference: Formulas and Rules

Essential Formulas N = objects, R = RTT, T_{t} = transmission time, T_{DNS} = DNS time Non-Persistent (HTTP/1.0) T = T_{DNS} + N \times (2 R + T_{t}) Persistent, Non-Pipelined (HTTP/1.1) T = T_{DNS} + R + N \times (R + T_{t}) Persistent, Pipelined (HTTP/1.1) T = T_{DNS} + 2 R + N \times T_{t} Key Facts Persistent connections are default in HTTP/1.1 Pipelining is optional in HTTP/1.1 One TCP handshake = 1 RTT One HTTP request-response = 1 RTT (on existing connection)

Last-Minute Checklist Before Exam

@keyframes fadeUp { from { opacity: 0; transform: translateY(15px); } to { opacity: 1; transform: translateY(0); } } Pre-Exam Verification Conceptual Clarity [ ] HTTP/1.0 creates new connections per object [ ] HTTP/1.1 keeps connections alive by default [ ] Pipelining sends requests without waiting [ ] HOL blocking is a pipelining limitation Calculation Skills [ ] Compute time for non-persistent connections [ ] Compute time for persistent non-pipelined [ ] Compute time for persistent pipelined [ ] Add DNS time when cache is empty Quick Diagnostics If stuck, ask: 1. How many objects? 2. Which HTTP version? 3. Is pipelining mentioned? 4. Is DNS cached? 5. What is the RTT value?

1 more card in this chapter

Application Layer Protocols and Web Communication Short Notes for GATE CS

Application Layer Protocols and Web Communication short notes for GATE CS: 4 study cards covering concepts, formulas, shortcuts and exam traps, plus solved practice questions.

Summary: DNS and Web Request Sequencing Checklist

Rapid Revision Checklist

DNS Default: Assume iterative resolution and empty caches unless specified.
DNS Pairs: Full resolution from host = 4 pairs (Host to Local, Local to Root, Local to TLD, Local to Auth). Resolver-only = 3 pairs.
TCP Handshake: Strictly SYN, then SYN-ACK, then ACK. Takes 1 RTT.
Application Layer: HTTP GET can only be sent after the TCP handshake is complete.
Directionality: "Leaving the computer" means excluding DNS Response and TCP SYN-ACK.
Protocol Mapping: DNS uses UDP (port 53). HTTP uses TCP (port 80). HTTPS uses TCP (port 443).

Quick Reference: Formulas and Rules

Essential Formulas

$N$ = objects, $R$ = RTT, $T_{t}$ = transmission time, $T_{DNS}$ = DNS time

Non-Persistent (HTTP/1.0)

T = T_{DNS} + N \times (2 R + T_{t})

Persistent, Non-Pipelined (HTTP/1.1)

T = T_{DNS} + R + N \times (R + T_{t})

Persistent, Pipelined (HTTP/1.1)

T = T_{DNS} + 2 R + N \times T_{t}

Key Facts

Persistent connections are default in HTTP/1.1
Pipelining is optional in HTTP/1.1
One TCP handshake = 1 RTT
One HTTP request-response = 1 RTT (on existing connection)

Last-Minute Checklist Before Exam

Pre-Exam Verification

Conceptual Clarity

[ ] HTTP/1.0 creates new connections per object [ ] HTTP/1.1 keeps connections alive by default [ ] Pipelining sends requests without waiting [ ] HOL blocking is a pipelining limitation

Calculation Skills

[ ] Compute time for non-persistent connections [ ] Compute time for persistent non-pipelined [ ] Compute time for persistent pipelined [ ] Add DNS time when cache is empty

Quick Diagnostics

If stuck, ask: 1. How many objects? 2. Which HTTP version? 3. Is pipelining mentioned? 4. Is DNS cached? 5. What is the RTT value?

Topic Revision Summary

Delivery Models: Unicast (1:1), Multicast (1:Many, specific group), Broadcast (1:All, local segment).
Primary Broadcast Trigger: Address uncertainty (the bootstrap problem, e.g., a client needing an IP address via DHCP).
Transport Constraint: Broadcast and Multicast must use connectionless transport (UDP). TCP is strictly 1:1.
Critical Distinction: ARP is a Link Layer broadcast protocol. DHCP is an Application Layer broadcast protocol.
Address Types: Limited broadcast (255.255.255.255) is never routed. Directed broadcast (e.g., 192.168.1.255) can be routed to the target subnet, then broadcast locally.
Exam Heuristic: "Zero-configuration" or "dynamic discovery" on a local network strongly implies a broadcast or multicast mechanism.