Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 8736,RFC 9436

Authors:

Y. Cai
L. Wei
H. Ou
V. Arya
S. Jethwani

Stream:

IETF

Source:

pim (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6754

Discuss this RFC: Send questions or comments to the mailing listpim@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6754

Abstract

A Protocol Independent Multicast (PIM) router uses the Reverse PathForwarding (RPF) procedure to select an upstream interface and routerin order to build forwarding state. When there are equal costmultipaths (ECMPs), existing implementations often use hashalgorithms to select a path. Such algorithms do not allow the spreadof traffic among the ECMPs according to administrative metrics. Thisusually leads to inefficient or ineffective use of network resources.This document introduces the ECMP Redirect, a mechanism to improvethe RPF procedure over ECMPs. It allows ECMP selection to be basedon administratively selected metrics, such as data transmissiondelays, path preferences, and routing metrics. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.