Network Working Group H. Deng
Internet-Draft China Mobile
Intended status: Standards Track P. Yang
Expires: January 14, 2009 Hitachi
Q. Wu
Tsinghua Univ.
July 13, 2008
Problem Statement and Requirement: Mobile Multicast
draft-deng-multimob-ps-mobilemulticast-02
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 14, 2009.
Deng, et al. Expires January 14, 2009 [Page 1]
Internet-Draft PS-MC Mobile-TV July 2008
Abstract
This document discusses the problem and requirement of multicast
solution in the mobile networks. One current issue in mobile
multicast solution has been raised and requirements of mobile IPTV on
multicast mobility will also be summarized especially for some
mechanisms such as the tunneling, service capability and security
discussion which is basis of supporting the mobile IPTV applications.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. IP mobility management multicast support in mobile network . . 4
2.1. Mobile IPTV multicast framework . . . . . . . . . . . . . 4
2.2. Mobile IPv4 support Multicast . . . . . . . . . . . . . . 4
2.3. Mobile IPv6 support Multicast . . . . . . . . . . . . . . 5
3. Security Considerations . . . . . . . . . . . . . . . . . . . 7
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
5. Normative References . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . . . . 11
Deng, et al. Expires January 14, 2009 [Page 2]
Internet-Draft PS-MC Mobile-TV July 2008
1. Introduction
While more and more operators begin to provide the wireless broadband
network systems, the needs for multicast and and broadcast service in
mobile network become promising. Recently IPTV might become one of
the desirable applications for mobile network. Mobile IPTV service
is a kind of A/V services which are combined with interactive data
for the related or supplementary information of A/V program using bi-
directional wireless broadband links. User can enjoy the downlink
A/V stream and access more detailed or value-added information via
uplink simultaneously.
In the mobile network, Mobile IPv4 (MIPv4)[RFC3344], Mobile
IPv6[RFC3775], DSMIP6 [DSMIPv6] and PMIP6[Gundavelli08]is the basic
way to support IP mobility management. It allows the mobile
nodes(MN) to maintain the reachability while moving in the IP
network. After registration to home agent(HA), the packets destined
to MN could be routed correctly by using the tunneling mechanism,
while MN is away from the home network.
But the current IP mobility management mechanism lack of full support
of multicast service.This document will illustrate the main issue of
them. Since DSMIP6 is principally similar to MIP6, so it will not be
illustrated independently in this document.
Deng, et al. Expires January 14, 2009 [Page 3]
Internet-Draft PS-MC Mobile-TV July 2008
2. IP mobility management multicast support in mobile network
2.1. Mobile IPTV multicast framework
ITU make detailed description on IPTV architecture and multicast
framewroks. Mobile IPTV content delivery infrastructure may consists
of four different layers, i.e. Content Source, Core, Metro(Edge),
and Access. Content source is where IPTV service contents are
originated and they can be placed in either inside or outside of
delivery infrastructure. Core is service/network provider_is
backbone infrastructure. Metro, in other words Aggregation or Edge,
is where it connects and aggregates between core and access. Access
is user domain that includes last mile.
The transport profile of Mobile IPTV are shown in the picture below:
Wired or Wireless
|
| +.........................................+
+----------+ | . Mobile IPTV Transport Profile .
| Mobile | V . +--------+ +------+ +------+ .
| IPTV |---------| Access |------| Edge |------| Core | .
| Terminal | . +--------+ +------+ +------+ .
+----------+ . // || || .
. // || || .
. +-------------+ || || .
. | Content |==============|| || .
. | Source | || .
. +-------------+ || .
+................\\...................||..+
\\ ||
+----------------+ ||
| content source |==
+----------------+
In the case of IPTV support in mobile network, such architecture will
be considered and mapped to the network entity of IP mobility
management.
2.2. Mobile IPv4 support Multicast
Section 4.3 and 4.4 of [RFC3344] discuss the support of multicast and
broadcast. In order to receive multicast packet through it's home
network, a mobile node MUST join the multicast group in one of two
ways. One is based on co-located care-of address, the other is based
on the home address (foreign agent care-of address). In both cases,
a mobile node tunnels IGMP messages to its home agent, the home agent
Deng, et al. Expires January 14, 2009 [Page 4]
Internet-Draft PS-MC Mobile-TV July 2008
forwards multicast datagrams down the tunnel to the mobile node.
Access network
(Wired or Wireless) IP multicast
| packets
+----+ | |
| MN1| V +------+ +------+ |
+----+---------------|======|=============| | |
+----+ | FA | | HA | V
| MN2|---------------|======|=============| |-----
+----+ +------+ +------+
Figure 1: Nested tunneling in MIP4 for Multicast
In the case of co-located care-of address, the home agent SHOULD
tunnel the datagram to this care-of address directly; In the case of
foreign agent care-of address, the home agent MUST first encapsulate
the datagram in a unicast datagram addressed to the mobile node's
home address and then MUST tunnel the resulting datagram (nested
tunneling) to the mobile node's care-of address.If there are more
than 500 MNs under the same FA, there will be 500 tunnels between HA
and FA to transmit multicast packets.
2.3. Mobile IPv6 support Multicast
In this document, the analysis on multicast of mobile IPv6 will be
made only based on mobile IPTV. The Home Agent(HA) may be part of
the core function in the mobile IPTV framework. The edge function
normally coould be considered as the access gateway(AGW) in the
deployment of mobile IPv6 in mobile network.
Access network
(Wired or Wireless) IP multicast
+------+ | packets
| | | |
| MN | V +------+ +------+ |
| |===============|======|=============| | |
+------+ | | | | V
bi-dictional tunnel | AR | | HA |-----
+------+ | | | |
| |===============|======|=============| |
| MN | +------+ +------+
| |
+------+
Figure 2: Nested tunneling in MIP6 for Multicast
Notification: it's recommended to have some notification machenism in
Deng, et al. Expires January 14, 2009 [Page 5]
Internet-Draft PS-MC Mobile-TV July 2008
mobile IPv6. It's useful to do synchronous actions for incoming
mobile IPTV service events.
By the way, it is recommended that DSMIP6 has similar situation, and
Proxy mobile IPv6 will be described in a seperate document.
Deng, et al. Expires January 14, 2009 [Page 6]
Internet-Draft PS-MC Mobile-TV July 2008
3. Security Considerations
Multicast security is one of the most crucial issues in mobile IPTV
service such that it is required to provide security capabilities to
protect mobile IPTV multicast network from any malicious attempts
caused by multicast security holes such as denial of service attacks.
After the integration IP mobility management like MIP4, MIP6 with the
multicast service, it should not depreciate the security protection
of the basic IP mobility management mechanism.
Deng, et al. Expires January 14, 2009 [Page 7]
Internet-Draft PS-MC Mobile-TV July 2008
4. IANA Considerations
This document makes no requests to IANA.
Deng, et al. Expires January 14, 2009 [Page 8]
Internet-Draft PS-MC Mobile-TV July 2008
5. Normative References
[DSMIPv6] Soliman, H., "Mobile IPv6 support for dual stack Hosts and
Routers (DSMIPv6)",
draft-ietf-mip6-nemo-v4traversal-06.txt (work in
progress), November 2007.
[Gundavelli08]
Gundavelli, S., "Proxy Mobile IPv6",
draft-ietf-netlmm-proxymip6-18.txt (work in progress),
May 2008.
[RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344,
August 2002.
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004.
Deng, et al. Expires January 14, 2009 [Page 9]
Internet-Draft PS-MC Mobile-TV July 2008
Authors' Addresses
Hui Deng
China Mobile
53A,Xibianmennei Ave.,
Xuanwu District,
Beijing 100053
China
Email: denghui02@gmail.com
Peng Yang
Hitachi
301, North Wing, Tower C Raycom Infotech Park
2 kexueyuan Nanlu
Haidian District
Beijing, 100080
P.R. China
Phone: +861082862918(ext.)328
Email: pyang@hitachi.cn
Qian Wu
Tsinghua Univ.
Deng, et al. Expires January 14, 2009 [Page 10]
Internet-Draft PS-MC Mobile-TV July 2008
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Deng, et al. Expires January 14, 2009 [Page 11]