# Multicast PIM Bootstrap (BSR)

**URL:** <https://forum.networklessons.com/t/multicast-pim-bootstrap-bsr/1340>\
**Category:** Lessons Discussion\
**Created:** [December 29, 2016, 9:17pm UTC](https://forum.networklessons.com/t/multicast-pim-bootstrap-bsr/1340 "2016-12-29T21:17:31Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![ReneMolenaar](https://cdn-forum.networklessons.com/user_avatar/forum.networklessons.com/renemolenaar/32/488_2.png) [@ReneMolenaar](https://forum.networklessons.com/u/ReneMolenaar)\
**Post date:** [July 18, 2019, 8:51am UTC](https://forum.networklessons.com/t/multicast-pim-bootstrap-bsr/1340/25 "2019-07-18T08:51:44Z")

</div>

Hi Tony Ellis,

I just made some changes, you are right this is confusing. In RFC5059 they state it like this:

> BSR Priority  
> Contains the BSR priority value of the included BSR. This field  
> is considered as a high-order byte when comparing BSR addresses.  
> BSRs should by default set this field to 64. Note that for  
> historical reasons, the highest BSR priority is 255 (the higher  
> the better), whereas the highest RP Priority (see below) is 0  
> (the lower the better).

They talk about highest priority for BSR and RP selection, but for BSR highest priority means the highest value (255) and for RP, it means lowest value (0).

Rene

---

_[View the full topic](https://forum.networklessons.com/t/multicast-pim-bootstrap-bsr/1340)._