RFC 3618, "Multicast Source Discovery Protocol (MSDP)", October 2003

Errata ID: 5356
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Frank Hua Li
Date Reported: 2018-05-10
Rejected by: Alvaro Retana
Date Rejected: 2018-05-24

Section 5.3 says:

5.3.  SA Cache Timeout (SA-State Timer)

   Each entry in an SA Cache has an associated SA-State Timer.  A
   (S,G)-SA-State-Timer is started when an (S,G)-SA message is initially
   received by an MSDP peer.  The timer is reset to [SG-State-Period] if
   another (S,G)-SA message is received before the (S,G)-SA-State Timer
   expires.  [SG-State-Period] MUST NOT be less than [SA-Advertisement-
   Period] + [SA-Hold-Down-Period].

It should say:

5.3.  SA Cache Timeout (SA-State Timer)

   Each entry in an SA Cache has an associated SA-State Timer.  A
   (S,G)-SA-State-Timer is started when an (S,G)-SA message is initially
   received by an MSDP peer.  The timer is reset to [SG-State-Period] if
   another (S,G)-SA message is received before the (S,G)-SA-State Timer
   expires.  [SG-State-Period] MUST NOT be less than [SA-Advertisement-
   Period].

Or define the [SA-Hold-Down-Period] refers to.

Notes:

There is no definition of [SA-Hold-Down-Period] timer in the document. We should either remove the reference of [SA-Hold-Down-Period] from 5.3 or clearly define what [SA-Hold-Down-Period] refers to. If not, this will cause confusion for implementation.
--VERIFIER NOTES--
The discussion on the WG list is here: https://mailarchive.ietf.org/arch/msg/pim/HeCvgF59HdxWMp7PYSUUteL2D5E

Report New Errata