RFC 4601, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", August 2006
Note: This RFC has been obsoleted by RFC 7761Source of RFC: pim (rtg)
Errata ID: 1143
Status: Held for Document Update
Publication Format(s) : TEXT
Reported By: Maren Peasley
Date Reported: 2007-12-21
Held for Document Update by: David Ward
Date Held: 2009-03-22
Section 4.1.3 says:
It should say:
PIM (*,G) Join/Prune state begins with a Join(*,G) sent to the RP. The metric to the RP is kept in the MRIB. Because the RP for this group can be any of several PIM routers, the source of the metric information in the MRIB is populated by any of the mechanisms discussed in section 4.7.
PIM state begins with a join for a group sent towards the RP. It is not readily evident that the BSR keeps a list of current RPs for use in the hash function to map groups onto these RPs in order to seed our state.