国外毕业答辩PPT模板.ppt

Edge-based Inference, Control, and DoS Resilience for the Internet The Internet 1969 2004 Internet Design Principles Network as a black-box Why End-Point Approach Today? Scalability e2e scalability Deployability IP and network core are not extensible and are slowly evolving: IPv6 (10 years) IP Multicast (domain dependent) Network Performance Internet traffic HTTP (web browsing) FTP (file transfer) Fact: 95% of the traffic today is TCP-based Performance QoS differentiation Net win for both HTTP and FTP flows End-point-based two-level differentiation scheme Denial of Service DoS attacks can demolish network performance Prevent DoS attacks via a robust end-point protocol design End-Point Service Differentiation TCP-Low Priority Utilizes only the excess network bandwidth Key mechanism Early congestion indications: one-way packet delay Performance Can improve the HTTP file transfers for more than 90% when FTP flows use TCP-LP Deployability no changes in the network core sender side modification of TCP High-speed version developed in cooperation with SLAC tested over Gb/s networks in US /networks/TCP-LP Denial of Service A malicious way to consume resources in a network, a server cluster or in an end host, thereby denying service to other legitimate users Example Well-known TCP’s vulnerability to high-rate non-responsive flows Design Principles - Revisited Implement more intelligence at routers? Scalability issue Detect misbehaving flows in routers is a hard problem Needle in a haystack Design Principles - Revisited Design Principles - Revisited Design Principles - Revisited End-Point Protocol Design Performance vs. Security End-point protocols are designed to maximize performance, but ignore security 95% of the Internet traffic is TCP traffic Can have catastrophic consequences DoS-resilient protocol design Jointly optimize performance and security Outperforms the core-based solutions Remaining Outline En