[pim] CRP message processing, Priority down to Group prefix level?

["Rajesh Nataraja" <rbnataraja at gmail.com>]

Hi,

 

I had a question in CRP message processing.

 

If a CRP does not advertise a particular group prefix in a message,

Should the BSR treat that Group prefix as not configured for the CRP any more and then adjust its BSR message to accomodate the removal of the group prefix immediately?

or

Should it courteously wait until the Group prefix, which could be started for the hold time the CRP advertised before, expire and then adjust its BSR message?

 

Why Iam asking this is to see if it is legal to advertise group prefixes for a CRP with granularity for the priority down to a group prefix level.

I have seen this in one of the implementations.

 

Thanks

Rajesh.

 

On 1/19/07, Rishabh Parekh <rishabh at ipinfusion.com> wrote:

Hi,

The latest BSR draft states "There MUST however be a minimum of BS_Min_Interval between each time a BSM is sent." This is mentioned in the context of generating BSMs on C-RP set changes.

However, the C-BSR state machine also originates BSMs in E-BSR state for the event "Recieve Non-Preferred BSM". This action is not limited by BS_Min_Interval. Should this action also be throttled by BS_Min_Interval value? If so, then the action should be to reduce BS Timer to BS_Min_Interval if it is greater than this interval.

Regards,

Rishabh.

_______________________________________________
pim mailing list
pim at ietf.org
https://www1.ietf.org/mailman/listinfo/pim

_______________________________________________
pim mailing list
pim at ietf.org
https://www1.ietf.org/mailman/listinfo/pim