Internet Engineering Task Force Q. Sun
Internet-Draft China Telecom
Intended status: Informational C. Zhou
Expires: August 24, 2013 Huawei Technologies
February 20, 2013
Multicast transition path optimization in IPv4 and IPv6 networks
draft-zhou-mboned-multrans-path-optimization-03
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.
Requirements Language
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 .
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 August 24, 2013.
Copyright Notice
Sun & Zhou Expires August 24, 2013 [Page 1]
Internet-Draft Multrans path optimization February 2013
Copyright (c) 2013 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Solution Overview . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. A general topology for IPv4 and IPv6 multicast networks . . 5
4.2. Parsing MTR to two virtual Routers . . . . . . . . . . . . 6
4.3. Selecting interfaces to Source or RP . . . . . . . . . . . 7
4.4. Selecting a multicast data flow from upstream interface . . 7
4.5. Requirements to the mulitcast Router . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
8. Informative References . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
Sun & Zhou Expires August 24, 2013 [Page 2]
Internet-Draft Multrans path optimization February 2013
1. Introduction
It is common to use multi-access LANs such as Ethernet for
transmitting multicast data in networks. Section 3.6 of[RFC4601]
describes Multi-Access Transit LANs.
The PIM Assert message could be used when there are two identical
multicast data flows (IPv4 and IPv6). When duplicate data packets
appear on the LAN from different routers, the routers notice this and
then select a single forwarder. This selection is performed using
datatracker.ietf.org