draft-ietf-multimob-pmipv6-source-08.txt   draft-ietf-multimob-pmipv6-source-09.txt 
MULTIMOB Group T. Schmidt, Ed. MULTIMOB Group T. Schmidt, Ed.
Internet-Draft HAW Hamburg Internet-Draft HAW Hamburg
Intended status: Experimental S. Gao Intended status: Experimental S. Gao
Expires: September 4, 2014 H. Zhang Expires: October 2, 2014 H. Zhang
Beijing Jiaotong University Beijing Jiaotong University
M. Waehlisch M. Waehlisch
link-lab & FU Berlin link-lab & FU Berlin
March 3, 2014 March 31, 2014
Mobile Multicast Sender Support in Proxy Mobile IPv6 (PMIPv6) Domains Mobile Multicast Sender Support in Proxy Mobile IPv6 (PMIPv6) Domains
draft-ietf-multimob-pmipv6-source-08 draft-ietf-multimob-pmipv6-source-09
Abstract Abstract
Multicast communication can be enabled in Proxy Mobile IPv6 domains Multicast communication can be enabled in Proxy Mobile IPv6 domains
via the Local Mobility Anchors by deploying MLD proxy functions at via the Local Mobility Anchors by deploying MLD proxy functions at
Mobile Access Gateways, via a direct traffic distribution within an Mobile Access Gateways, via a direct traffic distribution within an
ISP's access network, or by selective route optimization schemes. ISP's access network, or by selective route optimization schemes.
This document describes a base solution and an experimental protocol This document describes a base solution and an experimental protocol
to support mobile multicast senders in Proxy Mobile IPv6 domains for to support mobile multicast senders in Proxy Mobile IPv6 domains for
all three scenarios. Protocol optimizations for synchronizing PMIPv6 all three scenarios. Protocol optimizations for synchronizing PMIPv6
skipping to change at page 1, line 49 skipping to change at page 1, line 49
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on September 4, 2014. This Internet-Draft will expire on October 2, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 11 skipping to change at page 3, line 11
5.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 18 5.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3. Operations in Support of Multicast Senders . . . . . . . 19 5.3. Operations in Support of Multicast Senders . . . . . . . 19
5.4. Operations in Support of Multicast Listeners . . . . . . 19 5.4. Operations in Support of Multicast Listeners . . . . . . 19
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
7. Security Considerations . . . . . . . . . . . . . . . . . . . 21 7. Security Considerations . . . . . . . . . . . . . . . . . . . 21
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
9.1. Normative References . . . . . . . . . . . . . . . . . . 22 9.1. Normative References . . . . . . . . . . . . . . . . . . 22
9.2. Informative References . . . . . . . . . . . . . . . . . 23 9.2. Informative References . . . . . . . . . . . . . . . . . 23
Appendix A. Multiple Upstream Interface Proxy . . . . . . . . . 23 Appendix A. Multiple Upstream Interface Proxy . . . . . . . . . 24
A.1. Operations for Local Multicast Sources . . . . . . . . . 24 A.1. Operations for Local Multicast Sources . . . . . . . . . 24
A.2. Operations for Local Multicast Subscribers . . . . . . . 24 A.2. Operations for Local Multicast Subscribers . . . . . . . 24
Appendix B. Implementation . . . . . . . . . . . . . . . . . . . 25 Appendix B. Implementation . . . . . . . . . . . . . . . . . . . 25
Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction 1. Introduction
Proxy Mobile IPv6 (PMIPv6) [RFC5213] extends Mobile IPv6 (MIPv6) Proxy Mobile IPv6 (PMIPv6) [RFC5213] extends Mobile IPv6 (MIPv6)
[RFC6275] by network-based management functions that enable IP [RFC6275] by network-based management functions that enable IP
mobility for a host without requiring its participation in any mobility for a host without requiring its participation in any
mobility-related signaling. Additional network entities called the mobility-related signaling. Additional network entities called the
Local Mobility Anchor (LMA), and Mobile Access Gateways (MAGs), are Local Mobility Anchor (LMA), and Mobile Access Gateways (MAGs), are
responsible for managing IP mobility on behalf of the mobile node responsible for managing IP mobility on behalf of the mobile node
(MN). An MN connected to a PMIPv6 domain, which only operates (MN). An MN connected to a PMIPv6 domain, which only operates
skipping to change at page 4, line 22 skipping to change at page 4, line 22
discussed in [RFC5757]. Mobile Nodes in this setting remain agnostic discussed in [RFC5757]. Mobile Nodes in this setting remain agnostic
of multicast mobility operations. of multicast mobility operations.
2. Terminology 2. Terminology
This document uses the terminology as defined for the mobility This document uses the terminology as defined for the mobility
protocols [RFC6275], [RFC5213] and [RFC5844], as well as the protocols [RFC6275], [RFC5213] and [RFC5844], as well as the
multicast routing [RFC4601] and edge related protocols [RFC3376], multicast routing [RFC4601] and edge related protocols [RFC3376],
[RFC3810] and [RFC4605]. [RFC3810] and [RFC4605].
Throught this document, we use the following acronyms
HNP Home Network Prefix as defined in [RFC5213].
MAG Mobile Access Gateway as defined in [RFC5213]
MLD Multicast Listener Discovery as defined in [RFC2710] and
[RFC3810].
PIM Protocol Independent Multicast as defined in [RFC4601].
PMIPv6 Proxy Mobile IPv6 as defined in [RFC5213].
3. Base Solution for Source Mobility and PMIPv6 Routing 3. Base Solution for Source Mobility and PMIPv6 Routing
3.1. Overview 3.1. Overview
The reference scenario for multicast deployment in Proxy Mobile IPv6 The reference scenario for multicast deployment in Proxy Mobile IPv6
domains is illustrated in Figure 1. It displays the general setting domains is illustrated in Figure 1. It displays the general setting
for source mobility - Mobile Nodes (MNs) with Home Network Prefixes for source mobility - Mobile Nodes (MNs) with Home Network Prefixes
(HNPs) that receive services via tunnels, which are spanned between a (HNPs) that receive services via tunnels, which are spanned between a
Local Mobility Anchor Address (LMAA) and a Proxy Care-of-Address Local Mobility Anchor Address (LMAA) and a Proxy Care-of-Address
(Proxy-CoA) at a Mobility Access Gateway (MAG). MAGs play the role (Proxy-CoA) at a Mobility Access Gateway (MAG). MAGs play the role
skipping to change at page 14, line 44 skipping to change at page 14, line 44
the previous DR (MAG) deactivates the data encapsulation channels for the previous DR (MAG) deactivates the data encapsulation channels for
the transient source (i.e., all DownstreamJPState(S,*,VI) are set to the transient source (i.e., all DownstreamJPState(S,*,VI) are set to
NoInfo state). After reattaching and completing unicast handover NoInfo state). After reattaching and completing unicast handover
negotiations, the mobile source can continue to transmit multicast negotiations, the mobile source can continue to transmit multicast
packets, while being treated as a new source at its new DR (MAG). packets, while being treated as a new source at its new DR (MAG).
Source register encapsulation will be immediately initiated, and Source register encapsulation will be immediately initiated, and
(S,G) data continue to flow natively down the (*,G) RP-based tree. (S,G) data continue to flow natively down the (*,G) RP-based tree.
Source handover management in PIM phase one admits low complexity and Source handover management in PIM phase one admits low complexity and
remains transparent to receivers. In addition, the source register remains transparent to receivers. In addition, the source register
tunnel management of PIM is a fast protocol operation and little tunnel management of PIM is a fast protocol operation that introduces
overhead is induced thereof. In a PMIPv6 deployment, PIM RPs MAY be little overhead. In a PMIPv6 deployment, PIM RPs MAY be configured
configured to not initiated (S,G) shortest path trees for mobile to not initiated (S,G) shortest path trees for mobile sources, and
sources, and thus remain in phase one of the protocol. The price to thus remain in phase one of the protocol. The price to pay for such
pay for such simplified deployment lies in possible routing detours simplified deployment lies in possible routing detours by an overall
by an overall RP-based packet distribution. RP-based packet distribution.
4.3.3. Operations of PIM in Phase Two (Register-Stop) 4.3.3. Operations of PIM in Phase Two (Register-Stop)
After receiving source register packets, a PIM RP eventually will After receiving source register packets, a PIM RP eventually will
initiate a source-specific Join for creating a shortest path tree to initiate a source-specific Join for creating a shortest path tree to
the (mobile) source S, and issue a source register stop at the native the (mobile) source S, and issue a source register stop at the native
arrival of data from S. For initiating an (S,G) tree, the RP, as well arrival of data from S. For initiating an (S,G) tree, the RP, as well
as all intermediate routers, require route entries for the HNP of the as all intermediate routers, require route entries for the HNP of the
MN that - unless the RP coincides with the MAG of S - point towards MN that - unless the RP coincides with the MAG of S - point towards
the corresponding LMA of S. Consequently, the (S,G) tree will proceed the corresponding LMA of S. Consequently, the (S,G) tree will proceed
skipping to change at page 21, line 33 skipping to change at page 21, line 33
In addition, particular attention should be paid to implications of In addition, particular attention should be paid to implications of
combining multicast and mobility management at network entities. As combining multicast and mobility management at network entities. As
this specification allows mobile nodes to initiate the creation of this specification allows mobile nodes to initiate the creation of
multicast forwarding states at MAGs and LMAs while changing multicast forwarding states at MAGs and LMAs while changing
attachments, threats of resource exhaustion at PMIP routers and attachments, threats of resource exhaustion at PMIP routers and
access networks arrive from rapid state changes, as well as from high access networks arrive from rapid state changes, as well as from high
volume data streams routed into access networks of limited volume data streams routed into access networks of limited
capacities. In cases of PIM-SM deployment, handover operations of capacities. In cases of PIM-SM deployment, handover operations of
the MNs include re-registering sources at the Rendezvous Points at the MNs include re-registering sources at the Rendezvous Points at
possibly high frequency. In addition to proper authorization checks possibly high frequency. In addition to proper authorization checks
of MNs, rate controls at routing agents and replicators MAY be of MNs, rate controls at routing agents and replicators may be needed
required to protect the agents and the downstream networks. In to protect the agents and the downstream networks. In particular,
particular, MLD proxy implementations at MAGs SHOULD carefully MLD proxy implementations at MAGs SHOULD automatically extinct
procure for automatic multicast state extinction on the departure of multicast state on the departure of MNs, as mobile multicast
MNs, as mobile multicast listeners in the PMIPv6 domain will in listeners in the PMIPv6 domain will in general not actively terminate
general not actively terminate group membership prior to departure. group membership prior to departure.
The deployment of IGMP/MLD proxies for multicast routing requires The deployment of IGMP/MLD proxies for multicast routing requires
particular care, as routing loops on the upstream are not particular care, as routing loops on the upstream are not
automatically detected. Peering functions between proxies extend automatically detected. Peering functions between proxies extend
this threat in the following way. Routing loops among peering and this threat in the following way. Routing loops among peering and
upstream interfaces are prevented by filters on local sources. Such upstream interfaces are prevented by filters on local sources. Such
filtering can fail, whenever prefix configurations for downstream filtering can fail, whenever prefix configurations for downstream
interfaces at a proxy are incorrect or inconsistent. Consequently, interfaces at a proxy are incorrect or inconsistent. Consequently,
implementations of peering-enabled proxies SHOULD take particular implementations of peering-enabled proxies SHOULD take particular
care on maintaining (varying) IP configurations at the downstream in care on keeping IP configurations consistent at the downstream in a
a reliable and timely manner (see [RFC6224] for requirements on reliable and timely manner (see [RFC6224] for requirements on
PMIPv6-compliant implementations of MLD proxies). PMIPv6-compliant implementations of MLD proxies).
8. Acknowledgements 8. Acknowledgements
The authors would like to thank (in alphabetical order) David Black, The authors would like to thank (in alphabetical order) David Black,
Luis M. Contreras, Muhamma Omer Farooq, Bohao Feng, Sri Gundavelli, Luis M. Contreras, Spencer Dawkins, Muhamma Omer Farooq, Bohao Feng,
Dirk von Hugo, Ning Kong, Jouni Korhonen, He-Wu Li, Cong Liu, Akbar Sri Gundavelli, Dirk von Hugo, Ning Kong, Jouni Korhonen, He-Wu Li,
Rahman, Behcet Sarikaya, Stig Venaas, Li-Li Wang, Sebastian Woelke, Cong Liu, Radia Perlman, Akbar Rahman, Behcet Sarikaya, Stig Venaas,
Qian Wu, Zhi-Wei Yan for advice, help and reviews of the document. Li-Li Wang, Sebastian Woelke, Qian Wu, Zhi-Wei Yan for advice, help
Funding by the German Federal Ministry of Education and Research and reviews of the document. Funding by the German Federal Ministry
within the G-LAB Initiative (projects HAMcast, Mindstone and SAFEST) of Education and Research within the G-LAB Initiative (projects
is gratefully acknowledged. HAMcast, Mindstone and SAFEST) is gratefully acknowledged.
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.
[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast
Listener Discovery (MLD) for IPv6", RFC 2710, October Listener Discovery (MLD) for IPv6", RFC 2710, October
skipping to change at page 23, line 14 skipping to change at page 23, line 14
[RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support [RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support
in IPv6", RFC 6275, July 2011. in IPv6", RFC 6275, July 2011.
9.2. Informative References 9.2. Informative References
[I-D.ietf-multimob-fmipv6-pfmipv6-multicast] [I-D.ietf-multimob-fmipv6-pfmipv6-multicast]
Schmidt, T., Waehlisch, M., Koodli, R., Fairhurst, G., and Schmidt, T., Waehlisch, M., Koodli, R., Fairhurst, G., and
D. Liu, "Multicast Listener Extensions for MIPv6 and D. Liu, "Multicast Listener Extensions for MIPv6 and
PMIPv6 Fast Handovers", draft-ietf-multimob- PMIPv6 Fast Handovers", draft-ietf-multimob-
fmipv6-pfmipv6-multicast-03 (work in progress), February fmipv6-pfmipv6-multicast-05 (work in progress), March
2014. 2014.
[I-D.ietf-multimob-handover-optimization] [I-D.ietf-multimob-handover-optimization]
Contreras, L., Bernardos, C., and I. Soto, "PMIPv6 Contreras, L., Bernardos, C., and I. Soto, "PMIPv6
multicast handover optimization by the Subscription multicast handover optimization by the Subscription
Information Acquisition through the LMA (SIAL)", draft- Information Acquisition through the LMA (SIAL)", draft-
ietf-multimob-handover-optimization-07 (work in progress), ietf-multimob-handover-optimization-07 (work in progress),
December 2013. December 2013.
[Peering-Analysis]
Schmidt, TC., Woelke, S., and M. Waehlisch, "Peer my Proxy
- A Performance Study of Peering Extensions for Multicast
in Proxy Mobile IP Domains", Proc. of 7th IFIP Wireless
and Mobile Networking Conference (WMNC 2014) IEEEPress,
May 2014.
[RFC2236] Fenner, W., "Internet Group Management Protocol, Version [RFC2236] Fenner, W., "Internet Group Management Protocol, Version
2", RFC 2236, November 1997. 2", RFC 2236, November 1997.
[RFC4604] Holbrook, H., Cain, B., and B. Haberman, "Using Internet [RFC4604] Holbrook, H., Cain, B., and B. Haberman, "Using Internet
Group Management Protocol Version 3 (IGMPv3) and Multicast Group Management Protocol Version 3 (IGMPv3) and Multicast
Listener Discovery Protocol Version 2 (MLDv2) for Source- Listener Discovery Protocol Version 2 (MLDv2) for Source-
Specific Multicast", RFC 4604, August 2006. Specific Multicast", RFC 4604, August 2006.
[RFC5757] Schmidt, T., Waehlisch, M., and G. Fairhurst, "Multicast [RFC5757] Schmidt, T., Waehlisch, M., and G. Fairhurst, "Multicast
Mobility in Mobile IP Version 6 (MIPv6): Problem Statement Mobility in Mobile IP Version 6 (MIPv6): Problem Statement
skipping to change at page 25, line 25 skipping to change at page 25, line 34
Appendix B. Implementation Appendix B. Implementation
An implementation of the extended IGMP/MLD proxy has been provided An implementation of the extended IGMP/MLD proxy has been provided
within the MCPROXY project http://mcproxy.realmv6.org/. This open within the MCPROXY project http://mcproxy.realmv6.org/. This open
source software is written in C++ and uses forwarding capabilities of source software is written in C++ and uses forwarding capabilities of
the Linux kernel. It supports all regular operations according to the Linux kernel. It supports all regular operations according to
[RFC4605], allows for multiple proxy instances on one node, [RFC4605], allows for multiple proxy instances on one node,
dynamically changing downstream links, as well as proxy-to-proxy dynamically changing downstream links, as well as proxy-to-proxy
peerings and multiple upstream links with individual configurations. peerings and multiple upstream links with individual configurations.
The software can be downloaded from Github at https://github.com/ The software can be downloaded from Github at https://github.com/
mcproxy/mcproxy. mcproxy/mcproxy. Based on this software, an experimental performance
evaluation of the proxy peering function has been reported in
Appendix C. Change Log [Peering-Analysis].
The following changes have been made from version draft-ietf-
multimob-pmipv6-source-06:
1. Editorial improvements in response to WG Last Call.
2. Clarified mobile source handover treatment for peering proxies in
response to WG Last Call.
3. Updated and extended references.
4. Added pointer to available implementation in Appendix.
The following changes have been made from version draft-ietf-
multimob-pmipv6-source-05:
1. Editorial improvements in response to WG feedback.
2. Updated and extended references.
The following changes have been made from version draft-ietf-
multimob-pmipv6-source-04:
1. Cleaned structure in Section Section 5.
2. Clarified operations of the proxy peering function.
3. Completed Section on Security Considerations.
4. Editorial improvements in response to WG feedback.
5. Updated and extended references.
The following changes have been made from version draft-ietf-
multimob-pmipv6-source-03:
1. Fixed issues in Section Section 4.3 (PIM phase two and three
transition) according to WG feedback.
2. Editorial improvements, resolved nits.
3. Updated references.
The following changes have been made from version draft-ietf-
multimob-pmipv6-source-02:
1. Added clarifications and details as requested by the working
group, resolved nits.
2. Moved Multiple Upstream MLD proxy to Appendix in response to WG
desire.
3. Updated references.
The following changes have been made from version draft-ietf-
multimob-pmipv6-source-01:
1. Added clarifications and details as requested by the working
group, resolved nits.
2. Detailed out operations of Multiple Upstream MLD Proxies.
3. Clarified operations of MLD proxies with peering links.
4. Many editorial improvements.
5. Updated references.
The following changes have been made from version draft-ietf-
multimob-pmipv6-source-00:
1. Direct routing with PIM-SM and PIM-SSM has been added.
2. PMIP synchronization with PIM added for improved handover.
3. Direct routing with BIDIR-PIM has been added.
4. MLD proxy extensions requirements added.
5. Peering of MLD Proxies added.
6. First sketch of multiple upstream proxy added.
7. Editorial improvements.
8. Updated references.
Authors' Addresses Authors' Addresses
Thomas C. Schmidt (editor) Thomas C. Schmidt (editor)
HAW Hamburg HAW Hamburg
Berliner Tor 7 Berliner Tor 7
Hamburg 20099 Hamburg 20099
Germany Germany
Email: schmidt@informatik.haw-hamburg.de Email: schmidt@informatik.haw-hamburg.de
 End of changes. 14 change blocks. 
118 lines changed or deleted 51 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/