Comparison of Multicast Mobility Route Optimization draft-von-hugo-multimob-ro-compa-00.txt AMT-approach (WG MBONED) and proposed drafts within WG MultiMob D. von Hugo and H. 1

Requirements and charter demand Issues in requirements draft deng-multimob-pmip6-requirements-03 – Conservation of (radio and backhaul) network resources E.g. in terms of tunnel convergence, direct (local) routing option, dedicated multicast LMA option, … Set of ‘agreed on’ requirements to design/evaluate proposed approaches for extensions/modification – Multimob base protocol(s) – Adaption of PMIPv6 as referred to in Multimob base protocol – IGMP/MLD extension (after completion of MLD parameter tuning) Updated Charter demands – Jun Initial version of document on PMIPv6 routing optimizations to avoid tunnel convergence problem 2

How to achieve PMIPv6 routing optimizations Is there already an existing protocol (proposal)? – E.g. WG MBONED approach AMT If not which approach would solve the problem best? – Comparison of drafts I-D.asaeda-multimob-pmip6-extension I-D.sijeon-multimob-mms-pmip6 I-D.zuniga-multimob-smspmip 3

AddressingPMIPv6 routing optimizations to avoid tunnel convergence problem I-D.ietf-mboned-auto-multicast AMT approach of WG MBONED (Multicast Backbone Deployment) applied to PMIPv6 AMT MN1 AMT AMT Native Multicast Internet PMIP6 domainAMT-Tunnel MN2 MC source 4

AddressingPMIPv6 routing optimizations to avoid tunnel convergence problem AMT (Automatic Multicast communication without explicit Tunnels) – may be applied to isolated multicast-enabled sites or hosts, attached to a network without native multicast support - without need for any manual configuration. – Analogy between AMT-Gateway/-Relay and PMIP MAG/LMA also implies additional complexity – Adaptation of this scheme to PMIPv6 domains means additional interface and tunnel beside existing MAG-LMA relation – Local routing within PMIP domain seems to be more efficient via MLD 5

AddressingPMIPv6 routing optimizations to avoid tunnel convergence problem I-D.asaeda-multimob-pmip6-extension proposes for a PMIPv6 domain the (dynamic or static) establishment of a common dedicated multicast tunnel. Both MAG and LMA may be operated as MLD proxy or multicast router. 3 different scenarios Open question: > 1 LMA per MN? MN1 MC source Internet PMIP6 domain Local MC source M-Tunnel MN2 6

AddressingPMIPv6 routing optimizations to avoid tunnel convergence problem I-D.sijeon-multimob-mms- pmip6 describes a direct or local routing approach applicable to a network topology where multicast content delivery source is located in the same network such that the optimal multicast service delivery path is not via LMA. Support of optimal local (direct) routing uses a direct connection between MLD proxy at MAG and a Multicast router separated from LMA. p-MAG MN1 n-MAG LMA UC source MR Internet PMIP6 domain MN2 Local MC source 7

AddressingPMIPv6 routing optimizations to avoid tunnel convergence problem I-D.zuniga-multimob-smspmip proposes a multicast traffic replication mechanism by introducing a Dedicated Multicast LMA (M-LMA) (allowing also a Hybrid U/M one) as topological anchor point for multicast traffic. Protocol complexity is reduced in terms of time consuming tunnel set-up by definition of pre- or post-configured tunnels between LMA and MAG. p-MAG MN1 n-MAG LMA MC source DM-LMA Internet PMIP6 domain MN2 8

Comparison of proposed approaches proposalTypical feature Base multimob solution MLD/MRRequires extensions scalability asaeda- multimob- pmip6- extension M-tunnelYesBoth at LMA/alternat ive at MAG To PBU, … CXTP for dynamic tunnel management sijeon- multimob- mms-pmip6 Direct routing via NoMR instead of LMA noYes - but only applicable to locally available MC content zuniga- multimob- smspmip M-LMA or Hybrid U/M-LMA YesBoth at MAG New BUL, policy profile, … ? ietf-mboned- auto- multicast AMT-Gate- way/Relay Relation NonoNoYes 9