l2vpn-4----Page:4
1 2 3 4 5 6 7
|
Comments Addressed in v02 (Cont.) Proposal to overcome the burden of PIM Snooping in the core The PEs are configured to not exceed a threshold (tx_threshold) which represents the aggregate amount of PIM refresh traffic that can be generated in the core For every PIM JP PDU received by a PE from the access side, the PE will modify the holdtime to a large value (possibly even infinity) before sending out into the core The holdtime, call it “core_holdtime”, can be configured OR can be adaptively computed based on the number of entries the PE has. So the refresh rate is roughly 1/3rd the core_holdtime. The PE will forward refreshes that it receives from the access side into the core only if the refresh timer has expired. Otherwise, it is simply dropped. To take care of the possibility of JP PDUs getting lost, a robustness variable R (like in IGMP) is configured for the VPLS instance (possibly even per PW). This simply means that the PE will propagate the initial Joins R times into the core instead of only once. |