Вы находитесь на странице: 1из 13

I-TCP: Indirect TCP for Mobile Hosts by Ajay Bakre and B.R.

Badrinath
CSE 291K 1/16/03 Richard Huang

What is I-TCP?
l

Dividing normal TCP connection into two parts:

Wireless link between mobile host and

Mobility Support Router (MSR) Normal TCP link between MSR and fixed correspondent host

Why I-TCP?
l

Separate flow control and congestion control functionality of the wireless link from that of the fixed network Separate transport protocol for wireless link can support notification of events such as disconnections, moves, and other features of the wireless link such as available bandwidth Indirection allows base station to manage much of the communication overhead

Indirect TCP Overview

Performance over Local Area

l l

Why does I-TCP have better performance? I-TCP incurs copying overhead at the MSR

I-TCP wins
l

l l l

Sending host sees more uniform round-trip delays for TCP fragments as compared to regular TCP I-TCP might recover faster from a lost packet than regular TCP Congestion control kicked in during handoffs for regular TCP Simple reset of TCP retransmission timer at new MSR immediately after handoff forced slow start and getting wireless part out of congestion

Performance over Wide Area

Time needed to recover from falsely triggered congestion control increases with round-trip delay

I-TCP Implementation on Mach3/Unix

I-TCP Handoff Sequence

Disadvantages to I-TCP
l l

l l

End-to-end semantics is not followed I-TCP does not yield weaker end-to-end semantics in comparison to regular TCP, provided that there are no MSR failures and that the MH does not stay disconnected from the fixed network for too long What happens if MSR fails? What happens if MSR sends an ack to the correspondent but loses the packet to the mobile host? Copying overhead at MSR

Other side of the coin


l

How is MSR failing any different from a home agent failing? If MH stays disconnected from the network, how would using normal TCP or using Mobile IP help? Higher level applications such as ftp should have end-to-end checks

Conclusions from paper


l l

I-TCP confines mobility related problems to the wireless link Alleviate problems by adapting the TCP/IP software on the wireless link that requires no modifications from the hosts on the fixed network I-TCP particularly suited for applications which are throughput intensive

My conclusions
l

Good to isolate wireless link


semantics

Higher layers can take care of end-to-end

Extend work to support planned discontinuation

Вам также может понравиться