Multicast Mobility in MIPv6: Problem Statement & Brief Survey Update - draft-irtf-mobopts-mmcastv6-ps-02.txt - Thomas C. Schmidt, Matthias Wählisch {t.schmidt, waehlisch}@ieee.org HAW Hamburg & link-lab

Outline Status of the Draft Changes in Version 2 Scope of Document PMIPv6 Aspects MLD o.k.? Discussion: Future Steps & Open Issues ?

Status of the Draft State at IETF69: draft-irtf-mobopts-mmcastv6-ps-01.txt Version 01 – has received Conceptual review by Kevin C. Almeroth Positive reviews by Hesham Soliman & Stig Venaas Version 02 – major update including Document scope section added Extension of L2 section PMIPv6 aspects added Future roadmap section added Editorial improvements, updated bibliography

Scope: Focal Scenario – MIPv6 +------+ +------+ | MN | =====> | MN | | . +-------+ +-------+ | AR 1 | | AR 2 | | | *** *** *** *** * ** ** ** * * * * Fixed Internet * Covers key issues Mobile Multicast Membership as Listener as Source (ASM/SSM) Interplay of Multicast Routing and Mobility

PMIPv6 Aspects MN sees point-to-point link via mobile access gateway (MAG) to local mobility anchor (LMA/HA) Inherits tunnel convergence problem and MLD query issues on point-to-point links Prevents utilization of L2 multipoint capabilities Future designs / extensions to shared links should foresee native multicast distribution towards the edge network

Controversial Topic: Is MLD Itself a Problem? MLD well suitable to initiate L3+L2 multicast contexts Immediately after handoff Mobility agents/proxies (HA/MAP/AR) may Shield unneeded queries (P-t-P links) Track membership states to avoid query timeouts Otherwise: Query timers may be adjusted for mobility Why do we want to change MLD?

Future Steps: Review of Version 2 Imed Romdhani: Elaborate on MLD issues in problem section  Add transport issues, e.g., MRT … ? Action: - Refine multicast listener problem section Question: Do we want to extend the document on (multiple) transport layer aspects beyond UDP/RTP?

Questions Deployment Aspects: Layer 2 Aspects: Gaps to fill? Further prospects relevant for deployment? Layer 2 Aspects: Gaps to fill? Performance data for 802.16, MBMS, DVB-H? Multihoming: Are there Multicast-specific Issues? Interface/connectivity maintenance → unicast Of course: Multicast context transfer may use multiple bindings … as unicast does

Open Issues Anything else missing? Should we finalize this document and start working on the solutions?