httpn的mslcsmitedu.pptVIP

End-to-end Congestion Management for the NGI Hari Balakrishnan MIT Laboratory for Computer Science / DARPA NGI PI Meeting October 2, 2000 Srinivasan Seshan (CMU), Frans Kaashoek (MIT) Dave Andersen, Deepak Bansal, Dorothy Curtis, Nick Feamster iNAT Project: Motivation Increasing heterogeneity in the Internet Nodes: Mobiles, devices, sensors,... Links: Optical, wireless,... Services applications: Web, telepresence, streaming, remote device control Need a general solution for applications to discover resources and deal with mobility Need a general framework for learning about and adapting to changing network conditions iNAT Approach Intelligent naming Resource discovery: Intentional Naming System (INS) using expressive names and self-configuring name resolver overlay network Mobility: Via dynamic name updates and secure connection migration (check out demo!) Adaptive transmission End-system congestion management and adaptation framework for the NGI Congestion Manager software and algorithms The Problem End-to-end congestion management is essential Reacting when congestion occurs Probing for spare bandwidth when it doesn’t The future isn’t about just TCP! Many applications are inherently adaptive, but they don’t adapt today Enable applications to learn about network conditions Many applications use concurrent flows between sender and receiver, which has adverse effects Enable efficient multiplexing and path sharing The Big Picture CM Architecture Transmission API Traditional kernel buffered-send has problems Does not allow app to “pull back” data Transmission API (cont.) Callback-based send Transmission API (cont.) Request API works for asynchronous sources while (some_event) { get_data(); /* e.g., from a file, image capture, etc. */ send_data(); /* call cm_request() and send on callback */ } But what about synchronous sources (e.g., audio at constant sampling rate)? do_every_t_ms { /* timer loop */ get_data(); send(); /* oops, waiting for