RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

RFC 5060, "Protocol Independent Multicast MIB", January 2008

Source of RFC: pim (rtg)

Errata ID: 1448
Status: Rejected
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-06-14
Rejected by: Adrian Farrel
Date Rejected: 2011-09-28

Section 5, pg.47/48 says:

pimSGUpstreamPruneState OBJECT-TYPE
 |                forwarding (1),
                  ackpending (2),
                  pruned (3)
            "Whether the local router has pruned itself from the tree.
            This corresponds to the state of the upstream prune (S,G)
|           state machine in the PIM-DM specification.  This object is
|           used only by PIM-DM."


The DESCRIPTION clause says: "This object is used only by PIM-DM."
Does this mean: "This object is only instantiated for PIM-DM." ?
Otherwise, the alternative:
should perhaps be allowed in the SYNTAX clause and be the DEFAULT.

Similar issues exist for the subsequent columnar objects,
pimSGUpstreamPruneLimitTimer, pimSGOriginatorState,
pimSGSourceActiveTimer, and pimSGStateRefreshTimer.

Also, there's no hint in the RFC why the other applicable
timers, GraftRetryTimer and OverrideTimer have not been
modeled in this MIB module.
There are two issues in this Erratum...

1. "This object is only used..."

I interpret this to mean that an attempt to read the object in
other cases would return an error. Thus I don't see a problem
with the current text, and reject this part of the Erratum

2. "other timers are not modelled" Specifically:

GraftRetryTimer - I see pimInterfaceGraftRetryInterval
OverrideTimer - I see pimInterfaceOverrideInterval

The question is: why can't I see how the timer is running?
This looks like function that could have been added to the
MIB module, but was not.

However, someone who wants this function can add if they
feel inspired by revising the module or writing a new one.

Report New Errata