Chương 1

Bạn đang xem bản rút gọn của tài liệu. Xem và tải ngay bản đầy đủ của tài liệu tại đây (10.77 MB, 192 trang )

Trang 1<div class="page_container" data-page="1">

Chương 1: Tổng quan về mô hình truyền thơng



Nguyễn Thanh Đăng, bài giảng Mạng và Truyền dữ liệu, ÐHCN Tp.HCM, 2016.

</div>Trang 2<div class="page_container" data-page="2">

Chương 1:

Tổng quan về mơ hình truyền thơng

</div>Trang 3<div class="page_container" data-page="3">

1.1 Các thành phần chính của mạng máy tính.

n

</div>Trang 4<div class="page_container" data-page="4">

1.1 Các thành phần chính của mạng máy tính.

n

</div>Trang 6<div class="page_container" data-page="6">

1.2 Mơ hình OSI.

 Các cơng việc liên quan q trình gửi 1 bức thư

</div>Trang 7<div class="page_container" data-page="7">

1.2 Mơ hình OSI.

 n

</div>Trang 8<div class="page_container" data-page="8">

1.2 Mơ hình OSI.

 n

</div>Trang 9<div class="page_container" data-page="9">

1.2 Mơ hình OSI.

 Mơ hình OSI 7 lớp: gồm 7 lớp riêng biệt nhưng có liên hệ với nhau, mỗi lớp nhằm định nghĩa một phân đoạn trong quá trình di chuyển thông tin qua mạng.

</div>Trang 10<div class="page_container" data-page="10">

1.2 Mơ hình OSI.

 Chức năng mỗi lớp trong mơ hình OSI:

a)Lớp vật lý (Physical layer):Lớp vật lý chịu trách

nhiệm cho việc di chuyển các bit riêng lẻ từ 1 hop

(nút) đến nút kế tiếp. Lớp này liên quan đến các đặc tính cơ, điện của giao diện thiết bị và môi trường

truyền.

</div>Trang 11<div class="page_container" data-page="11">

1.2 Mô hình OSI.

</div>Trang 13<div class="page_container" data-page="13">

1.2 Mơ hình OSI.

b)Lớp liên kết dữ liệu (Data link layer): Lớp liên kết dữ liệu chịu trách nhiệm chuyển các frame từ 1 hop (nút) đến hop khác.

</div>Trang 14<div class="page_container" data-page="14">

1.2 Mơ hình OSI.

 Nhiệm vụ

 Break L3 (Network) data into reasonable size (Frame)

 Truyền khung/frame từ nút đến nút trong một mạng

 Guarantee Node-to-Node delivery (Frame Error Free)

 Service

 Tạo khung (thêm header & trailer)

 Định địa chỉ vật lý (MAC address: 12 digit hexadecimal (e.g. 080BF0AFDC09))

 Same sender network:source & destination address

 Outside sender network: source & connecting devices (bridge, router, gateway) address

 Điều khiển lưu lượng:frame acknowledgement, inform buffer size, etc.

 Kiểm soát lỗi:error detection and error correction

 Điều khiển truy cập: checking accessibility (ex. Multipoint connection)

</div>Trang 15<div class="page_container" data-page="15">

1.2 Mơ hình OSI.

 Phân phối hop đến hop

</div>Trang 16<div class="page_container" data-page="16">

1.2 Mơ hình OSI.

c) Lớp mạng (Network layer): Lớp mạng chịu trách nhiệm phân phối các gói tin riêng rẽ từ host nguồn đến host đích.

</div>Trang 17<div class="page_container" data-page="17">

 Logical (Network) address (header):IP address

 Định tuyến các gói tin đi qua thiết bị liên mạng

 Router || Gateway

</div>Trang 18<div class="page_container" data-page="18">

1.2 Mơ hình OSI.

 Phân phối từ nguồn đến đích

</div>Trang 19<div class="page_container" data-page="19">

1.2 Mơ hình OSI.

d)Lớp giao vận (Transport layer): Lớp giao vận chịu trách nhiệm phân phối message từ một quá

trình/process đến quá trình khác.

</div>Trang 20<div class="page_container" data-page="20">

1.2 Mơ hình OSI.

 Nhiệm vụ

 Đảm bảo phân phối toàn bộ từ nguồn đến đích cuối cùng

 Service

 Service-point addressing:Port address (16 bits: 0 – 65,535 ports)

 Each application is assigned a specific port address

 Segmentation and Reassembly

 Source:segment L5 data into small segments

 Destination:reassembly small segments into a whole message

 Điều khiển kết nối

 Khơng kết nối/Connectionless

 Hướng kết nối/Connection-oriented

 Kiểm sốt lỗi: dị và sửa sai tồn bộ message

 Điều khiển luồng

