< draft-von-hugo-multimob-future-work-01.txt		draft-von-hugo-multimob-future-work-02.txt >
	MULTIMOB Working Group D. von Hugo		MULTIMOB Working Group D. von Hugo
	Internet-Draft Deutsche Telekom Laboratories		Internet-Draft Deutsche Telekom Laboratories
	Intended status: Informational H. Asaeda		Intended status: Informational H. Asaeda
	Expires: August 26, 2010 Keio University		Expires: December 9, 2010 Keio University
	B. Sarikaya		B. Sarikaya
	Huawei USA		Huawei USA
	P. Seite		P. Seite
	France Telecom - Orange		France Telecom - Orange
	February 22, 2010		June 8, 2010
	Evaluation of further issues on Multicast Mobility: Potential future		Evaluation of further issues on Multicast Mobility: Potential future
	work for WG MultiMob		work for WG MultiMob
	<draft-von-hugo-multimob-future-work-01.txt>		<draft-von-hugo-multimob-future-work-02.txt>
	Abstract		Abstract
	The WG MultiMob aims at defining a basic mobile multicast solution		The WG MultiMob aims at defining a basic mobile multicast solution
	leveraging on network localized mobility management, i.e. Proxy		leveraging on network localized mobility management, i.e. Proxy
	Mobile IPv6 protocol. The solution would be basically based on		Mobile IPv6 protocol. The solution would be basically based on
	multicast group management, i.e. IGMP/MLD, proxying at the access		multicast group management, i.e. IGMP/MLD, proxying at the access
	gateway. If such a basic solution is essential from an operational		gateway. If such a basic solution is essential from an operational
	point of view, challenges with efficient resource utilization and		point of view, challenges with efficient resource utilization and
	user perceived service quality still persist. These issues may		user perceived service quality still persist. These issues may
	prevent large scale deployments of mobile multicast applications.		prevent large scale deployments of mobile multicast applications.
	This document attempts to identify topics for future extension of		This document attempts to identify topics for near future extension
	work such as modifying base PMIPv6 and MLD/IGMP for optimal multicast		of work such as modifying multimob base solution, PMIPv6 and MLD/
	support, extending to and modifying of MIPv4/v6 and DSMIP, sender		IGMP for optimal multicast support, and adaptation of Handover
	(source) mobility, consideration of Handover optimization, multiple		optimization. Far future items such as extending to and modifying
	flows with multihoming and any other different issues.		of MIPv4/v6 and DSMIP, sender (source) mobility, consideration of
			multiple flows and multihoming will be dealt with in a future
			version.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 2, line 9 ¶		skipping to change at page 2, line 9 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on August 26, 2010.		This Internet-Draft will expire on December 9, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2010 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 3, line 14 ¶		skipping to change at page 3, line 14 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7
	3. IGMP/MLD Proxy Architecture . . . . . . . . . . . . . . . . . 7		3. IGMP/MLD Proxy Architecture . . . . . . . . . . . . . . . . . 7
	4. Problem Description . . . . . . . . . . . . . . . . . . . . . 8		4. Problem Description . . . . . . . . . . . . . . . . . . . . . 8
	4.1. Modification of base PMIPv6 for optimal multicast		4.1. Modification of base PMIPv6 for optimal multicast
	support . . . . . . . . . . . . . . . . . . . . . . . . . 8		support . . . . . . . . . . . . . . . . . . . . . . . . . 8
	4.2. Modification of MLD/IGMP for optimal multicast support . . 8		4.2. Modification of MLD/IGMP for optimal multicast support . . 8
	4.3. Extensions to and modifying of MIPv4/v6 and DSMIPv6 . . . 9		4.3. Consideration of Handover Optimization . . . . . . . . . . 9
	4.4. Consideration of sender (source) mobility . . . . . . . . 9		4.4. Specific PMIP deployment issues . . . . . . . . . . . . . 9
	4.5. Consideration of Handover Optimization . . . . . . . . . . 9		5. Requirements on Solutions . . . . . . . . . . . . . . . . . . 10
	4.6. Support of multiple flows . . . . . . . . . . . . . . . . 10		6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
	4.7. Support of multi-hop transmission . . . . . . . . . . . . 10		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
	4.8. Mobility agnosticity . . . . . . . . . . . . . . . . . . . 10		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
	4.9. Local routing . . . . . . . . . . . . . . . . . . . . . . 10		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
	5. Requirements on Solutions . . . . . . . . . . . . . . . . . . 11		9.1. Normative References . . . . . . . . . . . . . . . . . . . 11
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 12		9.2. Informative References . . . . . . . . . . . . . . . . . . 12
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
	9.1. Normative References . . . . . . . . . . . . . . . . . . . 12
	9.2. Informative References . . . . . . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
	1. Introduction		1. Introduction
	Recently chartered WG MultiMob focuses on documentation of proper		Chartered work of WG MultiMob focuses on documentation of proper
	configuration and usage of existing (specified standard) protocols		configuration and usage of existing (specified standard) protocols
	within both mobility and multicast related areas to enable and		within both mobility and multicast related areas to enable and
	support mobility for multicast services and vice versa. Although the		support mobility for multicast services and vice versa. The current
	final recommendation is not yet available it is expected that such a		WG document [I-D.ietf-multimob-pmipv6-base-solution] does not address
	solution following the remote subscription aproach will not be		specific optimizations and efficiency improvements of multicast
			routing for network-based mobility and thus the operation may be not
	resource efficient nor grant the service quality expected by the end		resource efficient nor grant the service quality expected by the end
	user.		user.
	Such a solution would resolve the problem to ensure multicast		The described solution resolves the problem to ensure multicast
	reception in PMIPv6-enabled [RFC5213] networks without appropriate		reception in PMIPv6-enabled [RFC5213] networks without appropriate
	multicast support. However it would neither automatically minimize		multicast support. However it neither automatically minimizes
	multicast forwarding delay to provide seamless and fast handovers for		multicast forwarding delay to provide seamless and fast handovers for
	real-time services nor minimize packet loss and reordering that		real-time services nor minimizes packet loss and reordering that
	result from multicast handover management as stated in		result from multicast handover management as stated in [RFC5757].
	[I-D.irtf-mobopts-mmcastv6-ps]. Also Route Optimization is out of		Also Route Optimization is out of scope of the basic solution - an
	scope of the basic solution - an issue for reducing amount of		issue for reducing amount of transport resource usage and
	transport resource usage and transmission delay. Thus possible		transmission delay. Thus possible enhancements and issues for
	enhancements and issues for solutions beyond a basic solution need to		solutions beyond a basic solution need to be described to enable
	be described to enable current PMIPv6 protocols to fully support		current PMIPv6 protocols to fully support efficient mobile multicast
	efficient mobile multicast services. Such extensions may include		services. Such extensions may include protocol modifications for
	protocol modifications for both mobility and multicast related		both mobility and multicast related protocols to achieve
	protocols to achieve optimizations for resource efficient and		optimizations for resource efficient and performance increasing
	performance increasing multimob approaches. The document includes		multimob approaches. The document includes the case of mobile
	the case of mobile multicast senders using Any Source Multicast (ASM)		multicast senders using Any Source Multicast (ASM) and Source
	and Source Specific Multicast (SSM) [RFC4607].		Specific Multicast (SSM) [RFC4607].
	Figure 1 illustrates the key components of the foreseen basic		This document focuses on discussion work on multicast protocols
	Multimob solution. The extended multicast mobility scenario, leading		such as IGMP/MLD operational tuning (e.g. as proposed in
	to above issues, is sketched in Figure 2.		[I-D.asaeda-igmp-mld-optimization]) and enhancements of IGMP/MLD
			protocol behaviors and messages for optimal multicast support
			(proposed in [I-D.asaeda-igmp-mld-mobility-extension]).
	+------+ +------+		An alternative approach proposes the addition of acknowledgement
			messages on group management ([I-D.liu-multimob-reliable-igmp-mld])
			and changes the unreliable protocol concept.
			Furthermore a modification of PMIPv6 by introducing a dedicated
			multicast tunnel and support of local routing is discussed in
			[I-D.asaeda-multimob-pmip6-extension]. Other performance
			improvements have been outlined in
			[I-D.schmidt-multimob-fmipv6-pfmipv6-multicast] where extensions to
			Mobile IPv6 Fast Handovers (FMIPv6) [RFC5568], and the corresponding
			extension for Proxy MIPv6 operation [I-D.ietf-mipshop-pfmipv6].
			Another type of multimob work aims directly at enhancements of the
			current multimob base solution
			[I-D.ietf-multimob-pmipv6-base-solution] towards introduction of
			multicast traffic replication mechanisms and a reduction of the
			protocol complexity in terms of time consuming tunnel set-up by
			definition of pre- or post-configured tunnels (as provided by e.g.
			[I-D.zuniga-multimob-smspmip]). Further work within this topic deals
			with direct routing (e.g. [I-D.sijeon-multimob-mms-pmip6]) and with
			dynamic or automatic tunnel configuration (see e.g.
			[I-D.ietf-mboned-auto-multicast]).
			A large field of additional investigations which are partly described
			in detail in [RFC5757] will be mentioned for completeness and may be
			subject of a later WG re-chartering.
			+------+ +------+
	| MN | =====> | MN |		| MN | =====> | MN |
	+------+ +------+		+------+ +------+
	| .		| .
	| .		| .
	+--------+ +--------+		+--------+ +--------+
	| MAG 1 | | MAG 2 |		| MAG 1 | | MAG 2 |
	|IGMP/MLD| |IGMP/MLD|		|IGMP/MLD| |IGMP/MLD|
	|Proxy | |Proxy |		|Proxy | |Proxy |
	+--------+ +--------+		+--------+ +--------+
	| |		| |
	skipping to change at page 6, line 11 ¶		skipping to change at page 6, line 11 ¶
	+------+		+------+
	Figure 1: MultiMob Scenario for chartered PMIP6 issue		Figure 1: MultiMob Scenario for chartered PMIP6 issue
	+------+ +------+ +------+		+------+ +------+ +------+
	| MN | =====> | MN | ====> | MN |		| MN | =====> | MN | ====> | MN |
	+------+ +------+ +------+		+------+ +------+ +------+
	| . .		| . .
	| . .		| . .
	| . .		| . .
	+-------+ +-------+ +-------+ +-------+		+--------+ +--------+ +--------+ +--------+
	| MAG 1 | | MAG 2 | | AR 1 | | AR 2 |		| MAG 1 | | MAG 2 | | AR 1 | | AR 2 |
	|IGMP/MLD| |IGMP/MLD| |IGMP/MLD| |IGMP/MLD|		|IGMP/MLD| |IGMP/MLD| |IGMP/MLD| |IGMP/MLD|
	|Proxy | |Proxy | |Proxy | |Proxy |		| Proxy | | Proxy | | Proxy | | Proxy |
	+-------+ +-------+ +-------+ +-------+		+--------+ +--------+ +--------+ +--------+
	\ / | |		\ / | |
	*** *** *** *** *** *** *** ***		*** *** *** *** *** *** *** ***
	* ** *** ** * * ** *** ** *		* ** *** ** * * ** *** ** *
	* * * *		* * * *
	* Internet Subnet 1 * * Internet Subnet 2 *		* Internet Subnet 1 * * Internet Subnet 2 *
	* * * *		* * * *
	* ** *** ** * * ** *** ** *		* ** *** ** * * ** *** ** *
	*** *** *** *** *** *** *** ***		*** *** *** *** *** *** *** ***
	| | |		| | |
	+-------+ +-------+ |		+-------+ +-------+ |
	skipping to change at page 6, line 43 ¶		skipping to change at page 6, line 43 ¶
	* *_____* *		* *_____* *
	* ** ** ** * * ** *** ** *		* ** ** ** * * ** *** ** *
	*** *** *** *** *** .*** *** ***		*** *** *** *** *** .*** *** ***
	| .		| .
	+-------+ +-------+		+-------+ +-------+
	| CN | ====> | CN |		| CN | ====> | CN |
	+-------+ +-------+		+-------+ +-------+
	Figure 2: MultiMob scenario for extended MultiMob issues		Figure 2: MultiMob scenario for extended MultiMob issues
			Figure 1 illustrates the key components of the foreseen basic
			Multimob solution. The extended multicast mobility scenario, leading
			to above issues, is sketched in Figure 2.
	In summary additional to a 'Single hop, link, flow' Proxy MIP		In summary additional to a 'Single hop, link, flow' Proxy MIP
	mobility for listening MNs (scenario shown in Figure 1), the future		mobility for listening MNs (scenario shown in Figure 1), future work
	work will focus on optimization of performances and extend the		towards a complete performance-optimized scenario of a 'Multi-hop,
	scenario to 'Multi-hop, -homed, -flow' client mobility, thus also		-homed, -flow' client mobility (i.e. including MIPv6 [RFC3775] and
	including optimizations for MIPv6 [RFC3775]. The following is the		DSMIPv6 [RFC5555]) would cover a plurality of issues. For the near
	proposed work items to be covered in the MultiMob continuation: (see		future we see the following issues as most important:
	Figure 2).
			o Extension of multimob base solution
	o Modification of base PMIPv6 and MLD/IGMP for optimal multicast		o Modification of base PMIPv6 and MLD/IGMP for optimal multicast
	support.		support.
	o Extension to and modifying of MIPv4/v6 and DSMIP using IGMP/MLD
	Proxy and the Foreign Agent/ Access Router.
	o Consideration of sender (source) mobility.
	o Consideration of Handover optimization.		o Consideration of Handover optimization.
	o Support of multiple flows on multihomed mobile nodes.		All further issues which would include extensions to and
			modifications of MIPv4/v6 and DSMIP using IGMP/MLD Proxy and the
	o Multi-hop transmission.		Foreign Agent/Access Router, consideration of sender (source)
			mobility, support of multiple flows on multihomed mobile nodes,
	o Fixed mobile convergence support.		multi-hop transmission, Routing optimization, and so forth will be
			topics for a potential next stage of future work extension.
	o Consideration of earlier versions of IGMP and MLD in the
	solutions.
	o Consideration of locally available multicast without remote
	subscription.
	o Improve host mobility agnoticity
	o Routing optimization
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in BCP 14 [RFC2119].		document are to be interpreted as described in BCP 14 [RFC2119].
	This document uses the terminology defined in [RFC3775], [RFC3376],		This document uses the terminology defined in [RFC3775], [RFC3376],
	[RFC3810], [RFC5213], [I-D.irtf-mobopts-mmcastv6-ps].		[RFC3810], [RFC5213], [RFC5757].
	3. IGMP/MLD Proxy Architecture		3. IGMP/MLD Proxy Architecture
	Multimob basic solution is based on IGMPv3/MLDv2 Proxy support at the		Multimob basic solution is based on IGMPv3/MLDv2 Proxy support at the
	mobile access gateway (MAG) of Proxy Mobile IPv6 as shown in		mobile access gateway (MAG) of Proxy Mobile IPv6 as shown in
	Figure 1. IGMPv3/MLDv2 proxy keeps multicast state on the		Figure 1. IGMPv3/MLDv2 proxy keeps multicast state on the
	subscriptions of the mobile nodes and only an aggregate state is kept		subscriptions of the mobile nodes and only an aggregate state is kept
	at the local mobility anchor (LMA). When LMA receives multicast data		at the local mobility anchor (LMA). When LMA receives multicast data
	it can forward it to the MAG without duplication because MAG takes of		it can forward it to the MAG without duplication because MAG takes of
	the packet duplication. This leads to solving the avalanche problem.		the packet duplication. This leads to solving the avalanche problem.
	skipping to change at page 8, line 24 ¶		skipping to change at page 8, line 16 ¶
	from the parameters applicable to fixed users. It should be also		from the parameters applicable to fixed users. It should be also
	possible to distinguish between slow and fast movement and handover		possible to distinguish between slow and fast movement and handover
	frequency to form corresponding tunnels for mobile users.		frequency to form corresponding tunnels for mobile users.
	Based on the above observations we will state the problems next and		Based on the above observations we will state the problems next and
	then list the requirements on possible solutions.		then list the requirements on possible solutions.
	4. Problem Description		4. Problem Description
	The general issues of multicast mobility are extensively discussed		The general issues of multicast mobility are extensively discussed
	and described in [I-D.irtf-mobopts-mmcastv6-ps]. To reduce the		and described in [RFC5757]. To reduce the complexity of the
	complexity of the pleothera of requirements listed in		plethora of requirements listed in [RFC5757] and also in
	[I-D.irtf-mobopts-mmcastv6-ps] and in		[I-D.deng-multimob-pmip6-requirement] this document summarises some
	[I-D.deng-multimob-pmip6-requirement] this document tries to propose
	lightweight solutions for multicast mobility which allow for easy		lightweight solutions for multicast mobility which allow for easy
	deployment within realistic scenarios and architectures, and which		deployment within realistic scenarios and architectures. Moreover
	build directly on basic MultiMob solution which is based on IGMP/MLD		we focus on approaches building directly on basic MultiMob solution
	Proxy at the mobile access gateway.		[I-D.ietf-multimob-pmipv6-base-solution] which is based on IGMP/MLD
			Proxy functionality at the mobile access gateway, and for which
			already solution proposals have been described.
	4.1. Modification of base PMIPv6 for optimal multicast support		4.1. Modification of base PMIPv6 for optimal multicast support
	There would be potential solutions proposed for multicast		Currently discussed aspects of multicast optimization for PMIPv6
	optimization for PMIPv6 such as		include introduction of multicast tunnels and support of local
	[I-D.asaeda-multimob-pmip6-extension], agent-based reling on		routing such as described in [I-D.asaeda-multimob-pmip6-extension].
	additional encapsulation, and a hybrid approach. Since other		For a PMIPv6 domain the establishment of a dedicated multicast tunnel
	functional enhancements of PMIPv6 are currently under way in NETEXT		is proposed which may either be dynamically set up and released or be
	WG, both the impact of new features on Mobile Multicast as well as a		pre-configured in a static manner. Both mobility entities MAG and
	potential Multicast-initiated proposal for PMIPv6 modification have		LMA may be operate as MLD proxy or multicast router.
	to be considered in a continuous exchange process between both WGs.		Since further functional enhancements of PMIPv6 are currently under
			way in NETEXT WG, both the impact of new features on Mobile Multicast
			as well as such a Multicast-initiated proposal for PMIPv6
			modification have to be considered in a continuous exchange process
			between MultiMob and NETEXT WGs.
	4.2. Modification of MLD/IGMP for optimal multicast support		4.2. Modification of MLD/IGMP for optimal multicast support
	Potential approaches for enhancement of group management as specified		Potential approaches for enhancement of group management as specified
	e.g. by MLDv2 [RFC3810] include default timer value modification,		e.g. by MLDv2 [RFC3810] include operational improvements such as
	specific query message introduction, and standard (query) reaction		proper tuning in terms of default timer value modification, specific
			query message introduction, and standard (query) reaction
	suppression, beside introducing multicast router attendance control		suppression, beside introducing multicast router attendance control
	in terms of e.g. specification of a Listener Hold message as proposed		in terms of e.g. specification of a Listener Hold message as proposed
	in [I-D.asaeda-multimob-igmp-mld-mobility-extensions].		in [I-D.asaeda-multimob-igmp-mld-mobility-extensions].
	4.3. Extensions to and modifying of MIPv4/v6 and DSMIPv6		4.3. Consideration of Handover Optimization
	Operational interest clearly focusses on network-based mobility
	approaches, but in the framework of multiple technologies serving a
	mobile user there will be demand to include also other non-PMIPv6
	based specifications.
	This section addresses the compatibility of PMIPv6-based multicast
	solutions with MIPv6 [RFC3775], i.e. handover between network-based
	and client mobility support as well as interoperabiliy between IPv4
	and IPv6 mechanisms (e.g. FA handling, IPv4/v4-tunneling) with
	mobile multicast. DSMIPv6 [RFC5555] has a basic support for
	multicast which is based on remote subscription and bi-directional
	tunneling, but does not specify how to achieve group management and
	data forwarding unless the mobility anchor (i.e. Home Agent) is a
	fully functional IPv6 multicast router.
	4.4. Consideration of sender (source) mobility
	We see future demand for such a feature in terms of applications such
	as 'Push to talk over wireless technologies' (packet based point-to-
	multipoint (P2MP) group voice) like 3GPP or WiMAX, 'Multi-party
	mobile audio/video conferencing', 'mobile multi-player gaming' etc,
	where due to real-time constraints a solution based on a central
	server might add too much delay.
	According to [I-D.irtf-mobopts-mmcastv6-ps] generally (i.e. for ASM)
	a mobile multicast source must provide address transparency at
	Routing - for Reverse Path Forwarding (RPF) checks - as well as on
	Transport layer - to coincide with packet source address at receiver
	side. Further issues are temporal handover constraints, possible
	packet loss and multicast scoping, and enhanced complexity of inter-
	domain multicasting. Additional challenges arise for SSM (Source
	Specific Multicast) due to the principle of multicast decoupling
	between sender and receivers.
	4.5. Consideration of Handover Optimization
	This work item would deal with reduction of delay, packet loss, and
	packet reordering effort. In case these degradations are induced due
	to terminal movement it will be discussed how to make use of MIPSHOP
	approaches such as HMIP, FMIP etc. (predominantly focusing on intra-
	technology handover). Reusing multicast specific protocol extensions
	exceeding IGMP/MLD modifications shall further decrease the impact of
	group management induced delay.
	4.6. Support of multiple flows
	Considering a per-flow handover for parallel multicast sessions
	allows to treat different services requirements and labels of flows
	independently. This would improve user perceived service performance
	as well as allow for more efficient usage of network resources
	because of the enabled flexibility.
	4.7. Support of multi-hop transmission
	This scenario adds another level of complexity to Multicast Mobility		Ideally the customer experience while using multicast services should
	and is of interest e.g. in nested NEMO (Network Mobility, [RFC3963])		not be affected by transmission issues whether the terminal is
	scenarios, for MANETs (Mobile Adhoc NETworks) where also mechanisms		operated in a fixed or a mobile environment. This implies not only
	for multicast forwarding are dicussed, e.g. in terms of Simplified		that the terminal should be unaware of changes at network layer
	Multicast Forwarding (SMF, [I-D.ietf-manet-smf]) or for		connectivity (seamless communication) as is typically the case in a
	infrastructure mesh networks. Here, more than the mobile and		PMIPv6 domain, but also that any impact of connectivity changes
	temporary character of connections, it is the existence of (more or		(handover) should be minimized. In the framework of Multimob this
	less stable) multiple hops and multiple paths which is stressed.		relates to reduction of delay, packet loss, and packet reordering
			effort for mobile multicast by applying fast handover mechanisms,
			which have originally been developed for unicast traffic to multicast
			group management. [I-D.schmidt-multimob-fmipv6-pfmipv6-multicast]
			works on specification of extension of the Mobile IPv6 Fast Handovers
			(FMIPv6) [RFC5568] and the Fast Handovers for Proxy Mobile IPv6
			(PFMIPv6) [I-D.ietf-mipshop-pfmipv6] protocols to include multicast
			traffic management in fast handover operations. Issues for further
			work are details of including multicast group messaging in context
			transfer, for both predictive and reactive handover mode, as well as
			details of corresponding message exchange protocols and message
			design.
	4.8. Mobility agnosticity		4.4. Specific PMIP deployment issues
	In the idea of network based mobility management, the mobile node		Currently several proposals are under work which describe extensions
	should remain agnostic of the multicast mobility management when		of the base protocol WG draft
	roaming. In particular, the node MUST not be required to re-		[I-D.ietf-multimob-pmipv6-base-solution]. While MAG operation will
	subscribe to multicast group(s) after handoff. If the mobile node		remain that of an MLD proxy additional LMA functionalities are
	does no re-resubscribes, the new MAG must be able to retrieve the		described in [I-D.zuniga-multimob-smspmip] which allow for
	multicast states corresponding to the moving node.		replication of multicast traffic and solution of the tunnel
			convergence problem. The dedicated multicast LMA may either set up
			dedicated multicast tunnels dynamically or a-priory via
			pre-configuration or a delayed release.
	4.9. Local routing		Another solution on dynamic and/or automatic tunnel configuration is
			proposed within multicast WG MBONED [I-D.ietf-mboned-auto-multicast].
	Short term deployment focuses on architecture where multicast traffic		A direct or local routing approach is described in
			[I-D.sijeon-multimob-mms-pmip6]. This scenario may hold for short
			term deployment focusing on an architecture where multicast traffic
	is provided via the home network. However, depending on the network		is provided via the home network. However, depending on the network
	topology, namely the location of the content delivery network, the		topology, namely the location of the content delivery network, the
	LMA may not be on the optimal multicast service delivery path. This		LMA may not be on the optimal multicast service delivery path. This
	enables mobile nodes to access locally available multicast services		enables mobile nodes to access locally available multicast services
	such as local channels.		such as local channels.
	Figure 3 illustrates the use-case for local routing.		Figure 3 illustrates the use-case for local routing.
	+----+		+----+
	|LMA |		|LMA |
	skipping to change at page 12, line 18 ¶		skipping to change at page 11, line 18 ¶
	o Agnostic mobile host re-subscription. So, MAGs must be able to		o Agnostic mobile host re-subscription. So, MAGs must be able to
	retrieve multicast contexts of the mobile nodes.		retrieve multicast contexts of the mobile nodes.
	o Solution address IPv6, IPv4 only and dual stack nodes.		o Solution address IPv6, IPv4 only and dual stack nodes.
	o Supports sender (source) mobility.		o Supports sender (source) mobility.
	o Optimal local routing.		o Optimal local routing.
	o To be completed...		o To be completed...
	6. Security Considerations		6. Security Considerations
	This draft introduces no additional messages. Compared to [RFC3376],		This draft introduces no additional messages. Compared to [RFC3376],
	[RFC3810], and [RFC3775][RFC5213] there is no additional threats to		[RFC3810], [RFC3775], and [RFC5213] there have no additional threats
	be introduced.		been introduced.
	7. IANA Considerations		7. IANA Considerations
	None.		Whereas this document does not explicitly introduce requests to IANA
			some of the proposals referenced above (such as
			[I-D.asaeda-multimob-pmip6-extension] and
			[I-D.schmidt-multimob-fmipv6-pfmipv6-multicast]) specify flags for
			mobility messages or options. For details please see those
			documents.
	8. Acknowledgements		8. Acknowledgements
	The authors would thank all active mebers of MultiMob WG, especially		The authors would thank all active members of MultiMob WG, especially
	(in no specific order) Gorry Fairhurst, Jouni Korhonen, Thomas		(in no specific order) Gorry Fairhurst, Jouni Korhonen, Thomas
	Schmidt, Suresh Krishnan and Matthias Waehlisch for providing		Schmidt, Suresh Krishnan and Matthias Waehlisch for providing
	continuous support and helpful comments.		continuous support and helpful comments.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	skipping to change at page 13, line 37 ¶		skipping to change at page 12, line 40 ¶
	[23402] "3GPP TS 23.402 V8.4.1, Architecture enhancements for non-		[23402] "3GPP TS 23.402 V8.4.1, Architecture enhancements for non-
	3GPP accesses (Release 8).", 2009.		3GPP accesses (Release 8).", 2009.
	[I-D.asaeda-multimob-igmp-mld-mobility-extensions]		[I-D.asaeda-multimob-igmp-mld-mobility-extensions]
	Asaeda, H. and T. Schmidt, "IGMP and MLD Hold and Release		Asaeda, H. and T. Schmidt, "IGMP and MLD Hold and Release
	Extensions for Mobility",		Extensions for Mobility",
	draft-asaeda-multimob-igmp-mld-mobility-extensions-03		draft-asaeda-multimob-igmp-mld-mobility-extensions-03
	(work in progress), July 2009.		(work in progress), July 2009.
	[I-D.asaeda-multimob-igmp-mld-optimization]		[I-D.asaeda-multimob-igmp-mld-optimization]
	Asaeda, H., "IGMP and MLD Optimization for Mobile Hosts		Asaeda, H. and S. Venaas, "Tuning the Behavior of IGMP
	and Routers",		and MLD for Mobile Hosts and Routers",
	draft-asaeda-multimob-igmp-mld-optimization-01 (work in		draft-asaeda-multimob-igmp-mld-optimization-02 (work in
	progress), October 2009.		progress), March 2010.
	[I-D.asaeda-multimob-pmip6-extension]		[I-D.asaeda-multimob-pmip6-extension]
	Asaeda, H., Seite, P., and J. Xia, "PMIPv6 Extensions for		Asaeda, H., Seite, P., and J. Xia, "PMIPv6 Extensions for
	Multicast", draft-asaeda-multimob-pmip6-extension-02 (work		Multicast", draft-asaeda-multimob-pmip6-extension-02 (work
	in progress), July 2009.		in progress), July 2009.
	[I-D.deng-multimob-pmip6-requirement]		[I-D.deng-multimob-pmip6-requirement]
	Deng, H., Chen, G., Schmidt, T., Seite, P., and P. Yang,		Deng, H., Chen, G., Schmidt, T., Seite, P., and P. Yang,
	"Multicast Support Requirements for Proxy Mobile IPv6",		"Multicast Support Requirements for Proxy Mobile IPv6",
	draft-deng-multimob-pmip6-requirement-02 (work in		draft-deng-multimob-pmip6-requirement-02 (work in
	progress), July 2009.		progress), July 2009.
			[I-D.liu-multimob-reliable-igmp-mld]
			Liu, H. and Q. Wu, "Reliable IGMP and MLD Protocols in
			Wireless Environment",
			draft-liu-multimob-reliable-igmp-mld-00 (work in
			progress), March 2010.
			[I-D.schmidt-multimob-fmipv6-pfmipv6-multicast]
			Schmidt, T., Waehlisch, M., Koodli, R., and G. Fairhurst,
			"Multicast Listener Extensions for MIPv6 and PMIPv6 Fast
			Handovers",
			draft-schmidt-multimob-fmipv6-pfmipv6-multicast-01 (work
			in progress), March 2010.
			[I-D.sijeon-multimob-mms-pmip6]
			Jeon, S. and Y. Kim, "Mobile Multicasting Support in
			Proxy Mobile IPv6", draft-sijeon-multimob-mms-pmip6-02
			(work in progress), March 2010
			[I-D.zuniga-multimob-smspmip]
			Zuniga, J., Lu, G., and A. Rahman, "Support Multicast
			Services Using Proxy Mobile IPv6",
			draft-zuniga-multimob-smspmip-02 (work in progress),
			June 2010.
			[I-D.ietf-mboned-auto-multicast]
			Thaler, D., Talwar, M., Aggarwal, A., Vicisano, L., and
			T. Pusateri, "Automatic IP Multicast Without Explicit
			Tunnels (AMT)", draft-ietf-mboned-auto-multicast-10 (work
			in progress), March 2010
	[I-D.ietf-16ng-ipv4-over-802-dot-16-ipcs]		[I-D.ietf-16ng-ipv4-over-802-dot-16-ipcs]
	Madanapalli, S., Park, S., Chakrabarti, S., and G.		Madanapalli, S., Park, S., Chakrabarti, S., and G.
	Montenegro, "Transmission of IPv4 packets over IEEE		Montenegro, "Transmission of IPv4 packets over IEEE
	802.16's IP Convergence Sublayer",		802.16's IP Convergence Sublayer",
	draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-06 (work in		draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-07 (work in
	progress), June 2009.		progress), June 2010.
	[I-D.ietf-manet-smf]		[I-D.ietf-manet-smf]
	Macker, J. and S. Team, "Simplified Multicast Forwarding",		Macker, J. (editor), "Simplified Multicast Forwarding",
	draft-ietf-manet-smf-09 (work in progress), July 2009.		draft-ietf-manet-smf-10 (work in progress), March 2010.
	[I-D.irtf-mobopts-mmcastv6-ps]		[I-D.ietf-mipshop-pfmipv6]
	Fairhurst, G., Schmidt, T., and M. Waehlisch, "Multicast		Yokota, H., Chowdhury, K., Koodli, R., Patil, B., and F.
			Xia, "Fast Handovers for Proxy Mobile IPv6",
			draft-ietf-mipshop-pfmipv6-14 (work in progress), May
			2010
			[I-D.ietf-multimob-pmipv6-base-solution]
			Schmidt, T., Waehlisch, M., and S. Krishnan, "Base
			Deployment for Multicast Listener Support in PMIPv6
			Domains",
			draft-ietf-multimob-pmipv6-base-solution-02 (work in
			progress), May 2010.
			[RFC5757] Schmidt, T., Waehlisch, M., and G. Fairhurst, "Multicast
	Mobility in MIPv6: Problem Statement and Brief Survey",		Mobility in MIPv6: Problem Statement and Brief Survey",
	draft-irtf-mobopts-mmcastv6-ps-09 (work in progress),		RFC 5757, June 2010.
	October 2009.
	[RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P.		[RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P.
	Thubert, "Network Mobility (NEMO) Basic Support Protocol",		Thubert, "Network Mobility (NEMO) Basic Support Protocol",
	RFC 3963, January 2005.		RFC 3963, January 2005.
	[RFC5121] Patil, B., Xia, F., Sarikaya, B., Choi, JH., and S.		[RFC5121] Patil, B., Xia, F., Sarikaya, B., Choi, JH., and S.
	Madanapalli, "Transmission of IPv6 via the IPv6		Madanapalli, "Transmission of IPv6 via the IPv6
	Convergence Sublayer over IEEE 802.16 Networks", RFC 5121,		Convergence Sublayer over IEEE 802.16 Networks", RFC 5121,
	February 2008.		February 2008.
End of changes. 39 change blocks.
	182 lines changed or deleted		215 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/