1 / 8

IETF 84, Vancouver

Multrans Path Optimization draft-zhou-mboned-multrans-path-optimization-02 Cathy ZHOU <cathy.zhou@huawei.com> Qiong SUN <sunqiong@ctbri.com.cn>. IETF 84, Vancouver. Scenario. MTR(Multicast Translation Router ) can be mXlate and mAFTR. MTR1 has two upstream routers

rosalyn-yanez
Download Presentation

IETF 84, Vancouver

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Multrans Path Optimizationdraft-zhou-mboned-multrans-path-optimization-02Cathy ZHOU <cathy.zhou@huawei.com>Qiong SUN <sunqiong@ctbri.com.cn> IETF 84, Vancouver

  2. Scenario MTR(Multicast Translation Router) can be mXlate and mAFTR • MTR1 has two upstream routers • MRT1 can receive both IPv4 and IPv6 (*.G) Join request. • Problems • MTR1 needs to select a best path to RP or Source in both IPv4 and IPv6 networks. • MTR1 needs to send Prune Messages to the worse path, when it receives two multicast data flows in IPv4 and IPv6 interface. HGW IPv4 Router STB IPv6 TV MTR1 (*, G) Join IPv4 source Multicast data Flow IPv6 Router MTR2

  3. Proposed Solution MTR Router • When MTR receives two multicast data flows (one from IPv4 interface and the other from IPv6 interface), it compares two flows according to draft-boucadair-behave-64-multicast-address-format to confirm whether they are the same multicast data flow. If they are the same data flows, select one or two. • When MTR receives an IPv6 (S, G) or (*, G) Join, virtual IPv6 Router selects an interface to send Join message. The interface can be IPv6 upstream IF or IPv4 upstream IF (via interface between virtual IPv6 Router and virtual IPv4 Router) For simplification, we use two virtual Routers to replace MTR Router IPv6 upstream IF IPv4 upstream IF Virtual IPv6 Router Virtual IPv4 Router

  4. Select an Interface to the Source Multicast source m2 m3 IPv6 Router IPv4 Router (*, G) Join m1 MTR • If m2>m3+m1, sending PIM Join message from IPv4 interface; • If m2<m3+m1, sending PIM Join message from IPv6 interface;

  5. Select a Multicast Data Flow From Upstream IF Multicast source m2 m3 IPv6 Router IPv4 Router Multicast flow 2 Multicast flow 1 m1 MTR • If m2>m3+m1, MTR will send PIM Prune Messages to IPv6 interface; • If m2<m3+m1MTR will send PIM Prune Messages to interface of two virtual Routers. MTR will not translate or encapsulate multicast data from IPv4 to IPv6.

  6. Requirements to the Multicast Router • Check multicast data flow from IPv4 and IPv6 interfaces to determine whether they are the same multicast data flows. • Send PIM Assert message from IPv4 and IPv6 interfaces with different Metric value. • May stop translating or encapsulating IPv4 to IPv6 multicast flow or send Prune Messages to stop receiving IPv6/IPv4 multicast flow.

  7. References • RFC4601 • draft-lee-behave-v4v6-mcast-fwk • draft-ietf-softwire-dslite-multicast • draft-ietf-mboned-64-multicast-address-format

  8. Next Steps • Adopt as WG item?

More Related