</div>Trang 21<div class="page_container" data-page="21">

1.2 Mơ hình OSI.

e)Lớp phiên (Session layer): Lớp phiên chịu trách nhiệm điều khiển và đồng bộ dialog.

</div>Trang 22<div class="page_container" data-page="22">

 Traffic control & direction control

 Đồng bộ thông điệp/Message synchronization

 Adding checkpoints (synchronization points) in the message stream

</div>Trang 23<div class="page_container" data-page="23">

1.2 Mơ hình OSI.

f) Lớp trình diễn (Presentation layer): Lớp trình diễn chịu trách nhiệm biên dịch, nén và mã hóa

</div>Trang 24<div class="page_container" data-page="24">

 Ex. ASCII -> non ASCII system

 Mã hóa (privacy & security)

 Đối với các thông tin nhạy cảm: login-password, thẻ tín dung, tài khoản ngân hàng, thơng tin cá nhân

 Nén

 Ex. Zip, Gif, JPEG

</div>Trang 25<div class="page_container" data-page="25">

1.2 Mơ hình OSI.

g) Lớp ứng dụng (Application layer): Lớp ứng dụng chịu trách nhiệm cung cấp các dịch vụ đến người sử dụng.

</div>Trang 26<div class="page_container" data-page="26">

 Network Virtual Terminal

 Truyền , truy xuất và quản lý file/File transfer, access, and management (FTAM)

 Dịch vụ mail

 Truy cập WWW

</div>Trang 27<div class="page_container" data-page="27">

1.2 Mơ hình OSI.

 Giao tiếp giữa các lớp trong mơ hình OSI

</div>Trang 28<div class="page_container" data-page="28">

1.2 Mơ hình OSI.

 Trao đổi dữ liệu sử dụng mơ hình OSI

</div>Trang 29<div class="page_container" data-page="29">

1.3 Mơ hình TCP/IP



The layers in theTCP/IP protocol suitedo not exactlymatch those in the OSI model. The original TCP/IPprotocol suite was defined as having four layers:host-to-network,internet,transport, andapplication.However, when TCP/IP is compared to OSI, we cansay that the TCP/IP protocol suite is made of fivelayers:physical,data link,network,transport, and

application.

</div>Trang 30<div class="page_container" data-page="30">

1.3 Mơ hình TCP/IP

</div>Trang 31<div class="page_container" data-page="31">

1.3 Mơ hình TCP/IP

Network Access

</div>Trang 32<div class="page_container" data-page="32">

1.3 Mơ hình TCP/IP

a) Physical and Data Link Layers:

At the physical and data link layers, TCP/IP does not define any specific protocol. It supports all the standard and proprietary protocols. A network in a TCP/IP

internetwork can be a local-area network or a wide-area network

b) Network Layer:

At the network layer (or, more accurately, the

internetwork layer), TCP/IP supports the Internetworking Protocol. lP, in turn, uses four supporting protocols:

ARP, RARP, ICMP, and IGMP.

</div>Trang 33<div class="page_container" data-page="33">

1.3 Mơ hình TCP/IP

c) Transport Layer:

Traditionally the transport layer was represented in

TCP/IP by two protocols· TCP and UDP. IP is a host protocol, meaning that it can deliver a packet from one physical device to another. UDP and TCP are

host-to-transport level protocols responsible for delivery of a message from a process (running program) to another process. A new transport layer protocol, SCTP, has been devised to meet the needs of some newer applications.

</div>Trang 34<div class="page_container" data-page="34">

1.3 Mô hình TCP/IP

h

</div>Trang 35<div class="page_container" data-page="35">

1.3 Mơ hình TCP/IP

 UDP protocol:

The User Datagram Protocol (UDP) is called a

connectionless, unreliable transport protocol. It does not add anything to the services of lP except to

provide process-toprocess communication instead of host-to-host communication. Also, it performs very limited error checking.

</div>Trang 36<div class="page_container" data-page="36">

 Provides limited error checking

 Provides best-effort delivery

 Has no data-recovery features

UDP Characteristics

</div>Trang 37<div class="page_container" data-page="37">

1.3 Mơ hình TCP/IP

 Well-Known Ports for UDP

</div>Trang 38<div class="page_container" data-page="38">

1.3 Mô hình TCP/IP

Well-Known Ports for UDP

</div>Trang 40<div class="page_container" data-page="40">

1.3 Mơ hình TCP/IP

 Checksum

-The UDP checksum 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 lP

