PIM Backup Designated Router Procedure
draft-ietf-pim-bdr-01
| Document | Type |
Expired Internet-Draft
(pim WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mankamana Prasad Mishra , Sridhar Santhanam , Aravind Paramasivam , Imed Romdhani , Gyan Mishra | ||
| Last updated | 2022-09-08 (Latest revision 2022-03-07) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 Prasad Mishra
Sridhar Santhanam
Aravind Paramasivam
Imed Romdhani
Gyan Mishra
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)