PMIPv6 Multicasting Support using Native Infrastructure
draft-sijeon-multimob-direct-routing-pmip6-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Seil Jeon , Younghan Kim | ||
| Last updated | 2011-07-11 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
To support IP multicasting in PMIPv6 domain, [RFC6424] has been determined as a base solution. This solution requires all the LMA to forward multicast packets to MAG via PMIPv6 tunnel. This approach creates a tunnel convergence problem. To resolve the issue, the current MULTIMOB WG charter is trying to draw a solution about how to separate multicasting routing from a mobility anchor. To address the issue, we propose the local routing approach that makes the direct connection between MAG and multicast router. The advantages of the proposed local routing solution are compared with the base solution and dedicated LMA approach. In addition, we present the applicability of local routing solution depending on several constraints.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)