packet in which the user datagram is to be encapsulated with some fields filled with Os

</div>Trang 41<div class="page_container" data-page="41">

1.3 Mơ hình TCP/IP

Pseudoheader for checksum calculation

</div>Trang 42<div class="page_container" data-page="42">

1.3 Mơ hình TCP/IP

Example 23.2

Figure 23.11 shows the checksum calculation for a very small user datagram with only 7 bytes of data. Because the number of bytes of data is odd, padding is added for checksum calculation. The pseudoheader as well as the padding will be dropped when the user datagram is

delivered to lP.

</div>Trang 43<div class="page_container" data-page="43">

1.3 Mô hình TCP/IP

 User

</div>Trang 44<div class="page_container" data-page="44">

1.3 Mơ hình TCP/IP

 UDP Operation

-Connectionless Services: each user datagram sent by

UDP is an independent datagram. There is no connection establishment and no connection termination

-Flow and Error Control:UDP is a very simple,

unreliable transport protocol. There is no flow control and hence no window mechanism. The receiver may overflow with incoming messages 44

</div>Trang 45<div class="page_container" data-page="45">

1.3 Mơ hình TCP/IP

-Encapsulation and Decapsulation: To send a message

from one process to another, the UDP protocol encapsulates and decapsulates messages in an lP datagram.

-Queuing:

</div>Trang 46<div class="page_container" data-page="46">

1.3 Mơ hình TCP/IP

 Use of UDP:

- UDP is suitable for a process that requires simple response communication with little concern for flow and error control. It is not usually used for a process such as FfP that needs to send bulk data.

request--UDP is suitable for a process with internal flow and error control mechanisms. For example, the Trivial File Transfer

Ptotocol (TFTP) process includes flow and error control. It can easily use UDP.

</div>Trang 47<div class="page_container" data-page="47">

1.3 Mơ hình TCP/IP

- UDP is a suitable transport protocol for multicasting.

Multicasting capability is embedded in the UDP software but not in the TCP software.

- UDP is used for management processes.

- UDP is used for some route updating protocols such as Routing Information Protocol (RIP)

</div>Trang 48<div class="page_container" data-page="48">

1.3 Mơ hình TCP/IP

 TCP (Transmission Control Protocol) protocol: TCP is a connection-oriented protocol; it creates a virtual connection between two TCPs to send data. In

addition, TCP uses flow and error control mechanisms at the transport level. Therefore, TCP is called a

connection-oriented, reliable transport protocol. It

adds connection-oriented and reliability features to the services of lP

</div>Trang 49<div class="page_container" data-page="49">

1.3 Mơ hình TCP/IPTCP Characteristics

 Transport layer of the TCP/IP stack

 Access to the network layer for applications

</div>Trang 50<div class="page_container" data-page="50">

1.3 Mơ hình TCP/IP

 TCP Services

 Process-to-Process Communication: Like UDP, TCP

provides process-to-process communication using port numbers

</div>Trang 51<div class="page_container" data-page="51">

1.3 Mơ hình TCP/IP

Well-known ports used by TCP

</div>Trang 52<div class="page_container" data-page="52">

1.3 Mơ hình TCP/IP

 Stream Delivery Service: TCP, unlike UDP, is a

stream-oriented protocol. TCP allows the sending

process to deliver data as a stream of bytes and allows the receiving process to obtain data as a stream of

bytes. TCP creates an environment in which the two processes seem to be connected by an imaginary

"tube“ that carries their data across the Internet

</div>Trang 53<div class="page_container" data-page="53">

1.3 Mơ hình TCP/IP

Stream delivery

</div>Trang 54<div class="page_container" data-page="54">

1.3 Mơ hình TCP/IP

 Sending and Receiving Buffers: Because the

sending and the receiving processes may not write or read data at the same speed, TCP needs buffers for

storage. There are two buffers, the sending buffer and the receiving buffer, one for each direction

</div>Trang 55<div class="page_container" data-page="55">

1.3 Mơ hình TCP/IP

Sending and receiving buffers

</div>Trang 56<div class="page_container" data-page="56">

datagrams and transmitted. This entire operation is transparent to the receiving process

</div>Trang 57<div class="page_container" data-page="57">

1.3 Mơ hình TCP/IP

TCP segments

</div>Trang 58<div class="page_container" data-page="58">

1.3 Mơ hình TCP/IP

 Full-Duplex Communication: TCP offers full-duplex

service, in which data can flow in both directions at the same time. Each TCP then has a sending and

receiving buffer, and segments move in both directions.

</div>Trang 60<div class="page_container" data-page="60">

