1.2. The 4 Layer Internet Model

Layering is core concept to boost reusability and modularity in network design”

“Each layer doesn’t have to regard how the right below layer worked, it is Abstraction

I. Link Layer

carry the data(called frame) over one link at a time, hop-by-hop.

i.e. Ethernet(wired), Wi-Fi(wireless)

II. Network Layer

deliver data(called datagram) end-to-end, from src to des

*IP(Internet Protocol): Network Layer must use IP: not reliable, ordering, error-check

III. Transport Layer: TCP / UDP

deliver data(called packet) from src application to des application

A. TCP(Transmission Control Protocol):

1. Reliability: re-transmit until received successfully

2. In-Order: guarantee correct in-order delivery

i.e. web client, e-mail client

B. UDP(User Datagram Protocol):

no reliable, no ordering

i.e. video conferencing

IV. Application Layer:

have their-own protocol parsing semantics of byte-stream served by Transport Layer

i.e. http, ftp, www, ssh, telnet, dns, dhcp, sip

“Layer can use the service provided layer right below by well-defined API”

V. Terminology

A. Packet = data + header

header is meta-data describing what data is, where it is going, it comes from

OSI7_and_4LAYER_Mdoel
[OSI 7-layer to 4-layer Internet Model]

Unit 2. Transport

2.0. Introduction to Transport

2.1. TCP Service Model

2.2. UDP Service Model

2.3. ICMP Service Model

2.4. End-to-End Principle

2.5. Error Detection

2.6. Finite State Machine

2.7. Reliable Communication – Stop and Wait

2.8. Reliable Communication – Sliding Window

2.9. Reliable Communication – Retransmission Strategies

2.10. Reliable Communication – TCP header

2.11. Reliable Communication – Connection Setup and Teardown

2.12. Transport(recap)

2.13. TCP/IP – Kevin Fall