RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

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

Source of RFC: pim (rtg)

Errata ID: 5343
Status: Rejected
Type: Technical
Publication Format(s) : TEXT

Reported By: Frank Hua Li
Date Reported: 2018-04-28
Rejected by: Alvaro Retana
Date Rejected: 2018-05-24

Section 4.11 says:

4.11 Page 128: 
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.

It should say:

If the pseudo code in 4.4.2 page 43 is correct, the text should be:
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
RP_Keepalive_Period when a Register-Stop
is sent.

Notes:

4.11 Page 128: 4.11 Page 128:
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.

Frank's Note: This statement contradicts with pseudo code in 4.4.2 page 43.
In page 43, the KeepaliveTimer(S,G) is set to
RP_Keepalive_Period instead of max(Keepalive_Period, RP_Keepalive_Period).
quote from page 43:
if ( SPTbit(S,G) OR SwitchToSptDesired(S,G) ) {
if ( sentRegisterStop == TRUE ) {
set KeepaliveTimer(S,G) to RP_Keepalive_Period;
} else {
set KeepaliveTimer(S,G) to Keepalive_Period;
}
}
--VERIFIER NOTES--
See Errata ID 5342.

Report New Errata