draft-ietf-multimob-pmipv6-source-05.txt   draft-ietf-multimob-pmipv6-source-06.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: April 03, 2014 H. Zhang Expires: April 22, 2014 H. Zhang
Beijing Jiaotong University Beijing Jiaotong University
M. Waehlisch M. Waehlisch
link-lab & FU Berlin link-lab & FU Berlin
September 30, 2013 October 19, 2013
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-05 draft-ietf-multimob-pmipv6-source-06
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 the support of mobile multicast senders in This document describes the support of mobile multicast senders in
Proxy Mobile IPv6 domains for all three scenarios. Protocol Proxy Mobile IPv6 domains for all three scenarios. Protocol
optimizations for synchronizing PMIPv6 with PIM, as well as a peering optimizations for synchronizing PMIPv6 with PIM, as well as a peering
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 April 03, 2014. This Internet-Draft will expire on April 22, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 13 skipping to change at page 3, line 13
5.4. Operations at the Multicast Listener . . . . . . . . . . 19 5.4. Operations at the Multicast Listener . . . . . . . . . . 19
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.1. Normative References . . . . . . . . . . . . . . . . . . 21 9.1. Normative References . . . . . . . . . . . . . . . . . . 21
9.2. Informative References . . . . . . . . . . . . . . . . . 22 9.2. Informative References . . . . . . . . . . . . . . . . . 22
Appendix A. Multiple Upstream Interface Proxy . . . . . . . . . 23 Appendix A. Multiple Upstream Interface Proxy . . . . . . . . . 23
A.1. Operations for Local Multicast Sources . . . . . . . . . 23 A.1. Operations for Local Multicast Sources . . . . . . . . . 23
A.2. Operations for Local Multicast Subscribers . . . . . . . 24 A.2. Operations for Local Multicast Subscribers . . . . . . . 23
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 24 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
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 14, line 48 skipping to change at page 14, line 48
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
from the RP via the (stable) LMA, down the LMA-MAG tunnel to the from the RP via the (stable) LMA, down the LMA-MAG tunnel to the
mobile source. This tree can be of lower routing efficiency than the mobile source. This tree can be of lower routing efficiency than the
PIM source register tunnel established in phase one, but provides the PIM source register tunnel established in phase one.
advantage of immediate data delivery to receivers that share a MAG
with S.
On handover, the mobile source reattaches to a new MAG (DR), and On handover, the mobile source reattaches to a new MAG (DR), and
PMIPv6 unicast management will transfer the LMA-MAG tunnel to the new PMIPv6 unicast management will transfer the LMA-MAG tunnel to the new
point of attachment. However, in the absence of a corresponding point of attachment. However, in the absence of a corresponding
multicast forwarding state, the new DR will treat S as a new source multicast forwarding state, the new DR will treat S as a new source
and initiate a source registering of PIM phase one with the RP. In and initiate a source registering of PIM phase one with the RP. In
response, the PIM RP will recognize the known source at a new response, the PIM RP will recognize the known source at a new
(tunnel) interface and immediately responds with a register stop. As (tunnel) interface and immediately responds with a register stop. As
the RP had previously joined the shortest path tree towards the the RP had previously joined the shortest path tree towards the
source via the LMA, it will see an RPF change when data arrives at a source via the LMA, it will see an RPF change when data arrives at a
skipping to change at page 22, line 51 skipping to change at page 22, line 31
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-01 (work in progress), February fmipv6-pfmipv6-multicast-01 (work in progress), February
2013. 2013.
[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-04 (work in progress), ietf-multimob-handover-optimization-05 (work in progress),
September 2013. October 2013.
[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
skipping to change at page 24, line 48 skipping to change at page 24, line 27
could be either associated with selected uplinks to remote LMAs, could be either associated with selected uplinks to remote LMAs,
while a (*,*) default subscription entry (in the last table line) is while a (*,*) default subscription entry (in the last table line) is
bound to a local routing interface, or selected groups are configured bound to a local routing interface, or selected groups are configured
as local services first, while a (*,*) default entry (in the last as local services first, while a (*,*) default entry (in the last
table line) points to a remote uplink that provides the general table line) points to a remote uplink that provides the general
multicast support. multicast support.
Appendix B. Change Log Appendix B. Change Log
The following changes have been made from version draft-ietf- 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: multimob-pmipv6-source-04:
1. Cleaned structure in Section Section 5. 1. Cleaned structure in Section Section 5.
2. Clarified operations of the proxy peering function. 2. Clarified operations of the proxy peering function.
3. Completed Section on Security Considerations. 3. Completed Section on Security Considerations.
4. Editorial improvements in response to WG feedback. 4. Editorial improvements in response to WG feedback.
 End of changes. 9 change blocks. 
11 lines changed or deleted 16 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/