90 likes | 374 Views
Evaluation of IGMP/MLD Optimizations for Mobility Stig Venaas Behcet Sarikaya November 2009. Multimob WG IETF 76. Charter Item. To assess IGMPv3 and MLDv2 and determine to what extent these methods are sufficient in a mobile environment
E N D
Evaluation of IGMP/MLD Optimizations for Mobility Stig VenaasBehcet SarikayaNovember 2009 Multimob WGIETF 76
Charter Item • To assess IGMPv3 and MLDv2 and determineto what extent these methods are sufficient in a mobile environment • Recommend appropriate selection of timer values and protocol parameters
Current Draft • draft-asaeda-multimob-igmp-mld-optimization-01 • Section 3 is basically on evaluating current IGMPv3/MLDv2 procedures • Membership status tracking • Query Processing • Report Processing • Source Filtering • Section 4 suggests explicit membership notifications by mobile nodes
Current Draft • Section 6 is on tuning the timers and counters • Section 6 has several TODO paragraphs, it needs to be completed
What Should be in WG Draft? • Come up with mobile environment related adoptations or “optimizations” of IGMPv3/MLDv2 • General queries • Unsolicited notifications • Discuss tuning of IGMPv3/MLDv2 timers and counters and suggest new values
Evaluation • Discussion and recommendation on Lightweight IGMP/MLD • These protocols are not much relevant to Multimob • The documents are already progressing well in IESG • So should Lightweight IGML/MLD related text be removed?
Evaluation • Optimizations in Section 3 and 4. Charter requires no modifications to IGMPv3/MLDv2 which means no new message types and backward compatibility, etc. • Unsolicited IGMP/MLD Reports break this charter requirement. So they should be removed. • Unicasting general queries seems ?? • Multicasting notifications from the host seems ?? • Tuning of timers/counters: it is difficult to recommend definitive values due to the dynamic network conditions in wireless links
Evaluation • Overall, does draft-asaeda-multimob-igmp-mld-optimization-01 form a good basis for the charter item on IGMPv3/MLDv2? • Do we recommend adopting a revised version of this draft as a working group draft?