Re: [pim] Use of BS_Min_Interval in BSR draft

[Rishabh Parekh <rishabh at ipinfusion.com>]

Sumanta,
Please fine my reply inline.

Rishabh.
On Saturday 20 January 2007 01:20, sumanta seal wrote:
> BS_Min_Interval is 
> applied to the case when there is a need of sending BSM due to some event.
> For example, when a BSR, elected as DR, receives a new Hello or a Hello
> with new Gen Id from a PIM neighbor, it will send a BSM with the stored
> copy of Bootstrap information in it. This BSM should be send after
> BS_Min_Interval from the previous BSM it send. In normal scenario, BSMs are
> send at an interval of BS_Period by the elected BSR. Rgds,Sumanta
>
You are referring to the "No Forward" or Unicast BSMs which refresh BSR state 
at a new or re-starting neighbor. I don't think that these BSMs should be 
limited by the BS_Min_Interval because doing so will defeat the very purpose 
of such BSM messages.
I was referring to the regular BSM generated by an E-BSR due to two different 
events. In one case (C-RP set changes), the origin of BSM is limited by 
BS_Min_Interval while in other case (Recv Non-Preferred BSM) the origin is 
not regulated. My question is whether the latter case should also be limited 
by BS_Min_Interval or not?
>
>  Regards,
>  Rishabh.
>
>  _______________________________________________
> pim mailing list
> pim at ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>
>
>
> Thanks & Regards,
> **************************************************
> Sumanta Seal
> Salt Lake City, Kolkata
> West Bengal
> **************************************************
>
>
> ---------------------------------
>  Here?s a new way to find what you're looking for - Yahoo! Answers

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