1.3 Mô hình TCP/IP

 Reliable Service: TCP is a reliable transport protocol.

It uses an acknowledgment mechanism to checkthe safe and sound arrival of data

 'I'CP Features

 Numbering System:

-Byte Number: The bytes of data being transferred in

each connection are numbered by TCP. The numbering starts with a randomly generated number. 60

</div>Trang 61<div class="page_container" data-page="61">

1.3 Mơ hình TCP/IP

-Sequence Number: The value in the sequence number

field of a segment defines the number of the first data byte contained in that segment

-Acknowledgment Number: The value of the

acknowledgment field in a segment defines the number of the next byte a party expects to receive. The

acknowledgment number is cumulative

</div>Trang 62<div class="page_container" data-page="62">

1.3 Mơ hình TCP/IP

 Flow Control : The receiver of the data controls the

amount of data that are to be sent by the sender. This is done to prevent the receiver from being

overwhelmed with data. The numbering system allows TCP to use a byte-oriented flow control

 Error Control

 Congestion Control

</div>Trang 63<div class="page_container" data-page="63">

1.3 Mơ hình TCP/IP

 Segment

 Format:

</div>Trang 64<div class="page_container" data-page="64">

1.3 Mơ hình TCP/IP

Control field

</div>Trang 65<div class="page_container" data-page="65">

1.3 Mơ hình TCP/IP

 A TCP Connection

 Connection Establishment: TCP transmits data in full-duplex mode. When two TCPs in two machines are connected, they are able to send segments to each other simultaneously. This implies that each party

must initialize connnunication and get approval from the other party before any data are transferred

</div>Trang 66<div class="page_container" data-page="66">

1.3 Mơ hình TCP/IP

Establishing a Connection

</div>Trang 67<div class="page_container" data-page="67">

1.3 Mơ hình TCP/IP

-Three Way Handshaking: The connection establishment in TCP is called three way handshaking

</div>Trang 69<div class="page_container" data-page="69">

1.3 Mô hình TCP/IP

 Data Transfer

</div>Trang 70<div class="page_container" data-page="70">

1.3 Mơ hình TCP/IP

 Connection Termination

Connection termination using three-way handshaking

</div>Trang 72<div class="page_container" data-page="72">

1.3 Mơ hình TCP/IP

 Flow Control: TCP uses a sliding window to handle

flow control. The sliding window protocol used by TCP, however, is something between the Go-Back-Nand Selective Repeat sliding window.

</div>Trang 73<div class="page_container" data-page="73">

1.3 Mơ hình TCP/IP

Flow Control

</div>Trang 74<div class="page_container" data-page="74">

1.3 Mơ hình TCP/IPTCP Acknowledgment

</div>Trang 75<div class="page_container" data-page="75">

1.3 Mơ hình TCP/IPFixed Windowing

</div>Trang 76<div class="page_container" data-page="76">

1.3 Mơ hình TCP/IP

Sliding window: A sliding window is used to make

transmission more efficient as well as to control the flow of data so that the destination does not become

overwhelmed with data. TCP sliding windows are byte oriented

</div>Trang 77<div class="page_container" data-page="77">

1.3 Mơ hình TCP/IP

TCP Sliding Windowing

</div>Trang 78<div class="page_container" data-page="78">

1.3 Mơ hình TCP/IP

Some points about TCP sliding windows:

-The size of the window is the lesser of rwnd and cwnd.

-The source does not have to send a full window's worth of data.-The wmdow can be opened or closed by the receiver, but shouW not be shrunk.

-The destination can send an acknowledgment at any time as long as it does not result in a shrinking window.

- The receiver can temporarily shut down the window; the sender, however, can always send a segment of 1 byte after the window is shut down

78

</div>Trang 79<div class="page_container" data-page="79">

What is the value of the receiver window (rwnd) for host Aif the receiver, host B, has a buffer size of 5000 bytes and1000 bytes of received and unprocessed data?

Example 23.4

The value of rwnd = 5000 − 1000 = 4000. Host B canreceive only 4000 bytes of data before overflowing itsbuffer. Host B advertises this value in its next segment to A.

</div>Trang 80<div class="page_container" data-page="80">

1.3 Mơ hình TCP/IP

TCP Sequence and Acknowledgment Numbers

</div>Trang 81<div class="page_container" data-page="81">

1.3 Mơ hình TCP/IP

 Error Control

 Checksum:

-Each segment includes a checksum field which is used

to check for a corrupted segment. If the segment is

corrupted, it is discarded by the destination TCP and is considered as lost

-TCP uses a 16-bit checksum that is mandatory in every

</div>Trang 82<div class="page_container" data-page="82">

