40 likes | 159 Views
PIM group-to-RP mapping draft-pim-group-rp-mapping David McWalter dmcw@metaswitch.com. Comments on the draft: It’s too complex. We don’t want to deal with multiple mapping mechanisms running at the same time.
E N D
PIM group-to-RP mappingdraft-pim-group-rp-mappingDavid McWalter dmcw@metaswitch.com Comments on the draft: • It’s too complex. We don’t want to deal with multiple mapping mechanisms running at the same time. • Dynamic group-to-RP mapping mechanisms should be filtered at domain boundaries.We don’t need a complex algorithm to accommodate both auto-RP and BSR. • Static configuration to override dynamic mappings isn’t needed. Can use longest match or filtering if this is important. => Let’s assume implementations will filter auto-RP and/or BSR at domain boundaries.
PIM group-to-RP mappingdraft-pim-group-rp-mappingDavid McWalter dmcw@metaswitch.com Filters Implementations should allow configuration to block dynamic mechanisms for address ranges. For example, you should be able to allow 239/8 for AutoRP but block all BSR updates. Alternatively, you should be able to turn off receiving all BSR or AutoRP updates on the router.
PIM group-to-RP mappingdraft-pim-group-rp-mappingDavid McWalter dmcw@metaswitch.com Update draft to assume such filtering. So: How a router chooses its group-to-RP mapping: 1. Embedded RP 2. Longest match 3. Bidir over Sparse Mode 4. Dynamic over Static 5. Highest Hash (only for BSR-learned PIM-SM groups) 6. Highest RP address
PIM group-to-RP mappingdraft-pim-group-rp-mappingDavid McWalter dmcw@metaswitch.com Next step: • Revise draft. Comments welcome.