MULTIMOB Group H. Asaeda Internet-Draft Keio University Intended status: Standards Track P. Seite Expires: January 13, 2012 France Telecom J. Xia Huawei July 12, 2011 PMIPv6 Extensions for Multicast draft-asaeda-multimob-pmip6-extension-06 Abstract This document describes Proxy Mobile IPv6 (PMIPv6) extensions to support IP multicast. The Mobile Access Gateway (MAG) and the Local Mobility Anchor (LMA) are the mobility entities defined in the PMIPv6 protocol and act as PIM-SM routers. The proposed protocol extension addresses the tunnel convergence problem and provides seamless handover. This document defines the Proxy Binding Update and the Proxy Binding Acknowledgement messages with multicast extension. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on January 13, 2012. Copyright Notice Copyright (c) 2011 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 Asaeda, et al. Expires January 13, 2012 [Page 1] Internet-Draft PMIPv6 Extensions for Multicast July 2011 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. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Asaeda, et al. Expires January 13, 2012 [Page 2] Internet-Draft PMIPv6 Extensions for Multicast July 2011 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 6 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.1. Multicast Communication in PMIPv6 . . . . . . . . . . . . 7 3.2. Protocol Sequence for Multicast Channel Subscription . . . 8 4. Multicast Tunnel (M-Tunnel) . . . . . . . . . . . . . . . . . 10 5. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 12 6. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 13 7. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 14 8. Smooth Handover . . . . . . . . . . . . . . . . . . . . . . . 15 8.1. Handover with Policy Profile . . . . . . . . . . . . . . . 15 8.2. Handover with Extended Proxy Binding Update and Acknowledgement . . . . . . . . . . . . . . . . . . . . . 17 8.3. Handover with Extended Context Transfer Protocol . . . . . 19 9. Message Format Extension . . . . . . . . . . . . . . . . . . . 20 9.1. Proxy Binding Update with Multicast Extension . . . . . . 20 9.2. Proxy Binding Acknowledgement Message with Multicast Extension . . . . . . . . . . . . . . . . . . . . . . . . 23 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 11. Security Considerations . . . . . . . . . . . . . . . . . . . 26 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28 13.1. Normative References . . . . . . . . . . . . . . . . . . . 28 13.2. Informative References . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 Asaeda, et al. Expires January 13, 2012 [Page 3] Internet-Draft PMIPv6 Extensions for Multicast July 2011 1. Introduction Proxy Mobile IPv6 (PMIPv6) [2] enables network-based mobility for IPv6 mobile nodes (MNs) that do not implement any mobility protocols. The Local Mobility Anchor (LMA) is the topological anchor point to manages the mobile node's binding state. The Mobile Access Gateway (MAG) is an access router or gateway that manages the mobility- related signaling for an MN. An MN is attached to the Proxy Mobile IPv6 Domain (PMIPv6-Domain) that includes LMA and MAG(s), and is able to receive data coming from outside of the PMIPv6-Domain through LMA and MAG. Network-based mobility support for unicast is addressed in [2], while multicast support in PMIPv6 is not discussed in it. Since LMA and MAG set up a bi-directional IPv6-in-IPv6 tunnel for each mobile node and forwards all mobile node's traffic according to [2], it highly wastes network resources when a large number of mobile nodes join/ subscribe the same multicast sessions/channels, because independent data copies of the same multicast packet are delivered to the subscriber nodes in a unicast manner through MAG. The base solution described in [12] provides options for deploying multicast listener functions in PMIPv6-Domains without modifying mobility and multicast protocol standards. However, in this specification, MAG MUST act as an MLD proxy and hence MUST dedicate a tunnel link between LMA and MAG to an upstream interface for all multicast traffic. This limitation does not allow to use PIM-SM native routing on MAG, and hence does not solve the tunnel convergence problem; MAG receives the same data from multiple LMAs when MAG attaches to them for mobile nodes and has subscribed the same multicast channel to them. It does not enable local routing and does not support source mobility. Furthermore, although it would be able to minimize the join latency for mobile nodes attached to a new network by tuning the Startup Query Interval value for the new MAG as proposed in [18], the base solution does not provide any seamless handover mechanism with a context transfer function. This document describes PMIPv6 extensions to support IP multicast communication for mobile nodes in PMIPv6-Domain. The proposed protocol extension assumes that both LMA and MAG enable the Protocol- Independent Multicast - Sparse Mode (PIM-SM) multicast routing protocol [3]. The proposed extension uses a dedicated GRE [8] tunnel for multicast, called M-Tunnel, between LMA and MAG. The proposed extension supports seamless handover. It can cooperate with local routing to deliver IP multicast packets for mobile nodes and source mobility. In this document, because multicast listener mobility is mainly focused on, the detail specification of source mobility is not described. Asaeda, et al. Expires January 13, 2012 [Page 4] Internet-Draft PMIPv6 Extensions for Multicast July 2011 The PMIPv6 extension proposed in this document does not require to change unicast communication methods or protocols defined in [2], and therefore both unicast and multicast communications for mobile nodes in PMIPv6-Domain are enabled if this extension is implemented. Asaeda, et al. Expires January 13, 2012 [Page 5] Internet-Draft PMIPv6 Extensions for Multicast July 2011 2. Conventions and Terminology 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 RFC 2119 [1]. The following terms used in this document are to be interpreted as defined in the Proxy Mobile IPv6 specification [2]; Mobile Access Gateway (MAG), Local Mobility Anchor (LMA), Mobile Node (MN), Proxy Mobile IPv6 Domain (PMIPv6-Domain), LMA Address (LMAA), Proxy Care-of Address (Proxy-CoA), Mobile Node's Home Network Prefix (MN-HNP), Mobile Node Identifier (MN-Identifier), Proxy Binding Update (PBU), and Proxy Binding Acknowledgement (PBA). Asaeda, et al. Expires January 13, 2012 [Page 6] Internet-Draft PMIPv6 Extensions for Multicast July 2011 3. Overview 3.1. Multicast Communication in PMIPv6 Required components to enable IP multicast are multicast routing protocols and host-and-router communication protocols. This document assumes PIM-SM [3] as the multicast routing protocol and MLDv2 [4] or LW-MLDv2 [5] as the host-and-router communication protocol. The architecture of a Proxy Mobile IPv6 domain is shown in Figure 1. LMA and MAG are the core functional entities in PMIPv6-Domain. The entire PMIPv6-Domain appears as a single link from the perspective of each mobile node. +---------+ | Content | | Source | +---------+ | *** *** *** *** *** * ** ** ** ** * * * * Fixed Internet * * * * ** ** ** ** * *** *** *** *** *** / \ +----+ +----+ |LMA1| |LMA2| +----+ +----+ LMAA1 -> | | <-- LMAA2 | | \\ //\\ \\ // \\ \\ // \\ \\ // \\ \\ // \\ \\ // \\ Proxy-CoA1--> | | <-- Proxy-CoA2 +----+ +----+ |MAG1|---{MN2} |MAG2| +----+ | +----+ | | | MN-HNP1 --> | MN-HNP2 | <-- MN-HNP3, MN-HNP4 {MN1} {MN3} Figure 1: Proxy Mobile IPv6 Domain Asaeda, et al. Expires January 13, 2012 [Page 7] Internet-Draft PMIPv6 Extensions for Multicast July 2011 When a mobile node wants to subscribe/unsubscribe a multicast channel, it sends MLD Report messages specifying sender and multicast addresses to the access link. The attached MAG detects this membership information and sends the PIM Join/Prune message to the corresponding LMA over a multicast tunnel (M-Tunnel described in Section 4) when the LMA is selected as the previous-hop router for the multicast channel, or sends the PIM Join/Prune message to the adjacent upstream multicast router for the multicast channel. When the LMA or the adjacent router receives the PIM Join/Prune message, it coordinates the corresponding multicast routing tree if necessary and starts forwarding the data. When the MAG detects mobile node's handover, it can proceed the seamless handover procedures. Since both PMIPv6 and multicast protocols (i.e., MLD and PIM-SM) do not have functions for multicast context transfer in their original protocol specifications, the external functions or protocols should be used for handover. One of the possibile ways is the use of "mobile node's Policy Profile", as it could include "multicast channel information", which expresses mobile node's subscribing multicast channel list, as well as the mandatory fields of the Policy Profile specified in [2]. Mobile node's Policy Profile is provided by "policy store" whose definition is the same as of [2]. The Context Transfer Protocol (CXTP) [16] allows to minimize service disruption during handover. "CXTP extension for multicast" described in [11] is therefore alternative way that facilitates transferring multicast state specified in "Multicast-Context Transfer Data (M-CTD)" from previously attached MAG (p-MAG) to newly attached MAG (n-MAG). 3.2. Protocol Sequence for Multicast Channel Subscription A mobile node sends unsolicited MLD Report messages including source and multicast addresses when it subscribes a multicast channel. Although MLDv2 specification [4] permits to use the unspecified address (::) for a host whose interface has not acquired a valid link-local address yet, MAG SHOULD send MLDv2 Report messages with a valid IPv6 link-local source address as defined in [18]. As well, MLDv2 Report messages MAY be sent with an IP destination address of FF02:0:0:0:0:0:0:16, to which all MLDv2-capable multicast routers listen, but the IP unicast address of the attached MAG SHALL be used for the destination of MLDv2 Report messages. When the MAG operating as a PIM-SM router receives MLD Report messages from attached mobile nodes, it joins the multicast delivery tree by sending PIM Join messages to its neighboring routers (Figure 2). When the upstream router for the requested channel is LMA, the MAG sends the corresponding PIM Join messages over the M-Tunnel (described in Section 4), if the MAG has no multicast state Asaeda, et al. Expires January 13, 2012 [Page 8] Internet-Draft PMIPv6 Extensions for Multicast July 2011 for the requested channel. When the upstream router for the requested channel is an adjacent router that is not the LMA, the MAG sends the corresponding PIM Join messages to the adjacent upstream router natively, if the MAG has no multicast state for the requested channel. The LMA or the adjacent upstream router then joins the multicast delivery tree and forwards the packets to the downstream MAG. MN1 MN2 MAG LMA | | | | |------MLD Report--------->| | | (S1,G1) join | PIM (S1,G1) join | | | |===== M-Tunnel ===>| | | | |---> PIM (S1,G1) join | | | | | |--MLD Report-->| | | | (S2,G2) join | | | | |---> PIM (S2,G2) join | | | | | |--MLD Report-->| | | | (S1,G1) join | | | | | | Figure 2: MLD Report Messages Transmission The MAG selects only one upstream link for a multicast channel by the Reverse Path Forwarding (RPF) algorithm even if the MAG has established multiple M-Tunnels to LMAs. This does not cause the tunnel convergence problem, because duplicate packets are not forwarded to the MAG. Asaeda, et al. Expires January 13, 2012 [Page 9] Internet-Draft PMIPv6 Extensions for Multicast July 2011 4. Multicast Tunnel (M-Tunnel) M-Tunnel is a bi-directional GRE tunnel [8] dedicated for MLD message and IP multicast data transmissions between LMA and MAG as shown in Figure 3. MC1 \ \--> MC2---->LMA===MC1,MC2 for MNs====>MAG MC: Multicast packets, ==>: M-Tunnel Figure 3: Multicast channel subscription through M-Tunnel The format of the tunneled multicast packet forwarded from LMA is shown below. "S" and "G" are the same notation used for (S,G) multicast channel. IPv6 header (src= LMAA, dst= Proxy-CoA) /* Outer Header */ GRE header /* Encapsulation Header */ IPv6 header (src= S, dst= G) /* Inner Header */ Upper layer protocols /* Packet Content */ Figure 4: Tunneled IPv6 multicast packet from LMA to MAG When an MLD message is sent from MAG to LMA, the src and dst addresses of tunnel header will be replaced to Proxy-CoA and LMAA, respectively. To convey an MLD message, the src address of the packet header is changed to either LMA's or MAG's link-local address and the dst address of the packet header is assigned based on the MLD's condition. (See Section 5.1.15 and 5.2.14 of [4].) M-Tunnel is established between PIM-SM capable LMA and MAG. It is established in a bootstrap phase of MAG (without detecting a multicast channel subscription request from a mobile node) and kept while the MAG is running. M-Tunnel is not per mobile node basis, but per MAG basis; it is shared with all mobile nodes attached to the MAG. In order to distinguish tunneled unicast traffic and multicast traffic, LMA and MAG need to negotiate GRE encapsulation and GRE keys for M-Tunnel. The GRE Key option to be used for the negotiation of GRE tunnel encapsulation mode and exchange of the uplink and downlink GRE keys is defined in [9]. It is also possible to use the static fixed GRE keys for M-Tunnel. There can be multiple LMAs in a PMIPv6- Domain each serving a different group of mobile nodes. In that case, the MAG will connect to multiple LMAs with different M-Tunnels Asaeda, et al. Expires January 13, 2012 [Page 10] Internet-Draft PMIPv6 Extensions for Multicast July 2011 (having different GRE keys). Asaeda, et al. Expires January 13, 2012 [Page 11] Internet-Draft PMIPv6 Extensions for Multicast July 2011 5. Local Mobility Anchor Operation The LMA is responsible for maintaining the mobile node's reachability state and is the topological anchor point for the mobile node's home network prefix(es). This document assumes that the LMA is capable of forwarding multicast packets to the MAG by enabling the Protocol- Independent Multicast - Sparse Mode (PIM-SM) multicast routing protocol [3]. The LMA acting as a PIM-SM [3] multicast router may serve MAGs as downstream routers for some multicast channels when a mobile node is a multicast data receiver (or as upstream routers when a mobile node is a multicast data sender). The downstream (or upstream) MAG is connected to the LMA through an M-Tunnel for multicast communication. When the LMA sets up the multicast state and joins the group as the MAG's upstream router, the multicast packets are tunneled to the MAG that requested to receive the corresponding multicast session. The MAG then forwards the packets to the mobile node according to the multicast listener state maintained in the MAG. [2] supports only point-to-point access link types for MAG and mobile node connection; hence a mobile node and the MAG are the only two nodes on an access link, where the link is assumed to be multicast capable. Asaeda, et al. Expires January 13, 2012 [Page 12] Internet-Draft PMIPv6 Extensions for Multicast July 2011 6. Mobile Access Gateway Operation The MAG is the entity that performs the mobility management on behalf of a mobile node. This document assumes that MAG is capable of forwarding multicast packets to the corresponding mobile nodes attached to MAG by enabling the PIM-SM multicast routing protocol. In addition, MAG must maintain multicast membership status for the attached mobile nodes at the edge and forwards the multicast data to the member mobile nodes. This condition requires MAG to support MLDv2 [4] or LW-MLDv2 [5], as well. When mobile nodes subscribe multicast channel(s), they send MLD Report messages with their link-local address to the MAG, and the MAG sends the corresponding PIM Join messages to the upstream router if the MAG has no multicast state for the requested channel(s). The upstream router is selected by the Reverse Path Forwarding (RPF) lookup algorithm, and that is either LMA or an adjacent multicast router attached to the same link. If the LMA is the upstream router for the channel(s) for the MAG, the MAG encapsulates PIM Join messages using M-Tunnel. The MAG also sends MLD Query messages to attached mobile nodes to maintain up-to-date membership states. Since the MAG may deal with a large number of the downstream mobile nodes, the MLD protocol scalability should be taken into account as described in [18]. Asaeda, et al. Expires January 13, 2012 [Page 13] Internet-Draft PMIPv6 Extensions for Multicast July 2011 7. Mobile Node Operation Mobile nodes attached to MAG can behave as regular receiver hosts. A mobile node sends MLD messages to MAG when it wants to subscribe and unsubscribe IP multicast channels. In order to subscribe/unsubscribe multicast channel(s) by unsolicited report messages and inform current membersip state by solicited report messages, mobile nodes MUST support either MLDv1 [4], MLDv2 [4], or LW-MLDv2 [5], and SHOULD support MLDv2 or LW-MLDv2. Asaeda, et al. Expires January 13, 2012 [Page 14] Internet-Draft PMIPv6 Extensions for Multicast July 2011 8. Smooth Handover MAG is responsible for detecting the mobile node's movements to and from the access link and for initiating binding registrations to the mobile node's LMA. MAG tracks the mobile node's movements to and from the access link and for signaling the mobile node's LMA. In PMIPv6, it SHOULD NOT require for mobile nodes to initiate to re- subscribe multicast channels, and MAG SHOULD keep multicast channel subscription status for mobile nodes even if they move to a different MAG (i.e., n-MAG) in PMIPv6-Domain. MAG needs to join the multicast delivery tree when an attached mobile node subscribes a multicast channel. When the mobile node changes the network, it should seamlessly receive multicast data from the new MAG according to the multicast channel information stored in the "MN's Policy Profile" or by the "multicast context transfer mechanism". Whether the MN's Policy Profile or the multicast context transfer mechanism mobile operators use depend on their policy or implementation. 8.1. Handover with Policy Profile When the multicast channel information subscribed by mobile nodes is maintained in "MN's Policy Profile" stored in a policy store [2], MAG can use the channel information to provide seamless handover. The procedures are described as follows and illustrated in Figure 5; 1. Figure 5 shows the examples that a mobile node has received multicast data from an upstream multicast router via p-MAG (*1) and from LMA via p-MAG (*2). 2. Whenever the mobile node moves a new network and attaches to n-MAG, the n-MAG obtains the MN-Identifier (MN-ID) and learns multicast channel information described in Mobile Node's Policy Profile associated to this MN-Identifier. Describing the method how the n-MAG identifies the p-MAG is out of scope of this document, while using the same mechanism described in [17] would be one of the possible methods. 3. If there are multicast channels the mobile node has subscribed but the n-MAG has not yet subscribed, n-MAG joins the corresponding multicast channels by sending the PIM Join message to its upstream router. If the upstream router is LMA, the PIM messages are encapsulated and transmitted over M-Tunnel (*4); otherwise the PIM messages are sent natively (*3). Asaeda, et al. Expires January 13, 2012 [Page 15] Internet-Draft PMIPv6 Extensions for Multicast July 2011 4. The multicast data is forwarded from LMA through an M-Tunnel between the LMA and n-MAG (*4) or from the adjacent upstream router (*3). MN p-MAG LMA n-MAG | | | | |--MLD Report->| | | | |---> PIM join (*1) | | | PIM join (*2) | | | |=== M-Tunnel ==>| | | | |---> PIM join (*2) | | | | | |<--Multicast--| | | | data (*1) | | | | | Multicast data (*2) | |<-------------|<== M-Tunnel ===| | | | | | Detach | | | | | | | Attach | | | | | | MN attachment event | | | (Acquire MN-ID and Profile) |----------------------RS-------------------------->| | | | | | | |<-------PBU--------| | | | | | | |--------PBA------->| | | | |---> PIM join (*3) | | | PIM join (*4) | | | |<=== M-Tunnel =====| | | | | |<---------------------RA---------------------------| | | | | | | Multicast data (*3) | |<--------------------------------------------------| | | |Multicast data (*4)| | | |==== M-Tunnel ====>| |<--------------------------------------------------| | | | | Figure 5: Handover with MN's Policy Profile After MN attaches to n-MAG, the multicast data will be delivered to the MN immediately. MN's multicast membership state is maintained with MLD Query and Report messages exchanged by MN and n-MAG. If p-MAG thinks that the moving mobile node is the last member of multicast channel(s), p-MAG confirms it by sending IGMP/MLD query. Asaeda, et al. Expires January 13, 2012 [Page 16] Internet-Draft PMIPv6 Extensions for Multicast July 2011 After the confirmation, p-MAG leaves the channel(s) by sending the PIM Prune message to its upstream router. 8.2. Handover with Extended Proxy Binding Update and Acknowledgement This document provides the multicast extension for the PBU message, which is named "Proxy Binding Update with multicast extension (PBU-M)" (detailed in Section 9.1), and the PBA message, which is named "Proxy Binding Acknowledge with multicast extension (PBA-M)" (detailed in Section 9.2), to inform n-MAG to subscribe multicast channel(s) for moving mobile nodes. 1. Figure 6 shows the examples that a mobile node has received multicast data from an upstream multicast router via p-MAG (*1) and from LMA via p-MAG (*2). 2. Whenever the mobile node moves a new network, the p-MAG sends de-registration PBU-M message having the lifetime value of zero (see Section 9.1) to the LMA. The LMA then transmits the PBA message and keeps the multicast channel information included in that message. 3. When the mobile node attaches to n-MAG, the n-MAG obtains the MN-Identifier (MN-ID) and transmits the regular PBU message. 4. Whenever the LMA receives the PBU message, it transmits the PBA-M message including multicast channel information that the mobile node has joined. 5. If there are multicast channels in the channel information the mobile node has subscribed but the n-MAG has not yet subscribed, the n-MAG joins the corresponding multicast channels by sending the PIM Join message to its upstream router. 6. Follow the procedures of step 3 and 4 in Section 8.1. Asaeda, et al. Expires January 13, 2012 [Page 17] Internet-Draft PMIPv6 Extensions for Multicast July 2011 MN p-MAG LMA n-MAG | | | | |--MLD Report->| | | | |---> PIM join (*1) | | | PIM join (*2) | | | |=== M-Tunnel ==>| | | | |---> PIM join (*2) | | | | | |<--Multicast--| | | | data (*1) | | | | | Multicast data (*2) | |<-------------|<== M-Tunnel ===| | | | | | Detach | | | | MN detachment event | | | | | | | |--DeReg PBU-M-->| | | | | | | | Accept PBU | | |<-----PBA-------| | Attach | | | | | | MN attachment event | | | (Acquire MN-ID) |----------------------RS-------------------------->| | | | | | | |<-------PBU--------| | | | | | | |-------PBA-M------>| | | (Acquire multicast channel | | information for MN-ID) | | | | | | | |---> PIM join (*3) | | | PIM join (*4) | | | |<=== M-Tunnel =====| | | | | |<---------------------RA---------------------------| | | | | | | Multicast data (*3) | |<--------------------------------------------------| | | |Multicast data (*4)| | | |==== M-Tunnel ====>| |<--------------------------------------------------| | | | | Figure 6: Handover with PBU-M and PBA-M Asaeda, et al. Expires January 13, 2012 [Page 18] Internet-Draft PMIPv6 Extensions for Multicast July 2011 8.3. Handover with Extended Context Transfer Protocol The Context Transfer Protocol (CXTP) [16] allows to minimize service disruption during handover. "CXTP extension for multicast" is therefore another option that facilitates transferring multicast state from p-MAG to n-MAG. All of the detail explanations and sequences are described in [11]. Asaeda, et al. Expires January 13, 2012 [Page 19] Internet-Draft PMIPv6 Extensions for Multicast July 2011 9. Message Format Extension 9.1. Proxy Binding Update with Multicast Extension 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sequence # | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|H|L|K|M|R|P|C| Reserved | Lifetime | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | . . . Mobility options . . . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 7: Proxy Binding Update Message with Multicast Extension A Binding Update message that is sent by MAG to LMA is referred to as the "Proxy Binding Update" message. A new flag (C) is included in the Proxy Binding Update message with Multicast extension (PBU-M). The rest of the Binding Update message format remains the same as defined in [13] and with the additional (R), (M), and (P) flags, as specified in [14], [15], and [2], respectively. Multicast Channel Subscription Flag A new flag (C) is included in the Binding Update message to indicate to LMA that the Binding Update message is a multicast channel subscription. The PBU-M message is transfered for binding de-registration from p-MAG to LMA as apecified in Section 8.2, the Lifetime value MUST be zero. When (C) flag is specified in PBU-M message, the mobility options field includes "multicast channel information", which is the same information of MLDv2 Report message, where the fields contain data with the same definitions in [4]. Asaeda, et al. Expires January 13, 2012 [Page 20] Internet-Draft PMIPv6 Extensions for Multicast July 2011 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type = 143 | Reserved | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved |Nr of Mcast Address Records (M)| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | . . . Multicast Address Record [1] . . . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | . . . Multicast Address Record [2] . . . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | . | . . . | . | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | . . . Multicast Address Record [M] . . . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 8: Multicast channel information Each Multicast Address Record has the following internal format, where the Record Type MUST be always "1" (i.e., MODE_IS_INCLUDE). Asaeda, et al. Expires January 13, 2012 [Page 21] Internet-Draft PMIPv6 Extensions for Multicast July 2011 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Record Type = 1| Aux Data Len | Number of Sources (N) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | * * | | * Multicast Address * | | * * | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | * * | | * Source Address [1] * | | * * | | +- -+ | | * * | | * Source Address [2] * | | * * | | +- -+ . . . . . . . . . +- -+ | | * * | | * Source Address [N] * | | * * | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | . . . Auxiliary Data . . . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 9: Multicast Address Record format Asaeda, et al. Expires January 13, 2012 [Page 22] Internet-Draft PMIPv6 Extensions for Multicast July 2011 9.2. Proxy Binding Acknowledgement Message with Multicast Extension 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Status |K|R|P|C|Reserve| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sequence # | Lifetime | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | . . . Mobility options . . . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 10: PBA with Multicast Extension A "Proxy Binding Acknowledgement" message is sent from LMA to MAG in response to a Proxy Binding Update message. A new flag (C) is included in the Proxy Binding Acknowledgement message with Multicast extension (PBA-M). The rest of the Binding Acknowledgement message format remains the same as defined in [13] and with the additional (R) flag, as specified in [14] and [2], respectively. Multicast Channel Subscription Flag A new flag (C) is included in the Binding Acknowledgement message to indicate to MAG that the Binding Acknowledgement message is a multicast channel subscription. When (C) flag is specified in PBA-M message, the mobility options field includes "multicast channel information", which is the same information of MLDv2 Report message [4] as described in Section 9.1. Asaeda, et al. Expires January 13, 2012 [Page 23] Internet-Draft PMIPv6 Extensions for Multicast July 2011 10. IANA Considerations This document creates a new registry for the flags in the Binding Update message called the "Binding Update Flags". The following flags are reserved: (A) 0x8000 [RFC3775] (H) 0x4000 [RFC3775] (L) 0x2000 [RFC3775] (K) 0x1000 [RFC3775] (M) 0x0800 [RFC4140] (R) 0x0400 [RFC3963] (P) 0x0200 [RFC5213] This document reserves a new flag (C) for "Proxy Binding Update with Multicast Extension" as described in Section 9.1 as follows: (C) 0x0100 The rest of the values in the 16-bit field are reserved. New values can be assigned by Standards Action or IESG approval. This document also creates a new registry for the flags in the Binding Acknowledgment message called the "Binding Acknowledgment Flags". The following flags are reserved: (K) 0x80 [RFC3775] (R) 0x40 [RFC3963] (P) 0x20 [RFC5213] This document reserves a new flag (C) for "Proxy Binding Acknowledgement with Multicast Extension" as described in Section 9.2 as follows: (C) 0x010 The rest of the values in the 8-bit field are reserved. New values Asaeda, et al. Expires January 13, 2012 [Page 24] Internet-Draft PMIPv6 Extensions for Multicast July 2011 can be assigned by Standards Action or IESG approval. Asaeda, et al. Expires January 13, 2012 [Page 25] Internet-Draft PMIPv6 Extensions for Multicast July 2011 11. Security Considerations TBD. Asaeda, et al. Expires January 13, 2012 [Page 26] Internet-Draft PMIPv6 Extensions for Multicast July 2011 12. Acknowledgements Many of the specifications described in this document are discussed and provided by the multimob mailing-list. Asaeda, et al. Expires January 13, 2012 [Page 27] Internet-Draft PMIPv6 Extensions for Multicast July 2011 13. References 13.1. Normative References [1] Bradner, S., "Key words for use in RFCs to indicate requirement levels", RFC 2119, March 1997. [2] Gundavelli, S, Ed., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. [3] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", RFC 4601, August 2006. [4] Vida, R. and L. Costa, "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. [5] Liu, H., Cao, W., and H. Asaeda, "Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) Protocols", RFC 5790, February 2010. [6] Deering, S., Fenner, W., and B. Haberman, "Multicast Listener Discovery (MLD) for IPv6", RFC 2710, October 1999. [7] Fenner, B., He, H., Haberman, B., and H. Sandick, "Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying")", RFC 4605, August 2006. [8] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, March 2000. [9] Muhanna, A., Khalil, M., Gundavelli, S., and K. Leung, "Generic Routing Encapsulation (GRE) Key Option for Proxy Mobile IPv6", RFC 5845, June 2010. [10] Asaeda, H. and Y. Uchida, "IGMP/MLD-Based Explicit Membership Tracking Function for Multicast Routers", draft-asaeda-mboned-explicit-tracking-02.txt (work in progress), March 2011. [11] von Hugo, D. and H. Asaeda, "Context Transfer Protocol Extension for Multicast", draft-vonhugo-multimob-cxtp-extension-00.txt (work in progress), July 2011. Asaeda, et al. Expires January 13, 2012 [Page 28] Internet-Draft PMIPv6 Extensions for Multicast July 2011 13.2. Informative References [12] Schmidt, T., Waehlisch, M., and S. Krishnan, "Base Deployment for Multicast Listener Support in Proxy Mobile IPv6 (PMIPv6) Domains", RFC 6224, April 2011. [13] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004. [14] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert, "Network Mobility (NEMO) Basic Support Protocol", RFC 3963, January 2005. [15] Soliman, H., Castelluccia, C., El Malki, K., and L. Bellier, "Hierarchical Mobile IPv6 Mobility Management (HMIPv6)", RFC 4140, August 2005. [16] Loughney, Ed., J., Nakhjiri, M., Perkins, C., and R. Koodli, "Context Transfer Protocol (CXTP)", RFC 4067, July 2005. [17] Yokota, H., Chowdhury, K., Koodli, R., Patil, B., and F. Xia, "Fast Handovers for Proxy Mobile IPv6", RFC 5949, September 2010. [18] Asaeda, H., Liu, H., and Q. Wu, "Tuning the Behavior of IGMP and MLD for Routers in Mobile and Wireless Networks", draft-ietf-multimob-igmp-mld-tuning-01.txt (work in progress), July 2011. Asaeda, et al. Expires January 13, 2012 [Page 29] Internet-Draft PMIPv6 Extensions for Multicast July 2011 Authors' Addresses Hitoshi Asaeda Keio University Graduate School of Media and Governance 5322 Endo Fujisawa, Kanagawa 252-0816 Japan Email: asaeda@wide.ad.jp URI: http://www.sfc.wide.ad.jp/~asaeda/ Pierrick Seite France Telecom 4, rue du Clos Courtel BP 91226, Cesson-Sevigne 35512 France Email: pierrick.seite@orange-ftgroup.com Jinwei Xia Huawei Technologies Co., Ltd. Huihong Mansion, No.91 Baixia Rd. Nanjing, Jiangsu 21001 China Email: xiajinwei@huawei.com Asaeda, et al. Expires January 13, 2012 [Page 30]