1.3 Mơ hình TCP/IP

 Acknowledgment: TCP uses acknowledgments to

confirm the receipt of data segments. Control segments that carry no data but consume a sequence number are also acknowledged. ACK segments

are never acknowledged.

 Retransmission: In modent implementations, a

retransmissimt occur s if the retransmission timer

expires or three duplicate ACK segments have arrived.

</div>Trang 83<div class="page_container" data-page="83">

1.3 Mơ hình TCP/IP

 Out-of-Order Segments: Data may arrive out of order

and be temporarily stored by the receiving TCP,

but TCP guarantees that no out-of-order segment is delivered to the process.

</div>Trang 84<div class="page_container" data-page="84">

1.3 Mơ hình TCP/IP

 Congestion Control: Congestion control refers to

techniques and mechanisms that can either prevent congestion, before it happens, or remove congestion,

after it has happened. Congestion control involves two

factors that measure the performance of a network:

delay and throughput

</div>Trang 85<div class="page_container" data-page="85">

1.3 Mơ hình TCP/IP

Congestion Window:

Congestion Policy: TCP's general policy for handling

congestion is based on three phases: slow start, congestion avoidance, and congestion detection. In the slow-start

phase, the sender starts with a very slow rate of

transmission, but increases the rate rapidly to reach a

threshold. When the threshold is reached, the data rate is reduced to avoid congestion. Finally if congestion is

detected, the sender goes back to the slow-start or

congestion avoidance phase based on how the congestion

</div>Trang 87<div class="page_container" data-page="87">

1.3 Mơ hình TCP/IP

d) Application Layer:

The application layer in TCP/IP is equivalent to the

combined session, presentation, and application layers in the OSI model. Many protocols are defined at this layer.

</div>Trang 88<div class="page_container" data-page="88">

1.3 Mơ hình TCP/IP

Mapping Layer 3 to Layer 4

</div>Trang 89<div class="page_container" data-page="89">

1.3 Mô hình TCP/IP

Mapping Layer 4 to Applications

</div>Trang 91<div class="page_container" data-page="91">

1.3 Mơ hình TCP/IP

Relationship of layers and addresses in TCP/IP:

</div>Trang 92<div class="page_container" data-page="92">

- The physical addresses have authority over the

network (LAN or WAN). The size and format of these addresses vary depending on the network. For

example, Ethernet

uses a 6-byte (48-bit) physical address that is imprinted on the network interface card (NIC).

</div>Trang 93<div class="page_container" data-page="93">

1.3 Mơ hình TCP/IP

-Ví dụ: a node with physical address 10 sends a frame to a node with physical address 87. The two nodes are connected by a link (bus topology LAN). As the figure shows, the computer with

physical address 10is the sender, and the computer with physical address 87is the receiver.

</div>Trang 94<div class="page_container" data-page="94">

1.3 Mơ hình TCP/IP

 Logical Addresses:

-Logical addresses are necessary for universal communicationsthat are independent of underlying physical networks. Physicaladdresses are not adequate in an internetwork environmentwhere different networks can have different address formats. Auniversal addressing system is needed in which each host canbe identified uniquely, regardless of the underlying physicalnetwork.

- A logical address in the Internet is currently a 32-bit address that can uniquely define a host connected to the Internet. No two

publicly addressed and visible hosts on the Internet can have the

same lP address.

</div>

Chương 1

<b>Chương 1: Tổng quan về mô hình truyền thơng</b>

<b>Nguyễn Thanh Đăng, bài giảng Mạng và Truyền dữ liệu, ÐHCN Tp.HCM, 2016.</b>

<b>Chương 1: </b>

<b>Tổng quan về mơ hình truyền thơng</b>

<b>1.1 Các thành phần chính của mạng máy tính.</b>

<b>n</b>

<b>1.1 Các thành phần chính của mạng máy tính.</b>

<b>n</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mô hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.2 Mơ hình OSI.</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>application.</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mô hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>UDP Characteristics</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mô hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mô hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IPTCP Characteristics</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mô hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>Establishing a Connection</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mô hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>Flow Control</b>

<b>1.3 Mơ hình TCP/IPTCP Acknowledgment</b>

<b>1.3 Mơ hình TCP/IPFixed Windowing</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>1.3 Mơ hình TCP/IP</b>

<b>TCP Sliding Windowing</b>

<b>1.3 Mơ hình TCP/IP</b>

<i>Example 23.4</i>

<b>1.3 Mơ hình TCP/IP</b>

<b>TCP Sequence and Acknowledgment Numbers</b>

<b>1.3 Mơ hình TCP/IP</b>