RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Rejected (2)

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

Source of RFC: msdp (rtg)

Errata ID: 4013
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Ramiro Garza Rios
Date Reported: 2014-06-12
Rejected by: Alia Atlas
Date Rejected: 2014-06-17

Section 12.2 says: 

12.2. Defined TLVs


   The following TLV Types are defined:

   Code                        Type
   ===================================================
     1                  IPv4 Source-Active
     2                  IPv4 Source-Active Request
     3                  IPv4 Source-Active Response
     4                  KeepAlive
     5                  Reserved (Previously: Notification)

It should say:

12.2. Defined TLVs


   The following TLV Types are defined:

   Code                        Type
   ===================================================
     1                  IPv4 Source-Active
     2                  (Previously IPv4 Source-Active Request)
     3                  (Previously IPv4 Source-Active Response)
     4                  KeepAlive
     5                  Reserved (Previously: Notification)

Notes:

Since SA caching is mandatory for all MSDP speakers, the Source-Active request and response messages are no longer necessary. They should be removed from the text to avoid confusion or include a reason as to why they are included and a description of their purpose.
--VERIFIER NOTES--
This needs to go through the standards process. Deprecating messages in the protocol is not an errata item.

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



Advanced Search