Multicast mobility deployment scenarios over distributed mobility management
draft-kjsun-dmm-deployment-scenarios-multicast-dmm-00
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
|---|---|---|---|
| Authors | Kyoungjae Sun , Van-Giang Nguyen , xuan@dcn.ssu.ac.kr , Younghan Kim | ||
| Last updated | 2015-07-06 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-kjsun-dmm-deployment-scenarios-multicast-dmm-00
Distributed Mobility Management Kyoungjae Sun
Internet Draft Van-Giang Nguyen
Intended status: Informational Truong-Xuan Do
Expires: January 2016 Younghan Kim
Soongsil University, Korea
July 6, 2015
Multicast mobility deployment scenarios over distributed mobility
management
draft-kjsun-dmm-deployment-scenarios-multicast-dmm-00.txt
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 6, 2009.
Copyright Notice
Copyright (c) 2015 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
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.
KJ Sun, et al. Expires January 6, 2016 [Page 1]
Internet-Draft Multicast deployment scenario over DMM July 2015
Abstract
This document presents deployment scenarios for supporting IP
multicast over distributed mobility management (DMM) architecture,
which considers the separation of the control and the data planes.
This document describes three main use cases of IP multicast
deployments over DMM depending on the placement of control and data
plane functional entities.
Table of Contents
1. Introduction ................................................ 2
2. Functional Decomposition..................................... 3
3. Terminology ................................................. 3
4. Use Cases Analysis .......................................... 4
4.1. Use Case 1: Spit all.................................... 5
4.2. Use Case 2: Distributed Multicast Data Plane............ 6
4.3. Use Case 3: Collocation of the multicast anchor and
multicast node .............................................. 7
4.4. Use Case 4: Floating multicast anchor................... 8
5. Security Considerations...................................... 8
6. IANA Considerations ......................................... 8
7. References .................................................. 8
7.1. Normative References.................................... 8
7.2. Informative References.................................. 9
8. Acknowledgments ............................................. 9
1. Introduction
Distributed mobility management is a new paradigm to solve current
problems of centralized mobility management, such as a single point
of failure, non-optimal routing [RFC7333].
IP multicast is an efficient content distribution mechanism which is
designed with the IP mobility to bring new user experience and
reduce bandwidth cost. In the [RFC7333], one requirement for DMM is
to enable multicast solutions to avoid the inefficiency in the
multicast traffic delivery.
Existing solutions for supporting multicast in DMM are bi-
directional tunnel [TUNNEL] and direct routing [ROUTING]. These
solutions focus on the placement of MLD proxy and multicast router
functions into the Mobility Access Router.
The current architecture of the DMM is being changed to employ the
concept of data and control plane separation. The data plane nodes
KJ Sun, et al. Expires January 6, 2016 [Page 2]
Internet-Draft Multicast deployment scenario over DMM July 2015
are configured by the control nodes via Forwarding Policy
Configuration protocol, as defined in [PFPC]. The several deployment
scenarios were presented in [DEPLOYMENT].
However, there is no work until now, mentioning about multicast
support in such new DMM architectures. Therefore, this document
presents possible deployment scenarios, which support multicast
listener in the DMM architectures based on the concept of the data
and control planes separation.
2. Functional Decomposition
Two options for deploying the multicast over conventional
distributed mobility management (i.e. without the control and data
plane separation) are MLD Proxy and Multicast router [RFC3810]
[RFC4605]. This section decomposes functions of MLD Proxy and
Multicast router that are required to deliver the multicast traffic
with the respect to the concept of data and control planes
separation.
+------------------------------------------------------------------+
| Function | Description |C/D Plane|
+------------------------------------------------------------------+
|Run | Used to join/leave the multicast tree | C-Plane |
|multicast | infrastructure to receive the multicast | |
|routing | data | |
|protocol | | |
+------------------------------------------------------------------+
|MLD | Used to notify about the multicast group | C-Plane |
|membership | membership on the directly attached link | |
|report | | |
+------------------------------------------------------------------+
|MLD | Used to discover multicast listeners on | C-Plane |
|Querier | the directly attached link | |
+------------------------------------------------------------------+
|Membership | Used to maintain the merger of multicast | C-Plane |
|database | subscriptions | |
+------------------------------------------------------------------+
|Multicast | Used to forward multicast packets based on| D-Plane |
|forwarding | the multicast subscriptions over each link| |
+------------------------------------------------------------------+
3. 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 [RFC2119].
KJ Sun, et al. Expires January 6, 2016 [Page 3]
Internet-Draft Multicast deployment scenario over DMM July 2015
This document uses the terminology defined in [RFC4605] and
[RFC3810]. Also, new entities are defined relying on the concept of
data and control planes separation and the functional decomposition.
- CMA (Control plane Multicast Anchor): CMA consists of the control
plane functions of the multicast router (Multicast Anchor). CMA is
responsible for joining the multicast tree.
- DMA (Data plane Multicast Anchor): DMA is the topological anchor
point for multicast channels, subscribed by the MN. DMA provides
packet treatment functions, such as packet forwarding, packet
encapsulation. The DMA can be configured by the CMA via Forwarding
Policy Configuration (FPC) protocol
- CMN (Control plane Multicast Node): CMN is responsible for
control plane functions of MLD-Proxy (multicast node) as described
in the previous section.
- DMN (Data plane Multicast Node): DMN is located at the first-hop
router where the MN is attached. The DMN has the protocol
interface with the CMN for configuration.
4. Use Cases Analysis
+--------------------+ +--------------------+
| +-----+ +-----+ | | +---------+ |
| | CMN | | CMA | | | | CMN+CMA | |
| +-----+ +-----+ | | +---------+ |
| +-----+ +-----+ | | +-----+ +-----+ |
| | DMN | | DMA | | | | DMN | | DMA | |
| +-----+ +-----+ | | +-----+ +-----+ |
+--------------------+ +--------------------+
Use Case 01 Use Case 02
+--------------------+ +--------------------+
| +-----------+ | | +---------+ |
| | CMN+CMA | | | | CMA | |
| +-----------+ | | +---------+ |
| +-----+ +-----+ | | +---------+ |
| | DMN | | DMA | | | | DMA | |
| +-----+ +-----+ | | +---------+ |
| | DMA | | DMN | | +--------------------+
| +-----+ +-----+ |
+--------------------+
Use Case 03 Use Case 04
Figure 1 Deployment Scenarios
We identify different deployment use cases for supporting multicast
over such DMM architecture. Basically, these use cases result from
the placement of CMA/DMA, CMN/DMN functional entities defined above.
KJ Sun, et al. Expires January 6, 2016 [Page 4]
Internet-Draft Multicast deployment scenario over DMM July 2015
Figure 1 depicts the four deployment scenarios for multicast
mobility over DMM architecture.
In the use case 01, the control plane and data plane are separated
in both multicast anchor and multicast node
In the use case 02, the control planes for multicast anchor and
multicast node are combined, the DMN and DMA are deployed on
separate access gateway.
In the use case 03, the DMN and DMA can be collocated on the same
access gateway.
In the use case 04, the access gateway has only the functions of DMA
4.1. Use Case 1: Spit all
+-------+ +--------+
. | | Aggregated | |
. | CMN |...........+| CMA |.
. +-------+ MLD Report +--------+ .
. . | + | .
. . |Setup | |Setup .
. . MLD :forwarding : :forwarding .
. . Report |rules | |rules .
. . | | | .
+ . + . + +
+-------+ +--------+ +--------+ +----------+
| | Traffic| | Traffic | | Traffic | Multicast|
| MN |+=======| DMN |+=========| DMA |+========| Tree |
+-------+ +--------+ +--------+ +----------+
Deliver multicast Deliver multicast
traffic traffic
Figure 2 Protocol operations in split all use case
In this use case, when the MN attaches to the new access gateway and
subscribes a multicast channel, the DMN will relay the multicast
subscription messages (i.e. MLD Report) to the CMN. The CMN
aggregates and exchanges the membership information with the CMA.
The CMA sends control messages to join the multicast tree. The CMN
and CMA configures the DMN and DMA using the sounth bound protocol
(e.g. the Forwarding Policy Configuration (FPC) protocol [PFPC]) to
forward the multicast traffic. Here, the multicast traffic will be
encapsulated at the DMA and sent to the DMN. Figure 2 shows protocol
operation in the split all use case.
KJ Sun, et al. Expires January 6, 2016 [Page 5]
Internet-Draft Multicast deployment scenario over DMM July 2015
4.2. Use Case 2: Distributed Multicast Data Plane
In this use case, the CMN and CMA are combined into one multicast
control entity (MC), but the DMN and DMA are deployed in separate
access gateways. The MC takes care of receiving the multicast
subscription from the MN and joins the multicast infrastructure. The
multicast traffic is delivered to the DMA, here encapsulated and
sent to the DMN. Figure 3 shows the protocol operation in
distributed multicast data plane use case.
+--------------+
+| |.
. | CMN+CMA | .
. +--------------++ .
. / | + . .
Relay MLD. / | | . . Aggregated
Report. /Setup : :Setup . . MLDReport
. /forwarding| |forwarding . .
. / rules | |rules . .
. / : : . .
. + + | . +
+-----+ MLD Report +--------+ +--------+ +----------+
| |.............+| | Traffic| | Traffic | Multicast|
| MN |+=============| DMN |+=======| DMA |+========| Tree |
+-----+ Traffic +--------+ +--------+ +----------+
Deliver multicast Deliver multicast
traffic traffic
Figure 3 Protocol operations in distributed multicast data plane use
case
KJ Sun, et al. Expires January 6, 2016 [Page 6]
Internet-Draft Multicast deployment scenario over DMM July 2015
4.3. Use Case 3: Collocation of the multicast anchor and multicast node
+--------------+
+| |.
. | CMN+CMA | .
. +--------------++ .
. / | + . .
Relay MLD. / | | . . Aggregated
Report. /Setup : :Setup . . MLDReport
. /forwarding | |forwarding . .
. / rules | |rules . .
. / : : . .
. + + | . +
+-----+ MLD Report +--------+ +--------+ +----------+
| |.............+| DMN | Traffic| DMA | Traffic | Multicast|
| MN |+=============|--------|+=======|--------|+========| Tree |
+-----+ Traffic | DMA | | DMN | +----------+
+--------+ +--------+
Deliver multicast Deliver multicast
traffic traffic
Figure 4 Protocol operations in collaboration of the multicast
anchor and multicast node use case
In this use case, the DMA and DMN can be collocated into one access
gateway. On a multicast channel basis, the respective functions are
activated for a new multicast channel. It means that when the MN
subscribes to a new multicast channel, which wasn't subscribed at
the previous DMA. The new DMA function in the access gateway will be
activated. In this case, the multicast traffic for old channel
(subscribed at the previous DMA) will be encapsulated and sent
between the previous DMA and current DMN. The multicast traffic for
new channel will be delivered to the new DMA function at the current
access gateway. Figure 4 shows the protocol operation in the
collaboration of the multicast anchor and multicast node use case.
KJ Sun, et al. Expires January 6, 2016 [Page 7]
Internet-Draft Multicast deployment scenario over DMM July 2015
4.4. Use Case 4: Floating multicast anchor
+----------+
| |
.| CMA |+
. +----------+. .
General MLD . + | + . .
Query/Report . . | | . . Aggregated
. . : :Setup . . MLD Report
. . | |forwarding . .
. . | |rules . .
. . : : . .
+ . + | + .
+---------+ +----------+ +------------+
| | Traffic | | Traffic | Multicast |
| MN |+==============| DMA |+==========| Tree |
+---------+ +----------+ +------------+
Delivery multicast
sTraffic
Figure 5 Protocol operations in floating multicast anchor use case
In this use case, the access gateway assumes the function of DMA and
there is no DMN function. The CMA receives the subscription
information from the MN and joins the multicast tree. At the same
time, the CMA configures the DMA to receive the multicast traffic.
Figure 5 shows the protocol operation in the floating multicast
anchor use case.
5. Security Considerations
T.B.D
6. IANA Considerations
T.B.D
7. References
7.1. Normative References
KJ Sun, et al. Expires January 6, 2016 [Page 8]
Internet-Draft Multicast deployment scenario over DMM July 2015
[RFC7333] H. Chan, D. Liu, P. Seite, H. Yokota, and J. Korhonen,
"Requirements for Distributed Mobility Management", IETF
RFC 7333, Aug. 2014.
[RFC3810] R. Vida, and L. Costa, "Multicast Listener Discovery
Version 2 (MLDv2) for IPv6", IETF RFC 3810, June 2004.
[RFC4605] B. Fenner, H. He, B. Haberman, H. Sandick, "Internet Group
Management Protocol (IGMP)/ Multicast Listener Discovery
(MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying")",
IETF RFC 4605, Aug. 2006.
7.2. Informative References
[TUNNEL] S. Figueiredo, S. Jeon, and R. L. Aguiar, "IP Multicast Use
Cases and Analysis over Distributed mobility
Management",draft-sfigueiredo-multimob-use-case-dmm-03
(expired April 2013).
[ROUTING] Y. Kim, T-X. Do, and Y. Kim, "Direct Routing for Mobile
Multicasting in Distributed Mobility Management Domain",
Proc. INTERNET 2013 pp. 1-3.
[PFPC] M. Liebsch, S. Matsushima, S. Bundavelli, D. Moses, "Protocol
for Forwarding Policy Configuration (FPC)", draft-ietf-
dmm-fpc-cpdp-00 (work in progress), May 6, 2015.
[DEPLOYMENT] S. Gundavelli, "Distributed Mobility Management:
Architectural Considerations", presented at IETF Meeting
92, April 2015.
8. Acknowledgments
KJ Sun, et al. Expires January 6, 2016 [Page 9]
Internet-Draft Multicast deployment scenario over DMM July 2015
Authors' Addresses
Kyoungjae Sun
Soongsil University
369, Sangdo-ro, Dongjak-gu
Seoul 156-743, Korea
Email: gomjae@ssu.ac.kr
Van-Giang Nguyen
Soongsil University
369, Sangdo-ro, Dongjak-gu
Seoul 156-743, Korea
Email: nvgiang@dcn.ssu.ac.kr
Truong-Xuan Do
Soongsil University
369, Sangdo-ro, Dongjak-gu
Seoul 156-743, Korea
Email: xuan@dcn.ssu.ac.kr
Younghan Kim
Soongsil University
369, Sangdo-ro, Dongjak-gu
Seoul 156-743, Korea
Email: younghak@dcn.ssu.ac.kr
KJ Sun, et al. Expires January 6, 2016 [Page 10]