RFC Errata
Found 4 records.
Status: Verified (4)
RFC 3973, "Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)", January 2005
Note: This RFC has been updated by RFC 8736, RFC 9436
Source of RFC: pim (rtg)
Errata ID: 3271
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Joseph Weinstein
Date Reported: 2012-06-28
Verifier Name: Adrian Farrel
Date Verified: 2012-08-22
Section 4.5.1 says:
if StateRefreshCapable(I) == TRUE set PT(S,G) to largest active holdtime read from a Prune message accepted on I;
It should say:
if StateRefreshCapable(I) == TRUE set PT(S,G,I) to the Holdtime from an active Prune received on interface I. The Holdtime used SHOULD be the largest active one but MAY be the most recently received active Prune Holdtime.
Notes:
It is not clear what is meant by the "largest active holdtime", and in any event sec. 4.4.2.3 specifies a slightly different rule:
Send State Refresh(S,G) out interface I
The router has refreshed the Prune(S,G) state on interface I.
The router MUST reset the Prune Timer (PT(S,G,I)) to the Holdtime
from an active Prune received on interface I. The Holdtime used
SHOULD be the largest active one but MAY be the most recently
received active Prune Holdtime.
Additionally...
No macro PT(S,G) is defined anywhere in the RFC; the reference appears to be to P(S,G,I).
The concept of an "active Prune" is not defined in this RFC, but simply means those prunes which have not expired.
Errata ID: 967
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mark Doll
Date Reported: 2007-05-16
Verifier Name: Adrian Farrel
Date Verified: 2011-09-04
Section 4.6.1 says:
assert_metric my_assert_metric(S,G,I) { if (CouldAssert(S,G,I) == TRUE) { return spt_assert_metric(S,G,I) } else { return infinite_assert_metric() } }
It should say:
assert_metric my_assert_metric(S,G,I) { if (CouldAssert(S,G,I) == TRUE) { return spt_assert_metric(S,I) } else { return infinite_assert_metric() } }
Notes:
In Section 4.6.1, spt_assert_metric(S,I) is defined to have two
parameters, not three.
from pending [error in data transfer corrected 2/15/08.]
Errata ID: 968
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mark Doll
Date Reported: 2007-05-16
Verifier Name: Adrian Farrel
Date Verified: 2011-09-04
Section 4.6.1 says:
assert_metric spt_assert_metric(S,I) { return {0,MRIB.pref(S),MRIB.metric(S),my_addr(I)} }
It should say:
assert_metric spt_assert_metric(S,I) { return {MRIB.pref(S),MRIB.metric(S),my_addr(I)} }
Notes:
In Section 4.6.1, assert_metric is defined to be a 3-tuple, not a
4-tuple.
Errata ID: 969
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mark Doll
Date Reported: 2007-05-16
Verifier Name: Adrian Farrel
Date Verified: 2011-09-04
Section 4.6.1 says:
assert_metric infinite_assert_metric() { return {1,infinity,infinity,0} }
It should say:
assert_metric infinite_assert_metric() { return {infinity,infinity,0} }
Notes:
In Section 4.6.1, assert_metric is defined to be a 3-tuple, not a
4-tuple.