datatracker.ietf.org
Sign in
Version 5.7.1.p2, 2014-10-29
Report a bug

Multicast transition path optimization in IPv4 and IPv6 networks
draft-zhou-mboned-multrans-path-optimization-03

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-08-25 (latest revision 2013-02-21)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-zhou-mboned-multrans-path-optimization-03.txt

Abstract

This document describes a mechanism to optimize the path between the multicast router and multicast source in both IPv4 and IPv6 networks. The basic idea is that when a multicast translation router has an IPv4 path and an IPv6 path to the same multicast data source, and both IPv4 and IPv6 joins are received, only one path is used. One path is pruned, instead of the same traffic flowing over both v4 and v6 paths. By adding a metric to the IPv4 path, the multicast translation router can determine which path to receive multicast data: IPv4 path, IPv6 path or both. Therefore, an optimization path will typically be chosen when an identical v4/v6 traffic flow exists.

Authors

Qiong <sunqiong@ctbri.com.cn>
Cathy Zhou <cathy.zhou@huawei.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)