AleksandarKuzmanovicEdwardW.Knightly课件.pptVIP

A Performance vs. Trust Perspective in the Design of End-Point Congestion Control Protocols Motivation Sender-based TCP Control functions given to the sender Receiver-Based TCP Receiver decides how much data can be sent, and which data should be sent by the sender DATA – ACK communication becomes REQ - DATA Example protocols TFRC [RFC3448], WebTP, and RCP Why Receiver-Based TCP? Example: Busy web server Receiver-based TCP distributes the state management across a large number of clients Generally Whenever a feedback is needed from the receiver, receiver-based TCP has advantage over sender-based schemes due to the locality of information Benefits [RCP03] Performance Functionality - Loss recovery - Seamless handoffs - Congestion control - Server migration - Power management for - Bandwidth aggregation mobile devices - Web response times - Network-specific congestion control Vulnerability Receivers remotely control servers by deciding which packets and when to be sent Receivers have both means and incentive to manipulate the congestion control algorithm Means: open source OS Incentive: faster web browsing file download An Example:Request-Flood Attack Request flood attack A misbehaving receiver floods the server with requests, which replies and congests the network Resource stealing A misbehaving receiver moderately re-tunes TCP parameters to gain performance, yet eludes detection Remaining Outline Modeling receiver misbehaviors Evaluate network-based solutions Present an end-point solution Conclusion Algorithmic Misbehavior Why parameter-based misbehaviors? Easy to implement Tells how much you can misbehave while eluding detection Bandwidth Stealing Network-Based Solutions RED-PD [MFW01] designed to detect non-responsive flows Monitors only a subset of flows at the router and compares their rates to the targeted bandwidth (TB) TB is computed as a TCP-fair throughput for Observed Ploss RTT=40ms If Ti TB