1 / 9

A Generic Feedback Redirection Service for Reliable Multicast Protocols

A Generic Feedback Redirection Service for Reliable Multicast Protocols. Jaiwant Mulik Department of Computer and Information Sciences Temple University. The Feedback Implosion Problem. 1. THIS DOES NOT SCALE. SOURCE. 3. 2. 4. 6. 7. 5. 0. 8. 7. 9. ASSUME ALL ROUTERS HAVE HOST

clinton-pierce
Télécharger la présentation

A Generic Feedback Redirection Service for Reliable Multicast Protocols

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. A Generic Feedback Redirection Service for Reliable Multicast Protocols Jaiwant Mulik Department of Computer and Information Sciences Temple University

  2. The Feedback Implosion Problem 1 THIS DOES NOT SCALE SOURCE 3 2 4 6 7 5 0 8 7 9 ASSUME ALL ROUTERS HAVE HOST ATTACHED

  3. Lightweight Multicast Service (LMS) solution to feedback implosion problem JUST ONE "NACK" 1 SOURCE ROUTER 2 HAS LINK TO ROUTER 5 AS ITS REPLIER LINK 3 2 4 6 7 5 0 8 7 9 ROUTER 6 HAS LINK TO ROUTER 0 AS ITS REPLIER LINK

  4. Motivation for a GENERIC Service LOSS RECOVERY TECHNIQUES END TO END ROUTER ASSIST (SRM,RMTP) (PGM, LMS) These use timers to suppress feedback These aggregate feedback at routers A TRANSPARENT GENERIC FEEDBACK REDIRECTION SERVICE COULD HELP

  5. A Feedback Redirection Service for Reliable Multicast 1 SOURCE 3 2 4 6 7 5 0 Maintain Dynamic Repairer Identification here 8 7 9

  6. Acquiring and Maintaining Repairer Identification Information 1 SOURCE 3 2 4 6 7 5 0 Maintain Dynamic Repairer Identification here 8 9 7 What feedback redirection information do we maintain ? Where do we store it ? How do we acquire and maintain it ? How do we act on the replier identification information ?

  7. Acquiring and Maintaining Repairer Identification Information What feedback redirection information do we maintain ? • Interface Index List • Host list Where do we store the replier identification information ? • Multicast Forwarding Cache

  8. Acquiring and Maintaining Repairer Identification Information How do we acquire it ? 1 SOURCE • Reactive • Proactive • Manual 3 2 4 6 7 5 0 8 7 9 How do we act on the replier identification information ?

  9. Future Work • Simulation in NS-2 • Recovery latency and bandwidth consumption comparison in SRM with and without the feedback redirection service • Analytical Modeling • Router Assist Services and Hacks (RASH)

More Related