CSE 588 - Spring 2002 - Transcription

CSE Home

CSE 588 Home

Scribe List

About Us

Search

Contact Info

• how would you redesign = BGP?
• ad-hoc routing is the answer? =
• how would you route in ad-hoc = configuration of portable computers?
• applications of ad-hoc routing: =
• military
• neighborhood, frat. house
• roof top network
• sensor nets (airplanes)
• appliances
• power savings: bluetooth vs. = 802.11
• options:
• wired base stations
• wired forwarding: tunneling other = people's packets
• how to prevent it from saturating my = own bandwidth?
• not very practical for short-range = devices
• does it have a future?
• Iridium, a project that could have = used some sort of ad-hoc routing
• is unreliable connection better than = no connection?
• how would you design ad-hoc routing = system? 
• what are the goals of such routing = system?
• connectivity with mobility
• fast convergence
• power/cpu/bandwidth
• velocity constraints?
• dynamic session support (while routing = changes underneath)
• bandwidth
• congestion/flow control
• security
• access control (who can use the = network)
• approaches to design it:
• link state:
• bad idea, topology changes too = often
• unless you access the network much = more often that topology changes underneath
• distance vector:
• need lazy computations
• frequency of updates proportional to = the velocity
• source routing, full = routing
• GPS
• aging/history information
• how do you choose  your neighbors = - beacon sending packets out to the neighbors
• arbitration: multiple people need to = talk through the common node
• carrier sense
• if you hear somebody talking - = don’t interrupt
• RTS (request to send), CTS (clear to = send)

	Department of Computer Science & Engineering University of Washington Box 352350 Seattle, WA  98195-2350 (206) 543-1695 voice, (206) 543-2969 FAX [comments to owner-cse588]