1. Multimob_BarBOF_dvh.ppt Multimob requirements towards existing mobility protocols Issues for update of draft ‚Multicast Support Requirements for Proxy Mobile IPv6‘ (draft-deng-multimob- pmip6-requirement-01) until next BOF

2. Multimob_BarBOF_dvh.ppt Motivation Why multicast mobility? Operator and commercial trends –Everything goes mobile / trend towards fixed-mobile converged networks and services, providing unified communications experience via convergent devices Large market and deployment expectations –Other standardisation organisations: 3GPP Rel. 9 MBMS (Multimedia Broadcast/Multicast Service) specification: ‘MBMS shall allow the utilisation of solutions using IETF protocols - MBMS architecture enables the efficient usage of radio-network and core-network resources, with an emphasis on radio interface efficiency’ Exemplary applications to benefit from efficient mobile multicast –Push to talk over WLAN and cellular (packet based P2MP group voice) –Multi-party audio/video conferencing –Mobile chat and (instant) messaging –Data file transfer to recipients group (also on the move) –multimedia streaming (video, games, music) Mobility (cell and technology handover) may not only occur due to user movement but also in case of operator decision e.g. for network load redistribution

3. Multimob_BarBOF_dvh.ppt Clear requirements draft necessary for successful BOF. Issues raised at IETF-73. multimob-pmip6-requirement summarizes requirements for multicast listener support in PMIPv6 scenarios –Current draft confusing, too many requirements –Optimization may not be protocol work, might be BCP, etc. –we need discussion, maybe even a document on how we deploy multicast over mobility –Missing multicast support in PMIP no problem as MIP defines measures (i.e. BT, RS) –focusing requirements on handover support and eliminating tunnels? –PMIPv6 is too restrictive? –NetLMM: overall problem defining multicast with mobility - then talk about PMIPv6

4. Multimob_BarBOF_dvh.ppt Proposed Multimob requirements. Topics of current draft. Basic functional requirements for new multicast mobility management protocol: –Transparent support of multicast traffic reception using existing protocols (i.e. Any Source Multicast - ASM or Source Specific Multicast - SSM) –Support of multicast group subscription initiated by the mobile terminal and by the network –Support of service continuity during inter-system mobility without terminal interaction or recognition –Compliance with transmission packet size restriction –Compliance with existing multicast scoping rules and restrictions –Support of both IPv6/IPv4 only and dual stack network and terminal nodes –Compatibility with fixed and mobile network architecture? –Compatibility with protocol structure of existing mobility management such as multihoming and vertical handover Performance requirements –Support of native multicast forwarding and efficient use of network resources and existing link layer multipoint distribution –Minimization of multicast forwarding delays to provide seamless and fast handovers for real-time services similar to unicast communication –Minimization or avoidance of additional packet loss (as compared to unicast performance) for mobile multicast transmission (seamless) –Minimization or avoidance of additional packet loss (as compared to static multicast transmission performance) ? –Minimization of transport costs (load on forwarding link and overhead on multicast delivery path) –Grant of routing convergence even in case of rapid terminal movement and high handover frequency –Robustness against irregular terminal movement (e.g. ping-pong mobility) and no compromise of (unicast) network performance Architecture requirements –Multicast bandwidth control for a user port to support a range of different service classes with various QoS requirements –Multicast AAA control preservation and application (e.g. access and admission control, accounting) Security requirements –no degradation of security protection of the basic mobility AAA mechanism –Grant of integrity of multicast sources prior to service delivery to prevent unauthorized sources from content distribution

5. Multimob_BarBOF_dvh.ppt Way forward? Work to be done until IETF-74. clarification of basics of mobile multicast and focusing on the deployment problems? –Inefficiency of MIP6 multicast support (BT, RS) from a network operator viewpoint –Compatibility to existing mobile management and fixed multicast protocols and architecture –Performance enhancement for multicast service users

6. Multimob_BarBOF_dvh.ppt Backup Motivation for standardisation work. Exemplary market and deployment expectations –Gartner: IPTV subscribers will grow to 50 million in 2010 –Infonetics: IPTV subscribers to reach 53 million in 2009 / equipment and service income of US$44 billion –Frost & Sullivan: Asia-Pacific mobile video services market growth by yearly rate of 27.4 % –IDC: converged mobile devices to adopt 82 Million units by 2011 –ITM (Informa Telecoms & Media): 120 million converged devices by 2012 –ABI: Capital expenditure for data services will surpass that for voice sometime in 2009 as 4G starts to arrive. By 2013, the percentage split will be 28 per cent for voice, 67 per cent for data, and five per cent for mobile TV."