Presentation on theme: "FIND Mobility/DTN Sub-Group Meeting Report At WINLAB, Rutgers University, NJ May 29-30, 2007 Presented by: Sanjoy Paul, WINLAB, Rutgers U."— Presentation transcript:
FIND Mobility/DTN Sub-Group Meeting Report At WINLAB, Rutgers University, NJ May 29-30, 2007 Presented by: Sanjoy Paul, WINLAB, Rutgers U.
Summary 1.5 day Meeting at WINLAB, Rutgers University, May 29-30 5 groups: 3 FIND projects and 2 external groups with projects in related space –Transient Network Architecture (TNA) -- CNRI/UNM: Henry Jerez –Day After Network (DAN) --- UIUC: Robin Kravets –Postcards from the Edge: A Cache and Forward Architecture – Rutgers & UMASS: Roy Yates, Sanjoy Paul, Dipankar Raychoudhuri and Jim Kurose –SPINDLE/DTN – BBN: Rajesh Krishnan –Ambient Networks – EU (Ericsson): Lars Lundgren Goal: explore synergies, identify gaps, define a comprehensive project in the area Agenda: –20-30 min talk from each of the 5 groups –Look for Similarities and Synergies –Use of GENI: What kind of experimental facility (say in GENI) be most valuable to instantiate the specific research project –Identify open issues/"holes" Summary of results to be presented at FIND meeting Detailed agenda, slides, etc. posted at: –http://gaia.cs.umass.edu/rutgers_FIND_meetinghttp://gaia.cs.umass.edu/rutgers_FIND_meeting FINDFIND
Synergies The main design drivers for the original Internet have changed Future Internet driven by –Mobility Router, and network mobility Endpoint mobility (nodes and services) –Disconnections Contemporaneous end-to-end path does not exist in many situations: special case Persistent storage in network nodes? –Efficient Content Dissemination/Access Content-oriented networking Naming/Role-based networking/Late-binding of names Service-oriented networking –Is this a special case of content-oriented networking? Are the above solved using a common overlay or in the core? –Enhance core routing –Redefine the functionality of the endpoint OR –Build a common overlay that takes advantage of the existing Internet
Mobility Some people think mobility is portability –Disconnecting laptop from one Access Point and reconnecting at a different Access Point What we mean by mobility is all of the below: –Endpoint moving continuously (laptop/cellphone in a car/bus) –Service moving in a seamless manner (VPN, Web, VoIP, Video) –Router carrying content as it moves –Network as a whole is moving
Disconnections/Opportunistic Some people think Disconnection is a long-term event What we mean by Disconnection/Opportunistic Transport is all of the below: –Disconnection resulting from distance (out of range transmissions) –Disconnection resulting from shielding (propagation) –Disconnection resulting from low battery power –Fluctuations resulting from time-varying nature of wireless links (time-varying capacity as well as error rate) Transport opportunistically when link has higher capacity and lower error rate –Use a moving vehicle (entity) to cache, carry and opportunistically transport content to another entity in the network
Content Dissemination/Access Some people think content dissemination is synonymous with caching/mirroring infrastructure (e.g., Akamai) –Deploy caching servers in select locations of the network –Replicate popular contents of a customer in the caching servers –Direct end-users to the nearest caching server –Centralized optimization and intelligence resides outside the network What we mean by content dissemination/access is all of the below: –Content is first class element in the network; not a side-effect of client- server conversation –Content is explicitly requested by end-clients from the network –Content discovery within the network –Content caching within the network –Content routing within the network –Distributed optimization and intelligence resides inside the network
Common Architectural Framework Introduction of functionality in the network (ALL) –Storage –More hop-by-hop functionality A new kind of naming and addressing (TNA/DAN) –Persistent identifiers for endpoints, roles, services –Content addressability Leverage the existing DTNRG work and build on it (BBN/Postcards) –DTN Architecture –Bundle Protocol –Bundle Security Protocol –Metadata Extension Block –Implementations –Related algorithms
Open Problems Routing –Scaleable integrated approaches that work in wired, wireless, mobile, and DTN environments in an end-to-end manner Should we explore this as a theme in an upcoming FIND meeting? –Interplay with name resolution and content (including queries) Discovery –Content discovery –Efficient peer/cache discovery and association –Available service discovery Content –Rights management –Privacy –Consistency and freshness management –Accounting (e.g., number of downloads of a movie/song) Designing the following into the system –Network heterogeneity –Diagnostics and Manageability –Security –Context awareness
Participants Jim Kurose, UMass, Amherst (Postcards) Sanjoy Paul, WINLAB, Rutgers U. (Postcards) Roy Yates, WINLAB, Rutgers U. (Postcards) Dipankar Raychaudhuri, WINLAB, Rutgers U. (Postcards) Henry Jerez, CNRI/UNM (TNA) Robin Kravets, UIUC (DAN) Lars Lundgren, Ericsson (Ambient Networks) Rajesh Krishnan, BBN (SPINDLE/DTN)
GENI Use Case Content (pictures, video clips, etc.) and Service (voice, video, messaging, VPN) delivery where the senders and/or receivers are mobile and may not be connected on a continuous basis –Mobile Host MH1 uploading a movie to Mobile Host MH2 –During the upload, MH2 gets disconnected due to mobility and then reconnected at a different point in the network –Fixed Host FH1 requests the same movie from the network (content)
PWN1 PEN1 PWN2PWN3 PEN4 Mobile Host (MH1) PCN1 PCN4 PEN3 PEN2 PWN4PWN5PWN6 PEN5 PWN7 Mobile Host (MH1) PCN5 Mobile Host (MH2) PWN6 Wireless subnet Fixed Wireless Host (FH1) PCN2 PCN3 -- Mobile Host MH1 uploading a movie to Mobile Host MH2 -- During the upload, MH2 gets disconnected due to mobility and then reconnected at a different point in the network -- Fixed Host FH1 requests the same movie from the network (content) PCN: Programmable Core Node PEN: Programmable Edge Node PWN: Programmable Wireless Node GENI Physical Network
Wireless subnet PWN1 PEN1 PWN3 PEN4 Mobile Host (MH1) PEN3 PEN2 PWN2 GENI Backbone Wireless subnet PWN4PWN5PWN6 PEN5 PWN7PWN6 Wireless subnet Mobile Host (MH2) -- Mobile Host MH1 uploading a movie to Mobile Host MH2 -- During the upload, MH2 gets disconnected due to mobility and then reconnected at a different point in the network -- Fixed Host FH1 requests the same movie from the network (content) PCN: Programmable Core Node PEN: Programmable Edge Node PWN: Programmable Wireless Node GENI Logical Network Fixed Wireless Host (FH1)
Wireless subnet PWN1 PEN1 PWN3 PEN4 Mobile Host (MH1) PEN3 PEN2 PWN2 GENI Backbone Wireless subnet PWN4PWN5PWN6 PEN5 PWN7 Mobile Host (MH1) PWN6 Wireless subnet Mobile Host (MH2) 1. MH1 deposits some chunks of a file in PWN2 and later some other chunks in PWN1 2. Chunks are forwarded hop-by-hop towards MH2s point of attachment PWN4. Chunks can be cached in intermediate nodes 3. As MH2s point of attachment changes, chunks are forwarded towards PWN7 5. Request from FH1 for the same content is served off PEN3 where it is cached 4. Chunks not delivered to MH2 are redirected from PWN4 to PWN7 Fixed Wireless Host (FH1)
Your consent to our cookies if you continue to use this website.