RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

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

Source of RFC: pim (rtg)
See Also: RFC 5060 w/ inline errata

Errata ID: 1449
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2008-06-14
Verifier Name: Adrian Farrel
Date Verified: 2011-09-28

Section 5, pg.49 ff. says:

...

pimSGIJoinPruneState OBJECT-TYPE
    SYNTAX     INTEGER {
|                 noInfo (1),
|                 join (2),
|                 prunePending (3)
               }
    MAX-ACCESS read-only
    STATUS     current
    DESCRIPTION
            "The state resulting from (S,G) Join/Prune messages
|           received on this interface.  This corresponds to the state
|           of the downstream per-interface (S,G) state machine in the
|           PIM-SM and PIM-DM specification."
    REFERENCE "RFC 4601 section 4.5.3 and RFC 3973 section 4.4.2"
    ...

...

It should say:

pimSGIJoinPruneState OBJECT-TYPE
    SYNTAX     INTEGER {
                  noInfo (1),
                  join (2),
                  prunePending (3),
                  pruned (4)
               }
    MAX-ACCESS read-only
    STATUS     current
    DESCRIPTION
            "The state resulting from (S,G) Join/Prune messages
            received on this interface.  This corresponds to the state
            of the downstream per-interface (S,G) state machine in the
            PIM-SM and PIM-DM specification."
    REFERENCE "RFC 4601 section 4.5.3 and RFC 3973 section 4.4.2"
    ::= { pimSGIEntry 4 }

Notes:

A fourth state is added to allow for the reporting of pruned state in PIM-DM.

Report New Errata



Advanced Search