IGMP and MLD Op-miza-on for Mobile Hosts and Routers

Transcription

1 76 th IETF, Nov. 2009, Hiroshima, Japan IGMP and MLD Op-miza-on for Mobile Hosts and Routers dra< asaeda mul-mob igmp mld op-miza-on 01 Hitoshi Asaeda (Keio University) 1

2 Overview This dra< aims to describe the ways of IGMP/ MLD protocol op-miza-on for mobility Discussion Various -mer values IGMP/MLD use Router and host behaviors for IGMP/MLD Note this may be excluded from dra< Concept Minimize mobile node s power consump-on, and maximize the available wireless resource By limi-ng the number of transmi\ed IGMP/MLD messages But does not lead addi-onal join and leave latency

3 Op-miza-on What is the op-miza-on? Need to provide defini-ve sta$c -mer values that could fit for any kinds of dynamic network condi-ons? Need to find the best fit -mer value for any kind of situa-on?

4 Proposals Tracking of membership status IGMP/MLD Query processing IGMP/MLD Report processing Mul-cast source filter Explicit membership no-fica-on

5 Tracking of Membership Status Explicit tracking func-on is the standard func-on defined in [RFC3376][RFC3810] Pros. Reduces the number of solicited membership reports requested by periodical IGMP/MLD Queries Possibly beneficial for shorter leave latency Cons. Router needs processing capability and large memory (Not con) IGMP/MLD Queries s-ll needed for missing nodes or old nodes and to be robust from lost packets No -mer change, no behavior change

6 IGMP/MLD Query Processing IGMP/MLD General Query is unicasted to recorded members and mul-casted to refresh membership info. with longer interval Pros. Make only the ac-ve nodes that have been receiving mul-cast contents respond the IGMP/MLD General Queries Cons. Longer [Mul-cast Query Interval] may introduce longer join/leave latency (Not con) IGMP/MLD Queries s-ll needed for missing nodes or old nodes, to be robust from lost packets New -mer values [Query Interval] is common, but [Mul-cast Query Interval] is defined as a new -mer value Moved to the extension dra<?

7 IGMP/MLD Report Processing Describe the a\en-on of or unspecified address (::) as the source address of IGMP/MLD Report Explicit tracking func-on should be disabled for the node whose des-na-on address is all 0 No special considera-on for mobility Will merge to the sec-on describing explicit tracking func-on

8 Mul-cast Source Filter Recommenda-on of LW IGMPv3/LW MLDv2 Pros. No possible applica-ons using EXCLUDE (S,G) join Both host side and router side implementa-ons of LW IGMPv3/LW MLDv2 are much simpler EXCLUDE (S,G) just breaks SSM communica-on And forwards many unneeded data (which only needed (?) by EXCLUDE join requester) Cons. Nothing This dra< does not deny to support the full version IGMPv3 [RFC3376] /MLDv2 [RFC3810]

9 Explicit Membership No-fica-on IGMP/MLD No-fica-on opera-on Mobile host periodically sends Current State Record messages expressing which mul-cast sessions the host is joining Pros. For both [Mul-cast Query Interval] and [Query Interval], much longer intervals can be set up Reduce the total number of Queries and Reports Cons. Due to addi-onal -mer value, it requires addi-onal complexity to adjust dynamic network condi-on New -mer value and new behavior [No-fica-on Interval] Moved to the extension dra<

10 Revised Plan Tracking of membership status IGMP/MLD Query processing Moved to extension dra< IGMP/MLD Report processing Merge into sect. describing explicit tracking func-on Mul-cast source filter Including LW IGMPv3/MLDv2 recommenda-on Explicit membership no-fica-on Moved to extension dra< Other condi-ons that should be discussed?

11 Conclusion This dra< aims to describe the ways of IGMP/ MLD protocol op-miza-on for mobility Defini-ve sta-c -mer values may or may not be provided in this dra< Next step Revise the dra<? Intended status: Informa-onal or BCP Or, new requirement dra< and extension dra<? Comment?