STANDARDIZATION OF SOLUTIONS

IETF-70 in Vancouver 1

STANDARDIZATION

OF

SOLUTIONS

Behcet Sarikaya

[email protected]

Huawei Research

IETF-70 in Vancouver 2

Multimob Solutions

• Two categories so far– Agent-based– Protocol-based

• Protocol solutions to modify– MLDv2 – MIPv6– HMIPv6– FMIPv6

IETF-70 in Vancouver 3

Multicast tunneling optimization for Mobile IPv6

P.Yang, H. Deng, Q. Wu

IETF-70 in Vancouver 4

Solution to optimize multicast routing in RFC3775

Two ways to do multicast routing in RFC3775– Remote multicast subscription: It relies on multicast

router, which is seldom available in the mobile network. It also suffers from the slow handover

– Bi-directional tunneling: Simple and transparent. It suffers from multiple tunnel overhead.

• The solution is proposed to optimize the bi-directional tunneling multicast solution of MIPv6. With simple extension, this solution could also be applied to other extended MIPv6 (PMIP, DSMIP, HMIP) as well.

IETF-70 in Vancouver 5

Mobile Multicast Agent

HA->MMA/AR MMA/AR ->MN

Tunnel format

Single Tunnel

IETF-70 in Vancouver 6

Call flow

IETF-70 in Vancouver 7

Agent-based multicast support for NEMO

D. Von Hugo

Deutsche Telecom

IETF-70 in Vancouver 8

Multicast Anchor Agent for NEMO• Agent approach adapted to support multicast listeners and senders located

within a moving IPv6 network (NEMO)– NEMO: Mobile Router (MR) handles all routing related tasks to provide

connectivity between the Mobile Network Nodes (MNNs) and an access network including mobility management

– MR also subscribes to multicast groups and forwards emerging multicast traffic on behalf of a MNN.

• Hierarchical multicast agent as logical entity providing an anchor to multicast tree for optimised routing of multicast data

• MR with corresponding functionality to decide on proper specific agent for distinct multicast traffic

• Decision and selection of MAA location is done by MR specifically for each multicast flow as a function of traffic characteristic (send, receive, session duration, ...)

• MR movement (HO rate) and multicast tree path distance as criteria• Potential MAA locations are

– MR HA– Current, former (old) or future (new) AR (AR/oAR/nAR)– Dedicated hierarchical multicast agent (e.g. at Gateway/GW or Local Mobility

Agent/LMA)• Forwarding of Multicast traffic and group management messages via tunnel

between MR and MAA

draft-von-hugo-multimob-agents-01

IETF-70 in Vancouver 9

Dynamic Selection of MAA at MR

• Potential locations of MAA

AR

MR

MNN

MR_HA

oAR

nAR

GW, LMA, ...CN

IETF-70 in Vancouver 10

Seamless Multicast Handover in a Hierarchical Mobile IPv6 Environment (M-HMIPv6)

T. Schmitt, M. Waehlisch

HAW Hamburg, FHTW Berlin

IETF-70 in Vancouver 11

Seamless Multicast Handover in a

HMIPv6 Environmentdraft-schmidt-waehlisch-mhmipv6-04

• Agent based solution: MAP as Multicast agent

• Built on Hierarchical MIPv6 (HMIPv6)

• Extends signalling of HMIPv6 by multicast advertisement flag

• MAP provides

– Regional tunnelling (shield multicast-agnostic regions)

– Native multicast forwarding

– Handover assistance

IETF-70 in Vancouver 12

M-HMIPv6 (2)• On Handovers for mobile listeners:

– Micro mobile handovers hidden by MAP

– Reactive handovers between MAPs, assisted by inter-MAP tunnel

• Two forwarding modes

– Unicast (tunnel) forwarding MN : MAP

– Option for remote subscription with MAP attendance

– Relies on MLD extension: multicast query with attendance flag facilitates MAP attendance without forwarding

• Third forwarding mode in preparation

– Native forwarding without MLD modifications

IETF-70 in Vancouver 13

M-HMIPv6: Multicast Listener

IETF-70 in Vancouver 14

M-HMIPv6: MAP-Local Handover

IETF-70 in Vancouver 15

M-HMIPv6: Inter-MAP Handover

IETF-70 in Vancouver 16

M-HMIPv6: Completion

IETF-70 in Vancouver 17

Hybrid Subscription for Multicast Receiver Mobility in MIPv6

F. Xia, B. Sarikaya

Huawei Research

IETF-70 in Vancouver 18

Hybrid Subscription

AR

HA(LMA) Rendezvous Point

• MN subscribes multicast service through Home agent at first.

• MN changes its subscription router to a local multicast router if the same multicast services are available

• Availability is assured by Home Subscription, while optimality is assured by Remote Subscription.

• MN switches subscription modes based on user’s profile, local policy and so on

MN

Home Subscription

Remote Subscription

draft-xia-multimob-hybrid-00.txt

IETF-70 in Vancouver 19

MLD Backward Compatible Extension

• Multicast Listener Hold-Release .

This message is to notify a multicast router (e.g. HA) to stop forwarding multicast data for the groups specified, but still maintain the multicast membership on that interface

• Multicast Listening State Advertisement.

This unsolicited message is sent by multicast routers to advertise available multicast services. MN can switch between Home Subscription and Remote Subscription based on this message.