Search RFCs

RFC Editor

Found 4 records.

Status:Verified (2)

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

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

Errata ID:5342
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Frank Hua Li
Date Reported: 2018-04-28
Verifier Name: Alvaro Retana
Date Verified: 2018-05-24

Section 4.4.2 says:

set KeepaliveTimer(S,G) to RP_Keepalive_Period;

It should say:

set KeepaliveTimer(S,G) to max(Keepalive_Period, RP_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.

Errata ID:7857
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alexander Okonnikov
Date Reported: 2024-03-19
Verifier Name: RFC Editor
Date Verified: 2024-03-20

Section 4.6.5 says:

     bool lost_assert(S,G,I) {       if ( RPF_interface(S) == I ) {          return FALSE       } else {          return ( AssertWinner(S,G,I) != NULL AND                   AssertWinner(S,G,I) != me  AND                   (AssertWinnerMetric(S,G,I) is better                      than spt_assert_metric(S,I) )       }     }

It should say:

     bool lost_assert(S,G,I) {       if ( RPF_interface(S) == I ) {          return FALSE       } else {          return ( AssertWinner(S,G,I) != NULL AND                   AssertWinner(S,G,I) != me  AND                   AssertWinnerMetric(S,G,I) is better                      than spt_assert_metric(S,I) )       }     }

Notes:

Excessive parenthesis before 'AssertWinnerMetric(S,G,I)'.

Status:Held for Document Update (1)

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

Note: This RFC has been updated byRFC 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.

Status:Rejected (1)

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

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

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 theRegister_Suppression_Time, or the RP may time out the (S,G) statebefore the next Null-Register arrives. Thus, the KAT(S,G) is set tomax(Keepalive_Period, RP_Keepalive_Period) when a Register-Stopis 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 theRegister_Suppression_Time, or the RP may time out the (S,G) statebefore the next Null-Register arrives. Thus, the KAT(S,G) is set toRP_Keepalive_Period when a Register-Stopis 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