I'll discuss with other authors and get back to you. The options seem
to be to either explicitly make a decision to include only one range
at the BSR or see if we can find a backwards compatible way to include
both...
Great, one other point for you to consider is how things can get messed
up on the BSR itself.
The BSR is responsible for tracking all the RP-candidates and so it would
know that one RP was bidir while the other was ASM and so it may refer
to its RP-cache and find a different RP than the BSR clients would.
(This might be an implementation question, but I'm pretty sure that
most implementations will have this problem)