PIM Flooding Protocol over Reliable Transport

Document Type Expired Internet-Draft (individual)
Last updated 2019-09-12 (latest revision 2019-03-11)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized 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


The PIM Flooding Protocol (PFM) defined in RFC8364 relies on sending periodic updates as it does not provide for any reliability. If a message is lost, the information will be provided in the next periodic update. This document extends the Reliable Transport Mechanism for PIM in RFC6559 to allow for sending PFM messages. This significantly reduces the PFM signaling by not requiring frequent periodic updates, and it provides for retransmission, allowing for quick recovery when an IP packet is dropped.


Stig Venaas (stig@cisco.com)
Balaji Ganesh (balagane@cisco.com)
Kesavan Thiruvenkatasamy (kethiruv@cisco.com)
Ramakrishnan Sundaram (ramaksun@cisco.com)

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