PIM Backup Designated Router Procedure
draft-mankamana-pim-bdr-05

Document Type Expired Internet-Draft (individual)
Authors Mankamana Mishra  , Sridhar Santhanam  , Aravind Paramasivam  , Joseph Goh  , Gyan Mishra 
Last updated 2021-10-10 (latest revision 2021-04-08)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-mankamana-pim-bdr-05.txt

Abstract

On a multi-access network, one of the PIM routers is elected as a Designated Router (DR). On the last hop LAN, the PIM DR is responsible for tracking local multicast listeners and forwarding traffic to these listeners if the group is operating in PIM-SM. In this document, we propose a mechanism to elect backup DR on a shared LAN. A backup DR on LAN would be useful for faster convergence. This draft introduces the concept of a Backup Designated Router (BDR) and the procedure to implement it.

Authors

Mankamana Mishra (mankamis@cisco.com)
Sridhar Santhanam (sridsant@cisco.com)
Aravind Paramasivam (arparama@cisco.com)
Joseph Goh (hocgoh@cisco.com)
Gyan Mishra (gyan.s.mishra@verizon.com)

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