RFC 7761, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", March 2016

Note: This RFC has been updated by RFC 8736, RFC 9436

Errata ID: 5367
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Frank Hua Li
Date Reported: 2018-05-24
Held for Document Update by: Alvaro Retana
Date Held: 2018-10-29

Section 4.4.2 says:

4.4.2 Page 44
   Thus, at the RP, KeepaliveTimer(S,G) should be restarted to ( 3 *
   Register_Suppression_Time + Register_Probe_Time ).

It should say:

4.4.2 Page 44
   Thus, at the RP, KeepaliveTimer(S,G) should be restarted to the 
   maximum of ( 3 * Register_Suppression_Time + Register_Probe_Time ) 
   and Keepalive_Period.

Notes:

The normal keepalive period for the KAT(S,G) defaults to 210 seconds. However, at the RP, the keepalive period must be at least the Register_Suppression_Time, or the RP may time out the (S,G) state before the next Null-Register arrives. Thus, the KAT(S,G) is set to max(Keepalive_Period, RP_Keepalive_Period) when a Register-Stop is sent.

====
Note that the text above comes from §4.11.

===
Please also refer to Errata ID 5342.

Report New Errata