1 / 8

CS 268: Lecture 25 Indirection

CS 268: Lecture 25 Indirection. Ion Stoica Computer Science Division Department of Electrical Engineering and Computer Sciences University of California, Berkeley Berkeley, CA 94720-1776. DNS Server. Home Agent. “foo.org”. (IP home ,data). foo.org IP foo. IP home IP mobile. IP foo.

darren
Download Presentation

CS 268: Lecture 25 Indirection

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. CS 268: Lecture 25Indirection Ion Stoica Computer Science Division Department of Electrical Engineering and Computer Sciences University of California, Berkeley Berkeley, CA 94720-1776

  2. DNS Server Home Agent “foo.org” (IPhome,data) foo.org IPfoo IPhome IPmobile IPfoo (IPmobile,data) (IPdst:Pdst,data) (IPfoot,data) IPfoo IPmofile DNS Mobile IP NAT Box (IPM,data) (IPnat:Pnat,data) IPnat:Pnat IPdst:Pdst Internet (IPMIPR1) (IPMIPR2) (IPR2,data) (IPR1,data) IPdst IPR2 IPR1 NAT IP Multicast Indirection is Everywhere!

  3. Why Indirection? • Decouple sender behavior from receiver behavior • Receiver movements and address changes transparent to sender • Changes in the number of receivers, transparent to sender • …

  4. Discussion • Control • Indirection point point wherecontrol is transferred from sender to receiver • Translation/forwarding entry usually controlled by receiver • Resolution • Early binding (e.g., DNS, SIP, HIP) • Late binding (e.g., Mobile IP, NAT,IP multicast, IP anycast)

  5. End-host Empowerment • Both the sender and receiver should be able to explicitly control the service-path • Note: multiple indirection points possible Internet Application Layer Service (ALS) 1 ALS 2 ALS 3 ALS 4 Receiver Indirection point (tussle boundary) Sender sender control receiver control

  6. ALS 2 (S2) ALS 1 (S1) ([idS1,idR], data) i3 idS2 S2 ids1 S1 R Internet i3 Name resolution infrastructure (e.g., OpenDHT) idS2 S2 idS1 idS1 S1 idR R S1 idS2 R idR S2 ([idS1,idS2], data) idS2 idR R idR [idS2,R] ALS 1 (S1) ALS 2 (S2) Internet DOA Realization: i3 vs DOA

  7. Discussion: DOA vs. HIP vs. i3 (1/2) • Naming: Flat ID space • DOA: two levels of IDs • EID: end-host IDs • SID: service IDs • Resolution: (SIDEID); (EIDIPaddr) • HIP • HIT: host identity tag • Resolution: (HITIPaddr) • i3 • ID: identifies “anything” • Resolution: (ID[IPaddr:Port]), where [IPaddr:Port] represents de-multiplexer

  8. Discussion: DOA vs. HIP vs. i3 (2/2) • Resolution: • HIP and DOA: early binding • i3 : late binding: • Lookup & Forwarding • i3: combines lookup & forwarding infrastructure • Degenerates to a lookup infrastructure when shortcuts are used • DOA: forwarding state at ALSes

More Related