90 likes | 199 Views
This research presents a Generic Feedback Redirection Service aimed at addressing the feedback implosion problem in reliable multicast protocols. The Lightweight Multicast Service (LMS) provides a potential solution by minimizing excessive feedback through the aggregation of feedback at routers. By implementing dynamic repairer identification techniques and storing essential feedback information, the service facilitates efficient end-to-end communication. Future work includes simulations, latency comparisons, and analytical modeling to evaluate the efficacy of this service in enhancing multicast transmission reliability.
E N D
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 ATTACHED
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
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
A Feedback Redirection Service for Reliable Multicast 1 SOURCE 3 2 4 6 7 5 0 Maintain Dynamic Repairer Identification here 8 7 9
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 ?
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
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 ?
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)