1 / 12

An End-to-End Approach to Host Mobility

An End-to-End Approach to Host Mobility. MobiCom ’00 Alex C. Snoeren and Hari Balakrishnan MIT Lab. For Computer Science Presenter: SangJeong Lee (3/18). Problem. Supporting Host Mobility Mobile? (mid ‘90s ~) Addressing Locating a mobile host Seamless connection Existing Solution

gefjun
Download Presentation

An End-to-End Approach to Host Mobility

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An End-to-End Approach to Host Mobility MobiCom ’00 Alex C. Snoeren and Hari Balakrishnan MIT Lab. For Computer Science Presenter: SangJeong Lee (3/18)

  2. Problem • Supporting Host Mobility • Mobile? (mid ‘90s ~) • Addressing • Locating a mobile host • Seamless connection • Existing Solution • Network level approach • Mobile IP: pure routing solution, transparent to upper layers, triangle routing, weak to ingress filtering, permanent home address • Application level approach • Proxy approach, client part • Transport level approach • MSOCKS: redirection using split-connection proxy at transport layer • The paper’s work

  3. Solution Approach • Solution Approach • Addressing • Manual, DHCP, or auto-configuration protocol • Don’t care • Locating a mobile host • No third-party agents • DNS lookup • Secure DNS update • Seamless connection • End-to-end approach • No third-party agents • TCP connection migration • Add TCP migration option

  4. Solution Approach (Cont.) • Security Issues • Denial of service • Migrate request (SYN): validation check with pre-computable token (1/264) • Connection hijacking • Replayed Migrate SYNs  Ignore duplicate Migrate SYNs • Bogus Migrate SYNs  New Migrate-Permitted option after handovers • Key security • ECDH • IPSec • Security associations (SAs) and security policy database (SPD) are on IP-address basis • Beyond the scope of the paper

  5. Strong Points • End-to-End Approach • No third-party participants • Routing optimization • Performance • Avoid ingress filtering due to DOS attack • Not consider IP address as an identity of a host, just an attachment point • Transport Approach • More deployable than Mobile IP • Deployed as TCP option  Backward compatible • Application is aware of handovers  optimization

  6. Weak Points • Deployment Issues • Changes to transport protocol • Address caching generally • Proxies and NATS  Secure? • Simultaneous Moves • Primarily targeting infrastructure-based • Not ad-hoc network topology • No Performance Comparison • Not experiment, but prototyping • Just proving that it behaves well

  7. New Ideas • Simultaneous Moves • Fast Handover • Issuing three DUP-ACKs immediately after migration • Different bandwidths of before- and after-migration • Deployment • Effective way • Mobile IP, Multicast, Active Network, … • Backward compatibility

  8. Mobile IP Overview Sender Home Agent Foreign Agent Tunnel Home Address Mobile Host Handoff Care-of Address

  9. TCP Connection Migration

  10. TCP Migrate-Permitted Option

  11. TCP Migrate Option

  12. MIGRATE_WAIT State

More Related