Network Working Group Seil Jeon Internet-Draft Soongsil University, Korea Intended status: Standards Track Younghan Kim Expires: September 4, 2010 Soongsil University, Korea March 4, 2010 Mobile Multicasting Support in Proxy Mobile IPv6 draft-sijeon-multimob-mms-pmip6-02.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and 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 September 4, 2010. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents Jeon, et al. Expires September 4, 2010 [Page 1] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 carefully, as they describe your rights and restrictions with respect to this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Jeon, et al. Expires September 4, 2010 [Page 2] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 Abstract To support IP multicasting in PMIPv6 domain, [I-D.ietf-multimob- pmipv6-base-solution] has been submitted as a base solution that locates MR on the LMA and uses the PMIPv6 tunnel between LMA and MAG for MLD messages. In this draft, we present the direct routing solution that uses the direct connection between MAG and MR, and locates the MLD forwarding proxy function on MAGs. The proposed direct routing solution is compared with the base deployment solution. Table of Contents 1. Introduction.....................................................4 2. Terminology and Functional Components............................5 3. Direct Routing Solution..........................................6 3.1. Architecture.................................................6 3.2. Handover Operation...........................................7 4. Comparison with Base Deployment Solution and Direct Routing Soluti on...............................................................8 4.1. Tunnel Convergence Problem...................................8 4.2. Complexity in LMA............................................8 4.3. Other Advantage..............................................8 5. Message Header...................................................9 5.1. MLD Query....................................................9 5.2. MLD Report...................................................9 5.3. Multicast Packet.............................................9 6. IANA Considerations.............................................10 7. Security Considerations.........................................10 8. References......................................................10 8.1. Normative References........................................10 8.2. Informative References......................................11 Author's Address...................................................12 Jeon, et al. Expires September 4, 2010 [Page 3] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 1. Introduction To support multicasting service in PMIPv6 domain, it is required to determine which multicasting function should be placed on which PMIPv6 component. From such a point of view, mobile multicasting solutions could be classified into two categories: a MR co-located LMA approach and a MR separated LMA approach. In the former case, the MR function is placed on LMA and the IGMP/MLD forwarding proxy function [RFC4605] is located on MAG. The MR co-located LMA approach is proposed a base solution [I-D.ietf-multimob-pmipv6-base-solution] without any modifications of [RFC5213]. But it introduces the tunnel convergence problem that a MAG may receive same multicast packets from several LMAs, which leads to waste of network bandwidth usage. In this draft, we propose a MR separated LMA approach without any load on LMA, which allows MAGs to receive multicast packets directly from MRs. So, it has not tunnel convergence problem and reduces the complexity on the LMA. Moreover, this solution could be also used in the environment that is not applied with PMIPv6 protocol. Jeon, et al. Expires September 4, 2010 [Page 4] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 2. Terminology and Functional Components The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] o Mobile Node (MN) o Previous Mobile Access Gateway (P-MAG) - The MAG that manages mobility related signaling for a MN before handover. o New Mobile Access Gateway (N-MAG) - The MAG that manages mobility related signaling for the MN after handover o Multicast Router (MR) o MLD Forwarding Proxy (MF-Proxy) Jeon, et al. Expires September 4, 2010 [Page 5] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 3. Direct Routing Solution 3.1. Architecture Multicast Tree : : || - PMIPv6 Tunnel +----------+ +----------+ | - Multicast Data Path | LMA | | Local MR | +----------+ +----------+ ||\\ /| || \\ / | || \\ / | || \\ / | || \\/ | || / \\ | || / \\ | || / \\ | +----------+ +----------+ | P-MAG | | N-MAG | |(MF-Proxy)| |(MF-Proxy)| +----------+ +----------+ : : +------+ +------+ | MN | -----> | MN | +------+ +------+ Figure 1. Direct Routing Solution for PMIPv6 Multicasting Figure 1 shows the proposed mobile multicasting solution for Proxy Mobile IPv6. There is no multicast routing function on the LMA. We call it the direct routing solution based on local routing scenario described in [I-D.deng-multimob-pmip6-requirement]. This solution has not tunnel convergence issue caused by a MAG receives the same multicast packets from several LMAs. To forward IGMP/MLD signaling and multicast packets, a MAG needs only the MLD forwarding proxy function defined in [RFC4605]. This solution is more simple than the base deployment solution and easy to deploy because LMAs are separated from multicast operation. Jeon, et al. Expires September 4, 2010 [Page 6] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 3.2. Handover Operation Multicast MN P-MAG N-MAG LMA MR Tree | | | | | | | | | | | | |<----------|<-- Multicast Data--------------|<-------| | | . | | | | | | . | | | | | | . | | | | Link->| Handover | | | | Disconnected Detection | | | | | | | | | | | | | | | | | | MN Attachment | | | | | | | | | | | | | | | |------ Rtr. Sol. ----->| | | | | | | | | | |<----- MLD Query ------| | | | | | | | | | |------ MLD Report ---->| | | | | | | Aggregated | | | | |--- MLD Report ---->| | | | | | | | | | | | | | |<----------------------|<-- Multicast Data--|<-------| | | | | | | | | | | | | | | | Proxy | | | | | |--Binding->| | | | | | Update | | | | | | | | | | | | Proxy | | | | | |<-Binding--| | | | | | Ack. | | | | | | | | | Figure 2. Handover Operation for Direct Routing Solution Figure 2 shows the handover operation for direct routing solution. When an MN hands off to the N-MAG from the P-MAG, the N-MAG detects Jeon, et al. Expires September 4, 2010 [Page 7] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 the newly arrived MN and transmits an MLD Query message to the MN. After receiving the MLD Query message, the MN sends an MLD Report message that includes the multicast group information. The N-MAG then sends an aggregated MLD Report message to the MR. When the N-MAG receives the multicast packets from the MR, it then simply forwards them without tunnel encapsulation. The N-MAG needs to update the MN's location information to the LMA by exchanging PBU/PBA signaling messages. 4. Comparison with Base Deployment Solution and Direct Routing Solution In this section, we compare the direct routing solution with the base deployment solution [I-D.ietf-multimob-pmipv6-base-solution] in terms of performance, easiness in deployment and others. 4.1. Tunnel Convergence Problem In the base deployment solution, the MR function is combined with LMA. Thus, all the packets are delivered to MNs through PMIPv6 tunnel between MAG and LMA, which raises the tunnel convergence problem because a MAG may receive the same multicast packets from several LMAs. The proposed direct routing solution does not introduce tunnel convergence problem because a MAG is directly connected to only one MR. 4.2. Complexity in LMA In the base deployment solution, the MR function is combined with LMA that should process the MLD messages and perform the join/leave procedure with other multicast routers accordingly. The complexity will increase as the number of multicast channels increases. 4.3. Other Advantage When we consider the MN's handover case from PMIPv6 domains to non- PMIPv6 domains as described in [I-D.von-hugo-multimob-future-work], we could also use the direct routing solution because it does not depend on PMIPv6 tunnel for multicasting operation. Jeon, et al. Expires September 4, 2010 [Page 8] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 5. Message Formats This section describes source and destination address of MLD signaling messages. The interface A-B means that an interface on node A, which is connected to node B. 5.1. MLD Query +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interface | Source Address | Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MR-MAG | MR link local | [RFC2710], [RFC3810] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MAG-MN | MAG link local | [RFC2710], [RFC3810] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 5.2. MLD Report +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interface | Source Address | Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MN-MAG | MN link local | [RFC2710], [RFC3810] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MAG-MR | MAG link local | [RFC2710], [RFC3810] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 5.3. Multicast Packets +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interface | Source Address | Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MR-MAG | Streaming Source Addr. | Multicast Group Addr. | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MAG-MN | Streaming Source Addr. | Multicast Group Addr. | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Jeon, et al. Expires September 4, 2010 [Page 9] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 6. IANA Considerations TBD. 7. Security Considerations This document does not discuss any special security concerns in detail. The protocol of this document is built on the assumption that all participating nodes are trusted each other as well as there is no adversary who modifies/injects false messages to corrupt the procedures. 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2710] S. Deering, W. Fenner, B. Harberman, "Multicast Listener Discovery (MLD) for IPV6", IETF RFC 2710, October 1999. [RFC3810] R. Vida, and L. Costa, "Multicast Listener Discovery Version(MLDv2) for IPv6", IETF RFC 3810, June 2004. [RFC5213] S. Gundavelli, K. Leung, V. Devarapalli, K. Chowdhury, and B. Patil, "Proxy Mobile IPv6", IETF RFC 5213, Augurst 2008. [RFC4605] B. Fenner, H. He, B. Haberman, and H. Sandick, "Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying")", IETF RFC 4605, August 2006. Jeon, et al. Expires September 4, 2010 [Page 10] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 8.2. Informative References [I-D.deng-multimob-pmip6-requirement] H. Deng, T. Schmidt, P. Seite, and P. Yang, "Multicast Support Requirements for Proxy Mobile IPv6", draft-deng- multimob-pmip6-requirement-02.txt (work in progress), July 2009. [I-D.ietf-multimob-pmipv6-base-solution] T.C. Schmidt, M. Waehlisch, S. Krishnan, "Base Deployment for Multicast Listener Support in PMIPv6 Domains", draft- ietf-multimob-pmipv6-base-solution-00.txt (work in progress), February 2010. [I-D.von-hugo-multimob-future-work] D. von Hugo, H. Asaeda, B. Sarikaya, P. Seite, "Evaluation of further issues on Multicast Mobility: Potential future work for WG MultiMob", draft-von-hugo-multimob-future- work-01.txt (work in progress), February 2010. Jeon, et al. Expires September 4, 2010 [Page 11] Internet-Draft Mobile Multicasting Support in PMIPv6 March 2010 Author's Addresses Seil Jeon Soongsil University 11F Hyungnam Engineering Bldg. 317, Sangdo-Dong, Dongjak-Gu, Seoul 156-743 Korea Phone: +82 2 814 0151 E-mail: sijeon@dcn.ssu.ac.kr Younghan Kim Soongsil University 11F Hyungnam Engineering Bldg. 317, Sangdo-Dong, Dongjak-Gu, Seoul 156-743 Korea Phone: +82 2 820 0904 E-mail: yhkim@dcn.ssu.ac.kr Jeon, et al. Expires September 4, 2010 [Page 12]